Results for “cst_write_offs”

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

Overview

CST_WRITE_OFFS is a transaction-table owned by the BOM (Bills of Material) schema within Oracle EBS 12.1.1 and 12.2.2. As its documented description states, the table "Holds Write-Off Header Information" — it stores the header-level record for inventory and receipt write-off transactions, capturing the accounting context, source transaction references, and amounts needed to post write-off entries to the General Ledger. In the cost management and inventory accounting flow, it acts as the anchor record that ties a write-off event to its originating inventory transaction, purchase order distribution, reason code, vendor, and item.

Under the heuristic Data Vault classification provided in the metadata, CST_WRITE_OFFS is best modeled as a link. This is inferred from its FK-heavy structure: it references multiple independent hubs (organizations, items, vendors, accounts, transactions) rather than carrying descriptive attributes of a single business entity. Analysts designing a warehouse or integration layer should treat it as a relationship record connecting these dimensions, with WRITE_OFF_ID as the natural per-record identifier.

Key Information Stored

The table contains 33 columns. The most operationally significant are:

• WRITE_OFF_ID — surrogate primary key, enforced by the unique index CST_WRITE_OFFS_U1; the documented business-key candidate.
• TRANSACTION_DATE — accounting/effective date of the write-off.
• ACCRUAL_ACCOUNT_ID, OFFSET_ACCOUNT_ID, ERV_ACCOUNT_ID — FK references into GL_CODE_COMBINATIONS for the accrual, offset, and exchange-rate-variance accounting entries.
• WRITE_OFF_AMOUNT, ENTERED_AMOUNT — functional and entered currency amounts of the write-off.
• CURRENCY_CODE, CURRENCY_CONVERSION_TYPE, CURRENCY_CONVERSION_RATE, CURRENCY_CONVERSION_DATE — currency and conversion context for multi-currency write-offs.
• TRANSACTION_TYPE_CODE — classifies the write-off event.
• PO_DISTRIBUTION_ID, INVOICE_DISTRIBUTION_ID, INVENTORY_TRANSACTION_ID — source document references (PO distribution, invoice distribution, and material transaction).
• REVERSAL_ID, REASON_ID — linkage to reversal records and to MTL_TRANSACTION_REASONS for the write-off cause.
• INVENTORY_ITEM_ID, VENDOR_ID, OPERATING_UNIT_ID, LEGAL_ENTITY_ID — the item, supplier, organization, and legal entity dimensions.
• DESTINATION_TYPE_CODE, WRITE_OFF_SELECT_FLAG — processing/destination descriptors.

Common Use Cases and Queries

The primary use cases involve reconciliation and audit of write-off activity. Cost accountants query the table to trace write-off amounts back to their originating inventory or PO transactions, and to confirm the GL accounts hit. A typical trace-back pattern joins the header to its source:

• Trace to source transaction: join CST_WRITE_OFFS to MTL_MATERIAL_TRANSACTIONS on INVENTORY_TRANSACTION_ID.
• Reason analysis: join to MTL_TRANSACTION_REASONS on REASON_ID to categorize write-off drivers.
• PO/invoice linkage: join to PO_DISTRIBUTIONS_ALL on PO_DISTRIBUTION_ID.
• Organization and entity reporting: join to HR_ALL_ORGANIZATION_UNITS on OPERATING_UNIT_ID and FV_LEGAL_ENTITIES on LEGAL_ENTITY_ID.
• Account validation: join the three *_ACCOUNT_ID columns to GL_CODE_COMBINATIONS to verify accrual, offset, and ERV postings.

A representative reporting query aggregates WRITE_OFF_AMOUNT by TRANSACTION_DATE, REASON_ID, and CURRENCY_CODE to produce a periodic write-off summary by reason and currency.

Related Objects

The documented foreign keys identify the most significant related objects:

• MTL_MATERIAL_TRANSACTIONS (INVENTORY_TRANSACTION_ID) — the inventory transaction driving the write-off.
• PO_DISTRIBUTIONS_ALL (PO_DISTRIBUTION_ID) — PO distribution reference.
• MTL_TRANSACTION_REASONS (REASON_ID) — standardized reason codes.
• MTL_SYSTEM_ITEMS_B (INVENTORY_ITEM_ID, OPERATING_UNIT_ID) — item/organization master.
• PO_VENDORS (VENDOR_ID) — supplier reference.
• HR_ALL_ORGANIZATION_UNITS (OPERATING_UNIT_ID) — operating unit.
• FV_LEGAL_ENTITIES (LEGAL_ENTITY_ID) — legal entity.
• GL_CODE_COMBINATIONS — referenced by ACCRUAL_ACCOUNT_ID, OFFSET_ACCOUNT_ID, and ERV_ACCOUNT_ID.

These relationships confirm the table's role as a central link record connecting inventory, purchasing, and financial accounting data.