Results for “order_line_num”

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

Overview

The APPS.RCV_MSL_V view is a Purchasing (PO) module object in Oracle E-Business Suite, documented with the description "10SC ONLY - Retrofitted." The name follows the RCV (Receiving) naming convention, and the "MSL" designation indicates a material shipment line (MSL) summary construct that consolidates receiving shipment line data together with associated requisition, purchase order, and inventory attributes. Although the view is owned by the APPS schema and marked VALID, its description signals that it is a retrofitted object whose original implementation dates to an earlier 10SC release and has been carried forward into 12.1.1 and 12.2.2.

Functionally, RCV_MSL_V exposes a denormalized reporting surface for receiving activity. Rather than requiring report authors and integrators to join RCV_SHIPMENT_LINES, RCV_SHIPMENT_HEADERS, PO requisition structures, and HR and MTL lookup tables manually, the view presents shipment line records enriched with decoded source document types, destination types, hazard classifications, delivery information, and routing data. This makes it suitable for operational reporting, reconciliation, and interface-style extracts within the receiving and procurement domain.

Because the definition includes a literal ' INTERNAL' as its first selected expression, the view is scoped to internal (non-supplier-facing) receiving contexts, consistent with the "MSL" material-shipment-line interpretation. The presence of the user's search term, SOURCE_DOCUMENT_TYPE, among its exposed columns makes the view a natural target for queries that must identify whether a receiving line originated from a requisition, a purchase order, or another source document class.

Underlying Base Objects

The documented view metadata lists a broad set of referenced base objects spanning packages, synonyms, views, and security constructs. These fall into several functional groups:

• Receiving tables: RCV_SHIPMENT_LINES (SYNONYM), RCV_SHIPMENT_HEADERS (SYNONYM), RCV_TRANSACTIONS_INTERFACE (SYNONYM), and RCV_ROUTING_HEADERS (VIEW) supply the shipment line, shipment header, interface, and routing data that form the core of the view.
• Purchasing and requisitioning views: PO_HEADERS_TRX_V, PO_LINES_TRX_V, PO_LINE_LOCATIONS_TRX_V, PO_REQ_HEADERS_TRX_V, PO_REQ_LINES_TRX_V, PO_LOOKUP_CODES, PO_VENDORS, and PO_VENDOR_SITES provide order, line, shipment, requisition, and supplier context.
• Inventory and item attributes: MTL_SYSTEM_ITEMS, MTL_TRANSACTION_REASONS, PO_HAZARD_CLASSES, and PO_UN_NUMBERS contribute item, reason, hazard, and UN number information.
• Human resources and security: PER_ALL_PEOPLE_F, HR_LOCATIONS_ALL_TL, HR_GENERAL, HR_SECURITY, and FND_GLOBAL supply delivery person, location, and session/security context.
• Supporting objects: PO_CLM_INTG_GRP (PACKAGE), PO_RELEASES_ALL (SYNONYM), and WMS_LICENSE_PLATE_NUMBERS (SYNONYM) support grouping, release, and warehouse management scenarios.

These relationships explain the view's composite nature: it is defined over the receiving shipment line table and outer-joins the purchasing, requisition, inventory, and HR objects to produce a single, report-ready result set.

Key Columns

The view's select list, visible in the ETRM excerpt, exposes a wide range of columns. Notable groups include:

• Source and destination decoding: SOURCE_DOCUMENT_CODE and its decoded counterpart SOURCE_DOCUMENT_TYPE (derived from PO_LOOKUP_CODES via POLC2.DISPLAYED_FIELD), plus DESTINATION_TYPE_CODE and DESTINATION_TYPE (POLC.DISPLAYED_FIELD). These identify the origin and destination context of each shipment line.
• Document identifiers: SHIPMENT_HEADER_ID, SHIPMENT_LINE_ID, REQUISITION_LINE_ID, REQ_DISTRIBUTION_ID, ROUTING_HEADER_ID, ITEM_ID, CHARGE_ACCOUNT_ID, and TRANSPORTATION_ACCOUNT_ID.
• Quantities and measures: QUANTITY_RECEIVED, QUANTITY_SHIPPED, UNIT_OF_MEASURE, UOM_CONVERSION_RATE, TRANSFER_COST, and TRANSPORTATION_COST.
• Descriptive and logistical attributes: ITEM_DESCRIPTION, ITEM_REVISION, HAZARD_CLASS, UN_NUMBER, PACKING_SLIP, LOCATOR_ID, TO_SUBINVENTORY, TO_ORGANIZATION_ID, and FROM_ORGANIZATION_ID.
• People and location: DELIVER_TO_PERSON (HE.FULL_NAME), DELIVER_TO_PERSON_ID, DELIVER_TO_LOCATION_ID, and LOCATION_CODE.
• Requisition-derived values: NEED_BY_DATE, ORDER_NUM, and REQUISITION_LINE_NUM, each conditionally decoded only when SOURCE_DOCUMENT_CODE equals 'REQ'.
• Standard audit columns: ROW_ID (ROWID), CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, and the WHO/request columns.

The select list also contains placeholder expressions such as TO_NUMBER(NULL) and NULL, which are typical of retrofitted views that preserve column positions for downstream consumers.

Common Use Cases and Queries

RCV_MSL_V is principally used to report receiving activity without reconstructing complex joins. Typical scenarios include receipt reconciliation, open shipment line analysis, source document auditing, and extracts feeding downstream receiving or interface processes. The SOURCE_DOCUMENT_TYPE column supports grouping and filtering by document origin, while quantity, item, and destination columns support inventory and logistics reporting.

A representative query selecting receipts by source document type:

• SELECT shipment_line_id, source_document_code, source_document_type, item_description, quantity_received, unit_of_measure FROM rcv_msl_v WHERE source_document_type = '&source_document_type' ORDER BY shipment_line_id;
• SELECT order_num, requisition_line_num, need_by_date, quantity_shipped, quantity_received FROM rcv_msl_v WHERE source_document_code = 'REQ';
• SELECT to_organization_id, to_subinventory, locator_id, SUM(quantity_received) received_qty FROM rcv_msl_v GROUP BY to_organization_id, to_subinventory, locator_id;

Because the view is a retrofitted 10SC construct, implementers should validate its behavior against the specific 12.1.1 or 12.2.2 environment and confirm that returned columns are populated as expected before embedding it in production reports or interfaces.