Search Results p_batch

Overview

IPA_CLIENT_EXTN_TRX_SRC_PROC is a public PL/SQL extension package owned by the APPS schema in Oracle E-Business Suite. It is defined with AUTHID CURRENT_USER, meaning its SQL statements execute under the privileges of the invoking user rather than the package owner, which is the standard convention for client extension hooks in the ETRM (Enterprise Transaction Resource Manager) framework. The package supplies two client extension points for the Capitalized Interest transaction source: a pre-processing hook and a post-processing hook. These hooks allow implementers to inject site-specific logic into the transaction lifecycle of Capitalized Interest without modifying Oracle's seeded processing code. The header identifier (IPACLPRS.pls, version 120.0, dated 2005/05/31) confirms it is a long-standing extension interface that has carried forward into the 12.1.1 and 12.2.2 releases unchanged in structure.

Key Procedures and Functions

The package exposes two documented public procedures, both of which accept the same four IN parameters: the transaction source identifier, the batch name used to group transactions, the interface identifier, and the invoking user identifier. Because this is an extension package, the bodies are intentionally left for customer implementation; the seeded form normally contains stubs or placeholder logic.

• PRE_PROCESS_EXTN — Invoked before standard processing of Capitalized Interest transactions. It provides a point at which the implementer can validate, enrich, or transform interface records prior to the main transaction processing logic. The P_batch parameter supplies the batch grouping name so that pre-processing logic can act on a defined set of transactions rather than the entire interface.
• POST_PROCESS_EXTN — Invoked after standard processing completes. It provides a point for reconciliation, derived data updates, error handling, or downstream notifications once transactions for the batch have been processed. The same parameter set is passed so the extension can correlate work performed in the pre-processing phase.

No other procedures or functions are documented in the ETRM metadata.

Tables Accessed

The ETRM metadata does not document any tables referenced through APPS synonyms, and the package declares no %ROWTYPE anchors or explicit DML in the visible source excerpt. This is consistent with its role as an extension skeleton: the interface tables associated with Capitalized Interest processing are expected to be accessed indirectly through the driving ETRM logic that passes P_xface_id and P_batch into these procedures. Implementers who add logic here will typically query and update the ETRM interface and staging tables identified by P_xface_id, but the package itself imposes no dependency on them.

Usage Notes

The procedures are not entered directly by end users. They are dispatched by the ETRM processing engine when the Capitalized Interest transaction source is processed, passing the interface ID and batch name of the run in progress. Typical invocation paths include the concurrent programs that drive transaction sourcing and the ETRM runtime framework itself. Because no other packages reference this package (0 documented referencing packages), callers are external to the PL/SQL dependency graph — the framework resolves and calls these entry points at runtime.

The P_batch parameter is significant for extensibility: it identifies the batch into which transactions are grouped, so custom logic in either hook can restrict its scope to a single batch rather than the whole interface. Implementers should preserve the documented parameter signatures, as altering them will break the framework's runtime call. In 12.1.1 and 12.2.2, the recommended practice is to create a custom package containing site logic and keep IPA_CLIENT_EXTN_TRX_SRC_PROC as a thin wrapper that delegates to it, preserving a clean upgrade path.