Search Results sys_stub_for_purity_analysis




Overview
Explore in AI Chat

Overview

Within the Oracle E-Business Suite 12.1.1 and 12.2.2 environments, the package SYS.SYS_STUB_FOR_PURITY_ANALYSIS serves a specialized infrastructural rather than business-functional role. It is a system-level stub owned by the SYS schema and classified by the ETRM repository under the generic API classification of OTHER. The package does not implement end-user business logic; instead, it exists to satisfy the dependency and purity requirements imposed by the PL/SQL compiler when other packages reference purity-analysis signatures. Its procedures are declared with pragma directives that communicate read and write access intent to the Pl/SQL compiler, allowing it to validate operations such as function result caching, database trigger restrictions, and SQL statement invocation purity. Because the package is referenced by 545 other packages, it acts as a shared compilation anchor across the EBS data dictionary, ensuring that purity constraints declared by dependent objects can be resolved consistently during compilation, deployment, and runtime execution.

Key Procedures and Functions

The package exposes four documented procedures, each with a declared purity pragma. No parameter lists are documented, and the procedures are not intended for direct invocation.

  • PRDS — Declared with PRAGMA RESTRICT_REFERENCES(prds, wnds, rnps, wnps). It indicates that the routine writes no database state, references no packaged state, and writes no packaged state. It represents the strictest purity profile.
  • PWDS — Declared with PRAGMA RESTRICT_REFERENCES(pwds, rnds, rnps, wnps). It indicates that the routine reads and writes database state while neither reading nor writing packaged state.
  • PRPS — Declared with PRAGMA RESTRICT_REFERENCES(prps, rnds, wnds, wnps). It indicates that the routine reads and writes database state and reads packaged state, but writes no packaged state.
  • PWPS — Declared with PRAGMA RESTRICT_REFERENCES(pwps, rnds, wnds, rnps). It indicates that the routine reads and writes database state and writes packaged state, but reads no packaged state.

Collectively, these four stubs cover the common combinations of read/write behavior against database state (DS) and packaged state (PS), allowing the compiler to resolve purity assertions without requiring the underlying implementation to be materialized.

Tables Accessed

The ETRM metadata documents no tables referenced by this package, whether directly or via APPS synonyms. This is consistent with its role as a purity-analysis stub: the procedures are declarative placeholders whose purpose is to carry pragma restrictions, not to execute SQL. Any table access implied by the purity pragmas (for example, the read/write database state notations in PWDS, PRPS, and PWPS) reflects a declaration of intent rather than an actual DML or query against a specific EBS table. No base tables, views, or synonyms are populated in the dependency record.

Usage Notes

This package is not invoked from Oracle Forms, concurrent programs, or standard EBS application flows. It is a compilation-time artifact. The 545 packages that reference it do so to satisfy purity requirements when their own functions or procedures carry RESTRICT_REFERENCES pragmas or when they are called from SQL, triggers, or function-based indexes. In EBS 12.1.1 and 12.2.2, such references surface during database compilation, patching, and AD utilities runs. Custom developers should not call these procedures directly; doing so yields no functional effect. When a custom package declares purity pragmas and references the stub, the dependency must be preserved so that compilation succeeds. If the stub becomes invalidated or missing, dependent packages may fail to compile with purity-related errors, making this otherwise trivial package operationally significant during upgrades and cloning activities.