Search Results secondary_uom_code




Overview

GMF_XLA_LC_ADJS_V is a Subledger Accounting (SLA) Landed Cost adjustments view owned by the APPS schema in Oracle E-Business Suite, delivered as part of the GMF - Process Manufacturing Financials product family. Its functional purpose is to surface Landed Cost (LC) adjustment information for display within the Accounting Events screen of Subledger Accounting, allowing users to review the transactions that generate LC adjustment accounting entries before and after they are accounted.

The view is defined as a join across landed cost adjustment transactions, SLA extract headers, inventory organization parameters, inventory items, and legal entity profiles. Because it filters on the event types LC_ADJUST_RECEIVE, LC_ADJUST_DELIVER, LC_ADJUST_EXP_DELIVER, and LC_ADJUST_VALUATION combined with the event class code LC_ADJUSTMENTS, it presents only those accounting events that pertain to landed cost adjustment activity. The view is read-only in nature and does not store data of its own; it is a reporting and integration construct.

With respect to the searched term SECONDARY_UOM_CODE, this view exposes the item's secondary unit of measure as a direct passthrough from MTL_SYSTEM_ITEMS_B_KFV. This makes the view particularly useful for dual-unit-of-measure environments where users need to see both the primary and secondary UOM context of an LC adjustment event.

Underlying Base Objects

The view is documented in ETRM 12.2.2 as being defined over the following referenced base objects:

  • GMF_LC_ADJ_TRANSACTIONS (synonym) — the transactional source of landed cost adjustment records, aliased GLAT.
  • GMF_XLA_EXTRACT_HEADERS (synonym) — the SLA extract header table that ties each event to its source document, legal entity, ledger, organization, and event class, aliased EH.
  • MTL_PARAMETERS (synonym) — inventory organization parameters, aliased MP, providing the organization code.
  • MTL_SYSTEM_ITEMS_B_KFV (view) — the key flexfield value view of inventory items, aliased MSI, supplying concatenated item segments, description, primary UOM, and secondary UOM.
  • XLE_ENTITY_PROFILES (synonym) — legal entity profile information, aliased LE, providing the legal entity name.

Joins are established on source document ID to adjustment transaction ID, source line ID to receiving transaction ID, organization ID, inventory item ID, and legal entity ID, ensuring the event header, item, organization, and legal entity all resolve to a consistent LC adjustment event.

Key Columns

Common Use Cases and Queries

A typical use is diagnostic review of LC adjustment accounting events. The following query lists recent adjustments with both UOMs:

SELECT ADJ_TRANSACTION_ID,
       ADJUSTMENT_NUM,
       LEGAL_ENTITY_NAME,
       ORGANIZATION_CODE,
       ITEM_NAME,
       PRIMARY_UOM_CODE,
       SECONDARY_UOM_CODE,
       TRANSACTION_DATE
  FROM APPS.GMF_XLA_LC_ADJS_V
 WHERE TRANSACTION_DATE >= SYSDATE - 30
 ORDER BY TRANSACTION_DATE DESC;

Analysts may isolate records where a secondary unit of measure is defined, for example to reconcile dual-UOM inventory:

SELECT ADJ_TRANSACTION_ID, ITEM_NAME,
       PRIMARY_UOM_CODE, SECONDARY_UOM_CODE
  FROM APPS.GMF_XLA_LC_ADJS_V
 WHERE SECONDARY_UOM_CODE IS NOT NULL;

Because the view joins SLA extract headers to GMF_LC_ADJ_TRANSACTIONS, it also supports reconciliation between posted Landed Cost adjustments and their SLA events by ledger, legal entity, or organization. Results should always be filtered by the relevant ledger and date range to keep query performance acceptable on large volumes.