Search Results create_bf_localisation

Overview

APPS.PAY_DB_LOCALISATION_PKG is a seeded Oracle Payroll database package that provides a programmatic mechanism for loading or seeding legislation-specific (localisation) payroll configuration data. The package is owned by APPS and is classified under the ETRM API taxonomy as OTHER, indicating that it is an internal setup utility rather than a published public API intended for general customer integration.

The package header is stored in the source file pylocaln.pkh. It is declared AUTHID CURRENT_USER, meaning its SQL executes with the privileges of the invoker rather than as definer-rights code. The change list in the header records its evolution: it was first created on 26-Nov-92 by J.S.Hobbs, and the BF localisation routine was added on 16-Feb-93. The package was renamed to its current form on 05-OCT-94 (R.Fine, version 40.3). The header carries an Oracle Corporation UK Ltd. copyright, consistent with the package’s origin in payroll localisation work for the United Kingdom and other legislations.

In Oracle EBS 12.1.1 and 12.2.2, the package remains a lightweight, low-level utility. It is not referenced by any other documented payroll package, meaning it is normally invoked directly rather than through internal dependency chains.

Key Procedures and Functions

The package exposes two documented procedures, both declared without parameters in the header specification.

• CREATE_GB_LOCALISATION — Creates or seeds the localisation setup data required for the United Kingdom (GB) payroll legislation. This is the original localisation routine associated with the package’s initial 3.0 release.
• CREATE_BF_LOCALISATION — The routine the user searched for. Added in version 3.2 (16-Feb-93), it performs the equivalent seeding of localisation configuration for the BF legislation. It mirrors CREATE_GB_LOCALISATION in purpose but targets BF-specific setup rows. No parameter list is documented; the procedure takes no arguments and relies on the current database session context.

Both procedures are declaration-only in the specification; their implementation resides in the package body. No overloads, functions, or additional public entry points are documented.

Tables Accessed

The documented table references, resolved through APPS synonyms, reflect the payroll configuration entities that localisation seeding must populate. These include:

• PAY_BALANCE_DIMENSIONS, PAY_BALANCE_TYPES, PAY_BALANCE_TYPES_S — balance definition and its translatable (MLS) variant.
• PAY_DEFINED_BALANCES, PAY_DEFINED_BALANCES_S — defined balance configuration and translations.
• PAY_ELEMENT_CLASSIFICATIONS, PAY_ELEMENT_CLASSIFICATIONS_S — element classification setup and translations.
• PAY_LEGISLATION_RULES — legislation-specific processing rules.
• PAY_PAYMENT_TYPES, PAY_PAYMENT_TYPES_S — payment type setup and translations.
• PER_ASSIGNMENT_INFO_TYPES — assignment-level descriptive information type definitions.
• DUAL — used for singleton selects and validation/plausibility checks.

The mix of base and _S (translation) tables indicates the procedures insert or validate both the core setup rows and their language-specific translations.

Usage Notes

PAY_DB_LOCALISATION_PKG is a setup-time utility. It is not intended for routine transactional use. Typical invocation occurs during environment build, legislation configuration, or post-clone repair, either through SQL*Plus scripts executed by a DBA or via custom wrapper code that calls the procedure directly. It is not exposed on standard Oracle Payroll forms or concurrent programs, and it is not listed as a dependency of other documented packages. Because it is AUTHID CURRENT_USER, the invoking user must have the necessary object privileges on the referenced PAY and PER synonyms. Custom code should treat the package as unsupported internal functionality and screen for behaviour changes across 12.1.1, 12.2.2, and later releases.