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 71: DELETE FROM mrp_low_level_codes

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

Line 79: UPDATE mrp_low_level_codes

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

Line 86: DELETE FROM mrp_low_level_codes

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

Line 106: -- populate mrp_low_level_codes table.

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

Line 938: mrp_low_level_codes mllc,

934: mllc.wip_supply_type,
935: mllc.basis_type,
936: nvl(msi.fixed_order_quantity, nvl(msi.minimum_order_quantity, nvl(msi.maximum_order_quantity,1)))
937: FROM mtl_system_items msi,
938: mrp_low_level_codes mllc,
939: bom_inventory_components bic,
940: bom_bill_of_materials bbom,
941: bom_operational_routings bor,
942: mtl_parameters mp

Line 1007: -- as stored in the mrp_low_level_codes table

1003: OR p_explode_always = 'Y'
1004: OR (p_sales_order_demand = 'Y' AND msi.bom_item_type = 4));
1005:
1006: -- cursor component_cursor2 blows down demand to the components
1007: -- as stored in the mrp_low_level_codes table
1008: CURSOR component_cursor2 IS
1009: SELECT DISTINCT
1010: mllc.component_item_id,
1011: mllc.from_subinventory,

Line 1027: mrp_low_level_codes mllc

1023: mllc.wip_supply_type,
1024: mllc.basis_type,
1025: nvl(msi.fixed_order_quantity, nvl(msi.minimum_order_quantity, nvl(msi.maximum_order_quantity,1)))
1026: FROM mtl_system_items msi,
1027: mrp_low_level_codes mllc
1028: WHERE mllc.plan_id = g_kanban_info_rec.kanban_plan_id
1029: AND mllc.organization_id + 0 = g_kanban_info_rec.organization_id
1030: AND mllc.assembly_item_id = p_assembly_item_id
1031: AND ((mllc.to_subinventory = p_subinventory

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

1080: -- on the demand. So, when we call Cacade_Demand the first time, ie
1081: -- to pass down demand to components feeding into the line, then
1082: -- p_recursive is false. We just blow the demand down one level. Once
1083: -- we do that, we call Cascade_Fcst_Ap_Demand in the recursive mode with
1084: -- p_recursive set to true when we want to go after mrp_low_level_codes
1085: -- recursively and blow the demand all the way down.
1086:
1087: IF NOT p_recursive THEN
1088: IF NOT component_cursor1%ISOPEN THEN

Line 1474: ( select COMPONENT_ITEM_ID from mrp_low_level_codes

1470: WHERE organization_id = g_kanban_info_rec.organization_id
1471: AND scheduled_completion_date between g_kanban_info_rec.start_date AND
1472: g_kanban_info_rec.cutoff_date
1473: AND primary_item_id IN
1474: ( select COMPONENT_ITEM_ID from mrp_low_level_codes
1475: WHERE ORGANIZATION_ID = g_kanban_info_rec.organization_id
1476: AND PLAN_ID = g_kanban_info_rec.kanban_plan_id )
1477: AND primary_item_id = p_top_item_id
1478: AND nvl(alternate_bom_designator, 'NONE') = nvl(p_top_alt, 'NONE')

Line 1511: mrp_low_level_codes mllc,

1507: mllc.wip_supply_type,
1508: mllc.basis_type,
1509: nvl(msi.fixed_order_quantity, nvl(msi.minimum_order_quantity, nvl(msi.maximum_order_quantity,1)))
1510: FROM mtl_system_items msi,
1511: mrp_low_level_codes mllc,
1512: bom_inventory_components bic,
1513: bom_bill_of_materials bbom
1514: WHERE
1515: bbom.assembly_item_id = p_assembly_item_id

Line 1576: -- as stored in the mrp_low_level_codes table

1572: OR p_explode_always = 'Y'
1573: OR (p_sales_order_demand = 'Y' AND msi.bom_item_type = 4));
1574:
1575: -- cursor component_cursor2 blows down demand to the components
1576: -- as stored in the mrp_low_level_codes table
1577: CURSOR component_cursor2 IS
1578: SELECT DISTINCT
1579: mllc.component_item_id,
1580: mllc.from_subinventory,

Line 1596: mrp_low_level_codes mllc

1592: mllc.wip_supply_type,
1593: mllc.basis_type,
1594: nvl(msi.fixed_order_quantity, nvl(msi.minimum_order_quantity, nvl(msi.maximum_order_quantity,1)))
1595: FROM mtl_system_items msi,
1596: mrp_low_level_codes mllc
1597: WHERE mllc.plan_id = g_kanban_info_rec.kanban_plan_id
1598: AND mllc.organization_id + 0 = g_kanban_info_rec.organization_id
1599: AND mllc.assembly_item_id = p_assembly_item_id
1600: AND ((mllc.to_subinventory = p_subinventory

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

1654: -- on the demand. So, when we call Cacade_Demand the first time, ie
1655: -- to pass down demand to components feeding into the line, then
1656: -- p_recursive is false. We just blow the demand down one level. Once
1657: -- we do that, we call Cascade_Mds_Mps_Demand in the recursive mode with
1658: -- p_recursive set to true when we want to go after mrp_low_level_codes
1659: -- recursively and blow the demand all the way down.
1660:
1661: IF NOT p_recursive THEN
1662:

Line 2012: mrp_low_level_codes mllc,

2008: mllc.wip_supply_type,
2009: mllc.basis_type,
2010: nvl(msi.fixed_order_quantity, nvl(msi.minimum_order_quantity, nvl(msi.maximum_order_quantity,1)))
2011: FROM mtl_system_items msi,
2012: mrp_low_level_codes mllc,
2013: bom_inventory_components bic,
2014: bom_bill_of_materials bbom,
2015: bom_operational_routings bor,
2016: mtl_parameters mp

Line 2081: -- as stored in the mrp_low_level_codes table

2077: OR p_explode_always = 'Y'
2078: OR (p_sales_order_demand = 'Y' AND msi.bom_item_type = 4));
2079:
2080: -- cursor component_cursor2 blows down demand to the components
2081: -- as stored in the mrp_low_level_codes table
2082: CURSOR component_cursor2 IS
2083: SELECT DISTINCT
2084: mllc.component_item_id,
2085: mllc.from_subinventory,

Line 2101: mrp_low_level_codes mllc

2097: mllc.wip_supply_type,
2098: mllc.basis_type,
2099: nvl(msi.fixed_order_quantity, nvl(msi.minimum_order_quantity, nvl(msi.maximum_order_quantity,1)))
2100: FROM mtl_system_items msi,
2101: mrp_low_level_codes mllc
2102: WHERE mllc.plan_id = g_kanban_info_rec.kanban_plan_id
2103: AND mllc.organization_id + 0 = g_kanban_info_rec.organization_id
2104: AND mllc.assembly_item_id = p_assembly_item_id
2105: AND ((mllc.to_subinventory = p_subinventory

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

2157: -- on the demand. So, when we call Cacade_Demand the first time, ie
2158: -- to pass down demand to components feeding into the line, then
2159: -- p_recursive is false. We just blow the demand down one level. Once
2160: -- we do that, we call Cascade_Mds_Mps_Demand in the recursive mode with
2161: -- p_recursive set to true when we want to go after mrp_low_level_codes
2162: -- recursively and blow the demand all the way down.
2163:
2164: IF NOT p_recursive THEN
2165:

Line 2828: ( select COMPONENT_ITEM_ID from mrp_low_level_codes

2824: WHERE organization_id = g_kanban_info_rec.organization_id
2825: AND scheduled_completion_date between g_kanban_info_rec.start_date AND
2826: g_kanban_info_rec.cutoff_date
2827: AND primary_item_id IN
2828: ( select COMPONENT_ITEM_ID from mrp_low_level_codes
2829: WHERE ORGANIZATION_ID = g_kanban_info_rec.organization_id
2830: AND PLAN_ID = g_kanban_info_rec.kanban_plan_id )
2831: AND primary_item_id = p_inventory_item_id
2832: AND nvl(alternate_bom_designator, 'NONE') = nvl(p_alt_bom , 'NONE')

Line 3487: -- as in the mrp_low_level_codes table

3483:
3484: -- ========================================================================
3485: -- this function retrieves the kanban demand based on the
3486: -- input to the kanban plan and passes it down to the components
3487: -- as in the mrp_low_level_codes table
3488: -- ========================================================================
3489: FUNCTION Retrieve_Kanban_Demand RETURN BOOLEAN IS
3490:
3491: -- declare local variables

Line 3562: ( select COMPONENT_ITEM_ID from mrp_low_level_codes

3558: WHERE organization_id = g_kanban_info_rec.organization_id
3559: AND scheduled_completion_date between g_kanban_info_rec.start_date AND
3560: g_kanban_info_rec.cutoff_date
3561: AND primary_item_id IN
3562: ( select COMPONENT_ITEM_ID from mrp_low_level_codes
3563: where ORGANIZATION_ID = g_kanban_info_rec.organization_id
3564: AND PLAN_ID = g_kanban_info_rec.kanban_plan_id )
3565: group by primary_item_id,alternate_bom_designator,line_id;
3566: BEGIN

Line 4399: -- populate mrp_low_level_codes table.

4395: because we now want to commit after the snapshot is over so that
4396: there is less impact on rollback segment
4397:
4398: -- call the procedure to snapshot the item/locations and
4399: -- populate mrp_low_level_codes table.
4400: -- Note that we are calculating low level codes
4401: -- only to detect loops and not for planning purposes.
4402: -- We gather demand by looking at the input to the plan
4403: -- and then blow it down to the component item/locations

Line 4419: -- as in the mrp_low_level_codes table

4415: END IF;
4416:
4417: -- now call the procedure to retrieve the kanban demand based on
4418: -- the input to the kanban plan and pass it down to the components
4419: -- as in the mrp_low_level_codes table
4420:
4421: IF NOT Retrieve_Kanban_Demand THEN
4422: g_log_message := 'Error in RETRIEVE_KANBAN_DEMAND';
4423: MRP_UTIL.MRP_LOG (g_log_message);