Search Results insert_proposal_component

Overview

APPS.HR_MAINTAIN_PROPOSAL_SWI is a self-service wrapper package within the Oracle E-Business Suite Human Resources (HR) module, specifically supporting the Salary Proposal and Compensation Management functionality. The suffix "SWI" denotes "Self-Service Web Interface," which is a naming convention Oracle applies to PL/SQL packages that act as thin wrappers exposing underlying business logic APIs to self-service (web-based) applications, including Oracle Self-Service HR and iRecruitment-related compensation flows.

The package's primary business function is to provide a controlled, web-callable entry point for creating, modifying, approving, and deleting salary proposals and their constituent components. It is classified as "OTHER" in the API registry, meaning it is documented for internal development reference rather than as a published public API. According to the embedded header comments, the package explicitly states its "Access Status: Internal Development use only," signalling that Oracle does not recommend direct customer invocation without careful review.

The package delegates its substantive work to the corresponding business API, hr_maintain_proposal_api. Each wrapper procedure mirrors an API procedure one-to-one, ensuring consistent validation, business rule enforcement, and error handling while presenting a simplified interface to self-service callers. The header note in the source confirms this relationship for approve_salary_proposal, which wraps hr_maintain_proposal_api.approve_salary_proposal.

Key Procedures and Functions

The ETRM metadata documents nine procedures and functions within this package:

• INSERT_SALARY_PROPOSAL — Creates a new salary proposal record, establishing the parent proposal entity.
• UPDATE_SALARY_PROPOSAL — Modifies an existing salary proposal's attributes.
• DELETE_SALARY_PROPOSAL — Removes a salary proposal and its associated data.
• APPROVE_SALARY_PROPOSAL — Approves a submitted salary proposal; per the header comments, it accepts a proposal identifier, change date, proposed salary, object version number, validation flag, and returns error text and a return status.
• CRE_OR_UPD_SALARY_PROPOSAL — Provides a combined create-or-update operation, commonly used when the caller does not need to distinguish between insert and update.
• INSERT_PROPOSAL_COMPONENT — Adds a component (for example, a salary element such as basic pay, allowance, or bonus) to an existing salary proposal. This is the procedure referenced in the user's search term.
• UPDATE_PROPOSAL_COMPONENT — Modifies the details of an existing proposal component.
• DELETE_PROPOSAL_COMPONENT — Removes a component from a salary proposal.
• PROCESS_API — Serves as a central internal dispatcher or helper that routes requests to the appropriate underlying API logic.

Because parameter lists are not fully published in the metadata, exact signatures should be confirmed against the package specification (hrpypswi.pkh) in the target instance.

Tables Accessed

The documented table references via APPS synonyms are XMLDOM and XMLPARSER. These are Oracle XML database components rather than HR business tables. Their presence indicates the package performs XML parsing or DOM manipulation, likely to process structured self-service payloads passed from web-tier components, or to generate/consume XML for messages, error handling, or interface integration. The package does not directly list HR business tables such as PER_PAY_PROPOSALS or PAY_PROPOSAL_COMPONENTS; actual data manipulation is delegated to hr_maintain_proposal_api, which owns the transactional logic.

Usage Notes

This package is typically invoked from Oracle EBS self-service forms and web pages, particularly those supporting salary proposal maintenance in Manager Self-Service and Compensation Workbench contexts. It is also called indirectly by concurrent programs that process salary proposals in batch.

Because the object is marked "Internal Development use only," custom code should avoid calling it directly unless no public API alternative exists. When invoked from custom code, callers must derive all IN parameters correctly, handle the returned p_return_status to detect success or failure, and inspect p_error_text for diagnostics. The presence of object version numbers in the approve procedure indicates optimistic locking is enforced. The metadata notes the package is referenced by zero other packages, confirming it is an application-layer entry point rather than shared library code. Developers migrating between 12.1.1 and 12.2.2 should verify the header version (hrpypswi.pkh 120.3.12000000.1) to confirm behavioural consistency.