Search Results upload_salary_proposal

Overview

The APPS.HR_UPLOAD_PROPOSAL_API package body provides the server-side PL/SQL implementation behind Oracle EBS salary proposal maintenance. Its principal documented entry point, UPLOAD_SALARY_PROPOSAL, supports the creation and uploading of salary proposals — the dated, component-level records that capture proposed changes to an employee's pay before those changes are approved and applied to the assignment. In Oracle HRMS, a salary proposal is stored across PER_PAY_PROPOSALS (the proposal header, keyed by assignment and effective change date) and PER_PAY_PROPOSAL_COMPONENTS (the individual element or component lines, with their change percentages or amounts). The API encapsulates the validation, defaulting, and insertion logic required to build these records consistently from external or bulk sources rather than through online forms.

The package is classified as an API in the ETRM metadata, owner APPS, and it is referenced by one other package, indicating it forms part of a wider processing chain rather than being invoked in isolation. This makes it a reusable, callable unit for downward salary proposal creation and upload.

Key Procedures and Functions

• UPLOAD_SALARY_PROPOSAL — the single documented procedure. It performs the upload of a salary proposal for a given assignment, resolving and validating the pay basis, element, and component information supplied by the caller, then creating the corresponding proposal header and component rows in the proposal tables. Its role is to translate an external proposal definition into valid Oracle HRMS proposal data, applying the same element-link and input-value rules used by the standard salary proposal forms.

The package body additionally contains internal helper routines that are not exposed as documented public API. Notably, the body declares the private procedure update_last_change_date, which maintains proposal date sequencing: it locates the next proposal for an assignment with the earliest change date greater than the current record's change date and corrects that record's last_change_date. This helper is called on insert or delete of a proposal so that the immediately following proposal retains an accurate last_change_date, preserving the chronological integrity of the proposal history. The caller passes the assignment identifier and a change date as inputs.

Tables Accessed

The package references the following tables through APPS synonyms:

• PER_PAY_PROPOSALS — the proposal header (assignment, change date, last change date, pay basis). Read and written during upload and by update_last_change_date.
• PER_PAY_PROPOSAL_COMPONENTS — the component detail lines for the proposal; insert target for uploaded component values.
• PER_PAY_BASES — supplies pay basis definitions used to interpret proposal amounts.
• PER_ALL_ASSIGNMENTS_F — the assignment against which the proposal is created and dated.
• PAY_ELEMENT_TYPES_F, PAY_ELEMENT_LINKS_F, PAY_ELEMENT_ENTRIES_F, PAY_INPUT_VALUES_F — the payroll element definition, linking, entry, and input-value tables used to validate and resolve the components being uploaded.

Usage Notes

HR_UPLOAD_PROPOSAL_API is typically invoked from PL/SQL rather than directly by end users. It is suited to bulk or custom salary proposal loading — for example, batch uploads, data migration, or interfaces that populate proposals from an external salary review or budgeting process. Because the proposals it creates are later used by downstream approval and salary update processing (the package that references it), callers should ensure the assignment, effective date, and pay basis supplied are valid and that the proposal dates are sequenced correctly, since the package maintains last_change_date chaining across an assignment's proposals. On Oracle EBS 12.1.1 and 12.2.2 the object resides in the APPS schema with the standard HRMS public-synonym access model.