Search Results default_activity_info

Overview

AR_CM_APP_LIB_PVT is a private PL/SQL library package in the Oracle Receivables (AR) module whose name reflects its role as a supporting utility for Cash Management application processing (CM) and receivable application logic (APP_LIB). It is classified as a PVT package, meaning its procedures are intended for internal consumption by other Receivables APIs and concurrent programs rather than as a public, customer-callable interface. The package encapsulates reusable defaulting and derivation logic — resolving a transaction identifier from a user-supplied transaction number, supplying GL date defaults, and resolving application and unapplied activity identifiers — that other AR application routines invoke consistently. The source header indicates the package was shipped alongside ARXCMALB.pls, confirming its association with Oracle Receivables cash management and application processing components. Its debug tracing conventions (guarded by the FND_PROFILE 'AFLOG_ENABLED' setting and written through arp_util.debug) follow standard Oracle EBS PL/SQL instrumentation practices.

Key Procedures and Functions

The ETRM 12.2.2 metadata documents four procedures within the package body:

• DEFAULT_CUSTOMER_TRX_ID — Resolves a customer transaction identifier. Based on the excerpted source, this procedure accepts an in/out transaction ID together with a transaction number, and an out return status. When the transaction ID is null and a transaction number is supplied, it queries RA_CUSTOMER_TRX to derive the corresponding ID, raising the AR message AR_RAPI_TRX_NUM_INVALID via FND_MSG_PUB if no match is found. When the transaction ID is already populated but a number is also supplied, it issues an informational message (AR_RAPI_TRX_NUM_IGN) indicating the entered transaction number was ignored.
• DEFAULT_ACTIVITY_INFO — Populates default activity-related attributes used during application processing, consistent with the package's broader defaulting responsibility.
• DERIVE_ACTIVITY_UNAPP_IDS — Derives identifiers for unapplied activity records, supporting the linkage between applied receipts and unapplied cash.
• DEFAULT_UNAPP_ACTIVITY_INFO — Supplies default unapplied activity information. This is the procedure most often associated with the search term "default_unapp_activity_info"; it is not exposed as a public API but is referenced internally by dependent packages to initialize unapplied activity context before application processing.

Tables Accessed

The package operates against three documented base tables, reached through APPS synonyms:

• RA_CUSTOMER_TRX — The transaction header table, accessed by DEFAULT_CUSTOMER_TRX_ID to resolve a transaction number into a customer_trx_id.
• AR_PAYMENT_SCHEDULES — The receivables payment schedule table, used during activity and unapplied identification to establish the receivable balance context for application.
• AR_RECEIVABLE_APPLICATIONS — The application table recording where receipts are applied, used by the derive/default activity routines to determine existing applied and unapplied amounts.

Usage Notes

AR_CM_APP_LIB_PVT is not intended for direct invocation from forms, concurrent programs, or custom code. The metadata documents it as referenced by one other package, confirming it operates as a shared internal library within the Receivables application stack. Custom integrators performing receivable or cash application operations should call the supported public APIs (such as the Receivables application APIs) rather than these private helpers, which may change across patches. Debug output is controlled by the AFLOG_ENABLED profile option, allowing DBAs and support analysts to trace execution of the defaulting logic during diagnostics without code modification.