Search Results po_line_locations_interface_s

Overview

PO_PDOI_PREPROC_PVT is a private (PVT-classified) PL/SQL package body in the APPS schema that implements the pre-processing stage of the Purchasing Document Open Interface (PDOI) flow in Oracle E-Business Suite 12.1.1 and 12.2.2. PDOI is the inbound interface used to load purchase orders, blanket agreements, contracts, and releases from external or legacy systems into Oracle Purchasing. Before any interface row can be validated and imported, it must pass through the pre-processing phase, which this package orchestrates.

The business function of the package is to prepare raw staging rows for downstream validation and import. It assigns processing identifiers, resolves and derives surrogate keys such as vendor identifiers and PO header identifiers, filters the set of interface rows that are eligible for processing, and enforces document-level business rules including action-code consistency and release date constraints. The header comment identifies the single public entry point, process, as the "Main procedure of PRE-PROCESSING in PDOI". The package is version-tracked (header string 120.24) and is functionally dependent on PO_PDOI_CONSTANTS, PO_LOG, and PO_TIMING_UTL for logging and timing instrumentation.

Key Procedures and Functions

The only documented public procedure is process, which drives the entire pre-processing phase. It opens a logging context, starts the pre-processing timing bucket via PO_TIMING_UTL, and invokes the package's internal steps in sequence. The package specification excerpt also exposes the prototypes of its private helpers, which reveal the granular work performed:

• get_processable_records — selects the interface header rows eligible for this run based on process code and request ID; the NOCOPY OUT parameter indicates it returns a bulk collection of header IDs.
• assign_processing_id — stamps a processing identifier on interface rows to group them for the current run.
• derive_vendor_id — resolves the supplier identifier from the interface values provided.
• assign_po_header_id — assigns the PO header identifier used to relate interface lines and locations.
• validate_interface_values — performs pre-import validation of the staging record.
• verify_action_replace, verify_action_update, and verify_action_original — enforce the semantics of the ORIGINAL, UPDATE, and REPLACE action codes defined for PDOI.
• populate_line_loc_interface — populates the line and shipment (line location) interface tables.
• check_release_dates — validates new document start dates against release scheduling rules, returning a validity flag.
• update_dependent_line_acc_flag — a bug-fix routine (referenced to bug 5149827) that maintains a dependent line accrual flag.

Tables Accessed

The package reads and writes the core PDOI staging tables and the corresponding Purchasing base tables via APPS synonyms:

• Interface tables: PO_HEADERS_INTERFACE, PO_LINES_INTERFACE, PO_LINE_LOCATIONS_INTERFACE (and its _S sequence-backed variant), PO_DISTRIBUTIONS_INTERFACE (and _S), PO_ATTR_VALUES_INTERFACE, and PO_ATTR_VALUES_TLP_INTERFACE. These hold the staged inbound documents, lines, shipments, distributions, and descriptive attribute values.
• Base and transient tables: PO_HEADERS / PO_HEADERS_ALL / PO_HEADERS_S and PO_LINES_ALL, used to resolve and assign identifiers during pre-processing.
• Validation and lookup tables: PO_DOCUMENT_TYPES to confirm the document type of each staged record, PO_INTERFACE_ERRORS to record processing failures, and FND_NEW_MESSAGES for message resolution.

Usage Notes

Because PO_PDOI_PREPROC_PVT is classified as a private package, it is not intended for direct invocation by customers or third-party code. It is called internally by the PDOI orchestration layer, typically from the concurrent program "Import Standard Purchase Orders" (and related PDOI import programs) and from the PO_PDOI_PROCESS_PVT package that sequences the pre-processing, validation, and import phases. The documented metadata notes that it is referenced by one other package, and the search term "UPDATEC" corresponds to the verify_action_update action-code verification path executed when staged documents carry the UPDATE action. Customizations should never modify this package; interface data should be loaded into the PDOI interface tables and the standard import concurrent program submitted, allowing this package to perform pre-processing as designed. Diagnostic tracing is available through the PO_LOG and PO_TIMING_UTL instrumentation already embedded in the code.