Results for “po_pdoi_item_process_pvt”

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

Overview

The APPS.PO_PDOI_ITEM_PROCESS_PVT package is a private (PVT-classified) PL/SQL package within the Oracle E-Business Suite Purchasing module. Its role is to support the Processing Draft Purchase Orders Interface (PDOI) — the framework used to import, validate, and commit purchase order data staged in the interface tables. PDOI is the technology behind features such as Oracle Purchasing's "Process Draft Purchase Orders" concurrent program and certain XML/electronic commerce inbound flows that bring supplier-and-buyer data into EBS as draft or open purchase orders.

Item processing is a distinct and mandatory step within the PDOI pipeline. Before a purchase order line can be committed, the item referenced on the line must exist and be valid in the inventory master. If the item is new — for example, it has been supplied through an external catalog or an EDI transaction and has not yet been created in the target inventory organization — the interface framework must create it and any associated category assignments, revisions, and system-item attributes. PO_PDOI_ITEM_PROCESS_PVT encapsulates precisely this responsibility, keeping it isolated from the public calling surface used by application code and customizations.

Key Procedures and Functions

The package exposes a single documented procedure, CREATE_ITEMS. Consistent with PDOI conventions, it operates on the PO_PDOI_TYPES.lines_rec_type record structure carried in an IN OUT NOCOPY parameter. The procedure consumes the purchase order line records presented by the caller, determines whether the items those lines reference are already defined, and, where they are not, drives the interface tables to establish them. Because it is a private package, it is not intended as a supported extension point; its signature and behavior are subject to change between releases and patches.

• CREATE_ITEMS — Creates or validates inventory items required by purchase order lines being processed through the PDOI stream, updating the line structure with any resulting item identifiers or processing status so that downstream commit logic can continue.

Tables Accessed

The referenced objects reflect the two halves of the operation: reading purchase order context and writing inventory definitions.

• MTL_SYSTEM_ITEMS and MTL_SYSTEM_ITEMS_INTERFACE — the target item master and its staging table, used to detect existing items and to insert new system item definitions.
• MTL_ITEM_CATEGORIES and MTL_ITEM_CATEGORIES_INTERFACE — category assignment storage and staging, used to attach items to purchasing or inventory categories.
• MTL_ITEM_REVISIONS_INTERFACE — staging of revision information associated with the items being created.
• MTL_INTERFACE_ERRORS — the error log where validation or creation failures are recorded for review.
• PO_HEADERS_ALL, PO_HEADERS_DRAFT_ALL, PO_LINES_INTERFACE, and PO_LINE_LOCATIONS_INTERFACE — the purchase order header, draft header, line, and shipment interface tables supplying the context for item resolution.
• PO_SESSION_GT — a session-scoped temporary table used to track state within the running PDOI session.
• DUAL, DBMS_SQL, and PLITBLM — supporting utilities for scalar selection, dynamic processing, and PL/SQL table management.

Usage Notes

PO_PDOI_ITEM_PROCESS_PVT is not a documented public API and should not be called directly from custom code. It is invoked internally by the PDOI processing engine — the package framework that the "Process Draft Purchase Orders" concurrent program and related inbound purchasing flows execute — as one stage in the multi-step orchestration that moves data from the interface tables into the base purchasing tables. The package is referenced by one other application package, consistent with its role as a subordinate component rather than an entry point.

Administrators and developers encountering this object are typically diagnosing item-creation failures during a PDOI run. In that scenario, the relevant output is generally the rows written to MTL_INTERFACE_ERRORS, which explain why a given line's item could not be created or matched. Remediation normally consists of correcting the source item data, inventory organization setup, or item attribute controls and resubmitting, not of altering this package. Because the header comment identifies a 2005 revision and the object is marked noship, its behavior is stable but unsupported for direct extension; any customization should target the interface tables and the public PDOI entry points instead.