Search Results chk_rate_type

Overview

PAY_PYR_BUS is the business validation layer for the PAY_RATES entity within Oracle Payroll. It belongs to the family of Table Handler (TH) packages generated and maintained by Oracle's business object framework, evidenced by the inclusion of "BUS" in its name and the "Internal Table Handler Use only" access status stated in its header comments. The package encapsulates the row-level business rules that govern the creation, modification, and removal of pay rate definitions, ensuring that every insert, update, or delete performed against PAY_RATES from a supported API or form satisfies Oracle Payroll's referential and legislative constraints before the DML is committed.

In Oracle EBS 12.1.1 and 12.2.2 the package is owned by APPS and classified as OTHER in the ETRM inventory. It exposes ten documented procedures, of which five are dedicated field-level validators, one resolves the applicable legislation, one manages the session security context, and three provide the transactional entry points for the three DML operations. Because the validators raise application errors and terminate processing on failure, the package acts as the single point of enforcement for data integrity on pay rate records.

Key Procedures and Functions

• CHK_NAME — Validates that the rate name is mandatory, and enforces uniqueness of the name and rate type combination. For rate types other than 'A' the uniqueness test covers name and rate_type; when rate_type equals 'A' the test additionally includes the assignment rate type attribute.
• CHK_RATE_BASIS — Confirms that the supplied rate basis value exists in HR_LOOKUPS under the lookup type RATE_BASIS, validating the value against the effective date of the record.
• CHK_RATE_UOM — Validates the unit of measure associated with the rate against the permitted values for the applicable legislative context.
• CHK_RATE_TYPE — Confirms that the rate type supplied is a valid, permitted value for pay rate definitions; this is the validator most directly associated with the search term "chk_rate_type" and the procedure that callers should treat as the authoritative check on rate type input.
• CHK_PARENT_SPINE_ID — Validates the parent spine identifier, generally confirming that any referenced parent spine exists and is appropriate for the rate being processed.
• SET_SECURITY_GROUP_ID — Establishes the security group context used by the remaining validations, ensuring that lookups and business group scoped data are resolved against the correct security profile.
• RETURN_LEGISLATION_CODE — Returns the legislation code applicable to the current processing context, which drives which validation rules apply.
• INSERT_VALIDATE — Orchestrates the full set of validations executed before a new PAY_RATES row is inserted.
• UPDATE_VALIDATE — Orchestrates the validations executed before an existing PAY_RATES row is updated, typically re-validating changed attributes and object version integrity.
• DELETE_VALIDATE — Performs the checks that must pass before a PAY_RATES row may be deleted.

Tables Accessed

• PAY_RATES — The primary entity table; the package validates columns of this table and supports its insert, update, and delete operations.
• PAY_GRADE_RULES_F — Referenced to validate relationships between rates and grade rules, confirming that rate definitions do not conflict with configured grade rule structures.
• PER_PARENT_SPINES — Referenced by CHK_PARENT_SPINE_ID to verify the existence and validity of parent spine records used in rate hierarchies.
• DUAL — Used for single-row PL/SQL and SQL expressions, such as returning the legislation code or evaluating scalar predicates.

Additional lookups, notably HR_LOOKUPS for RATE_BASIS, are consulted through the validation logic described in the source header comments.

Usage Notes

PAY_PYR_BUS is an internal table handler and is not intended for direct invocation by customers or integrators. It is called by the Oracle Payroll rate maintenance forms, by the public PAY_RATES API layer, and by concurrent processes that create or amend pay rate definitions. Three other packages in the ETRM inventory reference it, indicating its role as a shared validation dependency.

Custom code that must create or modify pay rates should call the supported public API rather than PAY_PYR_BUS directly; the public API invokes these validators on the caller's behalf. When troubleshooting validation failures on pay rate records, the error raised by CHK_NAME or CHK_RATE_TYPE can be traced back to this package, and the row-level rules it documents—mandatory name, uniqueness of name/rate type, conditional uniqueness for assignment rate types, and lookup-backed rate basis values—define the expected data quality standard for PAY_RATES.