Search Results ap_chrg_allocations_u1

Overview

AP.AP_CHRG_ALLOCATIONS_ALL is an Oracle Payables table that links charges of type Miscellaneous, Freight, or Tax to the specific invoice distributions they apply to. A single charge may be allocated across multiple invoice distributions, and the ALLOCATED_AMOUNT column dictates the portion of the charge applicable to each distribution. The table enforces a directional allocation model: tax distributions can be allocated across FREIGHT, ITEM, or MISCELLANEOUS distributions, while freight or miscellaneous distributions can be allocated only across ITEM distributions.

The object resides in the AP schema, is registered under FND Design Data SQLAP.AP_CHRG_ALLOCATIONS_ALL, and is stored in the APPS_TS_TX_DATA tablespace with PCT Free 10. All fifteen documented columns carry the comment "No Longer Used," indicating the table is retained for backward compatibility and historical data rather than active transactional processing in Oracle EBS 12.1.1 and 12.2.2. From a Data Vault modeling perspective, the metadata heuristically classifies this object as standalone, which suggests modeling it as a hub if it is reproduced in an analytical warehouse, keyed on the surrogate identifier CHARGE_ALLOCATION_ID.

Key Information Stored

The table's physical structure centers on three surrogate identifiers and two amount columns:

• CHARGE_ALLOCATION_ID — Number(15); the surrogate primary key. It is enforced by unique index AP_CHRG_ALLOCATIONS_U1 and forms the basis of the primary key constraint AP_CHRG_ALLOCATIONS_ALL_PK. This is the stable identifier for a single allocation row.
• CHARGE_DIST_ID — Number(15); identifies the charge-side distribution (Tax, Freight, or Miscellaneous) being allocated. Together with ITEM_DIST_ID it forms business-key candidate AP_CHRG_ALLOCATIONS_U2, the unique index AP_CHRG_ALLOCATIONS_U2 (CHARGE_DIST_ID, ITEM_DIST_ID).
• ITEM_DIST_ID — Number(15); identifies the target ITEM-type distribution receiving the allocated portion. Also indexed individually by nonunique index AP_CHRG_ALLOCATIONS_N1.
• ALLOCATED_AMOUNT — Number; the entered amount of the charge attributed to the target distribution.
• ALLOCATED_BASE_AMOUNT — Number; the same amount converted to the ledger functional (base) currency.
• ORG_ID — Number(15); the operating unit owning the allocation row, supporting Multi-Org filtering.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN, CREATION_DATE, CREATED_BY, PROGRAM_ID, PROGRAM_APPLICATION_ID, REQUEST_ID, PROGRAM_UPDATE_DATE — standard Who and audit columns recording creation and last modification context, including the concurrent program and request that touched the row.

Common Use Cases and Queries

Practical access to this table is primarily investigative and historical: tracing how a freight, tax, or miscellaneous charge was apportioned, and confirming the relationship between a charge distribution and its item distributions. Keyset pagination using CHARGE_ALLOCATION_ID or the composite business key is the recommended pattern given the two unique indexes.

• Find all allocations for one charge distribution: SELECT charge_allocation_id, item_dist_id, allocated_amount, allocated_base_amount FROM ap.ap_chrg_allocations_all WHERE charge_dist_id = :p_charge_dist_id;
• Retrieve a single allocation by its business key: SELECT allocated_amount, allocated_base_amount FROM ap.ap_chrg_allocations_all WHERE charge_dist_id = :p_charge_dist_id AND item_dist_id = :p_item_dist_id;
• Aggregate allocated amount for a target distribution: SELECT item_dist_id, SUM(allocated_amount) FROM ap.ap_chrg_allocations_all WHERE item_dist_id IN (...) GROUP BY item_dist_id;
• Operating-unit-scoped reporting by joining on ORG_ID, and period reconciliation by filtering on CREATION_DATE or LAST_UPDATE_DATE.

Because the columns are documented as no longer used, reports should treat the table as a compatibility surface and rely on current invoice distribution structures for new analysis.

Related Objects

The documented foreign-key relationship is with AP_CHRG_ALLOCATIONS_ALL_EFC, whose CHARGE_ALLOCATION_ID references the primary key of this table; in Oracle EBS this companion table supports multi-organization security for the underlying records. Additional objects that interact with this data in the standard Payables model include:

• AP.AP_CHRG_ALLOCATIONS_ALL_EFC — join on CHARGE_ALLOCATION_ID for Multi-Org secured access.
• AP.AP_INVOICE_DISTRIBUTIONS_ALL — the source of CHARGE_DIST_ID and ITEM_DIST_ID values, joined via DISTRIBUTION_ID.
• AP.AP_INVOICES_ALL — header context for the distributions involved, joined through AP_INVOICE_DISTRIBUTIONS_ALL.INVOICE_ID.
• AP.AP_INVOICE_LINES_ALL — line-level attributes of Tax, Freight, and Miscellaneous lines referenced by the charge distributions.
• AP.AP_CHRG_ALLOCATIONS_ALL_PK — the primary key constraint on CHARGE_ALLOCATION_ID; AP_CHRG_ALLOCATIONS_U1, AP_CHRG_ALLOCATIONS_U2, and AP_CHRG_ALLOCATIONS_N1 are the supporting unique and nonunique indexes.