Search Results balance_dimension_rec

Overview

HR_JP_ID_PKG is a Japan legislation-specific server-side PL/SQL package owned by the APPS schema in Oracle E-Business Suite. It provides reusable lookup and validation utilities for Oracle Human Resources (HRMS/PER) and Oracle Payroll objects within a Japanese business group context. The package encapsulates logic required to resolve key flexfield combinations, business group attributes, legislation codes, key flexfield structure numbers, and default currency codes, then extends those primitives across a broad set of payroll and HR reference entities such as element sets, backpay sets, classifications, element types, balance types and dimensions, and assignment status types.

Functionally, HR_JP_ID_PKG acts as an identity-resolution layer: given a business group, a legislated identifier, or a concatenated flexfield segment string, it returns the corresponding numeric identifier or full row from the underlying base table. Constants such as C_DEFAULT_BUS (-1), C_ALL_BUS (-2), and C_DEFAULT_LEG ('X') support abbreviated calling conventions where a caller can refer to the current business group, all business groups, or the default legislation without supplying an explicit value.

A distinguishing feature is the LATEST_SQL function. In this codebase, LATEST_SQL is a conventional "SQL-returning" function used to supply a complete SQL statement as a VARCHAR2, typically consumed by a calling program that must dynamically derive the latest or current effective record for an entity. It is the function most often surfaced when developers search for the literal term "latest_sql" against this package.

Key Procedures and Functions

The package exposes 111 documented procedures and functions. Core primitives include:

• LATEST_SQL — returns a SQL statement string for dynamic execution, generally used to obtain the most current effective record for the entity in context.
• KEYFLEX_COMBINATION_ID — resolves a concatenated key flexfield segment string into a key flexfield combination identifier for a specified application, flexfield code and structure number, with an option to raise an error when the combination does not exist.
• BUSINESS_GROUP_REC — returns the complete PER_BUSINESS_GROUPS row for a given business group identifier.
• LEGISLATION_CODE — returns the legislation code associated with a business group.
• ID_FLEX_NUM — returns the key flexfield structure number for a business group and flexfield code.
• DEFAULT_CURRENCY_CODE — overloaded to return the default currency either from a business group or from a legislation code.

The remaining documented functions follow a consistent REC/ID pattern, returning either a full row-type record or the numeric identifier for element sets, backpay sets, classifications, element types, balance types, balance dimensions, and assignment status types.

Tables Accessed

The package reads from HR and Payroll base tables through APPS synonyms, including PER_BUSINESS_GROUPS, HR_ALL_ORGANIZATION_UNITS, HR_ORGANIZATION_INFORMATION, HR_ASSIGNMENT_SETS, and HR_LOCATIONS_ALL for organization and business group resolution. Flexfield validation relies on FND_FLEX_VALUES, FND_FLEX_VALUE_SETS, and the FF_FORMULAS_F, FF_FORMULA_TYPES, and FF_FUNCTIONS tables for formula and function metadata. Payroll configuration lookups span PAY_ALL_PAYROLLS_F, PAY_BACKPAY_RULES, PAY_BACKPAY_SETS, PAY_BALANCE_DIMENSIONS, PAY_BALANCE_FEEDS_F, and PAY_BALANCE_TYPES. These reads supply identifiers and validate existence before downstream processing; the package is primarily a read-and-resolve utility rather than a transactional writer.

Usage Notes

HR_JP_ID_PKG is referenced by 23 other packages within the APPS schema and is typically invoked from Japan-localized HR and Payroll forms, concurrent programs, and custom PL/SQL that requires legislation-aware identifier resolution. Developers should call it when they need a business group's legislation code, default currency, flexfield structure, or the identifier of a payroll or HR setup entity without duplicating lookup logic. Because most functions accept p_error_when_not_exist, callers must decide whether a missing record should raise an exception or return NULL. LATEST_SQL must be treated as a dynamic SQL provider: the returned string should be executed with care and, where applicable, bound variables rather than string concatenation.