Search Results remove_oipl_step_flavour

Overview

PQH_GSP_GRD_STEP_REMOVE is an Oracle EBS PL/SQL package owned by the APPS schema and classified under the ETRM as an "OTHER" API. Its header identifies an AUTHID CURRENT_USER declaration, and the source carries the revision string pqgspsde.pkh 120.0.12010000.1, dated 2008/07/28. The package belongs to the Public Sector/HR grade-step and pay-scale lineage (the PQH prefix family), and its business purpose is the controlled removal or rollback of grade step, grade point, and pay scale configuration data that was previously created or copied into an entity.

The procedures operate against a "copy entity" model, in which a transaction identifier (p_Copy_Entity_txn_Id) and a result identifier (p_Copy_Entity_Result_Id) track the outcome of a data-copy or configuration-change operation. The package provides the inverse of that copy: it purges or unlinks the dependent rows — pay scales, OPT/OPTION records, eligibility profiles, and standard and criteria rates — so that a grade step or pay scale definition can be removed without leaving orphaned or inconsistent configuration. This makes the package a cleanup and rollback utility in the grade-step/pay-scale maintenance flow rather than a primary entry-point API.

Key Procedures and Functions

The package exposes eleven documented procedures and functions:

• GET_OVN — function returning a Number; resolves the object version number for a given copy entity result.
• GET_DML_OPERATION — function returning a Varchar; determines the DML operation associated with the copy entity result.
• PURGE_PAY_SCALE — procedure that removes a pay scale, taking an OPT result identifier, an effective date, and a copy entity transaction identifier.
• PURGE_OPT_ABR_HRRATE_CRRATE — procedure that purges grade step standard rates and criteria rates for an OPT result, transaction, and effective date.
• REMOVE_ELIG_PROFILE — procedure that removes the eligibility profile tied to a copy entity transaction and result.
• REMOVE_OPT — procedure that removes an OPT record for a transaction, result, and effective date.
• REMOVE_OIPL_STEP_FLAVOUR — procedure that performs the STEP-flavoured OIPL removal, accepting a p_remove_opt flag defaulting to 'Y'.
• REMOVE_OIPL_POINT_FLAVOUR — procedure that performs the POINT-flavoured OIPL removal.
• REMOVE_OIPL — procedure that removes an OPTION/OPTION-line association, accepting the same p_remove_opt flag defaulting to 'Y'.
• REMOVE_PLIP — procedure that removes the pay-scale/plan line association for a transaction, result, and effective date.
• UNLINK_OPT_ABR_HRRATE_CRRATE — procedure that unlinks (rather than purges) grade step standard and criteria rates.

The two flavours of OIPL removal indicate that grade steps and grade points are handled by distinct code paths, with the p_remove_opt parameter allowing callers to control whether the underlying OPT record is also removed.

Tables Accessed

The only documented table referenced through APPS synonyms is BEN_COPY_ENTITY_RESULTS. This is the copy entity results table, and the package reads it to obtain the object version number and DML operation (via GET_OVN and GET_DML_OPERATION) and to correlate the transaction and result identifiers used throughout the removal procedures. Write activity against this table is implied by the rollback nature of the package. The rate, pay scale, eligibility profile, OPT, OIPL, and PLIP structures manipulated by the remaining procedures are accessed through additional APPS synonyms not enumerated in the supplied metadata.

Usage Notes

PQH_GSP_GRD_STEP_REMOVE is a back-end utility. It is not intended as a public integration API but is invoked internally by Oracle HRMS/Public Sector grade-step and pay-scale processing — typically during data-copy rollback or configuration cleanup initiated from the application. Because of the AUTHID CURRENT_USER declaration, callers execute with their own privileges against the APPS synonyms, so grants to APPS objects must be in place. The effective date parameter (p_Effective_Date) controls date-tracked removal, ensuring historical and future-dated rows are handled in a datetrack-aware manner. The package is referenced by one other package within the EBS codebase, indicating layered internal dependency; the get_ovn and get_dml_operation helpers suggest the package supports concurrency-checked DML consistent with Oracle's standard DML operation tracking. Custom code should not call these procedures directly unless the copy entity transaction and result context has first been established by the originating process.