Results for “msc_system_items_u1”

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

Overview

APPS.MSC_ITEM_TASK_SR_LEVELS_V is a sourcing-rule resolution view within the Oracle Advanced Supply Chain Planning (ASCP) schema. It exposes the effective sourcing hierarchy for planned items by joining sourcing-rule assignments to their receipt organizations, source organizations, and source trading partners. The view receives an inventory item, an organization, and a planning instance as inputs and returns the ranked sourcing levels that apply, including allocation percentages, partner identifiers, and effective/disable dates. It is used by planning engines and by custom reporting to determine from where a given item will be sourced at each level of the sourcing network.

The name reflects its role: "TASK" denotes a runtime planning request context, "SR" denotes sourcing rules, and "LEVELS" denotes the flattened, level-by-level output produced for each item. Because it is a view and not a table, no data is stored; all rows are derived at query time from the relational sourcing model.

Underlying Base Objects

The view is defined over the following documented objects:

• MSC_PLAN_ORGANIZATIONS_V (VIEW) — supplies PLAN_ID, COMPILE_DESIGNATOR, and the planning organization context (aliased PLANS).
• MSC_SR_ASSIGNMENTS (SYNONYM) — maps items to assignment sets and assignment types (aliased MSRA).
• MSC_SOURCING_RULES (SYNONYM) — holds the sourcing rule header, including name, description, and sourcing rule type (aliased MSR).
• MSC_SR_RECEIPT_ORG (SYNONYM) — provides the receipt organization and the rule's effective and disable dates (aliased RECEIPT_ORG).
• MSC_SR_SOURCE_ORG (SYNONYM) — provides the source organization, source partner and partner site, allocation percent, rank, and source type (aliased SOURCE_ORG).
• MSC_SYSTEM_ITEMS (SYNONYM) — supplies item attributes for both the planned item (ITEMS) and the comparison item (COMP_ITEMS), including MRP planning code, BOM item type, make/buy code, UOM, and DRP planned flags.
• MSC_ITEM_CATEGORIES (SYNONYM) and MSC_TRADING_PARTNERS (SYNONYM) — supporting item classification and partner resolution objects referenced by the lineage.

The defining text uses an ORDERED hint with nested-loop joins and explicit index hints (MSC_SR_ASSIGNMENTS_N1, MSC_SOURCING_RULES_U1, MSC_SR_RECEIPT_ORG_N1, MSC_SR_SOURCE_ORG_U3, MSC_SYSTEM_ITEMS_U1), indicating the query is tuned for the item/instance/organization driving path.

Key Columns

• INVENTORY_ITEM_ID, ORGANIZATION_ID, SR_INSTANCE_ID — the item, owning organization, and source instance that identify the assignment.
• PLAN_ID, COMPILE_DESIGNATOR — the plan context in which the sourcing level is evaluated.
• ASSIGNMENT_TYPE, ASSIGNMENT_SET_ID, ASSIGNMENT_ID — how the item was assigned to the sourcing rule.
• SOURCING_RULE_ID, SOURCING_RULE_NAME, SOURCING_RULE_TYPE, DESCRIPTION — the resolved rule and its classification.
• SOURCE_ORGANIZATION_ID, SOURCE_ORG_INSTANCE_ID, SOURCE_PARTNER_ID, SOURCE_PARTNER_SITE_ID, SOURCE_TYPE — the source side of the supply, including the trading partner and site.
• ALLOCATION_PERCENT, RANK, SOURCING_LEVEL — the percentage allocated to the source, its ordering rank, and the level indicator (literal 1 in the level branch shown).
• EFFECTIVE_DATE, DISABLE_DATE — the validity window of the receipt-organization rule.
• MRP_PLANNING_CODE, BOM_ITEM_TYPE, PLANNING_MAKE_BUY_CODE, UOM_CODE, DRP_PLANNED — planning attributes for the item and comparison item.

Common Use Cases and Queries

Typical usage is tracing why a planned item sources from a particular organization or supplier, validating allocation percentages, and auditing effective dates. A representative query:

• SELECT sourcing_rule_name, source_organization_id, source_partner_id, allocation_percent, rank, effective_date, disable_date FROM apps.msc_item_task_sr_levels_v WHERE inventory_item_id = :item AND organization_id = :org AND plan_id = :plan ORDER BY sourcing_level, rank;
• Filtering by source_partner_id to report all items sourced from a given trading partner.
• Joining back to MSC_TRADING_PARTNERS to resolve partner names for reporting.

The user search term "msc_trading_partners_u2" corresponds to the unique index on the MSC_TRADING_PARTNERS synonym, which this view's lineage ultimately depends on for partner resolution.