Search Results gmf_lc_adj_transactions_u1

Overview

GMF_LC_ADJ_TRANSACTIONS is a Process Manufacturing Financials (GMF) table that stores Estimated and Actual Landed Cost adjustments. Each row represents a single landed cost adjustment created during the Landed Cost Adjustment import process, capturing both the prior (estimated) landed cost and the newly computed (actual) landed cost for a shipment line or cost component. The table is owned by the GMF schema and is classified as VALID in the ETRM repository for Oracle EBS 12.1.1 and 12.2.2.

From a Data Vault modeling perspective, the heuristic classification for this object is hub-leaning. Its structure—a single-column surrogate primary key (ADJ_TRANSACTION_ID) combined with multiple business identifiers (SHIP_HEADER_ID, SHIP_LINE_ID, ADJUSTMENT_NUM, RCV_TRANSACTION_ID) and a foreign key to FV_LEGAL_ENTITIES—suggests it functions as a central anchor for landed cost adjustment events, with dependent detail captured in downstream cost adjustment tables.

Key Information Stored

The table contains 51 documented columns. The most significant are:

• ADJ_TRANSACTION_ID — Surrogate primary key (GMF_LC_ADJ_TRANSACTIONS_PK). Uniquely identifies each adjustment transaction.
• SHIP_HEADER_ID, SHIP_LINE_ID, SHIP_LINE_GROUP_ID, PARENT_SHIP_LINE_ID — Business-key candidates forming the unique index GMF_LC_ADJ_TRANSACTIONS_U1, tying the adjustment to a specific shipment and line.
• ADJUSTMENT_NUM — Business identifier for the adjustment record.
• RCV_TRANSACTION_ID — Links back to the receiving transaction that triggered or relates to the adjustment.
• LEGAL_ENTITY_ID — Foreign key to FV_LEGAL_ENTITIES, identifying the legal entity owning the transaction.
• PRIOR_LANDED_COST / NEW_LANDED_COST — The estimated versus actual landed cost values central to the adjustment.
• COMPONENT_TYPE / COMPONENT_NAME / CHARGE_LINE_TYPE_CODE — Identify the landed cost component (e.g., freight, duty) being adjusted.
• INVENTORY_ITEM_ID, ORGANIZATION_ID, ORG_ID — Item and organization context for the adjustment.
• TRANSACTION_DATE, TRANSACTION_QUANTITY, TRANSACTION_UOM_CODE — Timing and quantity/UOM of the adjustment.
• CURRENCY_CODE, CURRENCY_CONVERSION_RATE, CURRENCY_CONVERSION_DATE — Currency and conversion details used for valuation.
• LC_VAR_ACCOUNT_ID / LC_ABSORPTION_ACCOUNT_ID — Accounting flexfields for variance and absorption postings.
• ACCOUNTED_FLAG, FINAL_POSTING_DATE — Posting status and the date the adjustment was finalised to the ledger.
• LC_ADJUSTMENT_FLAG, COST_ACQUISITION_FLAG — Flags controlling adjustment and cost-acquisition behaviour.

Common Use Cases and Queries

Typical uses include reconciling estimated versus actual landed cost, auditing adjustments by shipment or legal entity, and reporting unposted or posted adjustments.

• Retrieve adjustments for a shipment line:

  SELECT ADJ_TRANSACTION_ID, ADJUSTMENT_NUM, PRIOR_LANDED_COST, NEW_LANDED_COST
  FROM   GMF.GMF_LC_ADJ_TRANSACTIONS
  WHERE  SHIP_HEADER_ID = :p_ship_header_id;

• Identify adjustments awaiting posting:

  SELECT * FROM GMF.GMF_LC_ADJ_TRANSACTIONS
  WHERE  NVL(ACCOUNTED_FLAG,'N') = 'N';

• Summarise adjustment variance by legal entity and item.
• Trace adjustments back to receiving via RCV_TRANSACTION_ID for cost audit trails.

Related Objects

• GMF_LC_LOT_COST_ADJS — References GMF_LC_ADJ_TRANSACTIONS via ADJ_TRANSACTION_ID; holds lot-level cost adjustment detail.
• FV_LEGAL_ENTITIES — Referenced by LEGAL_ENTITY_ID.
• RCV_TRANSACTIONS — Related through RCV_TRANSACTION_ID for receiving context.
• MTL_SYSTEM_ITEMS_B / MTL_PARAMETERS — Related through INVENTORY_ITEM_ID and ORGANIZATION_ID.
• GL_LEDGERS — Linked via LEDGER_ID.