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 919: --bom_operation_sequences bos_p

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

Line 966: --bom_operation_sequences bos_p

962: bom_operational_routings bor,
963: wip_lines wil
964: --bugfix 4615409
965: --bom_operational_routings bor_p,--parent
966: --bom_operation_sequences bos_p
967: where bic.bill_sequence_id = bom.common_bill_sequence_id
968: and bom.assembly_item_id = pParentItemId
969: and bom.organization_id = pOrganization_id
970: and bic.component_item_id = msi.inventory_item_id

Line 1051: bom_operation_sequences bos_p

1047: BEGIN
1048: select nvl(bos_p.OPERATION_LEAD_TIME_PERCENT,0)
1049: INTO pitems_table(l_index).operation_lead_time_percent
1050: from bom_operational_routings bor_p,--parent
1051: bom_operation_sequences bos_p
1052: where bor_p.assembly_item_id = pParentItemId
1053: and bor_p.organization_id = pOrganization_id
1054: and bor_p.ALTERNATE_ROUTING_DESIGNATOR is null
1055: and bos_p.routing_sequence_id = bor_p.common_routing_sequence_id

Line 1275: bom_operation_sequences bos_p

1271: BEGIN
1272: select nvl(bos_p.OPERATION_LEAD_TIME_PERCENT,0)
1273: INTO pitems_table(l_index).operation_lead_time_percent
1274: from bom_operational_routings bor_p,--parent
1275: bom_operation_sequences bos_p
1276: where bor_p.assembly_item_id = pParentItemId
1277: and bor_p.organization_id = pOrganization_id
1278: and bor_p.ALTERNATE_ROUTING_DESIGNATOR is null
1279: and bos_p.routing_sequence_id = bor_p.common_routing_sequence_id

Line 2884: from bom_operation_sequences

2880: --bugfix 2765109
2881: BEGIN
2882: Select nvl(line_op_seq_id,-99) --bugfix 2786582
2883: into l_operation_seq_id
2884: from bom_operation_sequences
2885: where routing_sequence_id = l_mlsupply_items(l_mlsupply_items(l_index).parent_index).routing_sequence_id
2886: and operation_seq_num = l_mlsupply_items(l_index).operation_seq_num
2887: and operation_type =1
2888: and nvl(EFFECTIVITY_DATE,sysdate+1) <= SYSDATE

Line 3937: bom_operation_sequences bos_p

3933: l_stmt_num := 70;
3934: select nvl(bos_p.OPERATION_LEAD_TIME_PERCENT,0)
3935: INTO pitems_table(l_index).operation_lead_time_percent
3936: from bom_operational_routings bor_p,--parent
3937: bom_operation_sequences bos_p
3938: where bor_p.assembly_item_id = pitems_table(l_parent_index).item_id
3939: and bor_p.organization_id = p_organization_id
3940: and bor_p.ALTERNATE_ROUTING_DESIGNATOR is null
3941: and bos_p.routing_sequence_id = bor_p.common_routing_sequence_id