Search Results po_chg_request_seq
Overview
PO_CHANGE_RESPONSE_PVT is a private PL/SQL package body in the APPS schema that encapsulates the core business logic for processing supplier responses to Oracle Purchasing change orders. When a buyer issues a change order against a purchase order, release, line, or shipment, the supplier can respond by accepting, rejecting, or partially accepting the change. This package implements the validation, workflow notification, and data manipulation required to record that response against the affected purchasing document. Because it is classified as a private (PVT) API, it is intended for internal consumption by Oracle Purchasing forms, workflow activities, and other public APIs rather than for direct customer invocation. The package draws on the shared FND_API, FND_MSG_PUB, and WF_ENGINE infrastructure to perform error stacking, message retrieval, and workflow item attribute updates, and it depends on the underlying change request data model rooted in PO_CHANGE_REQUESTS.
Key Procedures and Functions
- CHECKPARTIALACK — Evaluates whether a supplier response constitutes a partial acknowledgement of the change order, allowing the application to distinguish full acceptance from an acceptance that applies to only a subset of changed lines or distributions.
- CHECKCHANGEPENDING — Determines whether a change request is still pending a supplier response, used to guard subsequent processing and to keep document and workflow status consistent.
- GET_DISTRIBUTION_COUNT — Returns the count of distributions associated with the affected purchasing document lines, supporting partial acknowledgement evaluation and downstream data updates.
- MOVECHANGETOPO — Applies the accepted change values from the change request onto the purchase order, moving change data into the PO document tables so the accepted revision becomes the effective document state.
- UPDATE_CHANGE_RESPONSE — Persists the supplier's response (accept, reject, or partial accept) against the change request record and related purchasing entities.
- ROLL_BACK_ACCEPTANCE — Reverses a previously accepted change response, restoring prior document values and returning the change request to its pending state where appropriate.
Tables Accessed
The package operates across the central Purchasing document tables and the change request model. PO_CHANGE_REQUESTS stores the change request header and response state that this package reads and updates, while PO_CHG_REQUEST_SEQ supplies the sequence used to generate change request identifiers. PO_HEADERS_ALL, PO_LINE_LOCATIONS_ALL, PO_RELEASES_ALL, and the record type structures PO_DISTRIBUTIONS / PO_DISTRIBUTIONS_ALL are read and modified as change values are moved onto the document via MOVECHANGETOPO and rolled back via ROLL_BACK_ACCEPTANCE. PO_DOCUMENT_TYPES_ALL_B identifies the document type being changed, and PLITBLM is used for PL/SQL table manipulation during bulk processing. The package also references FND_API, FND_MSG_PUB, WF_ENGINE, and WF_ITEM for API error handling and workflow notification, and it coordinates with PO_ACKNOWLEDGE_PO_PVT and PO_DOCUMENT_UPDATE_GRP to complete acknowledgement and document update processing.
Usage Notes
PO_CHANGE_RESPONSE_PVT is invoked indirectly through the Oracle Purchasing change order and supplier acknowledgement flows. Supplier responses captured through iSupplier Portal or the Purchasing change order screens are routed into UPDATE_CHANGE_RESPONSE, which then calls the internal validation and document update routines. Workflow-driven background processing invokes CHECKCHANGEPENDING and CHECKPARTIALACK to determine routing outcomes, and ROLL_BACK_ACCEPTANCE supports reversal scenarios when an acceptance must be undone. Because the package is private and not referenced by any other database object externally, customizations should call the supported public acknowledgement APIs, such as PO_ACKNOWLEDGE_PO_PVT, rather than this package directly. The PO_CHG_REQUEST_SEQ sequence should always be used to generate change request keys to maintain referential consistency with records this package maintains.
-
SEQUENCE: PO.PO_CHG_REQUEST_SEQ
12.1.1
owner:PO, object_type:SEQUENCE, object_name:PO_CHG_REQUEST_SEQ, status:VALID,
-
SEQUENCE: PO.PO_CHG_REQUEST_SEQ
12.2.2
owner:PO, object_type:SEQUENCE, object_name:PO_CHG_REQUEST_SEQ, status:VALID,
-
SYNONYM: APPS.PO_CHG_REQUEST_SEQ
12.2.2
owner:APPS, object_type:SYNONYM, object_name:PO_CHG_REQUEST_SEQ, status:VALID,
-
SYNONYM: APPS.PO_CHG_REQUEST_SEQ
12.1.1
owner:APPS, object_type:SYNONYM, object_name:PO_CHG_REQUEST_SEQ, status:VALID,
-
PACKAGE BODY: APPS.PO_CHANGE_RESPONSE_PVT
12.1.1
owner:APPS, object_type:PACKAGE BODY, object_name:PO_CHANGE_RESPONSE_PVT, status:VALID,
-
12.1.1 DBA Data
12.1.1
-
12.1.1 DBA Data
12.1.1
-
12.2.2 DBA Data
12.2.2
-
PACKAGE BODY: APPS.PO_CHANGE_RESPONSE_PVT
12.2.2
owner:APPS, object_type:PACKAGE BODY, object_name:PO_CHANGE_RESPONSE_PVT, status:VALID,
-
12.2.2 DBA Data
12.2.2
-
PACKAGE BODY: APPS.PO_CHG_REQUEST_PVT
12.1.1
owner:APPS, object_type:PACKAGE BODY, object_name:PO_CHG_REQUEST_PVT, status:VALID,
-
PACKAGE BODY: APPS.PO_CHG_REQUEST_PVT
12.2.2
owner:APPS, object_type:PACKAGE BODY, object_name:PO_CHG_REQUEST_PVT, status:VALID,
-
PACKAGE BODY: APPS.PO_RCO_VALIDATION_PVT
12.1.1
owner:APPS, object_type:PACKAGE BODY, object_name:PO_RCO_VALIDATION_PVT, status:VALID,
-
PACKAGE BODY: APPS.PO_RCO_VALIDATION_PVT
12.2.2
owner:APPS, object_type:PACKAGE BODY, object_name:PO_RCO_VALIDATION_PVT, status:VALID,
-
12.1.1 DBA Data
12.1.1
-
12.2.2 DBA Data
12.2.2
-
APPS.PO_CHG_REQUEST_PVT dependencies on PO_CHG_REQUEST_SEQ
12.1.1
-
APPS.PO_CHANGE_RESPONSE_PVT dependencies on PO_CHG_REQUEST_SEQ
12.2.2
-
APPS.PO_RCO_VALIDATION_PVT dependencies on PO_CHG_REQUEST_SEQ
12.2.2
-
APPS.PO_CHG_REQUEST_PVT dependencies on PO_CHG_REQUEST_SEQ
12.2.2
-
APPS.PO_RCO_VALIDATION_PVT dependencies on PO_CHG_REQUEST_SEQ
12.1.1
-
APPS.PO_CHANGE_RESPONSE_PVT dependencies on PO_CHG_REQUEST_SEQ
12.1.1
-
12.2.2 DBA Data
12.2.2
-
12.1.1 DBA Data
12.1.1