Results for “drop_ship_flag”

50+ results




Overview
Explore in AI Chat

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

Overview

The APPS.ITG_SP_PO_LINE_SCHED_V view is a procurement integration object belonging to the ITG – Internet Procurement Enterprise Connector product. Its documented purpose is to generate XML payloads for the Sync PO process at the line schedule level. In other words, rather than extracting purchase order data at the header or line grain, this view exposes one row per purchase order shipment (schedule), drawing on the same underlying structures that the Oracle EBS user interface presents through the po_line_locations entity, which is the term most users associate with this data.

The view carries a VALID status in the APPS schema and is available in both Oracle EBS 12.1.1 and 12.2.2. Because it is a view rather than a table, it holds no data of its own; it is a read-only projection used by the ITG connector when publishing purchase order synchronization feeds to an external procurement or marketplace system. The view conforms to the multi-org architecture typical of Oracle Purchasing, since the underlying PO_LINE_LOCATIONS_ALL table is org-striped and secured through the standard operating unit security profile.

Underlying Base Objects

The ETRM metadata documents three referenced base objects, each exposed to the view through a synonym in the APPS schema:

  • PO_LINE_LOCATIONS_ALL (synonym) – aliased as PLLA, this is the primary source. It is the table that stores shipment and distribution scheduling information, and it is what users mean when they reference po_line_locations. The LINE_LOCATION_ID is the unique key for each schedule.
  • PO_LINES_ALL (synonym) – aliased as PLA, joined to PLLA on PO_LINE_ID. This provides the line-level unit of measure lookup code and reinforces the header-to-line-to-schedule hierarchy.
  • MTL_UNITS_OF_MEASURE (synonym) – aliased as UOM, joined on UOM.UNIT_OF_MEASURE = PLA.UNIT_MEAS_LOOKUP_CODE to translate the stored lookup code into a printable UOM code.

All three objects are referenced through APPS synonyms, so the view resolves entirely within the APPS schema without direct schema-qualified references to the transactional tables.

Key Columns

The view exposes identifying keys, scheduling attributes, quantity and unit information, and attachment descriptors:

Common Use Cases and Queries

The principal use case is generating the Sync PO XML at schedule grain, most often driven by a concurrent request or a connector program that filters to changed or newly approved schedules before serializing the rows. A frequent secondary use is reconciliation: confirming which schedules and which schedule-level attachment categories are included in a given synchronization run.

SELECT PO_HEADER_ID,
       PO_LINE_ID,
       LINE_LOCATION_ID,
       DATETIME_NEEDDELV,
       ORDERED_QUANTITY,
       ORDERED_UOM,
       SHIPMENT_NUM
  FROM APPS.ITG_SP_PO_LINE_SCHED_V
 WHERE PO_HEADER_ID = :p_po_header_id
 ORDER BY PO_LINE_ID, SHIPMENT_NUM;

To inspect schedule flexfield data alongside the delivered quantity:

SELECT UA_SCHEDLID,
       UA_SCHED_ATTR1,
       UA_SCHED_ATTR2,
       ORDERED_UOM,
       DATETIME_NEEDDELV
  FROM APPS.ITG_SP_PO_LINE_SCHED_V
 WHERE LINE_LOCATION_ID = :p_line_location_id;

Because the view joins the org-striped PO_LINE_LOCATIONS_ALL table, queries executed under a MOAC-enabled session automatically respect the operating unit security profile. When troubleshooting a Sync PO feed, compare the row count and LINE_LOCATION_ID values returned here against PO_LINE_LOCATIONS_ALL; any discrepancy typically points to the UOM join or to operating unit context rather than to missing schedules.