Search Results is_internal_line_changeable
Overview
PO_RCO_VALIDATION_PVT is a private (PVT-classified) PL/SQL package in the APPS schema that provides the validation and persistence layer for the Requisition Change Order (RCO) flow in Oracle E-Business Suite Purchasing. Its name reflects its role: Purchase Order – Requisition Change Order Validation. The package encapsulates the business rules that determine whether a requisition line, internal requisition line, or sales-order-linked line may be changed or cancelled, and it performs the resulting save and submit operations against the Purchasing requisition change tables.
In EBS 12.1.1 and 12.2.2, requisition changes and cancellations flow through a set of interface tables and change-request records rather than direct updates to the requisition. PO_RCO_VALIDATION_PVT centralizes the eligibility checks for that process, applying sourcing, work-order, and complex work-order considerations, and it records validated change data before it is submitted to the change-request workflow. Because the package is classified as PVT, it is an internal implementation unit: it is not a supported public API, and its procedures are intended for consumption by the Purchasing change-order programs, group, and workflow packages that call it.
Key Procedures and Functions
The documented interface exposes 24 procedures and functions, grouped functionally as follows.
- Change/cancel eligibility checks: IS_REQ_LINE_CHANGEABLE, IS_REQ_LINE_CANCELLABLE, IS_INTERNAL_LINE_CHANGEABLE, IS_INTERNAL_LINE_CANCELLABLE, and IS_SO_LINE_CANCELLABLE evaluate whether a given requisition, internal requisition, or sales-order line may be modified or cancelled. IS_ON_COMPLEX_WORK_ORDER and IS_COMPLEX_WORK_ORDER support work-order-related eligibility logic.
- Save operations: SAVE_REQCHANGE, SAVE_REQCANCEL, SAVE_IREQCHANGE, and SAVE_IREQCANCEL persist validated change and cancellation records for standard and internal requisitions into the change-request staging tables.
- Submit operations: SUBMIT_REQCHANGE, SUBMIT_REQCANCEL, SUBMIT_IREQCHANGE, and SUBMIT_IREQCANCEL initiate the change or cancellation request, moving the validated records into the change-request workflow.
- Sourcing/OE integration: UPDATE_REQCANCEL_FROM_SO and UPDATE_REQCHANGE_FROM_SO synchronize requisition change and cancellation data originating from Oracle Order Management sales orders.
- Validation and support utilities: VALIDATE_INTERNAL_REQ_CHANGES performs bulk validation of internal requisition change records, and GET_PREPARER_NAME derives the preparer name associated with a change request. CALCULATE_DISTTAX supports distribution tax calculation as part of the change flow.
Tables Accessed
The package reads and writes Purchasing and related Order Management tables through APPS synonyms. Core Purchasing tables include PO_CHANGE_REQUESTS (the change-request records themselves), PO_DISTRIBUTIONS and PO_DISTRIBUTIONS_ALL (distribution-level tax and charge detail), PO_HEADERS_ALL, PO_LINES_ALL, PO_LINE_LOCATIONS, and PO_LINE_LOCATIONS_ALL (document, line, and shipment/price reference data), and PO_CHG_REQUEST_SEQ (primary key sequencing for change requests). PO_ENCUMBRANCE_GT is used in the change/cancel accounting context. POR_NONCAT_TEMPLATES_ALL_B supplies non-catalog template data.
Order Management integration relies on OE_ORDER_HEADERS_ALL, OE_ORDER_LINES_ALL, and OE_HEADERS_IFACE_ALL to synchronize sales-order-driven requisition changes. Financial and accounting validation uses FINANCIALS_SYSTEM_PARAMETERS and GL_CODE_COMBINATIONS. The package also references PO_REQ_CANCEL_TABLE, PO_REQ_CHANGE_TABLE, and PO_REQ_CHANGE_ERR_TABLE for cancellation, change, and error staging.
Usage Notes
This package is invoked indirectly rather than called by end users or custom code. It depends on the PO_RCO_VALIDATION_GRP package group and is referenced by POS_SCO_TOLERANCE_PVT, PO_REQCHANGEREQUESTWF_PVT, and by itself. In practice, it is exercised when users modify or cancel requisitions from the Purchasing Requisitions form (including sales-order-sourced requisitions) and when the Requisition Change Request workflow runs. The save procedures stage validated data, the submit procedures drive the workflow, and the validation procedures gate the operation. Because PO_RCO_VALIDATION_PVT is a private package in the APPS schema, customizations should not call it directly; supported alternatives are the public Requisition APIs and the standard change-request forms and concurrent programs.