Search Results po_reqs_control_sv




Overview
Explore in AI Chat

Overview

The APPS.PO_REQS_CONTROL_SV package is a server-side (SV) PL/SQL control package within the Oracle E-Business Suite Purchasing module. It encapsulates the business logic required to enforce document control and security rules over requisition records. In Oracle EBS 12.1.1 and 12.2.2, requisitions flow through a series of lifecycle events—submission, approval, amendment, cancellation, and receipt—and each transition must be validated against organizational security, document type rules, and system parameters. The package centralizes these validations so that both standard Purchasing forms and the underlying public APIs invoke a single, consistent set of checks.

The object is registered in APPS with a status of VALID and is classified as an API of type OTHER, indicating that it is primarily an internal utility rather than a formally published external interface. Its documented surface comprises eight procedures and functions, of which three are exposed by name: NAME, VAL_DOC_SECURITY, and COMMIT_CHANGES. The package references the SYS.STANDARD package, reflecting its PL/SQL origin, and is referenced by a broad set of Purchasing components, underscoring its role as a shared control layer.

Key Procedures and Functions

The documented callable units serve the following purposes:

  • NAME — A helper that returns the package or object identity string used internally for diagnostics and error reporting.
  • VAL_DOC_SECURITY — The principal validation routine. It evaluates whether the current user or operating unit is authorized to act upon a given requisition under document security rules. Callers rely on this procedure to confirm that a requisition falls within the security profile before permitting approval, amendment, or cancellation actions.
  • COMMIT_CHANGES — Persists pending modifications accumulated during the control/validation cycle, issuing the transactional COMMIT so that requisition state changes and associated action history records become durable.

The remaining five routines are documented as existing within the package but are not individually named in the metadata; they support the same control and validation workflow. No parameter lists are asserted here, as the metadata does not define them; integrators should inspect the package specification PO_REQS_CONTROL_SV in the database for exact signatures.

Tables Accessed

The package operates across the following tables via APPS synonyms:

  • PO_REQUISITION_HEADERS — The primary requisition record whose control status and security attributes are validated and updated.
  • PO_ACTION_HISTORY — Captures the audit trail of actions (approve, cancel, amend) applied to the requisition.
  • PO_DOCUMENT_TYPES — Supplies document type definitions and their associated control rules.
  • PO_AGENTS — Provides buyer/agent information used in security and authority checks.
  • PO_SYSTEM_PARAMETERS — Delivers Purchasing system-level settings that influence control behavior.
  • MTL_SUPPLY — Consulted for supply/demand information related to the requisition line.

Usage Notes

PO_REQS_CONTROL_SV is not typically invoked directly by end users. It is called by higher-level Purchasing packages including POR_AMENDMENT_PKG, POR_RCV_ORD_SV, PO_CONTROL_ACTION_VALIDATIONS, PO_DOCUMENT_CONTROL_PVT, PO_REQ_DOCUMENT_CANCEL_PVT, and by itself. These callers correspond to the Requisitions form, amendment processing, receiving, and document cancellation flows. Custom extensions that modify requisition control behavior should reuse this package rather than reimplementing validation, to preserve consistency with Oracle's security enforcement. Because it is classified as OTHER and is internal, Oracle does not guarantee backward compatibility of its signatures across releases; custom code should be validated during 12.1.1-to-12.2.2 upgrades.