Results for “reason_type_display”

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

Overview

MTL_TRANSACTION_REASONS is the master reference table that stores the valid transaction reason codes used throughout Oracle E-Business Suite Inventory and its adjacent supply chain modules. Owned by the INV schema, the table provides the controlled vocabulary that qualifies why a material or cost transaction occurred — for example, a cycle count adjustment, a scrap write-off, a receipt rejection, or a manual subinventory transfer. It is referenced by the transaction, receipt, work-in-process, and warehouse management tables that record the actual movement events, making it a shared lookup that drives both data entry validation and downstream reporting and analysis.

In Data Vault modeling terms, the mined foreign key structure suggests this object is a hub-leaning entity: it holds the stable business concept of a reason and is referenced (not referencing) by a broad set of transactional satellites and links. The single attribute-driven design and its role as a join target for many downstream fact tables support this classification as a modeling suggestion rather than a prescriptive rule.

Key Information Stored

• REASON_ID — The surrogate primary key defined by MTL_TRANSACTION_REASONS_PK and reinforced by the unique index MTL_TRANSACTION_REASONS_U1. Every dependent transaction table joins back on this single numeric column.
• REASON_NAME — The user-visible reason description shown in transaction windows, reports, and list-of-values. This is the principal business-key candidate alongside the surrogate key.
• DESCRIPTION — Free-text elaboration of the reason's intended use.
• DISABLE_DATE — Timestamp governing whether the reason remains active and selectable; a populated value prevents new transactions from using the code.
• REASON_TYPE and REASON_TYPE_DISPLAY — Categorize the reason by functional grouping, enabling filtering of valid reasons by transaction context.
• REASON_CONTEXT_CODE — Further qualifies the reason's applicability to a given transaction class.
• WORKFLOW_NAME, WORKFLOW_DISPLAY_NAME, WORKFLOW_PROCESS, WORKFLOW_DISPLAY_PROCESS — Support workflow integration, allowing reason entry to trigger approvals or routing.
• ATTRIBUTE_CATEGORY and ATTRIBUTE1–ATTRIBUTE15 — The standard Oracle EBS descriptive flexfield columns for capturing client-specific reason attributes.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, LAST_UPDATE_LOGIN — Standard WHO audit columns tracking who created and last modified each row.

Common Use Cases and Queries

Reasons are captured on virtually every inventory-affecting event, so reporting commonly aggregates transaction activity by reason to explain variances, scrap rates, or adjustment patterns. A typical cycle count analysis joins MTL_CYCLE_COUNT_ENTRIES to this table:

• SELECT r.REASON_NAME, c.TRANSACTION_REASON_ID, COUNT(*) FROM MTL_CYCLE_COUNT_ENTRIES c, MTL_TRANSACTION_REASONS r WHERE c.TRANSACTION_REASON_ID = r.REASON_ID GROUP BY r.REASON_NAME, c.TRANSACTION_REASON_ID;
• Validating active reasons: SELECT REASON_ID, REASON_NAME FROM MTL_TRANSACTION_REASONS WHERE DISABLE_DATE IS NULL ORDER BY REASON_NAME;
• Auditing material movement by reason: join MTL_MATERIAL_TRANSACTIONS on REASON_ID to attribute scrap, issue, or transfer volumes to specific causes.

Related Objects

• MTL_MATERIAL_TRANSACTIONS.REASON_ID — The core inventory transaction table; the most frequently joined dependent object.
• MTL_TXN_REQUEST_LINES.REASON_ID — Move order lines carrying the reason for the movement.
• MTL_CYCLE_COUNT_ENTRIES.TRANSACTION_REASON_ID — Cycle count adjustments justified by reason.
• MTL_MATERIAL_STATUS_HISTORY.UPDATE_REASON_ID — Status-change audit trail with reason attribution.
• RCV_TRANSACTIONS / RCV_SHIPMENT_LINES.REASON_ID — Receiving transactions and shipment lines recording receipt and rejection reasons.
• WIP_TRANSACTIONS / WIP_MOVE_TRANSACTIONS.REASON_ID — Work-in-process issue, completion, and move transactions.
• CST_WRITE_OFFS.REASON_ID — Cost write-off entries referencing the reason.
• WMS_EXCEPTIONS / WMS_SKIP_TASK_EXCEPTIONS.REASON_ID — Warehouse management exception records.

Because more than twenty downstream tables reference REASON_ID, changes to reason codes must be managed carefully; disabling rather than deleting reasons preserves historical referential integrity across all dependent transaction records.