Results for “cst_ae_lines”

50+ results




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

Overview

CST_AE_LINES is a transaction table owned by the BOM (Bills of Material) schema in Oracle EBS 12.1.1 and 12.2.2. Its description states that it "stores debits and credits for Periodic Distributions." In practical terms, this table holds the individual accounting entry lines produced by the cost accounting engine when overhead, resource, activity, or repetitive schedule costs are distributed to the general ledger during period-end processing. Each row represents a discrete debit or credit against a specific GL account (identified by CODE_COMBINATION_ID) for a defined amount and currency, tied back to a controlling header record in CST_AE_HEADERS.

From a dimensional modeling perspective, the metadata's heuristic Data Vault classification is link. This suggests the table functions as a connector that associates multiple business entities — headers, accounts, currencies, resources, cost elements, activities, and repetitive schedules — rather than acting as a standalone hub of uniquely identified master data. It carries foreign keys to seven parent tables, reinforcing its role as an associative record within the costing transaction model.

Key Information Stored

The surrogate primary key is AE_LINE_ID, enforced by CST_AE_LINES_PK and the unique index CST_AE_LINES_U1. The table contains 52 documented columns; the most consequential for reporting and reconciliation include:

The remaining columns include audit fields (CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN), concurrent program context (PROGRAM_APPLICATION_ID, PROGRAM_ID, REQUEST_ID), STAT_AMOUNT, USSGL_TRANSACTION_CODE, and reference columns REFERENCE1 through REFERENCE10.

Common Use Cases and Queries

Cost accountants and EBS developers use CST_AE_LINES to reconcile periodic distribution amounts before and after transfer to the GL, to investigate accounting errors, and to build custom cost reports.

  • Reconciling debits and credits by header:
SELECT ae_header_id, SUM(accounted_dr) dr, SUM(accounted_cr) cr
FROM   cst_ae_lines
GROUP  BY ae_header_id;
  • Identifying lines that failed GL transfer:
SELECT line.ae_line_id, line.gl_transfer_error_code, line.accounting_error_code
FROM   cst_ae_lines line
WHERE  line.gl_transfer_error_code IS NOT NULL;
  • Drilling from a resource into its distributed amounts: joining to BOM_RESOURCES on RESOURCE_ID to analyze overhead cost by resource.
  • Period reporting: joining audit fields and header records to summarize distribution activity by organization and accounting period.

Related Objects

The following parent tables are referenced through documented foreign keys and are essential for joining and interpreting the line data:

  • CST_AE_HEADERS via AE_HEADER_ID — the controlling header for each set of lines.
  • GL_CODE_COMBINATIONS via CODE_COMBINATION_ID — resolves the GL account structure.
  • FND_CURRENCIES via CURRENCY_CODE — validates the currency.
  • BOM_RESOURCES via RESOURCE_ID — identifies the resource driving the cost.
  • CST_COST_ELEMENTS via COST_ELEMENT_ID — classifies the cost element (e.g., material, overhead).
  • CST_ACTIVITIES via ACTIVITY_ID — identifies the cost activity.
  • WIP_REPETITIVE_SCHEDULES via REPETITIVE_SCHEDULE_ID — links to repetitive manufacturing schedules.

Additionally, GL_SL_LINK_ID provides the tie to subledger accounting entries, enabling end-to-end traceability from the cost management distribution to the final posted GL journal.