Search Results po_line_locations_interface_n1

Overview

PO.PO_LINE_LOCATIONS_INTERFACE is the public interface (staging) table in the Oracle Purchasing module that holds shipment schedule and line location information consumed by the Purchasing Documents Open Interface (PDOI) program. It is used to create and update standard and blanket purchase orders, contract and global agreements, catalog quotations, and price break records, and it also supports price/sales catalog update processing via the 832 EDI transaction. Data loaded into this table is validated by PDOI, which derives or defaults additional attribute values and writes a row into PO_INTERFACE_ERRORS for every validation that fails, so that the source system can correct and resubmit the record. In Oracle EBS 12.1.1 and 12.2.2 the table resides in the APPS_TS_TX_DATA tablespace with 97 documented columns.

From a Data Vault modeling perspective, the heuristic relationship classification for this object is standalone; it may therefore be treated as a staging or raw-data construct rather than a fully resolved hub, link, or satellite. Where modeling is required, INTERFACE_LINE_LOCATION_ID is the natural candidate for a hub key, with INTERFACE_HEADER_ID and INTERFACE_LINE_ID forming a link-like relationship to the header and line interface tables.

Key Information Stored

The table is keyed by a surrogate identifier and organizes shipment-level detail beneath the header and line interface records.

• INTERFACE_LINE_LOCATION_ID — unique interface identifier for the line location row; this is the single-column unique key enforced by index PO_LINE_LOCATIONS_INTERFACE_U1.
• INTERFACE_HEADER_ID — groups the row under its interface header (indexed by PO_LINE_LOCATIONS_INTERFACE_N1).
• INTERFACE_LINE_ID — groups the row under its interface line (indexed by PO_LINE_LOCATIONS_INTERFACE_N2).
• PROCESSING_ID and PROCESS_CODE — identify the concurrent request that processed the row and the line status code (for example NOTIFIED, ACCEPTED, REJECTED) used in price/sales catalog updates.
• LINE_LOCATION_ID — the document shipment schedule identifier assigned upon successful creation.
• SHIPMENT_TYPE, SHIPMENT_NUM, QUANTITY, UNIT_OF_MEASURE — shipment definition and ordered quantity details.
• SHIP_TO_ORGANIZATION_ID, SHIP_TO_LOCATION_ID, SHIP_TO_ORGANIZATION_CODE, SHIP_TO_LOCATION — destination defaults.
• NEED_BY_DATE, PROMISED_DATE, START_DATE, END_DATE — scheduling and agreement effective dates.
• PRICE_OVERRIDE, PRICE_DISCOUNT, AMOUNT, LEAD_TIME — pricing and sourcing attributes.
• ACCRUE_ON_RECEIPT_FLAG, RECEIPT_REQUIRED_FLAG, INSPECTION_REQUIRED_FLAG, FIRM_FLAG — receiving and control indicators.
• REQUEST_ID, PROGRAM_ID, PROGRAM_APPLICATION_ID, CREATED_BY, LAST_UPDATE_DATE — concurrency and audit columns.
• PROJECT_ID, TASK_ID, AWARD_ID, BID_PAYMENT_ID — project and procurement-instrument references, the last two documented as foreign keys to IGF_AW_AWARD_ALL and PON_BID_PAYMENTS_SHIPMENTS respectively.

Common Use Cases and Queries

Typical uses include monitoring a PDOI submission run, diagnosing validation failures, and reporting on undelivered interface rows.

• Tracking a concurrent load: SELECT interface_line_location_id, processing_id, process_code FROM po_line_locations_interface WHERE processing_id = :request_id;
• Finding unprocessed rows for a header: SELECT * FROM po_line_locations_interface WHERE interface_header_id = :header_id AND processing_id IS NULL;
• Correlating failures with PO_INTERFACE_ERRORS on INTERFACE_LINE_LOCATION_ID to identify rejected shipment records.
• Confirming creation by matching INTERFACE_LINE_LOCATION_ID back to LINE_LOCATION_ID after successful processing.
• Reporting on receiving defaults such as ACCRUE_ON_RECEIPT_FLAG and RECEIPT_REQUIRED_FLAG for a project or agreement shipment.

Related Objects

The table participates in a small but well-defined dependency set:

• PO_INTERFACE_ERRORS — holds the validation failure messages written by PDOI.
• PO_LINE_LOCATIONS_INTERFACE indexes PO_LINE_LOCATIONS_INTERFACE_U1 (INTERFACE_LINE_LOCATION_ID), _N1, _N2, _N3 (PROCESSING_ID), and _N4 (LINE_LOCATION_ID) define access paths and joins back to the operational tables.
• PO_LINE_LOCATIONS_ALL — destination table populated via LINE_LOCATION_ID after successful processing.
• IGF_AW_AWARD_ALL — referenced through AWARD_ID.
• PON_BID_PAYMENTS_SHIPMENTS — referenced through BID_PAYMENT_ID.
• PO_HEADERS_INTERFACE and PO_LINES_INTERFACE — parent interface records joined on INTERFACE_HEADER_ID and INTERFACE_LINE_ID.
• The PDOI concurrent program itself is the principal consumer, validating, defaulting, and materializing rows into Purchasing documents.