Results for “nr_tax”

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

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:

• LCM_TRANSACTION_ID — the apparent surrogate identifier for the landed cost transaction event being staged.
• ACCOUNTING_EVENT_ID — links the staged row to the receiving accounting event; a principal business-key candidate.
• RCV_TRANSACTION_ID — the originating receiving transaction, tying the row back to inventory receipt activity.
• EVENT_TYPE_ID — foreign key to RCV_ACCOUNTING_EVENT_TYPES, classifying the accounting event.
• PO_HEADER_ID, PO_RELEASE_ID, PO_LINE_ID, PO_LINE_LOCATION_ID, PO_DISTRIBUTION_ID — the full purchasing document hierarchy; PO_RELEASE_ID is a documented foreign key to PO_RELEASES_ALL.
• INVENTORY_ITEM_ID, ORG_ID, SET_OF_BOOKS_ID — item, inventory organization, and ledger context.
• DEBIT_ACCOUNT_ID, CREDIT_ACCOUNT_ID, LCM_ACCOUNT_ID — the accounting flexfield targets for the generated entries.
• TRANSACTION_AMOUNT, UNIT_PRICE, PRIOR_UNIT_PRICE, UNIT_LANDED_COST — monetary measures, including the prior price required when a retrospective landed cost adjustment is applied.
• NR_TAX, REC_TAX, NR_TAX_AMOUNT, REC_TAX_AMOUNT — non-recoverable and recoverable tax indicators and amounts.
• CURRENCY_CODE, CURRENCY_CONVERSION_RATE, CURRENCY_CONVERSION_TYPE, CURRENCY_CONVERSION_DATE — currency conversion attributes.
• ACCOUNTED_FLAG, INVOICED_FLAG, PA_ADDITION_FLAG, CROSS_OU_FLAG — processing state indicators.
• TRX_FLOW_HEADER_ID, GL_GROUP_ID — linkage to transaction flow and general ledger grouping.

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

• RCV_ACCOUNTING_EVENT_TYPES — referenced via EVENT_TYPE_ID; defines the event classification.
• PO_RELEASES_ALL — referenced via PO_RELEASE_ID; supplies purchasing release detail.
• RCV_TRANSACTIONS — logical parent of RCV_TRANSACTION_ID; the receiving transaction source.
• PO_HEADERS_ALL, PO_LINES_ALL, PO_LINE_LOCATIONS_ALL, PO_DISTRIBUTIONS_ALL — the purchasing hierarchy referenced by the PO ID columns.
• MTL_SYSTEM_ITEMS_B — resolves INVENTORY_ITEM_ID.
• GL_LEDGERS / GL_CODE_COMBINATIONS — resolve SET_OF_BOOKS_ID and the account ID columns.
• XLA_EVENTS and the Subledger Accounting API set — downstream consumers that convert staged events into final journal entries.