Search Results my_get_defaults

Overview

APPS.HR_PAY_RATE_SS is a salary administration server-side PL/SQL package body that supports the Oracle EBS Salary Management and Grade/Step Rate (Pay Rate) functionality. It acts as the business-logic and validation layer behind the salary proposal, salary approval, and salary transaction flows used by HR professionals when they record or change an assignment's pay rate, salary basis, grade, and step. The package encapsulates row-level validation, workflow-driven transaction handling, currency conversion, and defaulting logic required to submit or approve salary changes through the HR API (HR_PROCESS_ASSIGNMENT_SS.PROCESS_API).

Its name and documented procedures indicate it belongs to the "SS" (Self-Service / SSHR) family of HR packages, and it is referenced by at least one other package in the EBS schema, confirming it is a shared utility rather than a standalone program. It is shipped in both 12.1.1 and 12.2.2 and is owned by APPS.

Key Procedures and Functions

• MY_GET_DEFAULTS — the routine the user searched for; returns default values used to seed the salary transaction form (such as rate type, currency, or salary basis defaults) based on the current assignment, person, and effective date.
• CHECK_ASG_TXN_DATA / CHECK_GSP_ASG_TXN_DATA — validate assignment-level and grade/step (GSP) transaction data before the API is invoked.
• CHECK_MID_PAY_PERIOD_CHANGE — enforces business rules for mid-pay-period salary changes.
• GET_RATE_TYPE / GET_RATE — retrieve the applicable rate type and corresponding pay rate for an assignment.
• CONVERT_AMOUNT — translates an amount between currencies using GL conversion types.
• START_TRANSACTION — initiates a salary transaction record and its workflow context.
• VALIDATE_SALARY_DETAILS — performs the detailed validation of proposed salary components.
• IS_TRANSACTION_EXISTS — checks whether a salary transaction already exists for the given criteria.
• GET_TRANSACTION_STEP_DETAILS / GET_TRANSACTION_DETAILS / GET_TXN_DETAILS_FOR_REVIEW — return transaction and transaction-step detail for display and review.
• PROCESS_SALARY_JAVA — processing entry point intended for Java/self-service callers.
• DELETE_TRANSACTION_STEP — removes a transaction step (e.g., when a workflow route is rejected or withdrawn).
• PROCESS_API — wraps HR_PROCESS_ASSIGNMENT_SS.PROCESS_API to apply the validated salary change.
• PRATE_APPLICANT_HIRE — applies pay rate handling in the applicant-to-hire path.

Tables Accessed

The package reads and writes standard HR and workflow tables via APPS synonyms. Assignment and person data come from PER_ALL_ASSIGNMENTS_F and PER_ALL_PEOPLE_F, with assignment status supplied by PER_ASSIGNMENT_STATUS_TYPES. Salary structures are resolved through PER_PAY_BASES, PAY_INPUT_VALUES_F, PAY_ELEMENT_TYPES_F, PAY_GRADE_RULES_F, and PAY_USER_COLUMN_INSTANCES_F. Currency conversion uses FND_CURRENCIES and GL_DAILY_CONVERSION_TYPES. Transaction and workflow state is persisted in HR_API_TRANSACTIONS, HR_API_TRANSACTION_VALUES, HR_API_TRANSACTION_STEPS, WF_ITEMS, and WF_PROCESS_ACTIVITIES. Benefits eligibility checks reference BEN_PGM_F.

Usage Notes

HR_PAY_RATE_SS is typically invoked from the Salary Management and Grade/Step forms (for example, the salary proposal and approval flows) and from self-service salary pages, which call PROCESS_SALARY_JAVA. It is also callable from custom PL/SQL code and concurrent programs that need to validate or apply salary changes programmatically. Because it relies on WF_ITEMS and WF_PROCESS_ACTIVITIES, transaction steps started through START_TRANSACTION are driven by Oracle Workflow. Customizations should treat the routines as internal server-side APIs: methods do not have a stable documented signature in this reference, so parameter lists must be confirmed against the shipped package before direct calls. Direct DML on the underlying HR_API_TRANSACTION* tables is not recommended; use the package procedures instead to preserve workflow and validation integrity.