Results for “mtl_cogs_recognition_temp_u1”

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

Overview

INV.MTL_COGS_RECOGNITION_TEMP is a global temporary table within the Oracle E-Business Suite Inventory (INV) schema, documented as VALID across both 12.1.1 and 12.2.2 reference models. Its purpose is to stage the COGS (Cost of Goods Sold) recognition details generated by the inventory transaction costing and period-close processes, so that cost lines can be recognized, deferred, or adjusted according to the configured COGS recognition percentage before being pushed to the General Ledger.

The table is session-scoped. As a global temporary table with a data duration of SYS$TRANSACTION, rows inserted by one session are invisible to other sessions and are automatically purged at transaction commit. This makes it a transient workspace rather than a durable subledger table, and any reporting against it must occur within the same database transaction that populated it. From a dimensional modeling perspective, the mined relationship evidence classifies this object as standalone: it functions as a work/staging satellite rather than a conformed hub or link, though its TRANSACTION_ID unique key suggests it could be treated as a candidate hub key for a transaction grain. Physical storage attributes include PCTFREE 10 and PCTUSED 40, with the single unique index MTL_COGS_RECOGNITION_TEMP_U1 on TRANSACTION_ID.

Key Information Stored

The table carries 177 documented columns, reflecting the full breadth of an inventory transaction record. The most consequential are:

• TRANSACTION_ID — surrogate primary key and the single business-key candidate, enforced by unique index MTL_COGS_RECOGNITION_TEMP_U1.
• INVENTORY_ITEM_ID, ORGANIZATION_ID, REVISION — identify the item and the inventory organization from which the cost flowed.
• TRANSACTION_TYPE_ID, TRANSACTION_ACTION_ID, TRANSACTION_SOURCE_TYPE_ID, TRANSACTION_SOURCE_NAME — classify the originating transaction and its source.
• TRANSACTION_QUANTITY, PRIMARY_QUANTITY, TRANSACTION_UOM — quantities in transaction and primary units of measure.
• TRANSACTION_DATE, ACCT_PERIOD_ID — the transaction date and the accounting period to which recognition belongs.
• ACTUAL_COST, TRANSACTION_COST, PRIOR_COST, NEW_COST, VARIANCE_AMOUNT — the costing columns that determine the amount to recognize.
• DISTRIBUTION_ACCOUNT_ID, MATERIAL_ACCOUNT, COGS_RECOGNITION_PERCENT, SO_ISSUE_ACCOUNT_TYPE — drive the accounting and percentage of cost to be recognized at issue.
• USSGL_TRANSACTION_CODE, ERROR_CODE, ERROR_EXPLANATION — support government accounting attributes and rejected line diagnostics.

Common Use Cases and Queries

The primary use case is diagnosing COGS recognition amounts during period close, particularly when a sales order issue has not fully recognized cost. A typical pattern joins the temp rows back to the permanent transaction table:

• Identify pending recognition: SELECT t.TRANSACTION_ID, t.TRANSACTION_QUANTITY, t.ACTUAL_COST, t.COGS_RECOGNITION_PERCENT FROM INV.MTL_COGS_RECOGNITION_TEMP t WHERE t.COSTED_FLAG = 'N';
• Reconcile recognized versus unrecognized cost by period: filter on ACCT_PERIOD_ID and aggregate VARIANCE_AMOUNT and TRANSACTION_COST.
• Trace recognition to a picking line or reservation using PICKING_LINE_ID and RESERVATION_ID.
• Isolate errors with WHERE ERROR_CODE IS NOT NULL to review ERROR_EXPLANATION before rerunning the Cost Manager or COGS recognition concurrent program.

Because the table is transaction-duration only, queries are normally embedded inside the concurrent program or debugging session; ad hoc reporting should target the permanent transaction and distribution tables instead.

Related Objects

The FK metadata identifies the following significant reference relationships, each joinable on the listed column:

• MTL_TXN_SOURCE_TYPES via TRANSACTION_SOURCE_TYPE_ID.
• MTL_RESERVATIONS via RESERVATION_ID.
• SO_PICKING_LINES_ALL via PICKING_LINE_ID.
• CST_COST_UPDATES via COST_UPDATE_ID, and CST_COST_TYPES via COST_TYPE_ID.
• CST_COST_GROUPS via COST_GROUP_ID.
• BOM_DEPARTMENTS via DEPARTMENT_ID, relevant to flow and repetitive manufacturing transactions.
• MTL_MOVEMENT_STATISTICS via MOVEMENT_ID, and JAI_OM_OE_RMA_LINES via RMA_LINE_ID for returns.