Search Results fetch_p

Overview

ARP_RECEIVABLES_TRX_PKG is a small, single-purpose PL/SQL package body owned by the APPS schema in Oracle E-Business Suite Release 12.1.1 and 12.2.2. Its role within the Oracle Receivables (AR) module is to provide a controlled, code-isolated mechanism for retrieving a complete row from the AR_RECEIVABLES_TRX table, which stores the definition of receivables transaction types used to classify and drive accounting for customer-facing transactions such as invoices, credit memos, debit memos, chargebacks, and deposits. By encapsulating the retrieval logic in a package, the Receivables application developers establish a reusable, maintainable access point that can be called from forms, concurrent programs, and other PL/SQL units without duplicating SELECT statements against the transaction type table. The package is classified in the ETRM metadata as an API of type OTHER, indicating that it is not a formal public business API such as the Receivables application programming interfaces supporting customer or transaction creation, but rather an internal utility routine exposed for internal application use.

Key Procedures and Functions

The documented package metadata lists exactly one procedure: FETCH_P. The name follows the widespread Oracle EBS naming convention in which a procedure prefixed with fetch performs a single-row lookup and returns the result to the caller. FETCH_P accepts an input identifier for a receivables transaction type and returns the corresponding row from the AR_RECEIVABLES_TRX table. The returned data is provided through an OUT parameter declared as a row type based on the table, allowing the caller to reference individual columns by name. Because the procedure is implemented as a straightforward primary-key lookup, its contract is limited and predictable: given a valid transaction type identifier, it returns the full record; callers are responsible for supplying a valid key and for handling the NO_DATA_FOUND or TOO_MANY_ROWS exceptions that a SELECT INTO can raise. The package contains no other documented procedures or functions, and ETRM records show that no other packages reference it, confirming its narrow internal scope.

Tables Accessed

The package accesses a single table, AR_RECEIVABLES_TRX, through its APPS synonym. AR_RECEIVABLES_TRX is the Receivables transaction type definition table. Each row defines a transaction type by name, class, and related accounting attributes, and the FETCH_P procedure retrieves such a row by its receivables_trx_id primary key. The package performs read-only access only; no INSERT, UPDATE, or DELETE operations are documented, consistent with an API classification of OTHER and with the read-oriented purpose implied by the FETCH_P name. Because the lookup is by primary key, the procedure depends on the table's unique index and returns at most one row.

Usage Notes

FETCH_P is typically invoked when a Receivables form, concurrent program, or custom PL/SQL routine needs the full definition of a transaction type after it has obtained the corresponding receivables_trx_id, for example from a lookup list, a foreign key column on another table, or a user selection in a form block. Callers pass the identifier and receive a record matching the AR_RECEIVABLES_TRX row structure. Because the procedure does not internally convert exceptions into return status values, invoking code must include its own exception handling for NO_DATA_FOUND and TOO_MANY_ROWS. Debug tracing is available through the FND_PROFILE option AFLOG_ENABLED; when logging is enabled, the procedure emits entry, exit, and exception messages via ARP_STANDARD.DEBUG, which is useful for diagnosing failures in custom integrations. As an internal utility rather than a public API, FETCH_P should be treated as subject to change across patches and releases, and direct SQL against AR_RECEIVABLES_TRX remains a viable alternative where the additional dependency is undesirable.