eTRM uses javascript that opens and focuses a separate window to display reports. Your browser does not appear to support javascript. This should not prevent you from using eTRM but it does mean the window focus feature will not work. Please check the contents of other windows on your desktop if you click on a link that does not appear to do anything.

APPS.MRP_KANBAN_PLAN_PK dependencies on MRP_LOW_LEVEL_CODES

Line 69: DELETE FROM mrp_low_level_codes

65: -- delete all the entries from the low level codes table except
66: -- entries list of kanban items that we had got in the very first
67: -- snapshot of items during a regular plan run
68:
69: DELETE FROM mrp_low_level_codes
70: WHERE plan_id = g_kanban_info_rec.kanban_plan_id
71: AND organization_id = g_kanban_info_rec.organization_id
72: AND (levels_below <> 1 OR
73: assembly_item_id = component_item_id OR

Line 77: UPDATE mrp_low_level_codes

73: assembly_item_id = component_item_id OR
74: assembly_item_id = -1 );
75:
76: -- update the low level code of each of the remaining records to null
77: UPDATE mrp_low_level_codes
78: SET low_level_code = null
79: WHERE plan_id = g_kanban_info_rec.kanban_plan_id
80: AND organization_id = g_kanban_info_rec.organization_id;
81:

Line 84: DELETE FROM mrp_low_level_codes

80: AND organization_id = g_kanban_info_rec.organization_id;
81:
82: ELSIF nvl(g_kanban_info_rec.replan_flag,2) = 2 THEN
83:
84: DELETE FROM mrp_low_level_codes
85: WHERE plan_id = g_kanban_info_rec.kanban_plan_id
86: AND organization_id = g_kanban_info_rec.organization_id;
87:
88: DELETE FROM mtl_kanban_pull_sequences

Line 104: -- populate mrp_low_level_codes table.

100: So, as you will see we have put a commit after the call
101: to snapshot_item_locations procedure
102: */
103: -- call the procedure to snapshot the item/locations and
104: -- populate mrp_low_level_codes table.
105: -- Note that we are calculating low level codes
106: -- only to detect loops and not for planning purposes.
107: -- We gather demand by looking at the input to the plan
108: -- and then blow it down to the component item/locations

Line 875: mrp_low_level_codes mllc,

871: mllc.wip_supply_type,
872: mllc.basis_type,
873: nvl(msi.fixed_order_quantity, nvl(msi.minimum_order_quantity, nvl(msi.maximum_order_quantity,1)))
874: FROM mtl_system_items msi,
875: mrp_low_level_codes mllc,
876: bom_inventory_components bic,
877: bom_bill_of_materials bbom,
878: bom_operational_routings bor,
879: mtl_parameters mp

Line 944: -- as stored in the mrp_low_level_codes table

940: OR p_explode_always = 'Y'
941: OR (p_sales_order_demand = 'Y' AND msi.bom_item_type = 4));
942:
943: -- cursor component_cursor2 blows down demand to the components
944: -- as stored in the mrp_low_level_codes table
945: CURSOR component_cursor2 IS
946: SELECT DISTINCT
947: mllc.component_item_id,
948: mllc.from_subinventory,

Line 964: mrp_low_level_codes mllc

