Search Results reject_headers_intf
Overview
PO_PDOI_UTL is a utility package within the Oracle E-Business Suite Purchasing module, tightly coupled to the PO Product Data Online (PDOI) interface processing framework. It is declared with AUTHID CURRENT_USER, meaning its unqualified references to database objects resolve against the privileges of the invoking schema rather than the APPS schema owner. The package serves as the backend service layer that supports validation, rejection, and cleanup of records staged in the Purchasing interface tables during import of purchase orders and related documents. Its central responsibility is the "reject" workflow: when a row in an interface table fails validation, the PDOI processor must be able to mark that row, cascade the rejection to dependent child records, and preserve an audit trail. PO_PDOI_UTL encapsulates these operations so that multiple callers — validation programs, the PDOI user interface, and downstream concurrent programs — share a single implementation. The package is referenced by approximately fifteen other packages, confirming its role as a foundational utility rather than an entry-point API.
Key Procedures and Functions
The package exposes fifteen documented procedures and functions, broadly divisible into session management, rejection logic, and supporting utilities.
- REMOVE_SESSION_GT_RECORDS — purges rows from the PO_SESSION_GT global temporary table for a given session key, ensuring temporary validation state does not leak between processing runs.
- COMMIT_WORK — issues a controlled commit of pending interface work, allowing callers to persist progress in batches.
- GET_NEXT_BATCH_ID — returns the next batch identifier used to group interface rows for a processing cycle.
- REJECT_HEADERS_INTF, REJECT_LINES_INTF, REJECT_LINE_LOCATIONS_INTF — mark rejected header, line, and line-location interface rows respectively. Each accepts an ID parameter type and a list of IDs, plus a cascade flag indicating whether dependent child records should also be rejected. The user query term reject_lines_intf corresponds directly to the second of these.
- REJECT_DISTRIBUTIONS_INTF, REJECT_PRICE_DIFF_INTF, REJECT_ATTR_VALUES_INTF, REJECT_ATTR_VALUES_TLP_INTF — extend rejection handling to distribution, price differential, and attribute value interface rows, including the TLP (two-level pricing) attribute table.
- POST_REJECT_DOCUMENT — performs post-rejection document processing, reconciling interface header, PO header, and draft identifiers and optionally removing the draft.
- GENERATE_ORDERED_NUM_LIST — produces an ordered numeric list used for sequencing batch operations.
- GET_PROCESSING_DOCTYPE_INFO — returns the document type and subtype currently being processed.
- IS_OLD_REQUEST_COMPLETE — checks whether a prior concurrent request has finished, supporting serialization of overlapping imports.
- REJECT_UNPROCESSED_INTF — rejects any remaining unprocessed interface rows for a given header.
Tables Accessed
The package reads and writes the core Purchasing interface tables through APPS synonyms: PO_HEADERS_INTERFACE, PO_LINES_INTERFACE, PO_LINE_LOCATIONS_INTERFACE, PO_DISTRIBUTIONS_INTERFACE, PO_PRICE_DIFF_INTERFACE, PO_ATTR_VALUES_INTERFACE, and PO_ATTR_VALUES_TLP_INTERFACE. These are the staging tables populated by the PO Open Interface and purged or flagged on rejection. PO_SESSION_GT is the session-scoped temporary table used to hold working validation state. DBMS_SQL is referenced to support dynamic numeric list generation and PLITBLM provides the PL/SQL integer table type declared within the package.
Usage Notes
PO_PDOI_UTL is not intended for direct end-user invocation. It is called from the PDOI validation and import concurrent programs, from the PDOI forms-based interface, and from other Purchasing packages performing interface cleanup. Customizations should call these procedures only with correctly typed ID tables and should respect the cascade parameter, since improper cascading can leave orphaned child interface rows. In 12.1.1 and 12.2.2 the package interface is unchanged, though the 12.2 codebase continues to reference it from the same fifteen dependent packages.
-
PACKAGE: APPS.PO_PDOI_UTL
12.2.2
-
PACKAGE: APPS.PO_PDOI_UTL
12.1.1
-
PACKAGE: APPS.PO_R12_CAT_UPG_UTL
12.1.1
-
PACKAGE: APPS.PO_R12_CAT_UPG_UTL
12.2.2
-
PACKAGE BODY: APPS.PO_PDOI_UTL
12.2.2
-
PACKAGE BODY: APPS.PO_PDOI_UTL
12.1.1
-
PACKAGE BODY: APPS.PO_R12_CAT_UPG_UTL
12.1.1
-
PACKAGE BODY: APPS.PO_R12_CAT_UPG_UTL
12.2.2
-
APPS.PO_PDOI_UTL dependencies on PO_TBL_NUMBER
12.2.2
-
APPS.PO_PDOI_UTL dependencies on PO_TBL_NUMBER
12.1.1
-
APPS.PO_R12_CAT_UPG_UTL dependencies on PO_R12_CAT_UPG_TYPES
12.1.1
-
APPS.PO_R12_CAT_UPG_UTL dependencies on PO_R12_CAT_UPG_TYPES
12.2.2
-
APPS.PO_R12_CAT_UPG_UTL dependencies on PO_R12_CAT_UPG_TYPES
12.1.1
-
APPS.PO_R12_CAT_UPG_UTL dependencies on PO_R12_CAT_UPG_TYPES
12.2.2
-
APPS.PO_PDOI_UTL dependencies on PO_TBL_NUMBER
12.1.1
-
APPS.PO_PDOI_UTL dependencies on PO_TBL_NUMBER
12.2.2
-
APPS.PO_PDOI_UTL dependencies on FND_API
12.2.2
-
APPS.PO_PDOI_UTL dependencies on FND_API
12.1.1
-
APPS.PO_PDOI_UTL dependencies on PO_LOG
12.2.2
-
APPS.PO_PDOI_UTL dependencies on PO_LOG
12.1.1
-
APPS.PO_PDOI_UTL dependencies on PO_PDOI_CONSTANTS
12.1.1
-
APPS.PO_PDOI_UTL dependencies on PO_PDOI_CONSTANTS
12.2.2
-
APPS.PO_R12_CAT_UPG_UTL dependencies on PO_R12_CAT_UPG_DEBUG
12.1.1
-
APPS.PO_R12_CAT_UPG_UTL dependencies on PO_R12_CAT_UPG_DEBUG
12.2.2