DBA Data[Home] [Help]

APPS.WIP_OSP dependencies on WIP_CONSTANTS

Line 50: P_Run_ReqImport IN NUMBER DEFAULT WIP_CONSTANTS.NO);

46: P_Organization_Id NUMBER,
47: P_Repetitive_Schedule_Id NUMBER,
48: P_Operation_Seq_Num NUMBER,
49: P_Resource_Seq_Num IN NUMBER DEFAULT NULL,
50: P_Run_ReqImport IN NUMBER DEFAULT WIP_CONSTANTS.NO);
51:
52: /* CREATE_ADDITIONAL_REQ
53: Create Additional PO requisitions
54:

Line 251: * p_is_scrap_txn Added for bug 4734309: Pass WIP_CONSTANTS.YES when

247: * quantity. This parameter is useful for scrap, unscrap
248: * and overmove case. We should not update all PO/req
249: * associated to the job. Instead, we should update only
250: * the one affected by these transactions
251: * p_is_scrap_txn Added for bug 4734309: Pass WIP_CONSTANTS.YES when
252: * calling from scrap processor. For scrap transactions, only PO/REQs
253: * connected to future operations will be affected.
254: * x_return_status There are 2 possible values
255: * *fnd_api.g_ret_sts_success*