Search Results asn_status

Overview

The RCV_SHIPMENT_HEADERS_MRC_V view is a reporting and integration construct in the Oracle E-Business Suite Receiving module, owned by the APPS schema and classified under the PO – Purchasing product family. Its name carries the "MRC" infix, denoting "Multiple Reporting Currencies," which signals that the view exists to expose shipment header data alongside the currency conversion attributes required for secondary ledger and reporting-currency reporting. In EBS 12.1.1 and 12.2.2, MRC-style views allow reporting applications to retrieve transactional amounts converted at the reporting set of books rate without directly joining conversion tables. ETRM lists the object status as VALID and notes the description as "Retrofitted," indicating it was ported into the current release from the earlier Multiple Reporting Currencies implementation model. The view presents one row per shipment header for the reporting set of books currently selected in the session, combining the operational shipment attributes with the reporting-currency conversion metadata.

Underlying Base Objects

The view is defined over two documented base objects, both referenced as SYNONYMs in ETRM: RCV_MC_SHIPMENT_HEADERS and RCV_SHIPMENT_HEADERS. The primary transactional table, RCV_SHIPMENT_HEADERS, supplies the core shipment attributes and is joined through SHIPMENT_HEADER_ID to RCV_MC_SHIPMENT_HEADERS, which carries the reporting-currency conversion columns. The view text confirms this join and constrains the secondary table with the predicate MC.SET_OF_BOOKS_ID = NVL(TO_NUMBER(SUBSTRB(USERENV('CLIENT_INFO'), 45, 10)), -99). This predicate reads the set of books identifier from the CLIENT_INFO session context and isolates the appropriate reporting-currency rows. Because it is an MRC view, the conversion columns are populated only when a reporting set of books is active in the session context; otherwise the -99 default may suppress rows.

Key Columns

The view exposes the full operational column set of RCV_SHIPMENT_HEADERS plus MRC conversion attributes. Notable columns include SHIPMENT_HEADER_ID, the primary key and join column; RECEIPT_NUM and SHIPMENT_NUM, the user-facing identifiers; VENDOR_ID and VENDOR_SITE_ID, identifying the supplier and location; SHIP_TO_LOCATION_ID and SHIP_TO_ORG_ID; and ORGANIZATION_ID, the receiving inventory organization. Financial attributes include INVOICE_AMOUNT, TAX_AMOUNT, and FREIGHT_AMOUNT. Two conversion column sets are present: CONVERSION_RATE_TYPE, CONVERSION_DATE, and CONVERSION_RATE, and a parallel MRC_ set (MRC_CONVERSION_RATE_TYPE, MRC_CONVERSION_DATE, MRC_CONVERSION_RATE). The PAYMENT_TERMS_ID column, exposed on the header, captures the payment terms reference for the shipment invoice. CURRENCY_CODE, INVOICE_NUM, INVOICE_DATE, and INVOICE_STATUS_CODE round out the invoice-tracking attributes. Descriptive and logistics columns include FREIGHT_CARRIER_CODE, PACKING_SLIP, BILL_OF_LADING, WAYBILL_AIRBILL_NUM, ASN_TYPE, ASN_STATUS, GROSS_WEIGHT, NET_WEIGHT, and TAR_WEIGHT with their UOM codes, plus fifteen ATTRIBUTE flex columns and the WHO audit columns (CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY).

Common Use Cases and Queries

This view is typically queried for reporting-currency shipment analysis, reconciliations, and downstream integrations that must carry reporting-currency amounts. A user searching for payment_terms_id would retrieve it here, for example to report shipments grouped by payment terms. To ensure correct results, the reporting set of books must be set in the session context.

• Retrieve shipments with payment terms and invoice amounts:

  SELECT h.shipment_header_id, h.receipt_num, h.payment_terms_id, h.invoice_amount, h.currency_code FROM rcv_shipment_headers_mrc_v h;

• Filter reporting-currency shipments by supplier:

  SELECT shipment_header_id, vendor_id, conversion_rate, mrc_conversion_rate FROM rcv_shipment_headers_mrc_v WHERE vendor_id = :vendor_id;

• Analyze conversions for a reporting period:

  SELECT shipment_header_id, conversion_date, conversion_rate, mrc_conversion_rate FROM rcv_shipment_headers_mrc_v WHERE conversion_date BETWEEN :start_date AND :end_date;

Because the SET_OF_BOOKS_ID predicate relies on CLIENT_INFO, applications that call this view programmatically should initialize the reporting context before querying to avoid empty result sets.