Search Results pay_au_process_modules_n2

Overview

HR.PAY_AU_PROCESS_MODULES is a seed-data configuration table within the Oracle E-Business Suite Australian Payroll (Payroll AU) product family. It defines the intersection between payroll processes and payroll modules, establishing which modules participate in a given process and in what order they execute. In functional terms, the table functions as the configuration backbone that determines how the Australian payroll run sequence is assembled from its constituent processing steps.

From a Data Vault modeling perspective, the ETRM metadata classifies this object heuristically as a link table. This classification reflects its structure: the table resolves a many-to-many relationship between two independent entities — PAY_AU_PROCESSES and PAY_AU_MODULES — through foreign key references rather than holding descriptive attributes about a single business entity. The presence of two foreign keys (PROCESS_ID and MODULE_ID) alongside its own surrogate key is characteristic of link-table design. Report developers and integration architects can treat this as a modeling suggestion when building downstream analytical layers, recognizing that the row itself represents an association rather than a standalone business object.

The table resides in the APPS_TS_SEED tablespace, confirming its role as seeded setup data rather than transactional data. It is owned by the HR schema and registered under FND Design Data as PAY.PAY_AU_PROCESS_MODULES.

Key Information Stored

The most significant columns in this table fall into three categories: identity, relationship, and control attributes.

• PROCESS_MODULE_ID — System-generated primary key sourced from the sequence PAY_AU_PROCESS_MODULES_S. This is the surrogate key and forms the leading column of the unique index PAY_AU_PROCESS_MODULES_U1, which is defined across (PROCESS_MODULE_ID, ZD_EDITION_NAME).
• PROCESS_ID — Foreign key to HR.PAY_AU_PROCESSES, identifying the parent payroll process to which the module assignment belongs.
• MODULE_ID — Foreign key to HR.PAY_AU_MODULES, identifying the module being associated with the process.
• PROCESS_SEQUENCE — Numeric value controlling the order in which the module executes within the process, governing sequencing behavior during the payroll run.
• ENABLED_FLAG — Indicator of whether the process-module association is currently active.
• OBJECT_VERSION_NUMBER — Optimistic locking counter incremented on each row update, used by the framework to detect concurrent modifications.
• ZD_EDITION_NAME — Editioning column supporting Oracle EBS Online Patching (adop) in Release 12.2.x, allowing edition-based redefinition without downtime.
• Standard WHO columns — CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, and LAST_UPDATE_LOGIN capture audit lineage for each row, with the user columns referencing FND_USER.USER_ID and the login column referencing FND_LOGINS.LOGIN_ID.

The unique index PAY_AU_PROCESS_MODULES_U1 functions as the business-key candidate, combining the surrogate identifier with the edition name to guarantee uniqueness across editions. A secondary nonunique index, PAY_AU_PROCESS_MODULES_N2, exists on MODULE_ID to support reverse lookups from module to process.

Common Use Cases and Queries

Typical uses of this table involve configuration validation, processing-order analysis, and dependency tracing. A common query joins the table to both parent entities to produce a readable list of module execution order within a process:

• Verifying which modules are enabled for a given payroll process, filtering on ENABLED_FLAG = 'Y' and ordering by PROCESS_SEQUENCE.
• Identifying all processes that reference a particular module, using the MODULE_ID index for efficient lookup.
• Auditing configuration changes by examining LAST_UPDATED_BY and LAST_UPDATE_DATE against FND_USER.
• Detecting gaps or duplicate sequence values within a process to prevent run-time ordering errors.

A representative query pattern is:

SELECT pm.PROCESS_MODULE_ID, pp.PROCESS_NAME, pm.MODULE_ID, pm.PROCESS_SEQUENCE, pm.ENABLED_FLAG
FROM HR.PAY_AU_PROCESS_MODULES pm
JOIN HR.PAY_AU_PROCESSES pp ON pp.PROCESS_ID = pm.PROCESS_ID
WHERE pm.ENABLED_FLAG = 'Y'
ORDER BY pp.PROCESS_ID, pm.PROCESS_SEQUENCE;

Related Objects

The table sits within a tightly coupled configuration cluster. The most significant related objects are:

• HR.PAY_AU_PROCESSES — Parent entity referenced via PROCESS_ID; defines the payroll processes available in the Australian localization.
• HR.PAY_AU_MODULES — Parent entity referenced via MODULE_ID; defines the payable modules assignable to processes.
• PAY_AU_PROCESS_MODULES_S — Sequence generating the surrogate primary key.
• FND_USER — Referenced indirectly through CREATED_BY and LAST_UPDATED_BY.
• FND_LOGINS — Referenced through LAST_UPDATE_LOGIN.
• PAY_AU_PROCESS_MODULES_U1 and N2 — Supporting indexes for uniqueness and module-based access.

Because the table is seed data, direct DML is typically performed through Oracle-delivered setup or patching rather than end-user screens, making it primarily a read target for reporting and validation queries.