Search Results get_bg_grd_keyflex_name

Overview

PER_RI_CONFIG_UTILITIES is an Oracle E-Business Suite PL/SQL package owned by the APPS schema that serves as a shared utility layer for the Oracle Human Resources "RI" (Rapid Implementation / Regional Information) configuration framework. Its principal business function is to provide reusable helper logic that the other RI configuration packages — PER_RI_CONFIG_FND_HR_ENTITY, PER_RI_CONFIG_FND_DEF_ENTITY, PER_RI_CONFIG_MAIN, PER_RI_CONFIG_DATAPUMP_ENTITY, and PER_RI_CONFIG_TECH_SUMMARY — invoke during enterprise and business group setup. In practical terms, the package encapsulates the low-level work required to create key flexfield structures and segments, resolve enterprise and business group identifiers, apply profile option values, and interrogate localisation and legislative attributes without forcing every consuming package to re-implement that logic. The ETRM record confirms the package is VALID in 12.1.1 and 12.2.2 and classifies it as API type OTHER, indicating an internal utility rather than a formally published public API.

The package is both a consumer and a provider within the RI dependency graph: it references FND and PER objects directly, and it is itself referenced by six other packages, including a self-reference. This mutual dependency pattern is characteristic of a central helper unit.

Key Procedures and Functions

ETRM documents 49 procedures and functions. The most significant fall into several functional groups.

• Flexfield construction: CREATE_KEY_FLEXFIELD and CREATE_FLEX_SEGMENTS build key flexfield structures and their segment definitions, supporting the generation of job, position, and grade key flexfields identified through GET_BG_JOB_KEYFLEX_NAME, GET_BG_POS_KEYFLEX_NAME, and GET_BG_GRD_KEYFLEX_NAME.
• Enterprise and business group resolution: BUSINESS_GROUP_DECISION, GET_OC_BG_NAME, GET_ENTERPRISE_BG_NAME, GET_LE_BG_NAME, GET_ENTERPRISE_SHORT_NAME, and GET_ENTERPRISE_NAME return naming and identification attributes used when constructing configuration records.
• Legislative and regional checks: LEGISLATION_SUPPORT, REGIONAL_VARIANCE_DEFINED, JPG_DEFINED, MANDATORY_ORG_INFO_TYPES, CHECK_CURRENCY_ENABLED, and GET_ENT_PRIMARY_INDUSTRY determine which localisation rules, currency availability, and mandatory information types apply to a given configuration.
• Setup and diagnostics: SET_PROFILE_OPTION_VALUE applies profile values during configuration, GET_CONFIG_LOCATION_CODE retrieves the configuration location, and WRITE_LOG emits diagnostic output to support troubleshooting.

Tables Accessed

All table access is performed through APPS synonyms. The package reads application registry data from FND_APPLICATION and menu structure from FND_MENUS. Responsibility and request group information is drawn from FND_RESPONSIBILITY, FND_RESPONSIBILITY_TL, and FND_REQUEST_GROUPS, supporting the creation or validation of menu and responsibility setups. Flexfield and value set metadata is sourced from FND_ID_FLEX_STRUCTURES and FND_FLEX_VALUE_SETS. Currency validation uses FND_CURRENCIES. Security and data group configuration is read from FND_DATA_GROUPS, FND_DATA_GROUP_UNITS, and FND_NODES. Profile behaviour relies on FND_PROFILE_OPTIONS and FND_PROFILE_OPTION_VALUES, while FND_LOOKUP_VALUES supplies extensible lookup codes. Configuration state is persisted or read through PER_RI_CONFIG_INFORMATION. Notably, FND_DATA_GROUPS_STANDARD_VIEW and FND_RESPONSIBILITY_VL appear in the dependency listing as views over these base tables.

Usage Notes

PER_RI_CONFIG_UTILITIES is not intended for direct invocation by end users. It is typically called from within the RI configuration packages and from concurrent programs that perform rapid implementation of HR setup, where a single run must create flexfields, responsibilities, request groups, and profile settings in sequence. Custom code extending the RI framework should call these utilities rather than duplicating flexfield or profile logic, and should treat the signatures as internal since ETRM classifies the package as OTHER rather than a supported public API. Because the package is referenced by six other packages, changes to its behaviour can cascade across the RI configuration toolset; regression testing should therefore cover the full set of dependent packages when the utilities are modified.