Search Results pay_au_processes_u1




Overview
Explore in AI Chat

Overview

HR.PAY_AU_PROCESSES is a seed data table in the Oracle E-Business Suite HR schema that defines the set of processes which may be executed by the generic code caller within the Australian payroll localization. Each row describes a discrete executable process, scoped optionally to a specific business group and to a legislation code, allowing localization or implementation teams to register, describe, and enable the processes available to downstream payroll and statutory reporting logic. The table resides in the APPS_TS_SEED tablespace, consistent with its role as reference and configuration data rather than transactional data.

From a Data Vault modeling perspective, the heuristic classification for this object is hub-leaning. The stable, system-generated PROCESS_ID serves as the primary key and the natural anchor for the entity, while the descriptive attributes and audit columns behave as satellite-style context. This classification is a modeling suggestion only; the physical implementation remains a conventional Oracle EBS table with standard WHO columns and a surrogate key.

Key Information Stored

The table contains fifteen documented columns. The most significant are summarized below.

  • PROCESS_ID (NUMBER, mandatory) — the surrogate primary key, system-generated from the sequence PAY_AU_PROCESSES_S and defined by the PAY_AU_PROCESSES_PK constraint.
  • SHORT_NAME (VARCHAR2(30)) — a concise internal identifier for the process, typically used by code callers.
  • NAME (VARCHAR2(30)) — the descriptive name of the process as presented to users.
  • ENABLED_FLAG (VARCHAR2(30)) — controls whether the process is active and available for execution.
  • BUSINESS_GROUP_ID (NUMBER) — part of the business unique key; scopes the process definition to a specific business group.
  • LEGISLATION_CODE (VARCHAR2(30)) — part of the business unique key; scopes the process to a legislation such as AU.
  • DESCRIPTION (VARCHAR2(80)) — free-text explanation of the process purpose.
  • ACCRUAL_CATEGORY (VARCHAR2(30)) — associates the process with an accrual category.
  • OBJECT_VERSION_NUMBER (NUMBER) — optimistic locking column that increments on each row update.
  • CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — the standard WHO audit columns tracking row provenance.
  • ZD_EDITION_NAME (VARCHAR2(30)) — editioning column supporting online patching in EBS 12.2.x.

The business-key candidate documented for this table is the unique index PAY_AU_PROCESSES_U1, defined over PROCESS_ID and ZD_EDITION_NAME. Business Group and Legislation Code are also described in the metadata as parts of the logical unique key.

Common Use Cases and Queries

Typical usage centers on validating which processes are enabled for a given business group and legislation, and on joining process metadata to the dependent module and parameter tables. A representative query lists enabled Australian processes:

  • SELECT p.PROCESS_ID, p.SHORT_NAME, p.NAME FROM HR.PAY_AU_PROCESSES p WHERE p.ENABLED_FLAG = 'Y' AND p.LEGISLATION_CODE = 'AU';
  • Restricting by business group: ... AND p.BUSINESS_GROUP_ID = :p_bg_id
  • Reporting joins to dependent tables as shown below are also common for auditing which modules and parameters attach to each process.

Related Objects

The table is referenced by two documented child tables, both joining on PROCESS_ID:

  • PAY_AU_PROCESS_MODULES — references HR.PAY_AU_PROCESSES.PROCESS_ID and defines the modules associated with each process.
  • PAY_AU_PROCESS_PARAMETERS — references HR.PAY_AU_PROCESSES.PROCESS_ID and defines the parameters accepted by each process.
  • PAY_AU_PROCESSES_S — the sequence that generates PROCESS_ID values.
  • FND_USER — the foreign-key target for CREATED_BY and LAST_UPDATED_BY.
  • FND_LOGINS — the foreign-key target for LAST_UPDATE_LOGIN.