Search Results pay_au_process_modules

Overview

PAY_AU_PROCESS_MODULES is a Payroll (PAY) module table owned by the HR schema. It defines the intersection between processes and modules consumed by the Australian payroll generic code caller. In practical terms, the table acts as a configuration map: it declares which functional modules participate in a given payroll process and the order in which those modules are invoked. This intersection determines the executable behaviour of Australian payroll processing, including which legislative or business rules are applied during a run.

The table is exposed in Oracle EBS 12.1.1 and 12.2.2, with the 12.2.2 documented physical schema listing 12 columns. From a dimensional modelling perspective, the FK topology suggests a link classification: the table resolves a many-to-many relationship between PAY_AU_PROCESSES and PAY_AU_MODULES and carries descriptive attributes such as sequence and enablement, making it a candidate for a Data Vault link rather than a standalone hub or satellite.

Key Information Stored

The most significant columns are:

PROCESS_MODULE_ID — the surrogate primary key (PAY_AU_PROCESS_MODULES_PK) uniquely identifying each process-to-module association.
PROCESS_ID — foreign key to PAY_AU_PROCESSES, identifying the parent process.
MODULE_ID — foreign key to PAY_AU_MODULES, identifying the participating module.
PROCESS_SEQUENCE — the execution order of the module within the process; part of the documented unique index PAY_AU_PROCESS_MODULES_UK1 alongside PROCESS_ID, making (PROCESS_ID, PROCESS_SEQUENCE) a business-key candidate.
ENABLED_FLAG — indicates whether the association is active.
CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — standard EBS audit columns.
OBJECT_VERSION_NUMBER — optimistic locking column supporting concurrent updates.
ZD_EDITION_NAME — editioning column supporting EBS 12.2 online patching; it appears in the unique index PAY_AU_PROCESS_MODULES_U1 with PROCESS_MODULE_ID.

Common Use Cases and Queries

Typical reporting and diagnostic scenarios include confirming which modules run for a process and in what order, auditing enablement, and rebuilding the process definition after patching. A representative join query is:

SELECT p.process_name, m.module_name, pm.process_sequence, pm.enabled_flag FROM pay_au_process_modules pm JOIN pay_au_processes p ON p.process_id = pm.process_id JOIN pay_au_modules m ON m.module_id = pm.module_id WHERE pm.enabled_flag = 'Y' ORDER BY p.process_name, pm.process_sequence;

Analysts may also extract the ordered module list for a single process by filtering on PROCESS_ID, or reconcile configuration across editions using ZD_EDITION_NAME. Because the table is configuration metadata, direct DML is generally avoided in favour of the application's own setup and upgrade paths.

Related Objects

PAY_AU_PROCESSES — referenced via PAY_AU_PROCESS_MODULES.PROCESS_ID; defines the parent processes.
PAY_AU_MODULES — referenced via PAY_AU_PROCESS_MODULES.MODULE_ID; defines the available modules.
Related process/module configuration tables in the PAY schema that share the same generic code caller framework, maintained through the same seeded setup data.
Audit and editioning infrastructure columns (WHO columns, ZD_EDITION_NAME) linked to standard EBS edition views.

Table: PAY_AU_PROCESS_MODULES 12.1.1
owner:HR, object_type:TABLE, fnd_design_data:PAY.PAY_AU_PROCESS_MODULES, object_name:PAY_AU_PROCESS_MODULES, status:VALID, product: PAY - Payroll , description: Defines the intersection between processes and modules used by the generic code caller. , implementation_dba_data: HR.PAY_AU_PROCESS_MODULES ,
Table: PAY_AU_PROCESS_MODULES 12.2.2
owner:HR, object_type:TABLE, fnd_design_data:PAY.PAY_AU_PROCESS_MODULES, object_name:PAY_AU_PROCESS_MODULES, status:VALID, product: PAY - Payroll , description: Defines the intersection between processes and modules used by the generic code caller. , implementation_dba_data: HR.PAY_AU_PROCESS_MODULES ,
Table: PAY_AU_PROCESSES 12.2.2
owner:HR, object_type:TABLE, fnd_design_data:PAY.PAY_AU_PROCESSES, object_name:PAY_AU_PROCESSES, status:VALID, product: PAY - Payroll , description: This table defines the processes that can be executed by the generic code caller. , implementation_dba_data: HR.PAY_AU_PROCESSES ,
Table: PAY_AU_PROCESSES 12.1.1
owner:HR, object_type:TABLE, fnd_design_data:PAY.PAY_AU_PROCESSES, object_name:PAY_AU_PROCESSES, status:VALID, product: PAY - Payroll , description: This table defines the processes that can be executed by the generic code caller. , implementation_dba_data: HR.PAY_AU_PROCESSES ,
Table: PAY_AU_MODULES 12.1.1
owner:HR, object_type:TABLE, fnd_design_data:PAY.PAY_AU_MODULES, object_name:PAY_AU_MODULES, status:VALID, product: PAY - Payroll , description: Defines the processes that can be executed by the generic code caller. , implementation_dba_data: HR.PAY_AU_MODULES ,
Table: PAY_AU_MODULES 12.2.2
owner:HR, object_type:TABLE, fnd_design_data:PAY.PAY_AU_MODULES, object_name:PAY_AU_MODULES, status:VALID, product: PAY - Payroll , description: Defines the processes that can be executed by the generic code caller. , implementation_dba_data: HR.PAY_AU_MODULES ,