35: -- Indicates API return status as 'S', 'E' or 'U'.
36: --x_req_status_rec
37: -- Table x_req_status_rec.updateable_flag will be 'Y' or 'N' for each input entity
38: --x_msg_count
39: -- The number of messages put into FND Message Stack by this API
40: --x_msg_data
41: -- First message put into FND Message Stack by this API
42: --Notes:
43: -- The implementation of updatable_flag involves a fake "update dual" statement to
37: -- Table x_req_status_rec.updateable_flag will be 'Y' or 'N' for each input entity
38: --x_msg_count
39: -- The number of messages put into FND Message Stack by this API
40: --x_msg_data
41: -- First message put into FND Message Stack by this API
42: --Notes:
43: -- The implementation of updatable_flag involves a fake "update dual" statement to
44: -- optimize performance.
45: --End of Comments
186: -- Indicates API return status as 'S', 'E' or 'U'.
187: --x_req_status_rec
188: -- Table x_req_status_rec.updateable_flag will be 'Y' or 'N' for each input entity
189: --x_msg_count
190: -- The number of messages put into FND Message Stack by this API
191: --x_msg_data
192: -- First message put into FND Message Stack by this API
193: --Notes:
194: -- The implementation of reservable_flag involves a fake "update dual" statement to
188: -- Table x_req_status_rec.updateable_flag will be 'Y' or 'N' for each input entity
189: --x_msg_count
190: -- The number of messages put into FND Message Stack by this API
191: --x_msg_data
192: -- First message put into FND Message Stack by this API
193: --Notes:
194: -- The implementation of reservable_flag involves a fake "update dual" statement to
195: -- optimize performance.
196: --End of Comments
322: -- Indicates API return status as 'S', 'E' or 'U'.
323: --x_req_status_rec
324: -- Table x_req_status_rec.updateable_flag will be 'Y' or 'N' for each input entity
325: --x_msg_count
326: -- The number of messages put into FND Message Stack by this API
327: --x_msg_data
328: -- First message put into FND Message Stack by this API
329: --Notes:
330: -- The implementation of unreservable_flag involves a fake "update dual" statement to
324: -- Table x_req_status_rec.updateable_flag will be 'Y' or 'N' for each input entity
325: --x_msg_count
326: -- The number of messages put into FND Message Stack by this API
327: --x_msg_data
328: -- First message put into FND Message Stack by this API
329: --Notes:
330: -- The implementation of unreservable_flag involves a fake "update dual" statement to
331: -- optimize performance.
332: --End of Comments
458: -- Indicates API return status as 'S', 'E' or 'U'.
459: --x_req_status_rec
460: -- The various status fields would have the PO/Rel Line/Shipment status values
461: --x_msg_count
462: -- The number of messages put into FND Message Stack by this API
463: --x_msg_data
464: -- First message put into FND Message Stack by this API
465: --End of Comments
466: -------------------------------------------------------------------------------
460: -- The various status fields would have the PO/Rel Line/Shipment status values
461: --x_msg_count
462: -- The number of messages put into FND Message Stack by this API
463: --x_msg_data
464: -- First message put into FND Message Stack by this API
465: --End of Comments
466: -------------------------------------------------------------------------------
467:
468: PROCEDURE get_status (
598: -- the updateable_flag would have 'Y' or 'N' for each entity in the Table
599: -- If p_mode contains GET_APPROVAL_STATUS,
600: -- various status fields for Header/Line like authorization_status, cancel_flag
601: --x_msg_count
602: -- The number of messages put into FND Message Stack by this API
603: --x_msg_data
604: -- First message put into FND Message Stack by this API
605: --Testing:
606: -- All the input table parameters should have the exact same length.
600: -- various status fields for Header/Line like authorization_status, cancel_flag
601: --x_msg_count
602: -- The number of messages put into FND Message Stack by this API
603: --x_msg_data
604: -- First message put into FND Message Stack by this API
605: --Testing:
606: -- All the input table parameters should have the exact same length.
607: -- Call the API when 1. only Requisition Header Exist, and 2. Line also exists
608: --End of Comments
730:
731: l_progress := '050';
732:
733: IF x_return_status is null THEN -- no valid check status request specified
734: FND_MESSAGE.set_name('PO', 'PO_STATCHK_GENERAL_ERROR');
735: FND_MESSAGE.set_token('ERROR_TEXT', 'Invalid p_mode: ' || p_mode);
736: FND_MSG_PUB.Add;
737: RAISE FND_API.G_EXC_ERROR;
738: END IF;
731: l_progress := '050';
732:
733: IF x_return_status is null THEN -- no valid check status request specified
734: FND_MESSAGE.set_name('PO', 'PO_STATCHK_GENERAL_ERROR');
735: FND_MESSAGE.set_token('ERROR_TEXT', 'Invalid p_mode: ' || p_mode);
736: FND_MSG_PUB.Add;
737: RAISE FND_API.G_EXC_ERROR;
738: END IF;
739: