Results for “sourcing_rule_type_text”

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

Overview

MRP_ITEM_SOURCING_V is an APPS-owned database view in the Oracle E-Business Suite Master Scheduling/MRP (MRP) product. It exposes the sourcing assignments defined for planned items, combining the sourcing records held in MRP_ITEM_SOURCING with the descriptive attributes of the organizations, items, suppliers, vendors, and lookup values they reference. In the ETRM documentation it is titled "View: MRP_ITEM_SOURCING_V" with the description "Plan items source view," and its status is VALID in both 12.1.1 and 12.2.2.

The view is primarily a reporting and integration object. It presents sourcing information in a denormalized form, so planning data can be queried directly without navigating the multiple base tables that store the raw assignment records. Typical consumers include custom reports, data extracts that feed external planning or procurement systems, and integration interfaces that need a consolidated picture of where a plan organization intends to obtain each item.

Underlying Base Objects

According to the documented view metadata, MRP_ITEM_SOURCING_V is defined over the following base objects: FND_GLOBAL (package), MFG_LOOKUPS (view), MRP_ITEM_SOURCING (synonym), MRP_PLAN_ORGANIZATIONS_V (view), MRP_SOURCING_RULES (synonym), MTL_PARAMETERS (synonym), MTL_SYSTEM_ITEMS_KFV (synonym), PO_VENDORS (view), and PO_VENDOR_SITES (view).

MRP_ITEM_SOURCING is the driving table; it holds one row per sourcing assignment, including source type, rank, allocation percent, quantity, effective and disable dates, and the identifiers for the sourcing rule, assignment set, vendor, vendor site, and source organization. MTL_SYSTEM_ITEMS_KFV supplies the concatenated item segment string, while MTL_PARAMETERS provides the organization code for both the planning organization and, where applicable, the source organization. MRP_PLAN_ORGANIZATIONS_V restricts the result set to valid planned organizations. MRP_SOURCING_RULES provides the sourcing rule name. PO_VENDORS and PO_VENDOR_SITES supply supplier and supplier site names. Three independent joins to MFG_LOOKUPS resolve the descriptive meanings for SOURCE_TYPE, ASSIGNMENT_TYPE, and SOURCING_RULE_TYPE using the lookup types MRP_SOURCE_TYPE, MRP_SR_ASSIGNMENT_TYPE, and MRP_SOURCING_RULE_TYPE respectively. All lookup joins are outer joins, so rows are retained even when no lookup value is defined.

Key Columns

• COMPILE_DESIGNATOR — identifies the plan compilation designator associated with the sourcing record.
• PLAN_ORGANIZATION_ID / ORGANIZATION_ID / ORGANIZATION_C — the planning organization and its code; ORGANIZATION_ID links to the item and sourcing rows.
• INVENTORY_ITEM_ID / ITEM_SEGMENTS — the planned item identifier and its concatenated segment display value.
• SOURCE_TYPE / MEANING — the sourcing method (for example, organization or supplier), with the decoded lookup meaning.
• SOURCE_ORGANIZATION_ID — the supplying organization when the source is an internal organization.
• VENDOR_ID, VENDOR_NAME, VENDOR_SITE_ID, VENDOR_SITE_CODE — the supplier and supplier site for supplier-based sourcing.
• SOURCING_RULE_ID / SOURCING_RULE_NAME — the sourcing rule that governs the assignment.
• SOURCING_RULE_TYPE / MEANING — the classification of the sourcing rule, decoded from the MRP_SOURCING_RULE_TYPE lookup.
• ASSIGNMENT_ID, ASSIGNMENT_SET_ID, ASSIGNMENT_TYPE / MEANING — the assignment grouping and its decoded type.
• ALLOCATION_PERCENT, RANK, QUANTITY — the allocation split, priority ranking, and quantity applicable to the assignment.
• EFFECTIVE_DATE, DISABLE_DATE — the validity window of the sourcing assignment.
• AVG_TRANSIT_LEAD_TIME, SHIP_METHOD, HISTORICAL_ALLOC_QTY — planning attributes describing transit time, shipping method, and historical allocation.

Common Use Cases and Queries

A frequent requirement is to list all sourcing assignments for an item within a planning organization, including supplier details and the decoded sourcing rule type. The following query illustrates this pattern, filtering on the lookup meaning for the sourcing rule type—the value most commonly associated with the user search term mrp_sourcing_rule_type:

• SELECT item_segments, organization_c, source_type, meaning,
•   vendor_name, vendor_site_code, sourcing_rule_name, sourcing_rule_type,
•   allocation_percent, rank, effective_date, disable_date
• FROM apps.mrp_item_sourcing_v
• WHERE inventory_item_id = :item_id
•   AND organization_id = :org_id
•   AND (disable_date IS NULL OR disable_date > SYSDATE);

Other practical uses include auditing allocation percentages across suppliers for a given item, extracting active sourcing rules for a plan organization to load into an external planning engine, and validating that every planned item has at least one effective sourcing assignment. Because the view already joins vendor and lookup information, these reports avoid repeating the multi-table join logic and remain consistent with the MRP planning data model.