Results for “container_sequence”
18 results
AI-generated from documented ETRM metadata — verify critical details on the linked pages.
Overview
WSH_FREIGHT_CHARGES_INTERFACE is an Order Entry (OE) schema interface table that stores freight charge records awaiting validation and import into the Oracle E-Business Suite delivery and shipping transaction model. It functions as a staging area between external or feeder processes and the freight charge data that ultimately attaches to delivery, container, picking line, and order entities used by Oracle Shipping Execution.
The table exists primarily to decouple the collection of freight charge data from the validation and persistence logic in the shipping transaction APIs. Records written here are processed by concurrent programs and submission routines that validate keys, currency, freight charge types, and parent references before transferring or consuming the values for shipment cost and freight rating purposes.
The ETRM relationship metadata classifies this object as satellite-leaning based on its foreign key structure. In a Data Vault modeling sense, it is best understood as a satellite that hangs off the delivery/order hub and link structures, since it carries descriptive and measurable attributes (amount, currency, charge type) rather than defining new business keys on its own.
Key Information Stored
The table contains 54 documented columns. The most significant include:
- TRANSACTION_ID — references WSH_DELIVERIES_INTERFACE, tying each freight charge row to a delivery interface transaction.
- FREIGHT_CHARGE_TYPE_ID and FREIGHT_CHARGE_TYPE_DESC — the freight charge type (foreign key to SO_FREIGHT_CHARGE_TYPES) and its description.
- AMOUNT — the freight charge value being interfaced.
- CURRENCY_CODE and CURRENCY_NAME — the currency of the amount.
- CONTAINER_ID — references WSH_PACKED_CONTAINERS, linking the charge to a specific packed container.
- CONTAINER_SEQUENCE and DELIVERY_FLAG — control the association and whether the charge applies at delivery level.
- ORDER_HEADER_ID — the originating order header.
- PICKING_LINE_DETAIL_ID — references SO_PICKING_LINE_DETAILS, associating the charge with a picking line.
- ERROR_CODE and ERROR_EXPLANATION — capture validation failures for rejected rows.
- AUDIT columns — CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN, PROGRAM_ID, REQUEST_ID, PROGRAM_APPLICATION_ID, PROGRAM_UPDATE_DATE.
- ATTRIBUTE1–ATTRIBUTE15 and AC_ATTRIBUTE1–AC_ATTRIBUTE15 — descriptive flexfield and context-sensitive attribute segments.
No single surrogate primary key is documented as a unique index in the provided metadata; the primary key is implicitly the composite relationship defined by TRANSACTION_ID together with the container, order, and picking line references.
Common Use Cases and Queries
Typical scenarios include staging freight charges from external freight rating engines, reconciling charges against deliveries, and diagnosing import failures. Analysts commonly query error rows:
- Retrieve failed rows:
SELECT TRANSACTION_ID, ERROR_CODE, ERROR_EXPLANATION FROM WSH_FREIGHT_CHARGES_INTERFACE WHERE ERROR_CODE IS NOT NULL; - Sum interfaced amounts by charge type:
SELECT FREIGHT_CHARGE_TYPE_ID, SUM(AMOUNT) FROM WSH_FREIGHT_CHARGES_INTERFACE GROUP BY FREIGHT_CHARGE_TYPE_ID; - Join to delivery interface:
SELECT f.TRANSACTION_ID, f.AMOUNT FROM WSH_FREIGHT_CHARGES_INTERFACE f, WSH_DELIVERIES_INTERFACE d WHERE f.TRANSACTION_ID = d.TRANSACTION_ID; - Container-level reporting using CONTAINER_ID and CONTAINER_SEQUENCE.
These queries support freight cost analysis, shipment cost reconciliation, and validation troubleshooting.
Related Objects
The principal related objects, based on documented foreign keys, are:
- WSH_DELIVERIES_INTERFACE — joined via TRANSACTION_ID.
- SO_FREIGHT_CHARGE_TYPES — joined via FREIGHT_CHARGE_TYPE_ID.
- WSH_PACKED_CONTAINERS — joined via CONTAINER_ID.
- SO_PICKING_LINE_DETAILS — joined via PICKING_LINE_DETAIL_ID.
- WSH_FREIGHT_CHARGES and related shipping transaction API packages — the permanent freight charge destination consumed after interface processing.
- Order Entry and Shipping Execution concurrent programs that validate and import these rows.
Together these objects form the freight charge staging and persistence chain within Oracle Shipping Execution.
-
Interface table for freight charges
-
Interface table for freight charges
-
APPS.WSH_PICKING_DETAILS_INTERFACE·↳ MTL_TRANSACTIONS_INTERFACE·↳ SO_HEADERS_ALL·↳ SO_LINES_ALL·Explore OE module →
-
APPS.WSH_PICKING_DETAILS_INTERFACE·↳ MTL_TRANSACTIONS_INTERFACE·↳ SO_HEADERS_ALL·↳ SO_LINES_ALL·Explore OE module →
-
eTRM - OE Tables and Views 12.2.2
Temporary table
-
eTRM - OE Tables and Views 12.1.1
Temporary table