Results for “header_pre_delete”
10 results
AI-generated from documented ETRM metadata — verify critical details on the linked pages.
Overview
ARP_PROCESS_COMMITMENT is a PL/SQL package body owned by the APPS schema in Oracle E-Business Suite Release 12.1.1 and 12.2.2. Its documented API classification is OTHER, and the package is listed with a status of VALID. The package is part of the Oracle Receivables (AR) infrastructure that supports commitment processing against customer transactions. Commitment processing in Receivables generally concerns the tracking and accounting treatment associated with sales commitments, deferred revenue arrangements, and related adjustments that must be reflected in the transaction and distribution records.
Functionally, the package operates as an event-handling layer rather than a standalone business API. It supplies pre- and post-insert, update, and delete logic used when transaction header records are manipulated, together with a utility routine (SET_TO_DUMMY) used to neutralize or reset a value during processing. The presence of these procedures indicates that ARP_PROCESS_COMMITMENT is invoked indirectly by broader Receivables transaction processing logic to maintain data consistency before and after DML occurs on the underlying Receivables tables. The package body is not referenced by any other database object, but it depends on a set of AR processing packages and reference tables, confirming its role as an internal processing component.
Key Procedures and Functions
The ETRM metadata documents six procedures within the package body. No parameter lists are published, and none are reproduced here.
- HEADER_PRE_INSERT — Executes logic prior to insertion of a transaction header record. It prepares or validates header-level values required by commitment processing before the row is written.
- HEADER_POST_INSERT — Executes logic after the header record has been inserted, performing any dependent updates or derivations that require the header row to exist.
- HEADER_PRE_UPDATE — Executes logic before an existing transaction header is modified, ensuring commitment-related values remain consistent with the pending change.
- HEADER_POST_UPDATE — Executes logic after the header update completes, propagating or reconciling downstream effects of the change.
- HEADER_PRE_DELETE — Executes logic before a transaction header is removed, supporting validation or cleanup of commitment-related data tied to that header.
- SET_TO_DUMMY — A utility routine that assigns a dummy or placeholder value, typically used to disable or bypass standard processing within a controlled branch of the commitment logic.
The naming convention confirms that the package is oriented around header-level commitment events rather than line-level or distribution-level processing.
Tables Accessed
The package references the following APPS synonym tables:
- RA_CUSTOMER_TRX — The transaction header table; the pre- and post-insert/update/delete procedures operate around this entity.
- RA_CUSTOMER_TRX_LINES — Transaction lines associated with the header, consulted for line-level context.
- RA_CUST_TRX_LINE_GL_DIST — Accounting distributions for transaction lines, relevant to commitment accounting treatment.
- RA_CUST_TRX_LINE_SALESREPS — Salesperson assignments at the line level, used where commitment ownership or credit attribution is required.
- RA_CUST_TRX_TYPES — Transaction type definitions, used to determine processing rules applicable to the header.
- FND_CURRENCIES — Currency reference data, consulted for currency-related validation or conversion context.
Additional dependencies include FND_PROFILE, GL_SETS_OF_BOOKS, and several AR packages: ARP_AUTO_ACCOUNTING, ARP_CTLGD_PKG, ARP_CTLS_PKG, ARP_CTL_PKG, ARP_GLOBAL, and ARP_UTIL. These indicate reliance on profile options, set of books configuration, automatic accounting, and standard AR control and utility routines.
Usage Notes
ARP_PROCESS_COMMITMENT is an internal, event-driven package rather than a directly callable public API. It is invoked implicitly during Receivables transaction header processing, typically through the standard Oracle Receivables forms and the underlying transaction insertion, update, and deletion logic. Because it is not referenced by any other database object and is not exposed as a documented public API, it should not be called directly from custom code.
Customizations should treat this package as an implementation detail of Oracle Receivables. Any extension requirements related to commitment processing should be addressed through supported APIs or documented hooks, since modifying or invoking this package directly risks inconsistency with the surrounding AR control and accounting logic. The package is documented as VALID, and the metadata reports that it is referenced by seven other packages, confirming its position within the internal dependency chain of Receivables processing.