APPS.WIP_FLOW_VALIDATION dependencies on WIP_FLOW_SCHEDULES

Line 999: the other into wip_flow_schedules, we don't have

995: begin
996:
997: /**************************************************
998: As we are inserting the flow schedules one after
999: the other into wip_flow_schedules, we don't have
1000: to check for duplicate schedule_number in MTI
1001: itself as this will error out by itself
1002: ***************************************************/
1003:

Line 1034: the other into wip_flow_schedules, we don't have

1030: begin
1031:
1032: /**************************************************
1033: As we are inserting the flow schedules one after
1034: the other into wip_flow_schedules, we don't have
1035: to check for duplicate schedule_number in MTI
1036: itself as this will error out by itself
1037: ***************************************************/
1038:

Line 1089: * the unit number in wip_flow_schedules.

1085: * enabled for model unit effectivity
1086: * AND the assembly is a unit effective item
1087: * AND that the unit number exists in the master org of the current organization
1088: * AND in the case of scheduled flow schedules the unit number provided matches
1089: * the unit number in wip_flow_schedules.
1090: ******************************************************************************/
1091:
1092: function unit_number(p_rowid in rowid) return number is
1093: x_success number := 0;

Line 1112: FROM wip_flow_schedules wfs

1108: WHERE P.organization_id = mti.organization_id and
1109: P.master_organization_id = N.master_organization_id)
1110: AND (mti.scheduled_flag <> 1
1111: OR exists (SELECT 1
1112: FROM wip_flow_schedules wfs
1113: WHERE wfs.wip_entity_id = mti.transaction_source_id
1114: AND wfs.end_item_unit_number = mti.end_item_unit_number
1115: )))));
1116: