Search Results pay_payroll_list




Overview

PAY_PAYROLL_LIST is a table in the HR schema within Oracle E-Business Suite, owned by the Payroll (PAY) product. Its documented purpose is to hold the list of payrolls that a secure user can access, functioning as the intersection between payroll definitions and Oracle EBS security profiles. The table enables row-level data security by determining which payrolls a given security profile — and therefore a given user assigned to that profile — is permitted to view, query, or process within the Payroll module. Physically, the table is documented in ETRM 12.2.2 with the HR owner and six columns.

From a Data Vault modeling perspective, the heuristic classification of this object is satellite-leaning. This suggests that PAY_PAYROLL_LIST is best modeled as a satellite attached to a parent hub or link (here, the security profile), capturing the associations and attributes dependent on that parent key rather than acting as an independent hub. It records the assignment of payrolls to security profiles, a relationship-driven, attribute-bearing structure consistent with satellite treatment.

Key Information Stored

The table is documented with six columns, of which the following are the most significant for identification and relationship purposes:

  • PAYROLL_ID — Identifies the payroll that the security profile is permitted to access. This is a core business-key candidate in combination with the security profile identifier.
  • SECURITY_PROFILE_ID — The foreign key referencing PER_SECURITY_PROFILES, establishing which security profile governs the payroll access grant. Together with PAYROLL_ID, it forms the natural composite key of the association.
  • REQUEST_ID — The concurrent request identifier under which the access-list record was created or maintained, useful for auditing and tracing the process that generated the assignment.
  • PROGRAM_APPLICATION_ID — The application identifier of the concurrent program that created or updated the record.
  • PROGRAM_ID — The concurrent program identifier responsible for the record, supporting audit lineage.
  • PROGRAM_UPDATE_DATE — The date and time the record was last updated by the concurrent program, serving as a timestamp for change tracking.

The documented foreign key relationship is PAY_PAYROLL_LIST.SECURITY_PROFILE_ID referencing PER_SECURITY_PROFILES. No separate unique index is documented in the supplied metadata beyond the implied composite business key of PAYROLL_ID and SECURITY_PROFILE_ID; the surrogate primary key role is carried by the combination of these access-defining columns.

Common Use Cases and Queries

The most common use case is determining which payrolls a security profile or user may access. A typical query joins the payroll list to the security profile and the user's assigned profile to constrain Payroll reports:

  • Access resolution: SELECT ppl.payroll_id FROM pay_payroll_list ppl WHERE ppl.security_profile_id = :profile_id — returns the payrolls granted to a profile.
  • Security auditing: Join to PER_SECURITY_PROFILES to enumerate profiles and their permitted payrolls, identifying over-broad grants.
  • Change tracking: Use PROGRAM_UPDATE_DATE to report recently modified access grants.
  • Reporting: Payroll reports and concurrent processes consult this table to enforce data-level security, restricting results to payrolls the running user's profile authorizes.

Because the table is security-oriented, queries are frequently combined with the security profile tables and user assignments to resolve effective access at runtime.

Related Objects

  • PER_SECURITY_PROFILES — Referenced by PAY_PAYROLL_LIST.SECURITY_PROFILE_ID; the parent security profile table that anchors this association.
  • PAY_ALL_PAYROLLS_F / PAY_PAYROLLS_F — The payroll definition tables; join on PAYROLL_ID to resolve payroll names and attributes.
  • FND_CONCURRENT_REQUESTS — Relates on REQUEST_ID to describe the concurrent request that created or updated access records.
  • FND_APPLICATION / FND_CONCURRENT_PROGRAMS — Relate on PROGRAM_APPLICATION_ID and PROGRAM_ID to identify the program responsible for the record.

These relationships confirm the table's role as a security-assignment satellite linking payroll definitions to security profiles, with audit attributes inherited from the concurrent processing framework.