APPS.WIP_MOVPROC_PRIV dependencies on WIP_OVERCOMPLETION

Line 996: WIP_OVERCOMPLETION.insert_child_move_txn

992: x_returnStatus => l_returnStatus);
993: END IF;
994:
995: -- call PL/SQL api to insert to WMTI
996: WIP_OVERCOMPLETION.insert_child_move_txn
997: (p_primary_quantity => p_oc_pri_qty,
998: p_parent_txn_id => p_parent_txn_id,
999: -- pass move_profile equal to background so that it will always insert
1000: -- parent group_id to child group_id

Line 1017: l_errMsg := 'WIP_OVERCOMPLETION.insert_child_move_txn failed';

1013: p_first_department_code => l_first_dept_code,
1014: p_err_mesg => l_msgData);
1015:
1016: IF(p_gib.move_profile.child_txn_id IS NULL) THEN
1017: l_errMsg := 'WIP_OVERCOMPLETION.insert_child_move_txn failed';
1018: raise fnd_api.g_exc_unexpected_error;
1019: END IF;
1020:
1021: IF(l_first_op_seq_num IS NOT NULL) THEN

Line 1734: fnd_message.set_name('WIP', 'WIP_OVERCOMPLETION_MISMATCH');

1730: END IF; -- time out check
1731: END IF; -- BACKGROUND check
1732:
1733: IF(l_proc_status = TVE_OVERCOMPLETION_MISMATCH) THEN
1734: fnd_message.set_name('WIP', 'WIP_OVERCOMPLETION_MISMATCH');
1735: fnd_msg_pub.add;
1736: l_errMsg := 'parent txn is not really overcompletion txn';
1737: raise fnd_api.g_exc_unexpected_error;
1738: ELSE

Line 9181: * WIP_OVERCOMPLETION.update_wip_req_operations. This procedure is used to

9177:
9178: /*****************************************************************************
9179: * This procedure is equivalent to witoc_update_wro in wiltps5.ppc
9180: * This update statement in this procedure is equivalent to the one in
9181: * WIP_OVERCOMPLETION.update_wip_req_operations. This procedure is used to
9182: * update WIP_REQUIREMENT_OPERATIONS table
9183: ****************************************************************************/
9184: PROCEDURE update_wro(p_gib IN group_rec_t,
9185: x_returnStatus OUT NOCOPY VARCHAR2) IS