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.FLM_EXECUTION_UTIL dependencies on WIP_FLOW_SCHEDULES

Line 257: wip_flow_schedules wfs,

253: -- standard operation.
254: CURSOR op_seq_csr IS
255: select bos.operation_sequence_id
256: from bom_operation_sequences bos,
257: wip_flow_schedules wfs,
258: bom_operational_routings bor
259: where wfs.wip_entity_id = i_wip_entity_id
260: and bor.organization_id = i_org_id
261: and bor.assembly_item_id = wfs.primary_item_id

Line 271: wip_flow_schedules wfs,

267: CURSOR start_op_csr IS
268: select bos.operation_sequence_id seq_id,
269: bos.operation_seq_num seq_num
270: from bom_operation_sequences bos,
271: wip_flow_schedules wfs,
272: bom_operational_routings bor
273: where wfs.wip_entity_id = i_wip_entity_id
274: and bor.organization_id = i_org_id
275: and bor.assembly_item_id = wfs.primary_item_id

Line 1599: from wip_flow_schedules

1595: BEGIN
1596:
1597: select wip_entity_id
1598: into l_wip_ent_id
1599: from wip_flow_schedules
1600: where organization_id = orgId
1601: and schedule_number = schNum;
1602:
1603: return (scheduleRecordedDetailsExist(orgId, l_wip_ent_id));

Line 1939: wip_flow_schedules wfs

1935: CURSOR bill_seq IS
1936: select bbom.bill_sequence_id,
1937: wfs.bom_revision_date
1938: from bom_bill_of_materials bbom,
1939: wip_flow_schedules wfs
1940: where wfs.wip_entity_id = p_wip_entity_id
1941: and wfs.organization_id = p_org_id
1942: and bbom.assembly_item_id = wfs.primary_item_id
1943: and bbom.organization_id = wfs.organization_id