Results for “substitute_ccid”

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

Overview

ARP_ALLOCATION_PKG is the Receivables allocation engine responsible for distributing transaction amounts, tax, freight, and revenue across the appropriate accounting distributions and receivable application records. Within Oracle E-Business Suite 12.1.1 and 12.2.2, the package body executes the core logic that splits a receivable or adjustment amount into its component General Ledger distributions, allocating those amounts to the correct accounting flexfield combinations derived from AutoAccounting rules, legal entity context, and tax determination results. It is a foundational component of the AutoAccounting and tax calculation flow in Oracle Receivables, invoked whenever distributions must be generated, reallocated, or corrected during transaction entry, adjustment processing, or revenue recognition. The package is classified as OTHER in the ETRM registry, indicating it is an internal supporting API rather than a published PL/SQL interface for external integration, though its procedures may legitimately be called from custom code in controlled circumstances. The user search term "ar_distribution_split_s" corresponds to one of the documented sequence and table dependencies of this package, reflecting its role in managing distribution split identifiers used to track how a single distribution line proliferates into multiple accounting entries.

Key Procedures and Functions

The package exposes five documented procedures and functions:

• ALLOCATE_TAX — Allocates tax amounts across distributions and application records, using tax determination rules and the ZX tax engine results to place tax into the correct accounting distributions.
• RETAIN_NEG_IND — Determines and preserves the sign (positive or negative) indicator during allocation, ensuring credit and debit allocations retain their intended polarity through the split and distribution process.
• GET_TAX_COUNT — Returns a count of tax-related allocation records, used internally to drive iterative allocation logic and to validate that tax lines have been fully processed.
• SET_ADJ_CCID — Establishes the accounting flexfield combination identifier (CCID) for an adjustment, mapping the adjustment to its correct GL account.
• SUBSTITUTE_CCID — Replaces or substitutes a distribution's code combination identifier, used when AutoAccounting or manual overrides require a distribution to point to a different account.

These routines collectively handle tax placement, sign handling, distribution counting, and account substitution — the essential mechanics of splitting a receivable amount into its accounting components.

Tables Accessed

The package reads and writes a broad set of Receivables and General Ledger interface tables. It writes to AR_DISTRIBUTIONS through the AR_DISTRIBUTIONS_S sequence to persist accounting distributions, and uses AR_DISTRIBUTION_SPLIT_S to manage the split identifiers that relate originating distributions to their derived entries. It accesses AR_ADJUSTMENTS when processing adjustment CCIDs, AR_RECEIVABLE_APPLICATIONS and AR_PAYMENT_SCHEDULES to align allocations with application and schedule records, and RA_CUSTOMER_TRX, RA_CUSTOMER_TRX_LINES, and RA_CUST_TRX_LINE_GL_DIST for transaction and line-level distribution context. Tax handling draws on AR_VAT_TAX and ZX_SCO_RATES, while global temporary tables AR_AE_ALLOC_REC_GT, AR_BASE_DIST_AMTS_GT, and AR_LINE_APP_DETAIL_GT provide transient staging for allocation records and distribution amounts. System configuration is read from AR_SYSTEM_PARAMETERS and AR_SYSTEM_PARAMETERS_ALL, and legal entity mapping is supported through ARP_LEGAL_ENTITY_UTIL and GL_SETS_OF_BOOKS.

Usage Notes

ARP_ALLOCATION_PKG is invoked internally by Oracle Receivables forms and concurrent programs during transaction entry, adjustment creation, tax calculation, and revenue adjustment processing. It is referenced by six other packages documented in the ETRM registry, confirming its role as a shared internal utility within the AR module. Custom code should exercise caution: because it is classified as OTHER rather than a public API, its procedures are not guaranteed as a stable interface across patch levels. Developers who require allocation behavior in custom extensions should generally call the higher-level public APIs such as AR_RECEIVABLE_APPLICATIONS_API or the revenue adjustment public interfaces, which in turn invoke ARP_ALLOCATION_PKG internally. Direct invocation is appropriate only when replicating standard AR distribution logic in a controlled extension, and should be accompanied by explicit handling of the distribution split identifiers to keep AR_DISTRIBUTIONS and AR_DISTRIBUTION_SPLIT_S consistent.