Search Results opsm_integrated_flag

Overview

RCV_OPSM_LINE_V is a Purchasing (PO) module view owned by the APPS schema in Oracle E-Business Suite 12.1.1 and 12.2.2. It presents a consolidated, reporting-oriented projection of Receiving shipment line data joined to Oracle Order Management sales order context and to Oracle Warehouse Management (WMS/OSM) integration attributes held as item cross-references. The view's principal role is to expose, at shipment line granularity, whether a received item has been flagged for OPSM (Outbound Product Serialization Management) integration, together with the serial control type implied by that cross-reference.

The presence of the derived column OPSM_INTEGRATED_FLAG is the defining characteristic of this view. It is computed from MTL_CROSS_REFERENCES_VL rather than being stored on RCV_SHIPMENT_LINES, which makes the view the documented access path for integrations that must determine the OPSM status of an inbound or RMA receipt line without querying item cross-references directly.

Underlying Base Objects

The view is defined over the following documented objects: FND_LANGUAGES (synonym), MTL_CROSS_REFERENCES_VL (view), MTL_PARAMETERS (synonym), MTL_SYSTEM_ITEMS_B_KFV (view), OE_ORDER_HEADERS_ALL (synonym), OE_ORDER_LINES_ALL (synonym), OE_TRANSACTION_TYPES_TL (synonym), RCV_SHIPMENT_LINES (synonym), and RCV_TRANSACTIONS (synonym).

• RCV_SHIPMENT_LINES supplies the primary row grain: shipment header and line identifiers, item, description, quantities shipped and received, unit of measure, shipment line status, bar code label, QC grade, ASN line flag, and destination type.
• MTL_SYSTEM_ITEMS_B_KFV provides the concatenated item segment and item-level control attributes (lot control, serial number control, primary UOM).
• MTL_CROSS_REFERENCES_VL drives OPSM_INTEGRATED_FLAG and SERIAL_TYPE, using the cross-reference type 'OPSM INTEGRATED'.
• MTL_PARAMETERS resolves the master organization used in the SERIAL_TYPE subquery.
• OE_ORDER_HEADERS_ALL, OE_ORDER_LINES_ALL, OE_TRANSACTION_TYPES_TL supply sales order number, order type name, line number, and the sold-to, ship-to, and invoice-to organization and contact identifiers.
• RCV_TRANSACTIONS contributes the receipt transaction context: transaction and parent transaction identifiers, type, date, quantities, and UOM codes.

Key Columns

• OPSM_INTEGRATED_FLAG — Returns 0 when the most recent 'OPSM INTEGRATED' cross-reference for the item/organization combination is 'NO'; otherwise returns 1. The flag is determined by the cross-reference row with the latest LAST_UPDATE_DATE.
• SERIAL_TYPE — Returns ATTRIBUTE1 from the master-organization 'OPSM INTEGRATED' cross-reference whose CROSS_REFERENCE equals 'YES'.
• SHIPMENT_HEADER_ID / SHIPMENT_LINE_ID / ITEM_ID — Core receiving identifiers; ITEM exposes the concatenated segments via MTL_SYSTEM_ITEMS_B_KFV.
• QUANTITY_SHIPPED / QUANTITY_RECEIVED / UNIT_OF_MEASURE — Received and expected quantities at line level.
• SHIPMENT_LINE_STATUS_CODE, QC_GRADE, ASN_LINE_FLAG, BAR_CODE_LABEL — Receiving status and labeling attributes.
• Order attributes — ORDER_NUMBER, ORDER_TYPE, LINE_NUMBER, and the SOLDBY, SHIPFROM, and BILLEDBY organization and contact identifiers link the receipt to its originating sales order.
• Transaction attributes — TRANSACTION_ID, PARENT_TRANSACTION_ID, TRANSACTION_TYPE, TRANSACTION_DATE, TRANSACTION_QTY, and the primary and secondary quantity/UOM pairs.
• 'RMA RECEIPT' — A literal projected column identifying the receipt classification.

Common Use Cases and Queries

The most frequent requirement is identifying which received lines are in scope for OPSM integration, or locating the source of an unexpected flag value. Because the flag is derived from cross-reference history, a diagnostic query on MTL_CROSS_REFERENCES_VL for cross-reference type 'OPSM INTEGRATED' is the standard companion check.

Example — list received lines and their OPSM status for one organization:

• SELECT shipment_line_id, item, organization_code, quantity_received, opsm_integrated_flag, serial_type FROM apps.rcv_opsm_line_v WHERE organization_id = :org_id AND opsm_integrated_flag = 1;

Example — reconcile RMA receipts against their originating sales order:

• SELECT shipment_line_id, order_number, order_type, line_number, transaction_date, transaction_qty FROM apps.rcv_opsm_line_v WHERE shipment_line_status_code = 'RECEIVED' ORDER BY transaction_date DESC;

Example — find items flagged for OPSM integration but lacking a serial type:

• SELECT item, organization_code, serial_type FROM apps.rcv_opsm_line_v WHERE opsm_integrated_flag = 1 AND serial_type IS NULL;

Given the correlated subqueries and the date-to-character comparison in the flag logic, queries against this view should be filtered by organization or shipment before joining to large reporting sets to avoid full scans of MTL_CROSS_REFERENCES_VL.