Search Results ap_chrg_allocations_all




Overview
Explore in AI Chat

Overview

AP_CHRG_ALLOCATIONS_ALL is a table in the AP (Payables) schema of Oracle E-Business Suite, documented as VALID in both release 12.1.1 and 12.2.2. Despite its continued physical presence and valid status, Oracle's own ETRM (E-Business Suite Technical Reference Manual) metadata explicitly describes the object with the note "No longer used." This is a significant qualification: the table is a legacy artifact retained in the schema for backward compatibility, historical data preservation, and referential integrity, but it is no longer populated or referenced as part of the standard Payables charge allocation processing flow in current release code.

Historically, the table supported the allocation of charges (such as freight, tax, or miscellaneous charges) across individual invoice line distributions. Each row represented a link between a charge distribution and an item distribution, capturing how a given charge amount was apportioned. In the context of Oracle's charge allocation and landed cost logic, this object served as the association mechanism tying charge-related accounting entries to their underlying item lines. Because the feature is documented as no longer used, consulting the table for current transactional reporting will generally yield stale or empty results, and any integration or custom code that still references it should be treated as a modernization candidate.

Using Data Vault modeling heuristics mined from the foreign-key structure, this object is classified as standalone. In Data Vault terms this suggests a design in which the table behaves as its own independent structure rather than participating in a hub-and-satellite chain through shared business keys. This classification is a modeling suggestion only and should not be read as an authoritative architectural statement by Oracle.

Key Information Stored

The table contains 15 documented columns in the 12.2.2 physical schema. The most important are:

The combination of CHARGE_DIST_ID and ITEM_DIST_ID forms the second documented business-key candidate, enforced by unique index AP_CHRG_ALLOCATIONS_U2. This pair is the natural (business) key expressing the allocation relationship, while CHARGE_ALLOCATION_ID is the technical surrogate. Standard Who columns are also present: LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN, CREATION_DATE, CREATED_BY, PROGRAM_ID, PROGRAM_APPLICATION_ID, REQUEST_ID, and PROGRAM_UPDATE_DATE. These support auditability and concurrent-program traceability.

Common Use Cases and Queries

Because the table is documented as no longer used, current use cases center on historical analysis, data migration, and cleanup rather than active reporting. Typical patterns include:

  • Determining whether the table holds residual rows in a given instance, which indicates prior use of charge allocation that may require archival.
  • Reconciling legacy charge apportionment against charge and item distributions during upgrade or migration efforts.
  • Identifying orphaned or superseded records before decommissioning custom extensions.

Representative query for residual data:

SELECT charge_allocation_id,
       charge_dist_id,
       item_dist_id,
       allocated_amount,
       allocated_base_amount,
       org_id
  FROM ap.ap_chrg_allocations_all
 WHERE org_id = :p_org_id;

For migration checks, join to the distribution tables using CHARGE_DIST_ID and ITEM_DIST_ID to determine whether the referenced distributions still exist and whether the allocation remains meaningful.

Related Objects

The documented foreign-key relationship shows that AP_CHRG_ALLOCATIONS_ALL_EFC references this table via CHARGE_ALLOCATION_ID, pointing to the primary key. The _EFC suffixed object is the "elections for configuration" / multi-org-enabled counterpart maintained for operating-unit security, and it is the most direct dependent of this table in the provided metadata. Beyond that, the natural join paths implied by the business keys are to the charge distribution and item distribution tables in the Payables invoice distribution model (commonly AP_INVOICE_DISTRIBUTIONS_ALL, keyed by DISTRIBUTION_ID), because CHARGE_DIST_ID and ITEM_DIST_ID reference those distribution rows. Any reporting or migration script should treat AP_CHRG_ALLOCATIONS_ALL as a standalone legacy object and validate its contents against the current Payables distributions before relying on it.