Search Results rr_sparse

Overview

The APPS.PAY_LEGISLATION_RULES_PKG package body (pylegrul.pkb) is a core Oracle Payroll deliverable that centralizes the definition and retrieval of legislation rules across the Oracle E-Business Suite. A "legislation rule" is a named, country-specific configuration switch that governs the behaviour of the payroll engine, payroll processes, and related object validation. Rather than hard-coding regional or regulatory behaviour throughout the Payroll modules, Oracle stores each rule as a short alphanumeric key (for example SEED_FEEDS, ENABLE_QP_OFFSET, RUN_RETRO_FORMULA, DEFAULT_RUN_TYPE, DYNAMIC_TAX_UNIT, BAL_CATEGORY_MANDATORY, RETRO_CONTEXT_OVERRIDE, ADVANCED_RETRO, RR_SPARSE, and ADV_EE_SUBPRIORITY) and resolves its value at runtime through this package.

The package therefore acts as the single point of truth for payroll legislation behaviour, isolating country extensions from the base product. The object is classified as OTHER in the ETRM metadata, indicating it is a supporting internal API rather than a formal public interface. It is owned by APPS and is present in both release 12.1.1 and 12.2.2 with identical core semantics. The change history embedded in the source spans from its initial creation in March 2001 through subsequent additions of individual rules, reflecting the incremental manner in which Oracle exposes new payroll configuration switches.

Key Procedures and Functions

The ETRM metadata documents a single public program unit within this package body:

• CHECK_LEG_RULE — This is the primary (and only) documented entry point. Its purpose is to evaluate whether a specified legislation rule is enabled for a given business group or legislation context, returning a result that calling code uses to branch payroll behaviour. It is the generic accessor through which all named rules (SEED_FEEDS, ENABLE_QP_OFFSET, RUN_RETRO_FORMULA, DEFAULT_RUN_TYPE, and the many others listed in the package header change log) are resolved. No parameter list is documented, and it should not be assumed; consumers should reference the installed package specification for exact signatures.

All other logic in the package body supports this single accessor — populating, caching, and validating rule values — but is not exposed in the documented metadata.

Tables Accessed

The ETRM metadata records no directly referenced tables via APPS synonyms for this package. In practice, the package relies on the Oracle Payroll legislation rule infrastructure tables (PAY_LEGISLATION_RULES and associated lookups) to hold the rule codes and their per-legislation values, reading them to satisfy CHECK_LEG_RULE requests. Because no table dependencies are documented, integrators should not build direct dependencies on any specific underlying table and must treat CHECK_LEG_RULE as the supported interface.

Usage Notes

PAY_LEGISLATION_RULES_PKG is invoked internally by numerous Oracle Payroll processes and is referenced by at least one other documented package. Typical invocation scenarios include:

• Payroll processing and concurrent programs — Payroll run, QuickPay, RetroPay, and balance processes call CHECK_LEG_RULE to determine processing options such as retro formula control and positive offset handling.
• Forms and validation — Payroll setup and entry forms use the rule check to drive field behaviour and validation (for example mandatory balance categories).
• Country legislation extensions — Localization code queries the package to switch behaviour per country without modifying base code.
• Custom code — Customers may call CHECK_LEG_RULE from their own PL/SQL, but should always reference the package specification rather than the body, and avoid querying underlying rule tables directly. The body should never be modified; customization is not supported.