Results for “ship_line_id”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

GMF_LC_ADJ_HEADERS_V is a read-only view owned by the APPS schema in Oracle E-Business Suite, delivered as part of the GMF (Process Manufacturing Financials) product family. Its documented purpose is to expose Landed Cost (LC) adjustment data that is populated from the LCM (Landed Cost Management) tables. The view consolidates shipment line landed cost allocations with receipt transaction and unit of measure context, producing a denormalized result set intended for reporting, reconciliation, and downstream integration of landed cost adjustments.

Because the object is a view rather than a base table, it performs no persistence of its own. All values are derived at query time from the underlying landed cost calculation views and the purchasing, receiving, and inventory synonyms to which it is joined. In the 12.1.1 and 12.2.2 releases the view is registered as VALID, indicating that its definition compiles successfully against the current data dictionary.

Underlying Base Objects

The documented base objects referenced by the view are:

• INL_DET_LANDED_COSTS_V (VIEW) — supplies the detailed landed cost allocation rows.
• INL_SHIP_HEADERS_ALL (SYNONYM) — provides inbound shipment header information, including shipment number and operating unit.
• MTL_UNITS_OF_MEASURE (SYNONYM) — resolves the primary unit of measure code for the transaction quantity.
• PON_PRICE_ELEMENT_TYPES (SYNONYM) — supplies price element (charge) definitions such as the price element type ID, code, cost acquisition code, and cost component class.
• RCV_SHIPMENT_HEADERS (SYNONYM) and RCV_SHIPMENT_LINES (SYNONYM) — link landed cost adjustments to the receiving shipment and receipt number.
• RCV_TRANSACTIONS (SYNONYM) — provides receipt transaction attributes, including transaction date, quantity, UOM, transaction type, and primary quantity.

The joins stitch together the landed cost allocation line, the originating receipt transaction, the inbound shipment, and the associated unit of measure and price element definitions. This assembly allows a single query to return landed cost adjustments with their receipt and shipment context.

Key Columns

The projection includes identifiers, monetary allocations, and classification attributes. Notable columns include:

• PARENT_SHIP_LINE_ID — derived with NVL from either the parent ship line or the ship line, establishing lineage for the adjustment.
• ADJUSTMENT_NUM, SHIP_HEADER_ID, SHIP_LINE_GROUP_ID, SHIP_LINE_ID, ORGANIZATION_ID, INVENTORY_ITEM_ID — the core keys identifying the adjustment and its inventory context.
• LANDED_COST and PRIOR_LANDED_COST — the allocated amount and the LAG-derived prior allocated amount, partitioned by transaction, component name, and component type to support sequential adjustment analysis.
• ALLOCATION_PERCENT, COMPONENT_TYPE, COMPONENT_NAME — describe the allocation basis and the component being charged.
• CHARGE_LINE_TYPE_ID, CHARGE_LINE_TYPE_CODE, COST_ACQUISITION_FLAG, COST_CMPNTCLS_ID, COST_ANALYSIS_CODE — price element classification attributes.
• PARENT_TABLE_NAME and PARENT_TABLE_ID — a DECODE-driven discriminator that identifies whether the parent is RCV_TRANSACTIONS or INL_SHIP_LINES.
• TRANSACTION_DATE, TRANSACTION_QUANTITY, TRANSACTION_UOM_CODE, PRIMARY_QUANTITY, PRIMARY_UOM_CODE — receipt transaction measures. TRANSACTION_UOM_CODE is the unit of measure associated with TRANSACTION_QUANTITY, exposed directly from RCV_TRANSACTIONS.UOM_CODE; PRIMARY_UOM_CODE supplies the corresponding primary unit of measure.
• LC_ADJUSTMENT_FLAG, RCV_TRANSACTION_ID, RCV_TRANSACTION_TYPE, LC_SHIP_NUM, LC_SHIP_LINE_NUM, RECEIPT_NUM, ORG_ID — status and traceability attributes.

Common Use Cases and Queries

Because the view exposes TRANSACTION_UOM_CODE alongside transaction and primary quantities, it is frequently used to report landed cost adjustments in the unit of measure in which the receipt was transacted, and to compare that against the primary stocking UOM. Typical scenarios include landed cost variance analysis per receipt, reconciliation of LCM adjustments to RCV transactions, and extracts for cost accounting or external reporting. A representative query is:

• SELECT adjustment_num, ship_line_id, inventory_item_id, component_name, landed_cost, transaction_quantity, transaction_uom_code, primary_quantity, primary_uom_code, transaction_date FROM apps.gmf_lc_adj_headers_v WHERE organization_id = :org_id AND transaction_date BETWEEN :start_date AND :end_date ORDER BY transaction_date, adjustment_num;

The view can also be filtered by inventory_item_id or charge_line_type_code to isolate specific cost components, and grouped by transaction_uom_code to summarize adjustment amounts by unit of measure. Because it is a view, it should be queried rather than used as a DML target.