Search Results pay_functional_usages




Overview
Explore in AI Chat

Overview

PAY_FUNCTIONAL_USAGES is a Payroll (PAY) module table owned by the HR schema in Oracle E-Business Suite 12.1.1 and 12.2.2. Its documented purpose is to enable functional areas for specific legislations, business groups, and payrolls. In practical terms, the table acts as a configuration matrix: it records which payroll functional areas are active for a given combination of legislation, business group, and payroll. This controls the availability of downstream payroll features and drives processing behavior across the Payroll application.

The ETRM metadata classifies this object, using a heuristic derived from its foreign-key structure, as satellite-leaning in Data Vault terms. This suggests modeling PAY_FUNCTIONAL_USAGES as a satellite attached to a hub or link representing the payroll or business group context, with the enabled functional area treated as descriptive, time-varying attribute data rather than as an independent business key.

Key Information Stored

The table contains 11 documented columns. The surrogate primary key is USAGE_ID, enforced through the PAY_FUNCTIONAL_USAGES_PK unique index. In 12.2.2, that index is defined over the composite of USAGE_ID and ZD_EDITION_NAME, reflecting the edition-based redefinition architecture introduced with Online Patching.

  • USAGE_ID — Surrogate primary key uniquely identifying each functional usage record.
  • AREA_ID — Foreign key to PAY_FUNCTIONAL_AREAS, identifying the specific payroll functional area being enabled.
  • LEGISLATION_CODE — The legislation for which the functional area is enabled, a core business-key candidate.
  • BUSINESS_GROUP_ID — The business group context for the enablement, a core business-key candidate.
  • PAYROLL_ID — The specific payroll for which the functional area is enabled, a core business-key candidate.
  • LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — Standard WHO audit columns recording the most recent modification.
  • CREATED_BY, CREATION_DATE — Standard WHO audit columns recording record creation.
  • ZD_EDITION_NAME — Edition identifier supporting Online Patching in 12.2.2.

The combination of AREA_ID, LEGISLATION_CODE, BUSINESS_GROUP_ID, and PAYROLL_ID constitutes the effective business key, while USAGE_ID remains the technical identifier.

Common Use Cases and Queries

Typical uses include auditing which functional areas are enabled for a payroll, comparing configurations across business groups, and troubleshooting why a payroll feature is unavailable. A representative query joining the areas table is:

  • SELECT pfu.usage_id, pfa.area_name, pfu.legislation_code, pfu.business_group_id, pfu.payroll_id FROM pay_functional_usages pfu JOIN pay_functional_areas pfa ON pfu.area_id = pfa.area_id WHERE pfu.business_group_id = :p_bg_id;
  • Filtering by PAYROLL_ID to list enabled areas for a single payroll.
  • Grouping by AREA_ID to report functional area adoption across legislations.

These patterns support functional configuration reports, upgrade and patch impact analysis, and data migration validation.

Related Objects

  • PAY_FUNCTIONAL_AREAS — Referenced via PAY_FUNCTIONAL_USAGES.AREA_ID; defines the functional area catalog.
  • PAY_FUNCTIONAL_USAGES_PK — Primary key index on USAGE_ID and ZD_EDITION_NAME.
  • HR business group and payroll entities — Referenced through BUSINESS_GROUP_ID and PAYROLL_ID.
  • Payroll legislation configuration objects — Referenced through LEGISLATION_CODE.

Together these objects define the scope and enablement of payroll functionality across the enterprise.