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.CTO_SUBASSEMBLY_SUP_PK dependencies on BOM_OPERATION_SEQUENCES

Line 336: bom_operation_sequences bos_p

332: FROM BOM_INVENTORY_COMPONENTS bic,
333: bom_bill_of_materials bom,
334: --bugfix 4615409
335: bom_operational_routings bor_p,
336: bom_operation_sequences bos_p
337: WHERE bic.bill_sequence_id = bom.common_bill_sequence_id
338: and bom.assembly_item_id = p_parent_item_id
339: and bom.organization_id = p_organization_id
340: AND bic.COMPONENT_ITEM_ID = p_item_id

Line 916: --bom_operation_sequences bos_p

912: bom_operational_routings bor,
913: wip_lines wil
914: --bugfix 4615409
915: --bom_operational_routings bor_p,--parent
916: --bom_operation_sequences bos_p
917: where bic.bill_sequence_id = bom.common_bill_sequence_id
918: and bom.assembly_item_id = pParentItemId
919: and bom.organization_id = pOrganization_id
920: and bic.component_item_id = msi.inventory_item_id

Line 959: --bom_operation_sequences bos_p

955: bom_operational_routings bor,
956: wip_lines wil
957: --bugfix 4615409
958: --bom_operational_routings bor_p,--parent
959: --bom_operation_sequences bos_p
960: where bic.bill_sequence_id = bom.common_bill_sequence_id
961: and bom.assembly_item_id = pParentItemId
962: and bom.organization_id = pOrganization_id
963: and bic.component_item_id = msi.inventory_item_id

Line 1040: bom_operation_sequences bos_p

1036: BEGIN
1037: select nvl(bos_p.OPERATION_LEAD_TIME_PERCENT,0)
1038: INTO pitems_table(l_index).operation_lead_time_percent
1039: from bom_operational_routings bor_p,--parent
1040: bom_operation_sequences bos_p
1041: where bor_p.assembly_item_id = pParentItemId
1042: and bor_p.organization_id = pOrganization_id
1043: and bor_p.ALTERNATE_ROUTING_DESIGNATOR is null
1044: and bos_p.routing_sequence_id = bor_p.common_routing_sequence_id

Line 1241: bom_operation_sequences bos_p

1237: BEGIN
1238: select nvl(bos_p.OPERATION_LEAD_TIME_PERCENT,0)
1239: INTO pitems_table(l_index).operation_lead_time_percent
1240: from bom_operational_routings bor_p,--parent
1241: bom_operation_sequences bos_p
1242: where bor_p.assembly_item_id = pParentItemId
1243: and bor_p.organization_id = pOrganization_id
1244: and bor_p.ALTERNATE_ROUTING_DESIGNATOR is null
1245: and bos_p.routing_sequence_id = bor_p.common_routing_sequence_id

Line 2871: from bom_operation_sequences

2867: --bugfix 2765109
2868: BEGIN
2869: Select nvl(line_op_seq_id,-99) --bugfix 2786582
2870: into l_operation_seq_id
2871: from bom_operation_sequences
2872: where routing_sequence_id = l_mlsupply_items(l_mlsupply_items(l_index).parent_index).routing_sequence_id
2873: and operation_seq_num = l_mlsupply_items(l_index).operation_seq_num
2874: and operation_type =1
2875: and nvl(EFFECTIVITY_DATE,sysdate+1) <= SYSDATE

Line 3905: bom_operation_sequences bos_p

3901: l_stmt_num := 70;
3902: select nvl(bos_p.OPERATION_LEAD_TIME_PERCENT,0)
3903: INTO pitems_table(l_index).operation_lead_time_percent
3904: from bom_operational_routings bor_p,--parent
3905: bom_operation_sequences bos_p
3906: where bor_p.assembly_item_id = pitems_table(l_parent_index).item_id
3907: and bor_p.organization_id = p_organization_id
3908: and bor_p.ALTERNATE_ROUTING_DESIGNATOR is null
3909: and bos_p.routing_sequence_id = bor_p.common_routing_sequence_id