Search Results p_language_code

Overview

APPS.PAY_FRR_DATA_PUMP is a private PL/SQL package body within the Oracle E-Business Suite Payroll (PAY) module that supports the Oracle HRMS Data Pump architecture. Its principal business function is to resolve and translate user-friendly, language-dependent reference values — element names, input value names, assignment statuses, and formula result rule identifiers — into the internal surrogate primary keys stored in the underlying Payroll and People tables. During a data pump or element migration, source definitions are frequently supplied by name rather than by internal ID, and this package bridges that gap by performing the required lookups against the translation-enabled (TL) tables.

The package is designated with an API classification of OTHER in the ETRM metadata, indicating that it is an internal utility rather than a formally published, externally supported PL/SQL API. It is referenced by zero other packages in the documented metadata, confirming its narrow, self-contained role within the data pump subsystem.

The user search term p_language_code reflects a recurring parameter convention throughout the package. Multiple private helper functions accept a language code argument alongside business group and name parameters, ensuring that translated rows in the TL tables are matched in the correct session or installation language. This is a well-established pattern in Oracle HRMS localization, where element names and status descriptions must be resolved consistently with the user's language environment.

Key Procedures and Functions

The documented metadata lists five procedures and functions within this package body:

• GET_STATUS_PROCESSING_RULE_ID — Resolves the internal identifier of a payroll status processing rule, used to associate processing behaviour with assignment statuses during data loading.
• GET_ELEMENT_TYPE_ID — Returns the element type identifier corresponding to a supplied element name and business group, performing a join across the element type definition and its translation table.
• GET_INPUT_VALUE_ID — Returns the identifier of a payroll input value, allowing data pump routines to map input value names to their internal keys.
• GET_FORMULA_RESULT_RULE_OVN — Retrieves the descriptive or overflow name associated with a formula result rule, supporting rule identification during migration.
• GET_FORMULA_RESULT_RULE_ID — Returns the internal identifier of a formula result rule, the core reference key used elsewhere in the data pump process.

In addition to the documented set, the source excerpt reveals private helper functions such as get_source_element_type_id and get_ass_status_typ_id, both of which accept a p_language_code parameter and raise failures through hr_data_pump.fail on error.

Tables Accessed

The package reads from the following tables (via APPS synonyms):

• HR_PUMP_BATCH_LINE_USER_KEYS — stores user-defined key mappings for data pump batch lines.
• PAY_ELEMENT_TYPES_F and PAY_ELEMENT_TYPES_F_TL — the base and translated element type definitions, joined on element type ID and language.
• PAY_FORMULA_RESULT_RULES_F — the definition of formula result rules.
• PAY_INPUT_VALUES_F — the definition of payroll element input values.
• PAY_STATUS_PROCESSING_RULES_F — the definition of status processing rules.
• PER_ASSIGNMENT_STATUS_TYPES, PER_ASSIGNMENT_STATUS_TYPES_TL, and PER_ASS_STATUS_TYPE_AMENDS — the base, translated, and amendment records for assignment statuses.

All access is read-only; the package resolves identifiers and does not modify payroll definitions.

Usage Notes

PAY_FRR_DATA_PUMP is invoked internally by Oracle HRMS data pump and element migration processes rather than being called directly from forms or concurrent program parameters. Its functions are called when batch lines carry names instead of identifiers and the loader must resolve the corresponding internal keys before committing records. Because the package uses the TL tables, the correct p_language_code must be supplied by the calling process, typically the session language or the business group's language context. Customers performing custom data migration in Oracle EBS 12.1.1 or 12.2.2 should not call these private functions directly; they should rely on the supported data pump APIs, since the package is subject to change and is not documented as a public interface.