Search Results compile_type_description

Overview

MTL_ABC_COMPILE_HEADERS_V is an APPS-owned database view in the Oracle E-Business Suite Inventory (INV) module. It presents a denormalized, reporting-friendly projection of ABC compile header records. ABC (Activity-Based Costing) compilation in Oracle Inventory is the process by which inventory items are classified into ABC rank classes according to their cumulative usage or value, typically enabling cycle count scheduling and inventory prioritization. This view exposes each compile run as a single logical record enriched with decoded lookup meanings, allowing users and downstream programs to interpret compile type, compile status, item scope, and cost code values in human-readable form without joining to lookup tables manually.

The view carries a "Retrofitted" description in the ETRM repository, indicating that it was introduced or reconciled as part of the 12.1.1 to 12.2.2 upgrade and maintenance stream. The user search term "mrp_forecast_name" is significant: the underlying MTL_ABC_COMPILE_HEADERS table includes an MRP_FORECAST_NAME column, which the view also exposes, linking ABC compilation to a named forecast when the compile scope is derived from a forecast. This makes the view relevant to both inventory costing and planning reporting.

Underlying Base Objects

The documented view metadata lists three referenced base objects, all resolved through synonyms in the APPS schema:

• MTL_ABC_COMPILE_HEADERS (SYNONYM) — the driving table, holding one row per ABC compile run with columns such as COMPILE_ID, COMPILE_NAME, ORGANIZATION_ID, COMPILE_TYPE, COMPILE_STATUS, ITEM_SCOPE_CODE, COST_CODE, MRP_PLAN_NAME, and MRP_FORECAST_NAME.
• MFG_LOOKUPS (VIEW) — the shared Oracle Manufacturing lookup view, joined four times to decode COMPILE_TYPE, COMPILE_STATUS, ITEM_SCOPE_CODE, and COST_CODE into descriptive meanings.
• CST_COST_TYPES (SYNONYM) — the costing cost type definition table, outer-joined on COST_TYPE to supply the cost type description used during compilation.

Lookups are anchored by lookup_type values MTL_ABC_COMPILE_TYPE, MTL_ABC_COMPILE_STATUS, MTL_ABC_ITEM_SCOPE, and MTL_PRIMARY_COST. The item scope join applies NVL(A.ITEM_SCOPE_CODE, 1), providing a default when no scope is set. The COST_CODE and COST_TYPE joins are outer joins, so compile records without a valid cost code or cost type still appear in the result set with null descriptions.

Key Columns

• COMPILE_ID / COMPILE_NAME — unique identifier and descriptive name of the ABC compile run.
• ORGANIZATION_ID — inventory organization in which the compile was executed.
• COMPILE_TYPE_DESCRIPTION / COMPILE_TYPE — decoded and raw compile classification.
• COMPILE_STATUS_DESCRIPTION / COMPILE_STATUS — decoded and raw status of the compile run.
• ITEM_SCOPE_DESCRIPTION / ITEM_SCOPE_CODE — decoded and raw item scope used to select items for compilation.
• SECONDARY_INVENTORY — subinventory restriction applied to the compile.
• COST_CODE_DESCRIPTION / COST_CODE and COST_TYPE_DESCRIPTION / COST_TYPE — costing basis used for value accumulation.
• MRP_PLAN_NAME / MRP_FORECAST_NAME — the MRP plan and forecast source associated with the compile, the columns most relevant to the user's search.
• SCHEDULE_TYPE / SCHEDULE_DESIGNATOR — schedule identifiers for forecast-driven compiles.
• START_DATE / CUTOFF_DATE / COMPILE_DATE — temporal boundaries of the compile window.
• CUMULATIVE_QUANTITY / CUMULATIVE_VALUE — aggregate metrics accumulated during compilation.
• ATTRIBUTE1–ATTRIBUTE15, REQUEST_ID, PROGRAM_APPLICATION_ID, PROGRAM_ID — descriptive flexfield and concurrent program context, useful for auditing and traceability.

Common Use Cases and Queries

A frequent need is listing all ABC compiles that reference a specific forecast or plan. The view makes this a single-table query because lookup decoding is already applied:

• Forecast-driven compiles: SELECT compile_id, compile_name, organization_id, mrp_forecast_name, compile_status_description FROM mtl_abc_compile_headers_v WHERE mrp_forecast_name = :forecast_name;
• Completed compiles for an organization: SELECT compile_id, compile_name, compile_date FROM mtl_abc_compile_headers_v WHERE organization_id = :org_id AND compile_status = 'COMPLETED';
• Compiles by cost basis: SELECT compile_name, cost_code_description, cost_type_description FROM mtl_abc_compile_headers_v WHERE cost_code IS NOT NULL;
• Concurrent program audit: SELECT compile_id, request_id, program_id, program_update_date FROM mtl_abc_compile_headers_v WHERE compile_date >= :start_date;

Because the underlying table stores the compile header only, detailed item-level results reside in MTL_ABC_COMPILE_ITEMS (or its equivalent detail table), and this view is best used to identify and qualify compile runs before drilling into item detail. When used in custom reports or integrations, filter on ORGANIZATION_ID and COMPILE_STATUS to bound result sets, and treat MRP_FORECAST_NAME and MRP_PLAN_NAME as optional, since both are null for compiles not driven by MRP input.