Search Results shipment_line_status_code

Overview

RCV_SHIPMENT_LINES_MRC_V is a multi-reporting-currency (MRC) view in the Oracle E-Business Suite Procurement (PO / Purchasing) module, classified as retrofitted in the ETRM repository. It exposes the shipment-line financial attributes of the RCV_SHIPMENT_LINES entity in the reporting currency selected through the MRC mechanism rather than in the functional currency. Oracle EBS implements multiple reporting currencies by maintaining translated or derived amount columns keyed by currency, and the "_MRC_V" suffix identifies a view whose purpose is to project those currency-specific values into a single, session-dependent row set.

Its role is analytical and integration-oriented. Receiving, inspection, delivery, and cost-distribution reports that must present values in a reporting currency—rather than only the ledger's functional currency—draw on views of this family. The view carries the shipment line identity alongside converted unit price, transfer cost, and transportation cost, allowing downstream reporting to reconcile received quantities against their reporting-currency valuations.

The ETRM metadata records the object as "Not implemented in this database" in the documented environment, and no owner is populated. Consequently, the view may be absent or may present no rows in a given instance; its presence in the data dictionary should not be assumed without verification.

Underlying Base Objects

The ETRM metadata lists no documented referenced base objects for this view. The published view text, however, is defined over an MRC shipment-unit-price/cost source that stores multi-currency values in a delimited string format, with the shipment line identifier carried through as SHIPMENT_LINE_ID. This is consistent with the standard EBS MRC design, in which the MULTI_CURRENCY table for the transaction holds one delimited value per currency, and the "_MRC_V" view extracts the currency-specific element from that string.

The extraction logic is the defining characteristic of this view. It uses USERENV('CLIENT_INFO') to read the caller's session context, trims the currency identifier from position 45 of the client information string, and then applies nested SUBSTRB/INSTR operations to locate the substring delimited by "<currency>". Because the currency is resolved from session context at runtime, the same view returns different values depending on the reporting currency selected by the calling session. Relationship management is therefore to the MRC multi-currency storage layer rather than to a plain relational parent table.

Key Columns

• SHIPMENT_LINE_ID — The primary shipment line identifier, joining the view to RCV_SHIPMENT_LINES and to receiving, inspection, and delivery entities.
• Shipment unit price (reporting currency) — The MRC shipment unit price extracted from the delimited multi-currency string and converted to a number with a fixed 38-digit precision and 18-decimal format mask.
• Transfer cost (reporting currency) — The MRC transfer cost attributable to the shipment line, extracted using the same delimiter-driven logic.
• Transportation cost (reporting currency) — The MRC transportation cost attributable to the shipment line, obtained by identical SUBSTRB/INSTR parsing of the corresponding multi-currency column.
• Shipment line status code — The operational status of the shipment line (for example, expected, received, or delivered), returned from the base receipt line record. This is the column most frequently searched in relation to this view and is the principal filter for receipt reconciliation queries.

Common Use Cases and Queries

The view is used to report receipt-line values in a reporting currency, to reconcile received quantities against transfer and transportation costs, and to feed downstream cost-distribution interfaces. A typical query filters by shipment line status and selects the monetary columns supplied by the view:

• Receiving reconciliation: SELECT shipment_line_id, shipment_line_status_code FROM rcv_shipment_lines_mrc_v WHERE shipment_line_status_code = 'RECEIVED';
• Cost analysis joining back to RCV_SHIPMENT_LINES on SHIPMENT_LINE_ID to retrieve quantity and item information alongside reporting-currency unit price and transfer cost.
• Integration extracts that must present valuation in a currency other than the functional currency, relying on the session's reporting-currency context to select the correct delimited segment.

Because the currency is resolved from USERENV('CLIENT_INFO'), a query invoked without the appropriate reporting-currency context may return null or incorrect amounts. Analysts should confirm that the session sets client information before dependency on the view's monetary columns.