Results for “csd_rcv_line_status_v”

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

Overview

CSD_RCV_LINE_STATUS_V is a read-only PL/SQL view owned by the APPS schema in Oracle E-Business Suite releases 12.1.1 and 12.2.2. It belongs to the CSD (Depot Repair) product family and exists to support the receiving line status display on the Depot Repair status details tab within the Depot Repair HTML user interface. The view provides a consolidated read of receipt transaction activity alongside the associated order line and shipment numbering, allowing the Depot Repair status form to present receiving progress for repair-related order lines without querying the underlying Order Management and Receiving tables directly.

Because the view is a simple, non-versioned projection rather than a business object, it holds no data of its own and is regenerated automatically whenever the base tables change. It is not exposed through the public Oracle Integration Repository in a functional sense; it is an internal, presentation-oriented view whose primary consumers are Depot Repair application screens and any custom reports that reproduce the same query.

Underlying Base Objects

The view is defined over two base objects, both accessed through APPS synonyms:

• RCV_TRANSACTIONS (synonym) — the receiving transactions table, which supplies the order header reference, order line reference, received quantity, and transaction type.
• OE_ORDER_LINES_ALL (synonym) — the Order Management order lines table, joined to supply line number and shipment number for display formatting.

The join condition links OE.HEADER_ID = RCV.OE_ORDER_HEADER_ID and OE.LINE_ID = RCV.OE_ORDER_LINE_ID, so only receipt transactions that carry a populated Order Management header and line reference are returned. Rows are ordered by OE.LINE_NUMBER and OE.SHIPMENT_NUMBER, producing the natural line/shipment sequence shown on the status details tab.

Key Columns

• OE_ORDER_HEADER_ID — identifier of the Order Management order header associated with the receipt transaction; the primary correlation key back to OE_ORDER_HEADERS_ALL.
• OE_ORDER_LINE_ID — identifier of the Order Management order line associated with the receipt; joins to OE_ORDER_LINES_ALL.LINE_ID.
• LINE_NUMBER — a derived character string concatenating OE.LINE_NUMBER, a period, and OE.SHIPMENT_NUMBER (for example, "1.1"), used purely for display on the status details tab.
• QUANTITY — the quantity recorded on the receiving transaction.
• TRANSACTION_TYPE — the RCV_TRANSACTIONS transaction type, indicating the nature of the receiving activity (such as receipt, delivery, or return) for that line.

Common Use Cases and Queries

Typical usage is to retrieve receiving status for a specific Depot Repair or Order Management order line, or to catalogue all receipt transactions associated with a given order header. A representative query retrieving all receipt activity for a header is:

SELECT oe_order_header_id, oe_order_line_id, line_number, quantity, transaction_type FROM apps.csd_rcv_line_status_v WHERE oe_order_header_id = :p_header_id ORDER BY line_number;

A line-specific variant, useful when drilling into a single repair line, filters on both keys:

SELECT line_number, quantity, transaction_type FROM apps.csd_rcv_line_status_v WHERE oe_order_header_id = :p_header_id AND oe_order_line_id = :p_line_id;

Because the view joins only RCV_TRANSACTIONS and OE_ORDER_LINES_ALL, it can be safely reused in custom concurrent programs, BI Publisher data templates, and OAF page regions that need a compact receipt-status summary. Note that it does not restrict by organization, transaction date, or repair order, so queries should always be filtered by header or line to avoid full-table scans across aggregated receiving history.