Search Results per_pyp_shd




Overview
Explore in AI Chat

Overview

PER_PYP_SHD is a shadow (suffix "SHD") package body in the Oracle EBS HR/Payroll module, owned by the APPS schema and classified under the generic API classification OTHER. Its name derives from "PER" (Human Resources) and "PYP" (Pay Proposal), and the "_SHD" convention indicates that the package operates alongside a primary package, typically PER_PYP, to maintain a mirrored or historical copy of Pay Proposal records. In Oracle EBS 12.1.1 and 12.2.2, shadow packages are used to persist a redundant or audit-oriented version of a business entity so that downstream processes, reconciliation reports, or upgrade utilities can compare current and prior states without disturbing the operational table.

The object is documented as VALID with five procedures and references to the HR_API and HR_UTILITY utility packages. It is not referenced by any other database object, indicating that it is invoked directly or through the primary Pay Proposal package rather than being called as part of a broader dependency chain.

Key Procedures and Functions

  • RETURN_API_DML_STATUS — Returns the DML status of the most recent API operation, a standard pattern in Oracle HRMS APIs used to signal whether the last insert, update, or delete succeeded.
  • CONSTRAINT_ERROR — Handles or raises constraint violations encountered while writing to Pay Proposal shadow records, allowing callers to distinguish integrity errors from other failures.
  • API_UPDATING — Flags or tracks that an API-driven update is in progress, preventing recursive or conflicting modifications to the shadow data.
  • LCK — Provides row-level locking support so that concurrent sessions cannot simultaneously modify the same shadow Pay Proposal record.
  • CONVERT_ARGS — Converts or normalizes arguments passed into the shadow package, aligning the calling interface of PER_PYP_SHD with the primary Pay Proposal API.

No parameter lists are documented for these units; descriptions are limited to their evident API-support roles.

Tables Accessed

  • PER_PAY_PROPOSALS — The primary Pay Proposal entity. PER_PYP_SHD reads and writes this table to reflect proposal state changes into its shadow processing logic.
  • ALL_CONSTRAINTS — The data dictionary view of constraint definitions, queried to validate constraint behavior before applying DML, typically within CONSTRAINT_ERROR handling.

Both are accessed through APPS synonyms, consistent with standard EBS schema conventions.

Usage Notes

PER_PYP_SHD is not referenced by any other database object, so it is not part of an automated dependency chain. It is typically invoked from the Pay Proposal maintenance forms, from Concurrent Manager programs that reconcile Pay Proposal data, or from custom PL/SQL that must maintain shadow Pay Proposal records in step with the primary entity. Because it depends on HR_API and HR_UTILITY, callers should ensure those packages are valid in the target environment. In upgrades between 12.1.1 and 12.2.2, the package should be reviewed for compliance with the online patching editioning model introduced in 12.2, though its OTHER classification and lack of inbound references limit its exposure.