Search Results mtl_actions_b




Overview
Explore in AI Chat

Overview

MTL_ACTIONS_B is a reference (lookup) table owned by the INV schema in Oracle E-Business Suite 12.1.1 and 12.2.2. It stores the definitive list of action codes used throughout Oracle Inventory to classify the type of transaction applied to material, such as receipts, issues, transfers, and adjustments. The "_B" suffix follows the Oracle Applications convention for a base (non-translated) table, indicating that this table carries the code and descriptive content that driving functionality and reporting logic depend on.

The table is documented as standalone with a single-column primary key, and the mined Data Vault classification is standalone (neither hub, link, nor satellite). From a modeling perspective, this suggests MTL_ACTIONS_B can be treated as an independent reference/lookup set rather than a participant in a dimension-to-dimension join. Because the documented metadata exposes 38 columns, the design follows Oracle's standard pattern of a compact business key surrounded by mandatory audit columns and a wide block of descriptive-flex attributes.

Key Information Stored

The primary key is enforced by MTL_ACTIONS_B_PK on ACTION_CODE, which is also the only documented unique business-key candidate. ACTION_CODE is the natural business identifier: a short coded value that consuming transactions, forms, and reports store to indicate which action occurred. DISABLE_FLAG allows individual action codes to be retired without deleting history, preserving referential integrity for legacy transactions.

The remaining structure divides into two groups. First, the standard audit columns: CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, and LAST_UPDATE_LOGIN, which record who created and last modified each lookup row. Second, the descriptive-flex region: ATTRIBUTE_CATEGORY plus ATTRIBUTE1 through ATTRIBUTE30. These 31 attributes are reserved for customer-specific or localization-specific extension without altering the seeded schema. In practice, only a small subset is used by any given implementation, which is why the table's width is disproportionate to its functional footprint.

Common Use Cases and Queries

Typical use cases include validating action codes presented in transaction entry screens, joining transaction history to obtain a readable action description, and filtering reports to exclude disabled codes. A standard lookup pattern is:

  • Retrieve active action codes: SELECT action_code FROM mtl_actions_b WHERE NVL(disable_flag,'N') = 'N';
  • Join to transaction history: SELECT t.transaction_id, t.transaction_action_id, a.action_code FROM mtl_material_transactions t, mtl_actions_b a WHERE t.transaction_action_id = a.action_code;
  • Audit recently changed lookups: SELECT action_code, last_update_date, last_updated_by FROM mtl_actions_b ORDER BY last_update_date DESC;
  • Inventory of customer extensions: SELECT action_code, attribute_category, attribute1 FROM mtl_actions_b WHERE attribute_category IS NOT NULL;

Because the row count is low, the table is inexpensive to cache or embed in lookup views. ETL and reporting layers commonly denormalize ACTION_CODE into fact tables to avoid joins at query time, while retaining the table for label resolution and drill-down.

Related Objects

MTL_ACTIONS_B functions as a parent reference for transaction-processing tables in INV. The most significant related objects and their join columns are:

These relationships confirm that MTL_ACTIONS_B is a low-volume, high-utility reference table; changes to it propagate directly into transaction semantics, so maintenance should be restricted to authorized administrators.