Search Results cln_po_change_response_line_v

Overview

The CLN_PO_CHANGE_RESPONSE_LINE_V view is a Supply Chain Trading Connector for RosettaNet (CLN) mapping object owned by the APPS schema in Oracle E-Business Suite 12.1.1 and 12.2.2. Its documented purpose is to support the response mapping stage of the RosettaNet Partner Interface Process PIP-3A8, which governs the communication of purchase order change request responses between trading partners. In the ETRM documentation the object is registered as a VALID view with the description "used for mapping purposes in PIP-3A8Response."

The view does not store data itself; it presents a consolidated, line-level projection of purchase order change request records so that the RosettaNet messaging layer can emit an outbound response document. Each row corresponds to a distinct DOCUMENT_LINE_ID, with the change request status and response reason aggregated from the underlying request rows. Because the view filters by a dynamically derived change request group identifier, it is intended to return only the response payload relevant to the current integration cycle rather than the full history of change requests.

Underlying Base Objects

Per ETRM metadata, the view is defined over the following referenced objects:

• PO_CHANGE_REQUESTS (synonym) — the transactional table that records purchase order change requests at the line and shipment request levels. This is the primary source of the view's rows, columns, and aggregation logic.
• CLN_PO_CHANGE_RESPONSE_PKG (package) — the CLN package supplying GET_CHANGE_REQUEST_GROUP_ID(), which resolves the change request group identifier used in the view's correlated subquery. This package encapsulates the integration state that determines which group of change requests is eligible for the current PIP-3A8 response.
• DUAL (synonym) — used solely to invoke the package function in the subquery predicate.

The view therefore depends on both persistent transactional data (PO_CHANGE_REQUESTS) and PL/SQL-driven session state (CLN_PO_CHANGE_RESPONSE_PKG), which means its result set is context-sensitive and can change between executions depending on the current value returned by the package function.

Key Columns

• DOCUMENT_LINE_ID — the identifier of the purchase order document line; also the column by which the result set is grouped.
• REQUEST_STATUS — the request status for the row whose REQUEST_LEVEL is 'LINE', extracted through a conditional DECODE.
• MIN_REQUEST_STATUS — the minimum request status across all qualifying rows for that document line, useful for detecting a pending or unresolved state.
• RESPONSE_REASON — the response reason captured at the line request level.
• SUPPLIER_LINE_REF — the supplier's line reference, aggregated with MAX so that a single non-null reference is surfaced for the document line.

Common Use Cases and Queries

The principal scenario is generating the outbound PIP-3A8 response. A query such as the following retrieves one consolidated row per document line for the active change request group:

SELECT document_line_id,
       request_status,
       min_request_status,
       response_reason,
       supplier_line_ref
FROM   apps.cln_po_change_response_line_v;

Typical applications include:

• Verifying that each changed document line has an associated response reason before outbound transmission.
• Reconciling line-level and shipment-level request statuses by comparing REQUEST_STATUS with MIN_REQUEST_STATUS.
• Joining the view to purchase order line tables on DOCUMENT_LINE_ID to enrich the response payload with item and quantity information.
• Diagnosing stalled responses by identifying lines whose minimum request status remains unfulfilled.

Because the view is filtered by the package-derived group identifier, troubleshooting generally requires invoking the integration flow or confirming the value returned by CLN_PO_CHANGE_RESPONSE_PKG.GET_CHANGE_REQUEST_GROUP_ID() in the session performing the lookup.