Results for “cst_ae_headers”

50+ results




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

Overview

CST_AE_HEADERS is the header table for Periodic Accounting Distributions within Oracle E-Business Suite. Owned by the BOM schema and classified under the Bills of Material product family, it stores one row per periodic accounting event generated by the Cost Management (CST) and Work in Process (WIP) accounting engines. Each header represents a logical grouping of accounting distribution lines created during a cost accounting period, prior to or subsequent to transfer to the General Ledger.

In EBS 12.1.1 and 12.2.2 the table serves as the transactional anchor for the Periodic Actual Cost (PAC) process and the accounting event model. It links material, receiving, and WIP transaction activity to a legal entity, set of books, cost group, and cost type, and consolidates the resulting debit and credit entries carried in the child table CST_AE_LINES. It also tracks the GL transfer state of each event through dedicated flag and error columns.

Under the Data Vault classification heuristic derived from the foreign key structure, this table is satellite-leaning. Its many outbound dependencies (organization, ledger, legal entity, period, cost group, cost type, and accounting event source) suggest it should be modeled as a satellite attached to one or more hubs such as accounting event, ledger, and inventory organization, with CST_AE_LINES forming a dependent child satellite.

Key Information Stored

The primary key is a surrogate identifier, AE_HEADER_ID, enforced by CST_AE_HEADERS_PK and duplicated as the unique index CST_AE_HEADERS_U1, making it the only documented business-key candidate. The most significant columns include:

Standard Who columns (CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN) and request audit columns (PROGRAM_UPDATE_DATE, PROGRAM_APPLICATION_ID, PROGRAM_ID, REQUEST_ID) support concurrency and concurrent program tracking.

Common Use Cases and Queries

Typical reporting scenarios include identifying untransferred accounting events, reconciling PAC output against GL balances, and diagnosing accounting errors. A common query pattern filters headers by period and transfer state:

  • SELECT ah.ae_header_id, ah.accounting_event_id, ah.acct_event_source_table, ah.ae_category, ah.accounting_date FROM cst_ae_headers ah WHERE ah.gl_transfer_flag = 'N' AND ah.period_id = :p_period;
  • Error diagnosis: SELECT ae_header_id, gl_transfer_error_code, accounting_error_code FROM cst_ae_headers WHERE gl_transfer_error_code IS NOT NULL;
  • Distribution detail joined to lines: SELECT ah.ae_header_id, al.ae_line_id, al.amount FROM cst_ae_headers ah, cst_ae_lines al WHERE ah.ae_header_id = al.ae_header_id;
  • Legal entity and ledger roll-ups for financial reconciliation, grouping by set_of_books_id and legal_entity_id.

Related Objects

  • CST_AE_LINES — child table joined on CST_AE_LINES.AE_HEADER_ID = CST_AE_HEADERS.AE_HEADER_ID; holds the individual debit and credit distribution lines.
  • CST_PAC_PERIODS — joined on PERIOD_ID; defines the periodic accounting period.
  • GL_SETS_OF_BOOKS_11I — joined on SET_OF_BOOKS_ID; the ledger destination.
  • MTL_PARAMETERS — joined on ORGANIZATION_ID; the inventory organization context.
  • HR_ALL_ORGANIZATION_UNITS — joined on LEGAL_ENTITY_ID; the legal entity.
  • CST_COST_GROUPS and CST_COST_TYPES — joined on COST_GROUP_ID and COST_TYPE_ID respectively.
  • MTL_MATERIAL_TRANSACTIONS, WIP_TRANSACTIONS, and RCV_TRANSACTIONS — polymorphic source tables joined on ACCOUNTING_EVENT_ID, disambiguated by ACCT_EVENT_SOURCE_TABLE.