Search Results delete_rate

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

HR_RATE_SWI is a self-service wrapper package in the Oracle E-Business Suite HR (Human Resources) module, owned by the APPS schema and classified under the OTHER API category. Its principal role is to expose rate-related business logic to self-service interfaces — most notably Oracle iRecruitment and other SSHR-based flows — through thin PL/SQL wrappers around the underlying HR_RATE_API. The suffix "SWI" denotes "Self-service Web Interface," a convention used throughout Oracle HRMS to distinguish wrapper packages intended for web-facing use from the core server-side APIs they invoke.

The package is declared AUTHID CURRENT_USER, meaning executing code runs with the privileges of the calling schema rather than the definer. Its header carriage dates to 2004 (pypyrswi.pkh, version 115.0), reflecting its long-standing presence across EBS 11i, 12.1.1, and 12.2.2. The documented scope describes a business function that manages assignment-level rate definitions — the pay rate structures attached to employees, applicants, or assignments used in compensation, budgeting, and recruitment offer calculation.

Key Procedures and Functions

Five documented procedures make up the public interface. Each is a wrapper delegating to a corresponding routine in HR_RATE_API (or a directly related API), deriving IN parameters on behalf of the caller:

• CREATE_ASSIGNMENT_RATE — Creates a rate definition tied to an assignment. It validates the supplied effective date, business group, name, rate basis, and assignment rate type before delegating to hr_rate_api.create_assignment_rate. It also supports flexible attribute columns (attribute_category and attribute1 through attribute16) for descriptive flexfield capture, and a p_validate flag that allows a rollback-only test execution.
• CREATE_RATE — Creates a rate record at the object level (not assignment-specific), serving as the base creation entry point for rate definitions consumed by the assignment-level operations.
• UPDATE_ASSIGNMENT_RATE — Modifies an existing assignment rate, applying date-tracked changes through the underlying API while preserving the standard HR date-effective semantics.
• UPDATE_RATE — Updates the base rate definition, used when the rate structure itself (rather than its assignment linkage) requires amendment.
• DELETE_RATE — Removes a rate definition, invoking the API's deletion logic and its associated validation and referential checks.

All procedures follow the standard HRMS API pattern: a p_validate parameter defaulting to hr_api.g_false_num, and a p_return_status output indicating success or failure. Callers must inspect p_return_status rather than relying on exceptions alone, since the APIs typically report errors through this mechanism.

Tables Accessed

The ETRM metadata for this package does not list directly referenced tables under APPS synonyms; access occurs indirectly through the HR_RATE_API calls. Functionally, the operations touch the HR rate definition tables (the PAY_RATE / HR_RATE family) and the assignment rate storage that links rate definitions to assignments. Because the package is a wrapper, it inherits the DML profile of the underlying API, including date-tracked inserts and updates that maintain effective-dated history.

Usage Notes

The package documentation explicitly marks its access status as "Internal Development use only." It is not intended as a public extension point; customers and partners should call the underlying HR_RATE_API directly for supported integrations. The wrapper is invoked internally by self-service web flows — iRecruitment offer and applicant rate handling, and SSHR compensation-related pages — where the wrapper layer provides the appropriate security and session context. It is not typically registered against concurrent programs, and the metadata records no other packages referencing it. Custom code should avoid direct dependency on HR_RATE_SWI, as its interface is subject to change without notice and is not covered by Oracle's public API compatibility guarantees.