Search Results cst_lc_rae_events_gt




Overview
Explore in AI Chat

Overview

CST_LC_RAE_EVENTS_GT is a global temporary table owned by the BOM schema in Oracle E-Business Suite, documented as VALID in both Release 12.1.1 and 12.2.2. The name encodes its function: it stages Landed Cost (LC) Receiving Accounting Events (RAE) for downstream costing and accounting processing. In the EBS supply chain flow, when goods are received against a purchase order — particularly under landed cost arrangements where freight, duty, and other charges must be allocated to inventory — receiving accounting events must be transformed into cost adjustments and journal entries. This table serves as the transient work area where those events are collected, priced, and prepared for the Cost Management and Subledger Accounting engines.

Because it is a global temporary table, its contents are session-scoped and purged on commit or session termination according to the table's ON COMMIT definition. It is not a permanent transaction store; it is a staging structure populated and consumed within a single processing run. The documentation provides no explicit Data Vault classification, but the mined foreign-key structure — a standalone table with references outward to RCV_ACCOUNTING_EVENT_TYPES and PO_RELEASES_ALL — suggests a modeling role closer to a transient link-plus-satellite construct than a hub, since it carries descriptive measures (prices, taxes, quantities) alongside its foreign-key relationships.

Key Information Stored

The 65 documented columns describe a rich event payload. The most consequential include:

Standard audit columns (LAST_UPDATE_DATE, CREATED_BY, REQUEST_ID, PROGRAM_ID, and related) are present for concurrency and traceability.

Common Use Cases and Queries

Typical usage centers on reconciliation and diagnostics of landed cost accounting runs. A common pattern joins the staging table back to receiving and purchasing tables to trace why a landed cost adjustment produced a particular accounting entry:

  • Event reconciliation: Join ACCOUNTING_EVENT_ID to the receiving accounting events table to confirm the staged event matches its source.
  • PO release tracing: Join PO_RELEASE_ID to PO_RELEASES_ALL to resolve the release number behind a cost event.
  • Unprocessed event detection: Query rows where ACCOUNTED_FLAG = 'N' to find events captured but not yet transferred to the general ledger.
  • Tax and price validation: Compare UNIT_PRICE against PRIOR_UNIT_PRICE and reconcile NR_TAX_AMOUNT plus REC_TAX_AMOUNT against TRANSACTION_AMOUNT.
  • Cross-organization analysis: Filter on CROSS_OU_FLAG and TRANSFER_ORG_ID versus ORG_ID for intercompany landed cost postings.

Because the table is temporary, queries are meaningful only within the session that populated it; persistent reporting should target the permanent accounting and cost tables to which these rows are ultimately written.

Related Objects