[Home] [Help]
25: -- 1. The ID input tables p_req_header_id, p_req_line_id should be of same size.
26: -- 2. Each entity specifies a required field Requisition Header ID
27: -- Note that the Line is optional but a Header is required.
28: --Notes:
29: -- Detailed comments maintained in PVT Package Body PO_REQ_DOCUMENT_CHECKS_PVT.req_status_check
30: --End of Comments
31: -------------------------------------------------------------------------------
32: PROCEDURE validate_status_check_inputs (
33: p_api_version IN NUMBER,
111: -- Group procedure to find the status of a Requisition
112: -- This validates inputs and calls the private procedure req_status_check
113: --Notes:
114: -- For details on validations, refer to Group Procedure validate_status_check_inputs
115: -- Detailed comments maintained in PVT Package Body PO_REQ_DOCUMENT_CHECKS_PVT.req_status_check
116: --End of Comments
117: -------------------------------------------------------------------------------
118: PROCEDURE req_status_check (
119: p_api_version IN NUMBER,
156: x_msg_data => x_msg_data);
157:
158: --Call the private procedure to actually do req status check
159: l_progress := '020';
160: PO_REQ_DOCUMENT_CHECKS_PVT.req_status_check(
161: p_api_version => p_api_version,
162: p_req_header_id => p_req_header_id,
163: p_req_line_id => l_req_line_id,
164: p_req_distribution_id => l_req_distribution_id,
198: -- Finds the status of a Purchase Order or a Release
199: -- This is a convenience procedure for a single entity and takes in scalar input IDs
200: -- This in turn calls the group procedure req_status_check that takes Table input IDs
201: --Notes:
202: -- Detailed comments maintained in PVT Package Body PO_REQ_DOCUMENT_CHECKS_PVT.req_status_check
203: --End of Comments
204: -------------------------------------------------------------------------------
205: PROCEDURE req_status_check (
206: p_api_version IN NUMBER,