Results for “item_org”

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

Overview

MRP_SC_BILL_MAKE_AT_V is an APPS-owned database view in the Oracle E-Business Suite Master Scheduling/MRP product family. It is documented as the "Supply chain bill make at view" and is supplied as a read-only reporting object rather than a transactional entity. Its purpose is to expose sourcing-rule assignments of the "bill make at" type, presenting each qualifying source-to-destination relationship alongside the derived organization codes, item identities, calendar dates, allocation percentages, and ranking needed by planners and integration routines.

The view is particularly relevant to users searching on organization_code. The column ORGANIZATION_CODE and its companion SOURCE_ORGANIZATION_CODE are exposed directly on the view, so a query can resolve a numeric organization ID to the operating-unit code registered in MTL_PARAMETERS without a secondary join. A third, concatenated descriptor is also projected: the view builds a label of the form ALLOCATION_PERCENT || '% MAKE AT ' || ORGANIZATION_CODE, which is the human-readable ITEM_ORG value displayed in EBS supply-chain sourcing windows.

Underlying Base Objects

The view is defined over four documented base objects, all referenced through the APPS schema:

• MRP_SOURCES_V — the driving view, supplying ASSIGNMENT_SET_ID, ASSIGNMENT_TYPE, SOURCING_RULE_NAME, ORGANIZATION_ID, SOURCE_ORGANIZATION_ID, INVENTORY_ITEM_ID, ALLOCATION_PERCENT, RANK, EFFECTIVE_DATE, and DISABLE_DATE.
• MTL_PARAMETERS — joined twice (aliases PARAM1 and PARAM2) to translate ORGANIZATION_ID and SOURCE_ORGANIZATION_ID into ORGANIZATION_CODE, and to supply CALENDAR_CODE and CALENDAR_EXCEPTION_SET_ID.
• MTL_SYSTEM_ITEMS_KFV — joined on organization and inventory item to provide the concatenated item segments (ITEM_NAME / COMPONENT_NAME).
• BOM_CALENDAR_DATES — joined on calendar code and exception set to expand the sourcing assignment across valid calendar dates.

The joins enforce several documented restrictions: the destination organization is fixed to equal the source organization (SOURCES.ORGANIZATION_ID = SOURCES.SOURCE_ORGANIZATION_ID), the calendar date must fall between EFFECTIVE_DATE and NVL(DISABLE_DATE), and a cardinality/index hint (INDEX(SR MRP_SOURCING_RULES_U1)) steers the optimizer toward the sourcing rules unique index.

Key Columns

• ITEM_ORG — the concatenated descriptor combining allocation percent and destination organization code.
• ORGANIZATION_ID / ORGANIZATION_CODE — the destination (make-at) organization.
• SOURCE_ORGANIZATION_ID / SOURCE_ORGANIZATION_CODE — the supplying organization.
• INVENTORY_ITEM_ID / ITEM_NAME — the parent item and its concatenated key-flexfield segments.
• COMPONENT_ITEM_ID / COMPONENT_NAME — the component item and segments; USAGE carries the component quantity.
• SOURCING_RULE / ASSIGNMENT_SET_ID / ASSIGNMENT_TYPE — the sourcing rule identity and its assignment context.
• ALLOCATION_PERCENT / RANK — the percentage split and priority ordering among competing sources.
• EFFECTIVE_DATE — the calendar date on which the assignment is active.

Common Use Cases and Queries

Typical uses include validating make-at sourcing assignments for an organization, reconciling percentages across a sourcing rule, and feeding planning or integration extracts that require organization codes rather than internal IDs. Because the view returns one row per active calendar date, date filtering is essential in practice.

SELECT organization_code,
       item_name,
       component_name,
       sourcing_rule,
       allocation_percent,
       rank,
       effective_date
FROM   apps.mrp_sc_bill_make_at_v
WHERE  organization_code = 'M1'
AND    effective_date BETWEEN :start_date AND :end_date
ORDER  BY item_name, rank;

A second common pattern aggregates allocation by organization and item to detect over- or under-allocated sourcing rules:

SELECT organization_code,
       item_name,
       sourcing_rule,
       SUM(allocation_percent) total_allocation
FROM   apps.mrp_sc_bill_make_at_v
GROUP  BY organization_code, item_name, sourcing_rule
HAVING SUM(allocation_percent) <> 100;

Both queries rely on the documented ORGANIZATION_CODE column and require an active calendar date to return rows, reflecting the calendar-driven expansion built into the view definition.