Results for “mrp_using_assembly_sc_v”
30 results
AI-generated from documented ETRM metadata — verify critical details on the linked pages.
Overview
The view APPS.MRP_USING_ASSEMBLY_SC_V is a supply chain planning view within the Oracle E-Business Suite MRP – Master Scheduling/MRP product family. Its documented description is "MRP using assembly view for supply chain planning," which places it in the family of MRP-supplied views that expose the "using assembly" relationship between a component item and the assembly on which it is consumed. In EBS planning terms, a using assembly identifies the parent assembly associated with a component, including the component's effective date range, its supply type, and its driving item relationship. This view is consumed by planning engines, planning reports, and downstream integrations that need to resolve which assemblies consume a given component, the operation sequence at which the component attaches, and the offset percent applied to that operation.
The view is registered in the APPS schema with status VALID in release 12.2.2 and is equally available in 12.1.1. It carries no AOL or PL/SQL logic; it is a pure SQL definition composed of a UNION ALL of two near-identical query blocks. The "SC" suffix (supply chain) and the join to MRP_FORM_QUERY indicate the view is parameterized by an active form query, so its result set is scoped to the query context established by the planning session rather than returning the entire component master.
Underlying Base Objects
The documented base objects referenced by this view are: MFG_LOOKUPS (view), MRP_BOM_COMPONENTS (synonym), MRP_FORM_QUERY (synonym), MRP_SYSTEM_ITEMS (synonym), MTL_ITEM_FLEXFIELDS (view), and MTL_PARAMETERS (synonym). The primary planning relationship is carried by MRP_BOM_COMPONENTS ASSY, which supplies the using-assembly rows. It is joined to MRP_SYSTEM_ITEMS DRV on inventory item, organization, and compile designator to resolve the driving item, and to MTL_ITEM_FLEXFIELDS twice — once as ASSY_NAME for the assembly item number and once as COMP_NAME for the component item number. MTL_PARAMETERS supplies the organization code, MFG_LOOKUPS resolves the WIP supply type meaning, and MRP_FORM_QUERY constrains the rows to the active query context via NUMBER1 (inventory item), NUMBER2 (organization), and CHAR1 (compile designator).
Key Columns
- INVENTORY_ITEM_ID / ORGANIZATION_ID — Component item and the organization in which the using-assembly relationship is valid.
- COMP_NAME.ITEM_NUMBER / ASSY_NAME.ITEM_NUMBER — Concatenated flexfield values surfacing the component and using-assembly item numbers.
- USING_ASSEMBLY_ID — The assembly item that consumes the component.
- OPERATION_SEQ_NUM / OPERATION_OFFSET_PERCENT — Operation at which the component is consumed and the planning offset percentage applied.
- DRIVING_ITEM_ID — The item that drives the component's requirement; may differ from the component itself.
- USE_UP_CODE / DRV.INVENTORY_USE_UP_DATE — The use-up code and the driving item's inventory use-up date.
- DISABLE_DATE — Effective disable date of the using-assembly row; a DECODE substitutes DISABLE_DATE when FROM_END_ITEM_UNIT_NUMBER is null.
- REVISION / CHANGE_NOTICE / ALTERNATE_BOM_DESIGNATOR — Engineering and BOM context for the relationship.
- FROM_END_ITEM_UNIT_NUMBER / TO_END_ITEM_UNIT_NUMBER / OPTIONAL_COMPONENT — Unit-number effectivity bounds and optional-component flag.
- LU.MEANING — Decoded WIP supply type description (lookup type
WIP_SUPPLY).
Note that no column literally named SUGGESTED_EFFECTIVITY_DATE exists in this view. The closest analogues are the effective date range columns (FROM/TO end item unit numbers, DISABLE_DATE, and the derived inventory use-up date), which are what supply chain planning logic evaluates when determining suggested effectivity.
Common Use Cases and Queries
Typical uses include identifying assemblies that consume a component within a bounded effectivity window, validating component use-up logic, and feeding planning extracts that require parent-assembly context. The view is scoped by an active MRP_FORM_QUERY, so callers normally set up a query row before selecting.
- Locate using assemblies for a component within an organization.
- Report component effectivity against disable dates and use-up dates.
- Resolve WIP supply type meaning for planning documentation.
SELECT using_assembly_id,
assy_name.item_number AS assembly_item,
comp_name.item_number AS component_item,
operation_seq_num,
operation_offset_percent,
meaning
FROM apps.mrp_using_assembly_sc_v
WHERE organization_id = :p_org_id
AND inventory_item_id = :p_component_id;
Because the view is a UNION ALL, callers should expect potential duplicate rows across the two branches and apply DISTINCT or filtering as appropriate for the reporting requirement.
-
MRP using assembly view for supply chain planning
APPS.MRP_USING_ASSEMBLY_SC_V·↳ MFG_LOOKUPS·↳ MRP_BOM_COMPONENTS·↳ MRP_FORM_QUERY·Explore MRP module →
-
MRP using assembly view for supply chain planning
APPS.MRP_USING_ASSEMBLY_SC_V·↳ MFG_LOOKUPS·↳ MRP_BOM_COMPONENTS·↳ MRP_FORM_QUERY·Explore MRP module →
-
SYNONYM: APPS.MRP_FORM_QUERY 12.1.1
-
SYNONYM: APPS.MRP_FORM_QUERY 12.2.2
-
12.2.2 DBA Data 12.2.2
-
12.1.1 DBA Data 12.1.1
-
12.1.1 FND Design Data 12.1.1
-
12.2.2 FND Design Data 12.2.2
-
VIEW: APPS.MFG_LOOKUPS 12.1.1
-
VIEW: APPS.MFG_LOOKUPS 12.2.2
-
SYNONYM: APPS.MTL_PARAMETERS 12.1.1
-
SYNONYM: APPS.MTL_PARAMETERS 12.2.2
-
eTRM - MRP Tables and Views 12.2.2
Recommendations based on user criteria selected in MRP Planner WorkBench
-
eTRM - INV Tables and Views 12.2.2
-
eTRM - MRP Tables and Views 12.1.1
Recommendations based on user criteria selected in MRP Planner WorkBench
-
eTRM - INV Tables and Views 12.1.1
-
12.2.2 DBA Data 12.2.2
-
12.1.1 DBA Data 12.1.1
-
eTRM - MRP Tables and Views 12.1.1
Recommendations based on user criteria selected in MRP Planner WorkBench
-
eTRM - MRP Tables and Views 12.2.2
Recommendations based on user criteria selected in MRP Planner WorkBench
-
eTRM - INV Tables and Views 12.1.1
-
eTRM - INV Tables and Views 12.2.2