Results for “taxable_flag”

50+ results




Overview
Explore in AI Chat

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

Overview

CLN_PO_ECX_LINE_LOC_ARCH_V is a PL/SQL view owned by the APPS schema within the CLN – Supply Chain Trading Connector for RosettaNet product module. Its documented purpose is to support data mapping for the PIP-3A8Response business process, the RosettaNet Partner Interface Process that communicates a distributor or supplier's response to a previously received purchase order request. In Oracle EBS 12.1.1 and 12.2.2, the view exposes purchase order line and shipment (line location) attributes in a denormalized, integration-friendly format that the trading connector maps into the PIP-3A8 response message payload exchanged with external trading partners.

Because the view is intended for mapping purposes rather than for interactive reporting, it presents a focused projection of order scheduling data rather than the full column set of the underlying purchasing tables. It is commonly queried by the RosettaNet connector's mapping and extraction logic during outbound message generation, and it may also be referenced by diagnostic queries when validating the data that will be transmitted to a partner.

Underlying Base Objects

The view is defined over three documented base objects, each referenced through a public synonym in the APPS schema:

  • PO_LINE_LOCATIONS_ALL — the primary driving table, aliased PLLA, supplying shipment-level scheduling, quantity, pricing, and consignment attributes. It is joined to PO_LINES_ALL on both PO_LINE_ID and PO_HEADER_ID.
  • PO_LINES_ALL — aliased PLA, supplying the line number and a fallback unit of measure when the shipment record does not carry its own lookup code.
  • MTL_UNITS_OF_MEASURE_TL — aliased MUOMTL, the UOM translation table, providing the UOM_CODE resolved for the user's session language.

The join predicates require that the line and header identifiers match across PO_LINES_ALL and PO_LINE_LOCATIONS_ALL, that the open ordered quantity (QUANTITY minus QUANTITY_CANCELLED) is greater than zero, and that the effective unit of measure equals the translation table's UNIT_OF_MEASURE for the current language. The effective UOM is derived with a DECODE on PLLA.UNIT_MEAS_LOOKUP_CODE, falling back to PLA.UNIT_MEAS_LOOKUP_CODE when the shipment-level value is null.

Key Columns

Common Use Cases and Queries

Typical usage validates or extracts the open shipments to be returned in a PIP-3A8 response, often filtered by operating unit or order identifiers:

  • Extracting all open shipments for a given partner operating unit and needing them within a date window.
  • Reconciling the quantities and promised dates the connector will transmit against the underlying purchasing records.
  • Auditing UOM resolution for shipments where the shipment-level lookup code is null and the line-level code applies.

A representative query is:

  • SELECT supplier_order_line_number, line_num, shipment_num, ordered_quantity, uom, need_by_date, promised_date FROM cln_po_ecx_line_loc_arch_v WHERE partner_id = :org_id ORDER BY line_num, shipment_num;

Because the view excludes fully cancelled shipments and enforces UOM resolution, consumers should expect only currently actionable shipment lines to be returned.