Search Results remove_plip




Overview
Explore in AI Chat

Overview

PQH_GSP_GRD_STEP_REMOVE is a PL/SQL package owned by the APPS schema in Oracle E-Business Suite, classified under the ETRM as an "OTHER" API. Its name and declared procedures indicate that it belongs to the Oracle Human Resources grade/step and pay scale configuration area — the PQH namespace is used by the HR/payroll performance and grade-step frameworks. The package provides programmatic cleanup ("remove" and "purge") logic for records created during a grade step configuration or copy transaction. It is defined with AUTHID CURRENT_USER, meaning its SQL executes with the privileges of the calling user rather than the defining APPS user, so the invoking session must have the necessary object privileges.

The header ($Header: pqgspsde.pkh ... 2008/07/28) confirms this is the package specification (the .pkh extension). The companion body that implements the listed procedures is not part of the documented excerpt, but the specification enumerates the full public interface.

Key Procedures and Functions

  • GET_OVN — a function that returns a NUMBER, presumably the object version number associated with a copy entity result row, used for optimistic locking or change detection.
  • GET_DML_OPERATION — a function returning VARCHAR that reports the DML operation type (e.g., INSERT, UPDATE) associated with a given copy entity result.
  • PURGE_PAY_SCALE — removes a pay scale definition tied to an OPT result.
  • PURGE_OPT_ABR_HRRATE_CRRATE — purges grade step standard rates together with criteria rates (ABR, HR rate, CR rate) for an OPT result.
  • REMOVE_ELIG_PROFILE — removes the eligibility profile associated with a copy entity transaction/result.
  • REMOVE_OPT — removes the OPT (grade step / organization pay plan) record itself.
  • REMOVE_OIPL_STEP_FLAVOUR — removes a step-level OIPL (which likely represents a step flavor such as grade or point variants).
  • REMOVE_OIPL_POINT_FLAVOUR — removes the point-level OIPL flavor counterpart.
  • REMOVE_OIPL — removes the OIPL record generally; it exposes a control parameter allowing the caller to indicate whether the underlying OPT is also removed.
  • REMOVE_PLIP — this is the procedure the user searched for ("remove_plip"). It performs removal of PLIP (a pay-plan or grade-step link record) for a given copy entity transaction/result and effective date. It is invoked alongside the other remove procedures as part of the broader deletion of a copied grade-step configuration.
  • UNLINK_OPT_ABR_HRRATE_CRRATE — the inverse operation to PURGE_OPT_ABR_HRRATE_CRRATE; it unlinks (rather than deletes) grade step standard and criteria rates for an OPT result.

No parameter lists are invented here; documented procedures accept a copy entity transaction identifier, a copy entity result identifier, an OPT result identifier, and/or an effective date as reflected in the header.

Tables Accessed

The only table documented via APPS synonyms is BEN_COPY_ENTITY_RESULTS, a Benefits/HR copy framework table that stores the outcome of each copy entity transaction and the entity results produced. The package reads this table to resolve the OVN and DML operation (GET_OVN, GET_DML_OPERATION) and uses the result identifiers to drive the remove/purge operations. The underlying HR tables (pay scale, grade step rate, eligibility profile, OPT, OIPL and PLIP) acted upon by the remove procedures are not listed in the ETRM excerpt, but each procedure name directly maps to one of these configuration entities.

Usage Notes

This package is an internal HR setup utility rather than an end-user API. It is typically invoked during grade-step or pay-scale copy processing, when a previously copied configuration must be rolled back or a failed/stale copy entity result must be cleaned up. Callers supply the copy entity transaction ID, copy entity result ID, and an effective date, and the appropriate remove or purge procedure is executed. The package is referenced by one other package, indicating it is called from within the grade-step copy framework rather than directly by a form or concurrent program. Because it uses AUTHID CURRENT_USER and manipulates configuration data, it should be invoked only by privileged setup users or by the owning framework packages, and always within a controlled transaction so partial removals can be rolled back if necessary.