Search Results cst_accounting_packages




Overview
Explore in AI Chat

Overview

CST_ACCOUNTING_PACKAGES is an Oracle EBS reference table owned by the BOM (Bills of Material) schema. It stores metadata about the PL/SQL packages that are invoked during the periodic cost distribution process. Rather than holding transactional costing data itself, the table acts as a registry: each row identifies a user-defined or seeded accounting package, associates it with a cost method, and provides a descriptive label. Oracle Cost Management and the periodic distribution programs consult this registry to determine which accounting logic should be executed for a given cost method.

The table is classified under ETRM's heuristic Data Vault analysis as hub-leaning. As a modeling suggestion, this means ACCOUNTING_PACKAGE_ID behaves as a durable business key that anchors relationships — most notably the reference from CST_ACCT_LIB_PACKAGES — rather than acting as a pure satellite of descriptive attributes. The presence of the ZD_EDITION_NAME column and a unique index that includes it confirms the object is edition-enabled, consistent with the 12.2.2 multi-tenant, online-patching architecture.

Key Information Stored

The table contains 14 documented columns. The most significant are:

The distinction between the surrogate key (ACCOUNTING_PACKAGE_ID) and the business-key candidate (ACCOUNTING_PACKAGE_ID + ZD_EDITION_NAME) matters when writing queries: joins should generally use the surrogate key, while uniqueness validation must account for the edition.

Common Use Cases and Queries

Typical scenarios include auditing which accounting package is mapped to a cost method, tracing customized costing logic during month-end distribution, and validating package registration after patches or clones.

  • Listing active package assignments by cost method: 
    SELECT accounting_package_id, package_name, cost_method_id, description
FROM   bom.cst_accounting_packages
WHERE  zd_edition_name = 'SET1';
  • Joining to the calling library table to confirm which library packages reference a given accounting package: 
    SELECT p.package_name, l.*
FROM   bom.cst_accounting_packages p,
       bom.cst_acct_lib_packages l
WHERE  p.accounting_package_id = l.accounting_package_id;
  • Auditing change history by concurrent program: 
    SELECT accounting_package_id, package_name, last_update_date,
       last_updated_by, program_id, request_id
FROM   bom.cst_accounting_packages
ORDER BY last_update_date DESC;
  • Reporting use case: producing a setup workbook that maps cost method, package name, and description for implementation review or SOX documentation.

Related Objects

The most significant dependent object is the accounting library table, which references this registry by foreign key:

  • CST_ACCT_LIB_PACKAGES — References CST_ACCOUNTING_PACKAGES via CST_ACCT_LIB_PACKAGES.ACCOUNTING_PACKAGE_ID. This table records the library-level packages that call the accounting packages registered here and is the primary consumer of this registry.
  • CST_COST_METHODS / cost method reference data — COST_METHOD_ID links each package row to the cost method for which it applies.
  • CST_ACCOUNTING_PACKAGES_PK / CST_ACCOUNTING_PACKAGES_U1 — The primary key and edition-aware unique index that enforce row identity and business-key uniqueness.
  • Periodic distribution concurrent programs — Cost Management programs that resolve PACKAGE_NAME and dynamically execute the identified PL/SQL package during distribution.

Because the table is small and reference-oriented, it is safe to query directly in reporting views, but any direct DML should be avoided in favor of the supported Cost Management setup forms.