DBA Data[Home] [Help]

APPS.WIP_REPETITIVE_UTILITIES dependencies on WIP_CHANGE_STATUS

Line 253: wip_change_status.insert_period_balances(x_wip_id, p_org_id,

249: open per_bal;
250: fetch per_bal INTO x_line_id, x_class_code;
251: close per_bal;
252:
253: wip_change_status.insert_period_balances(x_wip_id, p_org_id,
254: p_new_sched_id, x_line_id,
255: x_class_code);
256:
257: -- set processed days, lusd, lucd of the old schedule to reflect days the

Line 743: wip_change_status.check_repetitive_routing(x_wip_id,

739:
740: IF ((x_found_next_sched) AND
741: (x_rollfwd_status_type = WIP_CONSTANTS.UNRELEASED)) THEN
742:
743: wip_change_status.check_repetitive_routing(x_wip_id,
744: p_org_id,
745: p_rollfwd_sched_id,
746: x_line_id);
747: END IF;

Line 964: wip_change_status.insert_period_balances(x_wip_id,

960: open per_bal;
961: fetch per_bal INTO x_class_code;
962: close per_bal;
963:
964: wip_change_status.insert_period_balances(x_wip_id,
965: p_org_id, p_rollfwd_sched_id,
966: x_line_id, x_class_code);
967:
968: x_dummy := fnd_release.get_release(x_rel, x_info);