Search Results update_trx

Overview

ARP_EBS_AUTOINV_PREPROC is an Oracle Accounts Receivables PL/SQL package owned by the APPS schema. Its name reflects its role within the eBusiness Suite (EBS) AutoInvoice interface pipeline: it performs preprocessing work on transactional data staged in the RA_INTERFACE tables before the standard AutoInvoice validation and import programs execute. The package is declared with AUTHID CURRENT_USER, meaning that its SQL statements execute with the privileges of the invoking user rather than the definer, which is significant in a shared APPS environment where interface tables and their APPS synonyms must be accessible to the calling session.

The package dates to an early release of the AutoInvoice codebase; its header comment identifies the source file as AREBSPPS.pls, a predecessor naming convention to the modern ARP_ prefix used across Oracle Receivables packages in Release 12. The package exposes a minimal, single-entry-point interface, indicating a narrowly scoped utility rather than a general-purpose framework.

Key Procedures and Functions

The ETRM metadata documents exactly one procedure within this package:

• UPDATE_TRX — The sole documented program unit. Based on its name and the package's AutoInvoice context, it updates transaction records that have been prepared in the interface staging tables, preparing them for downstream validation and import by the core AutoInvoice engine. It accepts a concurrent request identifier so that work performed can be tied to a specific submission, a functional currency code used for monetary conversion or validation, and an error code parameter passed as an IN OUT NOCOPY parameter to report processing status back to the caller. The IN OUT NOCOPY signature is notable because it allows the procedure to return an error status without the overhead of copying the value, a pattern used in high-volume batch processing within AutoInvoice.

Tables Accessed

The package reads and writes the following tables through APPS synonyms, each consistent with AutoInvoice preprocessing:

• RA_INTERFACE_LINES — The primary staging table for transaction lines awaiting import. UPDATE_TRX updates records here as part of preprocessing.
• RA_INTERFACE_LINES_GT — A global temporary table used to stage or transform interface line data during processing, avoiding permanent storage of intermediate results.
• RA_INTERFACE_DISTRIBUTIONS — Holds distribution information for interface lines; preprocessing may adjust or validate these before import.
• RA_INTERFACE_SALESCREDITS — Stores sales credit allocations associated with interface lines, which must remain consistent with the transaction header data.
• RA_INTERFACE_ERRORS — The error repository where AutoInvoice records validation failures; UPDATE_TRX may write entries here when preprocessing detects problems.
• RA_CUST_TRX_TYPES — The transaction type definition table, consulted to validate that interface records reference a valid, active transaction type.
• FND_CURRENCIES — The currency repository, used to validate the functional currency code passed to UPDATE_TRX and to support currency-related preprocessing logic.

Usage Notes

ARP_EBS_AUTOINV_PREPROC is an internal component of the AutoInvoice flow and is not exposed through a standard Oracle Forms user interface. It is invoked programmatically, typically by the AutoInvoice Master concurrent program or by another internal package within the AutoInvoice processing chain, before the main validation and import steps. Because the package is not referenced by any other documented package in the ETRM inventory, direct custom calls are uncommon and are generally not recommended.

Customizations that invoke UPDATE_TRX should do so with caution: the procedure depends on the concurrent request identifier and functional currency being correctly populated, and it signals failures through the error code OUT parameter rather than raising named exceptions. Implementations upgrading between 12.1.1 and 12.2.2 should verify that the package remains present and that any custom dependencies on its signature continue to resolve, as AutoInvoice internals have historically been subject to change across release boundaries.