Search Results submit_ireqchange

Overview

APPS.PO_RCO_VALIDATION_GRP is a grouping (GRP) package in the Oracle E-Business Suite Purchasing module that centralizes validation and save logic for requisition change and cancellation processing, including changes originating from outside Purchasing such as Sales Orders. The package body carries the header identifier POXGRCVB.pls 120.16.12020000.3, confirming its delivery as part of the PO patch family through the 12.1.1 and 12.2.2 releases. Its documented API classification of GRP indicates that it aggregates a family of related validation and persistence routines rather than exposing a single transactional interface.

The package serves two broad business purposes. First, it answers "can this happen?" questions — whether a requisition, requisition line, or any line on a requisition may be cancelled, changed, or withdrawn, taking into account whether downstream purchasing documents already reference the line. Second, it provides the save and submit entry points that commit requisition change and cancellation actions, including the specialized path invoked when a Sales Order drives the cancellation. The user search term update_reqcancel_from_so maps directly to the documented procedure UPDATE_REQCANCEL_FROM_SO, which is the Sales Order-facing variant of the standard cancellation routine.

Key Procedures and Functions

Validation functions: IS_REQ_CANCELLABLE and IS_REQLINE_CANCELLABLE determine whether a requisition header or an individual requisition line can be cancelled. The sample source shows IS_REQ_CANCELLABLE iterating the requisition lines cursor, checking for a populated line_location_id (a signal that a purchasing document exists, per Bug6747949) and delegating each line to IS_REQLINE_CANCELLABLE. IS_REQ_CHANGEABLE and IS_REQ_LINE_CHANGEABLE perform the parallel check for modification rather than cancellation. IS_ANY_LINE_WITHDRAWABLE establishes whether any line on the requisition may be withdrawn. IS_COMPLEX_WORK_ORDER and IS_ON_COMPLEX_WORK_ORDER resolve whether the requisition is associated with a complex work order, which affects the permissible actions.

Save and submit routines: SAVE_REQCHANGE and SAVE_REQCANCEL persist header-level change and cancellation actions, while SAVE_IREQCHANGE and SAVE_IREQCANCEL handle the corresponding internal requisition flows; SUBMIT_REQCHANGE, SUBMIT_REQCANCEL, SUBMIT_IREQCHANGE, and SUBMIT_IREQCANCEL drive the submission of those actions. The Sales Order integration procedures UPDATE_REQCANCEL_FROM_SO and UPDATE_REQCHANGE_FROM_SO apply cancellation and change updates when the originating demand comes from Order Management. CALCULATE_DISTTAX derives distribution-level tax amounts. GET_PREPARER_NAME returns the preparer associated with the requisition.

Tables Accessed

The package operates primarily against PO_REQUISITION_LINES_ALL, the base requisition line entity. IS_REQ_CANCELLABLE reads requisition_line_id and line_location_id from this table to establish the line set being evaluated and to detect lines already consumed by a purchasing document. Write paths for the save and update routines likewise target the requisition line records through the APPS synonym. DBMS_SQL indicates dynamic SQL usage, permitting runtime-constructed statements. PLITBLM is the standard EBS PL/SQL index-by table type used for array-style PL/SQL structures within the package's internal processing.

Usage Notes

PO_RCO_VALIDATION_GRP is invoked from the Purchasing requisition inquiry and maintenance forms, from the Autocreate and change-order related flows, and from Order Management when Sales Order activity triggers requisition cancellation or change. Because it is a GRP package, individual procedures are called rather than the package being driven as a single concurrent program. The metadata notes that it is referenced by one other package, indicating a deliberate layering relationship in which a higher-level API delegates validation and save work here. Customizations and extensions should call the appropriate IS_* validation function before invoking a SAVE_* or SUBMIT_* routine, so that downstream document dependencies are honored exactly as standard EBS behavior requires. Debug tracing is available through PO_DEBUG when the debug profile option is enabled, and the package writes to the standard PO logging infrastructure via PO_LOG.