Search Results pqp_exr_api




Overview
Explore in AI Chat

Overview

PQP_EXR_API is a public PL/SQL API package owned by the APPS schema in Oracle E-Business Labor Distribution and Oracle Projects resource management. Its name reflects its role as the application programming interface for "Exception Reports" (EXR). The package exposes a controlled, supported entry point for creating, maintaining, and removing exception report definitions that drive the exception-based review of payroll, time, and resource transactions. Exception reports allow implementers and administrators to define criteria that flag transactions failing validation or falling outside defined tolerances, supporting audit and correction workflows.

The package is classified in the ETRM metadata as an API object, confirming it is intended to be called programmatically rather than serving as an internal helper. It depends on HR_API, the Oracle HRMS common API utility package used across HRMS-family products for standard operations such as error handling and Object Version Number management. This dependency confirms the package follows HRMS API conventions and is embedded in the Oracle Time and Labor / resource management product group (the PQP prefix).

Key Procedures and Functions

The metadata documents three public procedures:

  • CREATE_EXCEPTION_REPORT — Inserts a new exception report definition into the repository. Invoked when a new reporting rule must be registered.
  • UPDATE_EXCEPTION_REPORT — Modifies an existing exception report definition, such as changing criteria or descriptive attributes.
  • DELETE_EXCEPTION_REPORT — Removes a previously defined exception report from the repository.

Specific parameter lists are not published in the supplied metadata and are deliberately not reproduced here; callers should consult the package specification in the database or the Oracle HRMS API documentation for exact signatures.

Tables Accessed

The documented table accessed via APPS synonyms is PQP_EXCEPTION_REPORTS. This is the base table storing exception report definitions. CREATE_EXCEPTION_REPORT inserts rows, UPDATE_EXCEPTION_REPORT modifies them, and DELETE_EXCEPTION_REPORT removes them. Supporting tables may be touched indirectly through HR_API and standard mechanisms (for example, WHO columns and Object Version Number handling), but PQP_EXCEPTION_REPORTS is the primary documented target.

Usage Notes

The package is referenced by PQP_ERT_SHD, PQP_EXR_SWI, and by its own body, indicating it is used both by a shadow (SHD) table maintenance package and by a service/utility wrapper (SWI). Typical invocation paths are:

  • Oracle Forms or OAF pages presenting exception report setup, where the form calls the API rather than performing direct DML.
  • Concurrent programs or batch setup scripts that seed exception report definitions during implementation.
  • Custom PL/SQL that must register or retire exception reports as part of a configuration migration.

Because the package is a supported API, direct DML against PQP_EXCEPTION_REPORTS should be avoided. Callers should invoke these procedures within a properly committed transaction and rely on the API's internal validation and error signaling to preserve data integrity. As with other HRMS-style APIs, the procedures are expected to populate standard WHO audit columns and raise exceptions on validation failure, so calling code should include error handling.