Search Results reap_batchresults

Overview

APPS.ITG_SYNCITEMINBOUND_PVT is a private (PVT) PL/SQL package belonging to the Oracle E-Business Suite item synchronization infrastructure. Its role is to support the inbound synchronization of item master data from external or legacy systems into the Oracle EBS item interface framework. The package provides the internal plumbing used by the batch management layer to stage, process, and reconcile item records that arrive through the inbound interface, rather than exposing a supported public API for direct customer use.

The package is classified as private, and its source header explicitly warns that the batch-related procedures and functions are not part of the ABO API and are internal callbacks from the batch management package. This classification indicates that the package is intended for use by Oracle internal processes and synchronization programs, not for direct invocation by customer code or extensions.

Key Procedures and Functions

• SYNC_ITEM — The primary documented procedure. It performs the inbound synchronization of an individual item, accepting attributes describing the item and its organizational context and returning status information. It is the core call used to push item data into the interface processing pipeline.
• GET_NEXTPROCESSSETID — Returns the next process set identifier. This is an internal callback used by the batch management package to obtain the identifier that groups a batch of item records for processing.
• START_BATCHPROCESS — Returns a Concurrent Manager (CCM) request id. It initiates the batch process for a given process set, synchronization indicator, and organization. As an internal callback, it is invoked by the batch management layer rather than by end users directly.
• REAP_BATCHRESULTS — Collects and returns the results of a previously submitted batch request, correlating the request identifier with the affected interface rows.
• ERROR_TRANSACTIONS — Moves or records failed transactions for a given request into the error handling structure, based on the supplied request identifier and table name.

The source comments explicitly state that the batch callback functions are not part of the ABO API, reinforcing that they exist solely to service the internal batch framework.

Tables Accessed

• MTL_SYSTEM_ITEMS_INTERFACE — The primary item interface table where inbound item records are staged before validation and import into the item master.
• MTL_SYSTEM_ITEMS_INTF_SETS_S — The interface set sequence used to assign and track interface set identifiers for staged records.
• MTL_ITEM_CATEGORIES_INTERFACE — Holds category assignment data associated with inbound items during synchronization.
• MTL_INTERFACE_ERRORS — Receives error rows generated when inbound interface records fail validation or processing.
• PO_HAZARD_CLASSES — Referenced in connection with hazardous material classification passed during synchronization.
• DUAL — Used for singleton sequence or scalar retrieval, consistent with the identifier-generation functions.

Usage Notes

Because this package is classified as private and its batch callbacks are explicitly excluded from the ABO API, it should not be invoked directly from custom forms, concurrent programs, or bespoke PL/SQL. It is referenced by one other package within the Oracle EBS object dependency set, which drives the synchronization workflow. Typical invocation occurs through Oracle's item inbound synchronization programs, which call START_BATCHPROCESS via the batch management package, then submit the resulting Concurrent Manager request and later call REAP_BATCHRESULTS to evaluate outcomes. Any rows that fail are routed through ERROR_TRANSACTIONS into the interface error tables. Customers and integrators requiring inbound item creation should use the supported public item interface APIs and import concurrent programs instead, leaving ITG_SYNCITEMINBOUND_PVT to its internal role.