Search Results pay_au_processes




Overview
Explore in AI Chat

Overview

PAY_AU_PROCESSES is an Oracle E-Business Suite payroll table owned by the HR schema and maintained within the PAY (Payroll) product family. It defines the processes that can be executed by the generic code caller, serving as a registry of callable payroll processes together with the descriptive and control attributes that govern their use. In the Australian (AU) localization context implied by the object name, the table supports the registration and identification of processes invoked through the Oracle Payroll generic code caller architecture, which allows payroll logic to be driven by data-defined process entries rather than hard-coded calls.

From a dimensional modeling perspective, the provided metadata yields a heuristic Data Vault classification of "hub-leaning." This classification derives from the observation that PAY_AU_PROCESSES functions primarily as a source of process identity, with a surrogate primary key (PROCESS_ID) and business-key candidates built on short name and name attributes. Downstream tables reference this object through PROCESS_ID foreign keys, distributing the descriptive and parameter detail to dependent structures. As a modeling suggestion, PAY_AU_PROCESSES is therefore best treated as a hub candidate, with its descriptive columns (such as ENABLED_FLAG, DESCRIPTION, and ACCRUAL_CATEGORY) potentially separated into satellite structures if a formal Data Vault design is applied.

Key Information Stored

The table is documented with 15 columns in the ETRM 12.2.2 physical schema. The most significant columns include:

  • PROCESS_ID — The surrogate primary key, defined by the PAY_AU_PROCESSES_PK constraint. This is the internal identifier used by all foreign key relationships.
  • SHORT_NAME — A business-key candidate forming part of the PAY_AU_PROCESSES_UK1 unique key together with BUSINESS_GROUP_ID and LEGISLATION_CODE. It provides a compact, human-readable process identifier.
  • NAME — A business-key candidate forming part of the PAY_AU_PROCESSES_UK2 unique key, again combined with BUSINESS_GROUP_ID and LEGISLATION_CODE.
  • BUSINESS_GROUP_ID — Identifies the business group that owns the process definition, enabling multi-tenant separation within a single installation.
  • LEGISLATION_CODE — The legislation under which the process is valid, which for this object is predominantly Australia.
  • ENABLED_FLAG — Controls whether the process is available for execution through the generic code caller.
  • DESCRIPTION — Free-text explanation of the process purpose.
  • ACCRUAL_CATEGORY — Classifies the process relative to accrual processing semantics.
  • OBJECT_VERSION_NUMBER, CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, and LAST_UPDATE_LOGIN — Standard Oracle EBS audit and concurrency-control columns.
  • ZD_EDITION_NAME — The editioning column used in the 12.2 online patching architecture and included in the PAY_AU_PROCESSES_U1 unique index alongside PROCESS_ID.

The separation of the surrogate key (PROCESS_ID) from the two business-key candidates (SHORT_NAME and NAME combined with BUSINESS_GROUP_ID and LEGISLATION_CODE) reflects the standard EBS pattern of permitting surrogate-key relationships while enforcing natural-key uniqueness across the legislative and organizational scope.

Common Use Cases and Queries

Typical usage centers on resolving process identity, reporting on enabled processes, and joining to dependent parameter and module definitions. The following query lists enabled processes for a given business group and legislation:

SELECT p.process_id, p.short_name, p.name, p.description FROM hr.pay_au_processes p WHERE p.business_group_id = :p_bg_id AND p.legislation_code = 'AU' AND p.enabled_flag = 'Y' ORDER BY p.name;

To retrieve the parameters associated with a process, join to PAY_AU_PROCESS_PARAMETERS on PROCESS_ID. To identify which modules expose a process, join to PAY_AU_PROCESS_MODULES on PROCESS_ID. These joins support reporting on the generic code caller configuration and are useful when auditing process availability after an upgrade or localization patch. Lookups by business key typically filter on SHORT_NAME or NAME together with BUSINESS_GROUP_ID and LEGISLATION_CODE, exploiting the PAY_AU_PROCESSES_UK1 and PAY_AU_PROCESSES_UK2 unique indexes.

Related Objects

The following tables reference PAY_AU_PROCESSES through the documented foreign keys and are the most significant related objects:

  • PAY_AU_PROCESS_MODULES — References PAY_AU_PROCESSES via PAY_AU_PROCESS_MODULES.PROCESS_ID, associating process definitions with the modules that expose them.
  • PAY_AU_PROCESS_PARAMETERS — References PAY_AU_PROCESSES via PAY_AU_PROCESS_PARAMETERS.PROCESS_ID, defining the parameters accepted by each callable process.

Additional dependencies include the primary key constraint PAY_AU_PROCESSES_PK on PROCESS_ID, the unique constraints PAY_AU_PROCESSES_UK1 and PAY_AU_PROCESSES_UK2, and the editioning index PAY_AU_PROCESSES_U1 on (PROCESS_ID, ZD_EDITION_NAME). These objects collectively enforce the identity, uniqueness, and online-patching integrity of the process registry.