Search Results delete_salary_proposal

Overview

HR_MAINTAIN_PROPOSAL_API is an Oracle E-Business Suite PL/SQL API that belongs to the Oracle HRMS (Human Resources Management System) product family. It provides a supported, programmatic interface for creating, modifying, approving, and deleting salary proposals and their associated components within the PER_PAY_PROPOSALS data model. In Oracle EBS 12.1.1 and 12.2.2, salary proposals represent proposed changes to an assignment's pay — such as a merit increase, promotion adjustment, or new salary basis assignment — that must be reviewed and approved before they take effect on the payroll or compensation record.

Because it is a server-side API package owned by the APPS schema and classified as an API, it encapsulates the business logic, validation rules, and multi-table maintenance required to keep salary proposals and their components consistent with the underlying HR and payroll element structures. It shields callers from the complexity of directly manipulating the pay proposal tables and instead exposes granular, transactional operations.

Key Procedures and Functions

The documented API exposes twelve procedures/functions, of which the following are the principal named operations:

• INSERT_SALARY_PROPOSAL — Creates a new salary proposal record for an assignment, establishing the proposed pay values and effective dates.
• UPDATE_SALARY_PROPOSAL — Modifies an existing salary proposal, allowing changes to proposed amounts, dates, or related attributes before approval.
• APPROVE_SALARY_PROPOSAL — Transitions a salary proposal to its approved state, triggering any downstream processing associated with applying the proposed change.
• DELETE_SALARY_PROPOSAL — Removes a salary proposal that is no longer required.
• INSERT_PROPOSAL_COMPONENT — Adds a component line to a salary proposal, representing an individual element or pay component within the overall proposal.
• UPDATE_PROPOSAL_COMPONENT — Amends an existing proposal component.
• DELETE_PROPOSAL_COMPONENT — Removes a proposal component from a salary proposal.
• CRE_OR_UPD_SALARY_PROPOSAL — A convenience wrapper that creates a new salary proposal or updates an existing one depending on whether the proposal already exists.
• DELETE_SALARY_HISTORY — Deletes salary history records associated with a proposal or assignment.

Additional internal operations support these public entry points, but only the procedures above are documented as the supported API surface.

Tables Accessed

The package reads and writes a tightly coupled set of HR and payroll tables, primarily through APPS synonyms. The central objects are PER_PAY_PROPOSALS and PER_PAY_PROPOSAL_COMPONENTS, which hold the proposal header and its component lines. Proposal components and history are maintained through PER_PPC_INS, PER_PPC_UPD, PER_PPC_DEL, PER_PYP_INS, PER_PYP_UPD, PER_PYP_DEL, PER_PYP_SHD, and PER_PAY_PROPOSALS_POPULATE. Supporting data is drawn from PER_ALL_ASSIGNMENTS_F and PER_PAY_BASES to validate the assignment and its pay basis, from BEN_CWB_PERSON_RATES for compensation workbench rates, and from the payroll element structures PAY_ELEMENT_TYPES_F, PAY_ELEMENT_LINKS_F, PAY_ELEMENT_ENTRIES_F, and PAY_INPUT_VALUES_F to resolve the elements and input values that a proposal references. HR_LOOKUPS, FND_GLOBAL, and FND_PROFILE provide lookup values and session context, while HR_API, HR_GENERAL, and HR_UTILITY supply shared HRMS utility routines.

Usage Notes

HR_MAINTAIN_PROPOSAL_API is typically invoked from Oracle HRMS compensation and salary forms, from concurrent programs that mass-process salary proposals, and from customer-written PL/SQL extensions or interfaces that need to create or approve proposals programmatically. The presence of the HR_MAINTAIN_PROPOSAL_BK1 through BK7 packages and the PER_PYP_SHD shadow table indicates that the API participates in the standard HRMS date-tracked, business-group-aware multi-table update pattern, including shadow-history maintenance. Callers should supply the standard HRMS API context — business group, effective date, and login/session information — and are expected to use the documented procedures rather than writing directly to PER_PAY_PROPOSALS. The package is referenced by twenty-four other database objects, confirming its role as a foundational component relied upon by downstream compensation and payroll functionality.