APPS.PO_DOCUMENT_UPDATE_GRP dependencies on PO_CHANGES_REC_TYPE

Line 12: -- takes in changes as a PO_CHANGES_REC_TYPE object. This allows the caller to

8: g_module_prefix CONSTANT VARCHAR2(40) := 'po.plsql.' || g_pkg_name || '.';
9:
10: --
11: -- In file version 115.3, added an overloaded update_document procedure that
12: -- takes in changes as a PO_CHANGES_REC_TYPE object. This allows the caller to
13: -- request changes to multiple lines, shipments, and distributions at once.
14:
15: -------------------------------------------------------------------------------
16: --Start of Comments

Line 30: p_changes IN OUT NOCOPY PO_CHANGES_REC_TYPE,

26: PROCEDURE update_document (
27: p_api_version IN NUMBER,
28: p_init_msg_list IN VARCHAR2,
29: x_return_status OUT NOCOPY VARCHAR2,
30: p_changes IN OUT NOCOPY PO_CHANGES_REC_TYPE,
31: p_run_submission_checks IN VARCHAR2,
32: p_launch_approvals_flag IN VARCHAR2,
33: p_buyer_id IN NUMBER,
34: p_update_source IN VARCHAR2,

Line 130: -- as a PO_CHANGES_REC_TYPE object.

126: -- resp_appl_id => 201 );
127: --Notes:
128: -- This procedure is for backward compatibility only. New callers should use
129: -- the overloaded UPDATE_DOCUMENT procedure above, which takes in changes
130: -- as a PO_CHANGES_REC_TYPE object.
131: --End of Comments
132: -------------------------------------------------------------------------------
133: PROCEDURE update_document (
134: p_PO_NUMBER IN VARCHAR2,

Line 195: l_changes PO_CHANGES_REC_TYPE;

191: and po_release_id = p_po_release_id
192: and shipment_num = p_SHIPMENT_NUMBER;
193:
194: l_header_table_name VARCHAR2(30);
195: l_changes PO_CHANGES_REC_TYPE;
196: l_new_shipment_price PO_LINE_LOCATIONS.price_override%TYPE;
197: l_po_header_id PO_HEADERS.po_header_id%TYPE;
198: l_po_release_id PO_RELEASES.po_release_id%TYPE;
199: l_po_line_id PO_LINES.po_line_id%TYPE;

Line 237: -- PO_CHANGES_REC_TYPE object instead of individual procedure arguments.

233:
234: --
235: -- Moved the following logic from the private API (PO_DOCUMENT_UPDATE_PVT)
236: -- to the group API, because the private API now takes changes as a
237: -- PO_CHANGES_REC_TYPE object instead of individual procedure arguments.
238:
239: l_progress := '010';
240:
241: -- Verify that the caller passed in values for all the required parameters.

Line 370: l_changes := PO_CHANGES_REC_TYPE.create_object (

366: RETURN;
367: END IF; -- l_revision_num
368:
369: -- Create an empty change object for this document.
370: l_changes := PO_CHANGES_REC_TYPE.create_object (
371: p_po_header_id => l_po_header_id,
372: p_po_release_id => l_po_release_id
373: );
374:

Line 616: -- now takes changes as a PO_CHANGES_REC_TYPE object, not as individual

612:
613: --
614: -- In file version 115.3, moved this procedure from the private API
615: -- (PO_DOCUMENT_UPDATE_PVT) to the group API, because the private API
616: -- now takes changes as a PO_CHANGES_REC_TYPE object, not as individual
617: -- procedure arguments.
618:
619: -------------------------------------------------------------------------------
620: --Start of Comments