Search Results mtl_abc_compile_status

Overview

APPS.MTL_ABC_COMPILE_HEADERS_V is a reporting and integration view in Oracle E-Business Suite (validated on 12.1.1 and 12.2.2) that exposes the header records of ABC (Activity-Based Costing) compile runs performed by the Oracle Inventory ABC analysis process. The underlying table, MTL_ABC_COMPILE_HEADERS, stores one row per ABC compile, capturing the parameters selected when the compilation was launched along with run statistics and the standard concurrent request audit columns. The view enriches those raw codes with human-readable lookup meanings so that reports, Discoverer workbooks, and downstream interfaces can present descriptive values without additional joins. It is owned by APPS and is commonly referenced by users searching for the lookup type MTL_ABC_COMPILE_TYPE, which classifies each compile run by its costing basis.

Underlying Base Objects

The view is defined over a single base table, MTL_ABC_COMPILE_HEADERS (exposed through the APPS synonym), outer-joined to four referencing objects that supply descriptive text:

• MFG_LOOKUPS (view) — joined four times, aliased MFG1 through MFG4, to translate coded values into meanings. These joins supply COMPILE_TYPE_DESCRIPTION (lookup type MTL_ABC_COMPILE_TYPE), COMPILE_STATUS_DESCRIPTION (MTL_ABC_COMPILE_STATUS), ITEM_SCOPE_DESCRIPTION (MTL_ABC_ITEM_SCOPE, using NVL on ITEM_SCOPE_CODE so that a null scope defaults to code 1), and COST_CODE_DESCRIPTION (MTL_PRIMARY_COST).
• CST_COST_TYPES (synonym) — outer-joined on COST_TYPE_ID to derive COST_TYPE_DESCRIPTION from the cost type name, since the header stores only the numeric cost type identifier.

The joins to MFG_LOOKUPS for compile type, compile status, and item scope are inner joins; the joins to the primary cost lookup and to CST_COST_TYPES are outer joins. This means a header row will not appear in the view if its compile type, status, or item scope code has no matching lookup entry, but missing cost code or cost type information does not suppress the row.

Key Columns

• COMPILE_ID, COMPILE_NAME, DESCRIPTION — identity and descriptive name of the ABC compilation.
• ORGANIZATION_ID — the inventory organization against which the compilation was executed.
• COMPILE_TYPE and COMPILE_TYPE_DESCRIPTION — the coded and translated costing basis for the compile; the description is resolved through the MTL_ABC_COMPILE_TYPE lookup that drives this article's search term.
• COMPILE_STATUS and COMPILE_STATUS_DESCRIPTION — run state (for example, completed or errored), translated via MTL_ABC_COMPILE_STATUS.
• ITEM_SCOPE_CODE and ITEM_SCOPE_DESCRIPTION — the population of items included; a null scope is defaulted to code 1 before lookup.
• SECONDARY_INVENTORY — subinventory restriction applied to the compile, if any.
• COST_CODE, COST_CODE_DESCRIPTION, COST_TYPE, COST_TYPE_DESCRIPTION — cost basis and cost type context for the run, the latter resolved from CST_COST_TYPES.
• COMPILE_ITEMS, COMPILE_DATE — number of items processed and the completion timestamp.
• CUMULATIVE_QUANTITY, CUMULATIVE_VALUE — aggregated quantity and value statistics produced by the compile.
• SCHEDULE_TYPE, SCHEDULE_DESIGNATOR, MRP_PLAN_NAME, MRP_FORECAST_NAME, START_DATE, CUTOFF_DATE — planning and date-window parameters limiting the scope of the analysis.
• ATTRIBUTE_CATEGORY and ATTRIBUTE1–15 — the standard flexible attribute columns.
• REQUEST_ID, PROGRAM_APPLICATION_ID, PROGRAM_ID, PROGRAM_UPDATE_DATE, CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, ROW_ID — concurrent request and audit columns; ROW_ID exposes the base-table ROWID for direct row addressing.

Common Use Cases and Queries

The view is typically queried to review the history of ABC compilations, to feed assignment reports, and to troubleshoot runs whose descriptions would otherwise require manual lookup decoding. A representative query listing recent compiles for an organization follows:

• SELECT compile_id, compile_name, compile_type_description, compile_status_description, compile_date, compile_items FROM mtl_abc_compile_headers_v WHERE organization_id = :org_id ORDER BY compile_date DESC;
• SELECT compile_id, item_scope_description, cost_type_description, cumulative_quantity, cumulative_value FROM mtl_abc_compile_headers_v WHERE compile_status = :status AND compile_type = :type;
• Filtering on REQUEST_ID links a header back to the concurrent manager log for the ABC compile program.

Because the view performs no aggregation, each row corresponds to one compile header, making it suitable for direct use in Oracle Reports, BI Publisher data models, and custom interfaces that populate external ABC analysis repositories.