960: mllc.wip_supply_type,
961: mllc.basis_type,
962: nvl(msi.fixed_order_quantity, nvl(msi.minimum_order_quantity, nvl(msi.maximum_order_quantity,1)))
963: FROM mtl_system_items msi,
964: mrp_low_level_codes mllc
965: WHERE mllc.plan_id = g_kanban_info_rec.kanban_plan_id
966: AND mllc.organization_id + 0 = g_kanban_info_rec.organization_id
967: AND mllc.assembly_item_id = p_assembly_item_id
968: AND ((mllc.to_subinventory = p_subinventory

Line 1013: -- p_recursive set to true when we want to go after mrp_low_level_codes

1009: -- on the demand. So, when we call Cacade_Demand the first time, ie
1010: -- to pass down demand to components feeding into the line, then
1011: -- p_recursive is false. We just blow the demand down one level. Once
1012: -- we do that, we call Cascade_Fcst_Ap_Demand in the recursive mode with
1013: -- p_recursive set to true when we want to go after mrp_low_level_codes
1014: -- recursively and blow the demand all the way down.
1015:
1016: IF NOT p_recursive THEN
1017: IF NOT component_cursor1%ISOPEN THEN

Line 1395: ( select COMPONENT_ITEM_ID from mrp_low_level_codes

1391: WHERE organization_id = g_kanban_info_rec.organization_id
1392: AND scheduled_completion_date between g_kanban_info_rec.start_date AND
1393: g_kanban_info_rec.cutoff_date
1394: AND primary_item_id IN
1395: ( select COMPONENT_ITEM_ID from mrp_low_level_codes
1396: WHERE ORGANIZATION_ID = g_kanban_info_rec.organization_id
1397: AND PLAN_ID = g_kanban_info_rec.kanban_plan_id )
1398: AND primary_item_id = p_top_item_id
1399: AND nvl(alternate_bom_designator, 'NONE') = nvl(p_top_alt, 'NONE')

Line 1432: mrp_low_level_codes mllc,

1428: mllc.wip_supply_type,
1429: mllc.basis_type,
1430: nvl(msi.fixed_order_quantity, nvl(msi.minimum_order_quantity, nvl(msi.maximum_order_quantity,1)))
1431: FROM mtl_system_items msi,
1432: mrp_low_level_codes mllc,
1433: bom_inventory_components bic,
1434: bom_bill_of_materials bbom
1435: WHERE
1436: bbom.assembly_item_id = p_assembly_item_id

Line 1497: -- as stored in the mrp_low_level_codes table

1493: OR p_explode_always = 'Y'
1494: OR (p_sales_order_demand = 'Y' AND msi.bom_item_type = 4));
1495:
1496: -- cursor component_cursor2 blows down demand to the components
1497: -- as stored in the mrp_low_level_codes table
1498: CURSOR component_cursor2 IS
1499: SELECT DISTINCT
1500: mllc.component_item_id,
1501: mllc.from_subinventory,

Line 1517: mrp_low_level_codes mllc

1513: mllc.wip_supply_type,
1514: mllc.basis_type,
1515: nvl(msi.fixed_order_quantity, nvl(msi.minimum_order_quantity, nvl(msi.maximum_order_quantity,1)))
1516: FROM mtl_system_items msi,
1517: mrp_low_level_codes mllc
1518: WHERE mllc.plan_id = g_kanban_info_rec.kanban_plan_id
1519: AND mllc.organization_id + 0 = g_kanban_info_rec.organization_id
1520: AND mllc.assembly_item_id = p_assembly_item_id
1521: AND ((mllc.to_subinventory = p_subinventory

Line 1570: -- p_recursive set to true when we want to go after mrp_low_level_codes

1566: -- on the demand. So, when we call Cacade_Demand the first time, ie
1567: -- to pass down demand to components feeding into the line, then
1568: -- p_recursive is false. We just blow the demand down one level. Once
1569: -- we do that, we call Cascade_Mds_Mps_Demand in the recursive mode with
1570: -- p_recursive set to true when we want to go after mrp_low_level_codes
1571: -- recursively and blow the demand all the way down.
1572:
1573: IF NOT p_recursive THEN
1574:

Line 1917: mrp_low_level_codes mllc,

1913: mllc.wip_supply_type,
1914: mllc.basis_type,
1915: nvl(msi.fixed_order_quantity, nvl(msi.minimum_order_quantity, nvl(msi.maximum_order_quantity,1)))
1916: FROM mtl_system_items msi,
1917: mrp_low_level_codes mllc,
1918: bom_inventory_components bic,
1919: bom_bill_of_materials bbom,
1920: bom_operational_routings bor,
1921: mtl_parameters mp

Line 1986: -- as stored in the mrp_low_level_codes table

1982: OR p_explode_always = 'Y'
1983: OR (p_sales_order_demand = 'Y' AND msi.bom_item_type = 4));
1984:
1985: -- cursor component_cursor2 blows down demand to the components
1986: -- as stored in the mrp_low_level_codes table
1987: CURSOR component_cursor2 IS
1988: SELECT DISTINCT
1989: mllc.component_item_id,
1990: mllc.from_subinventory,

Line 2006: mrp_low_level_codes mllc

2002: mllc.wip_supply_type,
2003: mllc.basis_type,
2004: nvl(msi.fixed_order_quantity, nvl(msi.minimum_order_quantity, nvl(msi.maximum_order_quantity,1)))
2005: FROM mtl_system_items msi,
2006: mrp_low_level_codes mllc
2007: WHERE mllc.plan_id = g_kanban_info_rec.kanban_plan_id
2008: AND mllc.organization_id + 0 = g_kanban_info_rec.organization_id
2009: AND mllc.assembly_item_id = p_assembly_item_id
2010: AND ((mllc.to_subinventory = p_subinventory

Line 2058: -- p_recursive set to true when we want to go after mrp_low_level_codes

2054: -- on the demand. So, when we call Cacade_Demand the first time, ie
2055: -- to pass down demand to components feeding into the line, then
2056: -- p_recursive is false. We just blow the demand down one level. Once
2057: -- we do that, we call Cascade_Mds_Mps_Demand in the recursive mode with
2058: -- p_recursive set to true when we want to go after mrp_low_level_codes
2059: -- recursively and blow the demand all the way down.
2060:
2061: IF NOT p_recursive THEN
2062:

Line 2646: ( select COMPONENT_ITEM_ID from mrp_low_level_codes

2642: WHERE organization_id = g_kanban_info_rec.organization_id
2643: AND scheduled_completion_date between g_kanban_info_rec.start_date AND
2644: g_kanban_info_rec.cutoff_date
2645: AND primary_item_id IN
2646: ( select COMPONENT_ITEM_ID from mrp_low_level_codes
2647: WHERE ORGANIZATION_ID = g_kanban_info_rec.organization_id
2648: AND PLAN_ID = g_kanban_info_rec.kanban_plan_id )
2649: AND primary_item_id = p_inventory_item_id
2650: AND nvl(alternate_bom_designator, 'NONE') = nvl(p_alt_bom , 'NONE')

Line 3159: -- as in the mrp_low_level_codes table

3155:
3156: -- ========================================================================
3157: -- this function retrieves the kanban demand based on the
3158: -- input to the kanban plan and passes it down to the components
3159: -- as in the mrp_low_level_codes table
3160: -- ========================================================================
3161: FUNCTION Retrieve_Kanban_Demand RETURN BOOLEAN IS
3162:
3163: -- declare local variables

Line 3234: ( select COMPONENT_ITEM_ID from mrp_low_level_codes

3230: WHERE organization_id = g_kanban_info_rec.organization_id
3231: AND scheduled_completion_date between g_kanban_info_rec.start_date AND
3232: g_kanban_info_rec.cutoff_date
3233: AND primary_item_id IN
3234: ( select COMPONENT_ITEM_ID from mrp_low_level_codes
3235: where ORGANIZATION_ID = g_kanban_info_rec.organization_id
3236: AND PLAN_ID = g_kanban_info_rec.kanban_plan_id )
3237: group by primary_item_id,alternate_bom_designator,line_id;
3238: BEGIN

Line 3905: -- populate mrp_low_level_codes table.

3901: because we now want to commit after the snapshot is over so that
3902: there is less impact on rollback segment
3903:
3904: -- call the procedure to snapshot the item/locations and
3905: -- populate mrp_low_level_codes table.
3906: -- Note that we are calculating low level codes
3907: -- only to detect loops and not for planning purposes.
3908: -- We gather demand by looking at the input to the plan
3909: -- and then blow it down to the component item/locations

Line 3925: -- as in the mrp_low_level_codes table

3921: END IF;
3922:
3923: -- now call the procedure to retrieve the kanban demand based on
3924: -- the input to the kanban plan and pass it down to the components
3925: -- as in the mrp_low_level_codes table
3926:
3927: IF NOT Retrieve_Kanban_Demand THEN
3928: g_log_message := 'Error in RETRIEVE_KANBAN_DEMAND';
3929: MRP_UTIL.MRP_LOG (g_log_message);