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.WIP_FLOWUTIL_PRIV dependencies on BOM_OPERATIONAL_ROUTINGS

Line 2057: from bom_operational_routings

2053: select common_routing_sequence_id,
2054: nvl(cfm_routing_flag, 2)
2055: into l_commonRoutSeqID,
2056: l_cfmRouting
2057: from bom_operational_routings
2058: where organization_id = p_orgID
2059: and assembly_item_id = p_assyID
2060: and nvl(alternate_routing_designator, 'NONE') =
2061: nvl(p_altRoutDesig, 'NONE');

Line 2546: bom_operational_routings bor

2542: -- line op doesn't have effectivity date
2543: select distinct bos.operation_sequence_id
2544: into l_opSeqID
2545: from bom_operation_sequences bos,
2546: bom_operational_routings bor
2547: where bor.common_routing_sequence_id = bos.routing_sequence_id
2548: and bor.assembly_item_id = p_assyItemID
2549: and bor.organization_id = p_orgID
2550: and nvl(alternate_routing_designator, 'NONE') =

Line 2558: bom_operational_routings bor

2554: else
2555: select distinct bos.operation_sequence_id
2556: into l_opSeqID
2557: from bom_operation_sequences bos,
2558: bom_operational_routings bor
2559: where bor.common_routing_sequence_id = bos.routing_sequence_id
2560: and bor.common_routing_sequence_id = p_routingSeqID
2561: and bos.operation_seq_num = p_terminalOpSeqNum
2562: and bos.operation_type = 3;