Search Results itg_batchmanagement_pvt




Overview
Explore in AI Chat

Overview

The APPS.ITG_BATCHMANAGEMENT_PVT package is a private (PVT-classified) PL/SQL API belonging to the Oracle E-Business Suite ITG (Internet Time and Expense / iExpenses family of ITG modules) application. It encapsulates the server-side logic used to manage the lifecycle of batches — groupings of expense or transaction request items that are processed together as a unit. The package acts as the internal engine behind batch creation, submission, workflow-driven state transitions, timeout detection, restart, and completion. Because it is classified as PVT, it is not intended as a public, formally supported integration API; rather it is consumed internally by other ITG components and by Oracle Workflow activities.

The package is owned by the APPS schema, is in VALID status, and depends on the standard Oracle EBS public API framework package FND_API (and the underlying SYS.STANDARD package). It is referenced by the ITG_BATCHMANAGEMENT_PVT object itself — that is, its public and private subunits call one another, consistent with a cohesive private package that does not expose interfaces to other packages (documented as "referenced by 0 other packages").

Key Procedures and Functions

The documented API surface consists of eight procedures/functions. Their documented purposes are as follows:

  • GET_PROCESSSETID — Resolves or returns the process set identifier associated with a batch, used to link a batch to the processing configuration that governs it. (Note the spelling "PROCESSSETID" is as documented.)
  • FLUSH_REQUESTITEMS — Persists or releases the accumulated set of request items staged for a batch, ensuring queued items are committed to their processing grouping.
  • ADDED_REQUESTITEM — Handles the event of a request item having been added to a batch, updating the internal batch state accordingly.
  • WF_CHECK_BATCH_TIMEOUT — Workflow-callable routine that evaluates whether a batch has exceeded its allowable processing time, supporting timeout enforcement.
  • WF_GET_BATCH_INFO — Workflow-callable routine that retrieves batch information for use by workflow processes and notifications.
  • WF_START_BATCH — Workflow-callable routine that initiates batch processing.
  • WF_RESTART_BATCH — Workflow-callable routine that reinitiates a batch after interruption, timeout, or failure.
  • WF_COMPLETE_BATCH — Workflow-callable routine that finalizes a batch and marks it complete.

The WF_ prefix on five of the routines indicates they are designed to be invoked as Oracle Workflow function activities, driving batch state transitions through workflow.

Tables Accessed

The documented table reference for this package is USER_OBJECTS, accessed through an APPS synonym. USER_OBJECTS is an Oracle data dictionary view that lists objects owned by the current schema; the package uses it, for example, to validate object existence or to drive metadata-driven processing logic. The ETRM excerpt records only this single documented table dependency; any additional ITG batch and request-item tables used internally are not enumerated in the supplied metadata.

Usage Notes

ITG_BATCHMANAGEMENT_PVT is an internal package and is not intended to be called directly by customer extensions. In practice it is invoked in three contexts:

  • Oracle Workflow — the WF_* routines are wired into ITG batch workflow definitions as function activities, so the workflow engine calls them to start, monitor, restart, and complete batches.
  • Concurrent programs and internal ITG code — batch-processing concurrent requests and sibling ITG packages call the non-WF routines (GET_PROCESSSETID, FLUSH_REQUESTITEMS, ADDED_REQUESTITEM) during batch assembly and submission.
  • Forms-driven transactions — ITG/Expense entry forms trigger batch handling that ultimately flows through this package.

Because it is a PVT package with no documented dependents outside itself, customizations should avoid direct calls; the supported approach is to use the public ITG APIs and Workflow, which in turn exercise this package. Behavior is consistent across EBS 12.1.1 and 12.2.2, with the latter being the documented reference release for the metadata above.