Results for “to_org_primary_quantity”

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

Overview

The CST_INTRANSIT_VALUE_VIEW is a SINGLE-ORG reporting view owned by the APPS schema in Oracle E-Business Suite, catalogued under the BOM (Bills of Material) product family. It presents in-transit value information for material moving between organizations, exposing the owning organization, cost group, source and destination organizations, and the associated shipment, receipt, freight, and cost attributes that describe goods currently in transit. Because the view is defined as a SINGLE-ORG view, it surfaces data for the organization determined by the FOB point of the inter-org transfer rather than aggregating across all organizations; this behavior is central to how cost and valuation queries against it must be scoped.

In Oracle EBS 12.1.1 and 12.2.2 reporting and integration scenarios, this view is valuable in that it joins shipping execution data from Receiving (RCV_SHIPMENT_HEADERS and RCV_SHIPMENT_LINES) with planning and cost data from inventory (MTL_SUPPLY, MTL_PARAMETERS) and inter-org configuration (MTL_INTERORG_PARAMETERS). This allows the in-transit value to be reconciled against shipment documents such as the waybill or airbill number, container counts, and carrier information.

Underlying Base Objects

The view is defined over the following documented base objects (all reached through APPS synonyms):

• RCV_SHIPMENT_HEADERS — shipment header details such as shipment number, receipt number, freight carrier code, waybill/airbill number, number of containers, and shipped date.
• RCV_SHIPMENT_LINES — shipment line details including line status, source document, deliver-to location, charge account, transportation account, shipment unit price, transfer cost, transportation cost, and shipment line ID.
• MTL_SUPPLY — the driving supply record (restricted to SUPPLY_TYPE_CODE IN ('SHIPMENT','RECEIVING')) providing item, revision, quantity, UOM, receipt/need-by/expected-delivery dates, subinventories, and to-organization primary quantities.
• MTL_INTERORG_PARAMETERS — inter-org transfer parameters providing the FOB point that determines the in-transit owning organization.
• MTL_PARAMETERS — organization cost method parameters supplying primary cost method and default cost group.
• MTL_UNITS_OF_MEASURE — joined twice (aliases UOM1 and UOM2) to translate the supply UOM and the to-org primary UOM into UOM codes.

Key Columns

• INTRANSIT_OWNING_ORG_ID — the organization that owns the goods while in transit, derived via DECODE(MIP.FOB_POINT, 1, SUP.TO_ORGANIZATION_ID, 2, SUP.FROM_ORGANIZATION_ID).
• COST_GROUP_ID — the cost group, taken from the supply record or defaulted from MTL_PARAMETERS based on the primary cost method.
• FROM_ORGANIZATION_ID, FROM_SUBINVENTORY, TO_ORGANIZATION_ID, TO_SUBINVENTORY — source and destination inventory locations.
• TRANSPORTATION_ACCOUNT_ID — the GL account charged for transportation of the shipment line; a frequent search target.
• CHARGE_ACCOUNT_ID, TRANSFER_COST, TRANSPORTATION_COST, SHIPMENT_UNIT_PRICE — cost and accounting attributes of the in-transit line.
• SHIPMENT_NUM, RECEIPT_NUM, WAYBILL_AIRBILL_NUM, FREIGHT_CARRIER_CODE — shipment identification and carrier data.
• ITEM_ID, QUANTITY, UNIT_OF_MEASURE, TO_ORG_PRIMARY_QUANTITY, RECEIPT_DATE, NEED_BY_DATE, EXPECTED_DELIVERY_DATE, SHIPMENT_LINE_ID.

Common Use Cases and Queries

Typical uses include in-transit inventory valuation reports, reconciliation of shipped-but-not-received balances, transportation cost analysis, and auditing the accounting assigned to in-transit movements. A common query filters by transportation account and destination organization:

• Value of goods in transit between two organizations for a period.
• Lines grouped by TRANSPORTATION_ACCOUNT_ID to verify freight accounting.
• Items still in transit beyond EXPECTED_DELIVERY_DATE.

Sample SQL:

• SELECT intransit_owning_org_id, from_organization_id, to_organization_id, item_id, quantity, transportation_account_id, transfer_cost, transportation_cost
• FROM apps.cst_intransit_value_view
• WHERE transportation_account_id = :p_account_id AND supply_type_code IN ('SHIPMENT','RECEIVING');