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 2024: from bom_operational_routings

2020: select common_routing_sequence_id,
2021: nvl(cfm_routing_flag, 2)
2022: into l_commonRoutSeqID,
2023: l_cfmRouting
2024: from bom_operational_routings
2025: where organization_id = p_orgID
2026: and assembly_item_id = p_assyID
2027: and nvl(alternate_routing_designator, 'NONE') =
2028: nvl(p_altRoutDesig, 'NONE');

Line 2507: bom_operational_routings bor

2503: -- line op doesn't have effectivity date
2504: select distinct bos.operation_sequence_id
2505: into l_opSeqID
2506: from bom_operation_sequences bos,
2507: bom_operational_routings bor
2508: where bor.common_routing_sequence_id = bos.routing_sequence_id
2509: and bor.assembly_item_id = p_assyItemID
2510: and bor.organization_id = p_orgID
2511: and nvl(alternate_routing_designator, 'NONE') =

Line 2519: bom_operational_routings bor

2515: else
2516: select distinct bos.operation_sequence_id
2517: into l_opSeqID
2518: from bom_operation_sequences bos,
2519: bom_operational_routings bor
2520: where bor.common_routing_sequence_id = bos.routing_sequence_id
2521: and bor.common_routing_sequence_id = p_routingSeqID
2522: and bos.operation_seq_num = p_terminalOpSeqNum
2523: and bos.operation_type = 3;