Search Results commit_changes

Overview

APPS.PO_REQS_CONTROL_SV is a server-side PL/SQL package in Oracle EBS Purchasing (Oracle Purchasing / iProcurement) that centralizes document security validation and transactional control for requisitions and purchase orders. In EBS 12.1.1 and 12.2.2 the object is classified in ETRM as an API of type OTHER, meaning it is not a published interface but a shared internal service package invoked by other Oracle-owned packages. Its principal business role is to determine whether a given agent (the acting user or employee) may act on a document instance based on the document type and subtype configuration defined in PO_DOCUMENT_TYPES, and then to persist and commit changes made by the calling transaction. Because access control for requisitions differs from the access control for purchase orders, releases, and related documents, the package branches its logic according to the document type passed by the caller, making it the single enforcement point for document-level security in the requisition and purchasing flow.

Key Procedures and Functions

• VAL_DOC_SECURITY — The core validation routine. It accepts document agent, agent, document type, and document subtype values and returns a Boolean result indicating whether the requesting agent is authorized for the specified document. For requisition document types, the routine evaluates the row in PO_DOCUMENT_TYPES against several mutually exclusive conditions: exact agent match, PUBLIC security level with FULL access, PURCHASING security level with FULL access where the agent is an active PO_AGENTS record (start date to effective end date), and HIERARCHY security level where the agent appears as a superior in PO_EMPLOYEE_HIERARCHIES for the document agent, restricted to the security position structure defined in PO_SYSTEM_PARAMETERS. For all other document types, the routine applies the equivalent PO/release security logic.
• COMMIT_CHANGES — The transaction finalization routine. It performs the commit of pending changes associated with the requisition control operations handled by this package, ensuring that validated document modifications are persisted.
• NAME — Listed as a documented element of the package, representing the package identity/name construct used for internal reference.

Tables Accessed

• PO_DOCUMENT_TYPES — Defines the security_level_code and access_level_code that drive the access decisions in VAL_DOC_SECURITY.
• PO_AGENTS — Supplies agent validity and active date ranges used for the PURCHASING security level check.
• PO_EMPLOYEE_HIERARCHIES — Provides superior relationships for HIERARCHY-level requisition access control.
• PO_SYSTEM_PARAMETERS — Supplies SECURITY_POSITION_STRUCTURE_ID, scoping the hierarchy check to the configured position structure.
• PO_REQUISITION_HEADERS — The requisition header table affected by the calling transaction's changes.
• PO_ACTION_HISTORY — Records action history entries associated with requisition and document activity.
• MTL_SUPPLY — Referenced in the supply/demand handling performed alongside requisition processing.

Usage Notes

PO_REQS_CONTROL_SV is invoked indirectly rather than called by end users. Oracle Forms servicing the Requisition and Purchasing windows, concurrent programs that process requisitions, and other server packages (ETRM records five dependent packages) call VAL_DOC_SECURITY before permitting a user to view or modify a requisition or purchasing document, and call COMMIT_CHANGES to finalize the resulting updates. Custom code should treat the package as an unsupported internal dependency: because it is classified as OTHER rather than a public API, its signature and logic may change between releases. The presence of a defect reference in the source header indicates the security logic has been revised across releases, so any custom extension that relies on this package should be revalidated when applying EBS patch levels.