Search Results get_cat_id

Overview

APPS.PAY_FR_DB_PAY_SETUP is a French localization database package within Oracle E-Business Suite Payroll (PAY) that provides a programmatic API for creating and configuring payroll setup entities. It is delivered under the APPS schema and is classified in ETRM as an "OTHER" API, meaning it is a supportive utilities package rather than a formally published public interface. The package body header (pyfrsetp.pkb, version 120.0) confirms its role as a setup helper for the French legislation.

The business function of PAY_FR_DB_PAY_SETUP is to automate the creation of core payroll configuration objects — elements, input values, payrolls, consolidation sets, balances, balance classifications, and element links — without requiring manual form entry through the Payroll setup windows. By encapsulating these operations, it ensures consistency across dependent records such as generated balance feeds, default processing rules, and owner definitions, which would otherwise need to be created in the correct sequence across multiple setup screens.

Key Procedures and Functions

The ETRM metadata documents thirteen callable units within the package. CREATE_ELEMENT creates an element type from the supplied attributes. As noted in the package source comments, when the element is a payroll element, the routine also creates a default PAY_VALUE and a status processing rule, and generates balance feeds for balances fed by the same classification as the element. CREATE_INPUT_VALUE creates the input values associated with an element. CREATE_PAYROLL defines a payroll. CREATE_CONSOLIDATION_SET creates a consolidation set used to group payrolls for reporting and costing. CREATE_OWNER_DEFINITIONS creates the ownership definitions that control which business groups and legislative entities may use an object. SET_SESSION_DATE establishes the effective session date used by subsequent date-effective operations.

CREATE_ELEMENT_LINK creates the link between an element and the eligibility criteria that determine who can receive it. CREATE_BALANCE_TYPE creates a balance type, while CREATE_BALANCE_CLASSIFICATION creates the classification records that group balances. CREATE_DEFINED_BALANCE creates a defined (user-defined) balance. INSERT_CUSTOMIZE_RESTRICTION and INSERT_RESTRICTION_VALUES insert restriction records and their associated values. GET_DEFAULT_CURRENCY is a function that returns the default currency for the relevant legislation or business group context.

Tables Accessed

The package operates against the following tables through APPS synonyms. FND_CURRENCIES is used by GET_DEFAULT_CURRENCY to resolve currency codes; FND_FORM, FND_LANGUAGES, and FND_SESSIONS support localization and session context. HR_APPLICATION_OWNERSHIPS and HR_OWNER_DEFINITIONS back the owner definition routines. Payroll entities are persisted in PAY_ALL_PAYROLLS_F and grouped through PAY_CONSOLIDATION_SETS and PAY_CONSOLIDATION_SETS_S (the date-effective and translated views of consolidation sets). Balance configuration is written to PAY_BALANCE_TYPES, PAY_BALANCE_CLASSIFICATIONS and its _S date-effective counterpart, PAY_BALANCE_CATEGORIES_F, PAY_BALANCE_DIMENSIONS, and PAY_BALANCE_FEEDS_F. The balance feeds table is especially significant because CREATE_ELEMENT automatically inserts feed records for balances sharing the element's classification.

Usage Notes

PAY_FR_DB_PAY_SETUP is typically invoked during French localization setup, either from concurrent programs, from setup forms that call the package as a server-side API, or from custom installation and data-migration scripts that bulk-create payroll structures. ETRM notes that it is referenced by zero other packages, confirming it is a top-level setup utility rather than a shared library routine. Because the package manipulates date-effective payroll entities, callers should invoke SET_SESSION_DATE before performing date-sensitive operations, and should be aware that element creation has side effects on balances and processing rules. It is not a public API and Oracle does not guarantee backward compatibility of its signatures across releases, so customizations should treat it as a localization-specific implementation detail.