Results for “arp_transaction_history_pkg”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

The APPS.ARP_TRANSACTION_HISTORY_PKG package body is a server-side PL/SQL component within the Oracle Receivables (AR) module of Oracle E-Business Suite. Its principal business function is to manage the persistence and retrieval of transaction history records stored in the AR_TRANSACTION_HISTORY table. Transaction history in Receivables records the movement and disposition of customer transactions — invoices, credit memos, debit memos, chargebacks, and adjustments — across their lifecycle, supporting audit, reporting, and inquiry functionality for collections and customer account analysis. The package encapsulates the standard CRUD (create, update, delete) and concurrency-control operations required to maintain these history records consistently, ensuring that row-level locking and multi-user access are handled correctly according to Oracle Applications conventions. It is a VALID object owned by the APPS schema, and it is referenced by eight other database objects, indicating that it acts as a shared utility layer rather than an end-user-facing program. It is not itself referenced by the standard Oracle ETRM API registry as a public interface; its API classification is listed as OTHER.

Key Procedures and Functions

The package exposes fifteen documented procedures and functions, organized into several functional families:

• SET_TO_DUMMY — Establishes a default or placeholder state, typically used during initialization or when a caller requires a no-op assignment.
• INSERT_P, UPDATE_P, DELETE_P — The core data manipulation procedures responsible for inserting new transaction history rows, updating existing ones, and deleting rows respectively.
• LOCK_P, LOCK_FETCH_P, NOWAITLOCK_P, NOWAITLOCK_FETCH_P, FETCH_P — Concurrency and retrieval procedures. The LOCK variants acquire row-level locks; the NOWAITLOCK variants attempt the lock without waiting, returning immediately if the row is busy; the FETCH variants retrieve rows, optionally combined with locking. These support the standard Oracle Forms locking model.
• Lock/Fetch by TRX_ID family — FETCH_F_TRX_ID, LOCK_F_TRX_ID, NOWAITLOCK_F_TRX_ID, LOCK_FETCH_F_TRX_ID, NOWAITLOCK_FETCH_F_TRX_ID — parallel operations keyed on the transaction identifier, enabling targeted access to a specific transaction's history.

Parameter signatures are not published in the available metadata and should be confirmed against the database source before direct invocation.

Tables Accessed

The package operates against the following documented objects:

• AR_TRANSACTION_HISTORY — the primary table holding transaction history rows; the target of INSERT, UPDATE, DELETE, LOCK, and FETCH operations.
• AR_TRANSACTION_HISTORY_S — the sequence used to generate unique primary keys for new history records.
• RA_CUSTOMER_TRX — the customer transaction header table; referenced to validate or join transaction context.
• AR_SYSTEM_PARAMETERS — Receivables system options, consulted for operating-unit or defaulting behavior.
• DUAL — used for single-row evaluations and sequence/function calls.

The package also depends on ARP_GLOBAL, ARP_STANDARD, and FND_PROFILE, reflecting shared Receivables and Oracle Application Object Library utilities.

Usage Notes

Given the presence of Forms-oriented LOCK/FETCH/INSERT/UPDATE/DELETE procedures, this package is most commonly invoked from Oracle Forms-based Receivables windows that display and maintain transaction history — for example, Collections or Account Details inquiries. Because the metadata records that it is referenced by eight other database objects, it also functions as a reusable service layer called by other PL/SQL packages, concurrent programs, or workflow activities that must record transaction history changes as a side effect of their own processing. Customizations should avoid direct DML against AR_TRANSACTION_HISTORY and instead route changes through this package so that locking, key generation from the sequence, and system-parameter defaults remain consistent. As with all APPS schema objects, the package executes with definer's rights and its dependencies should be verified after any patch or upgrade, particularly across the 12.1.1 to 12.2.2 release boundary.