Search Results print_fcn_label2

Overview

ARP_AUTO_ACCOUNTING_BR is a Receivables (AR) business rule (BR) package whose body is owned by the APPS schema. Its principal business function is to perform automatic accounting for AutoAccounting distributions on Receivables transactions, including credit memos. AutoAccounting derives the individual accounting flexfield segments for a Receivables distribution line by resolving each segment against its configured sources in the RA_ACCOUNT_DEFAULTS / RA_ACCOUNT_DEFAULT_SEGMENTS setup, rather than requiring a user to key a complete account. This package encapsulates that derivation logic and returns account combinations used to populate the GL distribution, referred to internally as the CCID (code combination identifier) held on the distribution tables.

The package declares a substantial set of package-level globals inherited from shared infrastructure: the debug logging flag sourced from the AFLOG_ENABLED profile, a linefeed constant (CRLF), YES/NO flags, message-level constants, and cache size limits for cursor, CCID, and segment caching (20, 1000, and 1000 respectively). Together with the system, profile, and accounting flexfield record types taken from arp_trx_global and the AutoAccounting system record ae_sys_rec_type, these globals are passed as arguments across the majority of the package routines, indicating a design that caches accounting metadata for performance across repeated calls within a single transaction-processing session.

Key Procedures and Functions

• INIT — Initialization routine that establishes the package state used by the remaining routines, including the shared system, profile, and flexfield information structures and associated caches.
• DO_AUTOACCOUNTING — The primary driver procedure. It performs the AutoAccounting derivation for a Receivables distribution, resolving the accounting flexfield segments and producing the resulting account combination.
• QUERY_AUTOACC_DEF — Queries the AutoAccounting definitions, returning the configured segment sources that govern how each accounting flexfield segment should be derived for a given transaction setup.
• SEARCH_GLCC_FOR_CCID — Searches GL_CODE_COMBINATIONS to locate or validate the code combination identifier corresponding to the derived account segments.
• TEST_BUILD_SQL — Builds test or diagnostic SQL used during development and debugging of the AutoAccounting logic. As the name implies, this is a utility routine rather than a runtime accounting path.

The package also carries an ETRM classification of OTHER. Its header comment identifies it as "$Header: ARTEAABB.pls 120.9 2005/11/14".

Tables Accessed

• RA_ACCOUNT_DEFAULTS, RA_ACCOUNT_DEFAULT_SEGMENTS — The AutoAccounting setup tables that define, per transaction type and segment, the source from which each accounting flexfield segment is derived.
• RA_CUST_TRX_TYPES — Transaction type definitions used to identify the applicable AutoAccounting rule set.
• RA_CUST_TRX_LINE_GL_DIST, AR_DISTRIBUTIONS — The Receivables distribution tables that receive the derived account (CCID) for each transaction line.
• GL_CODE_COMBINATIONS — The chart of accounts combinations against which derived segments are matched or validated to obtain a CCID.
• AR_RECEIPT_METHOD_ACCOUNTS — Receipt method account setup referenced during account derivation.
• HZ_CUST_SITE_USES — Customer site use information consulted for segment sources that depend on the customer or site context.
• DBMS_SQL, PLITBLM — Dynamic SQL and PL/SQL table utilities used to build and execute the generated accounting SQL at runtime.

Usage Notes

The package is invoked as an internal business rule during Receivables transaction processing — in particular when transaction distributions require AutoAccounting — rather than being exposed directly to end users. It is referenced by one other package, which calls into these routines to obtain derived account combinations. Because the package relies on dynamically constructed SQL (through DBMS_SQL) and caches CCIDs and segment values, it is not intended for ad hoc direct invocation; custom code should call the supported AutoAccounting APIs instead. In Oracle EBS 12.1.1 and 12.2.2 the body resides in the APPS schema under the AR product, and diagnostic use of the test and query routines is limited to development and troubleshooting scenarios.