Results for “pay_population_ranges”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

PAY_POPULATION_RANGES is a Payroll (PAY) module table owned by the HR schema in Oracle E-Business Suite 12.1.1 and 12.2.2. Its documented purpose is to store PERSON_ID ranges used for parallel processing of payroll runs. When a payroll action is submitted, Oracle Payroll divides the population of assignees into discrete chunks so that multiple worker processes can execute concurrently, substantially reducing the elapsed time of large payroll runs. PAY_POPULATION_RANGES is the persistent registry of those chunk boundaries, linking each chunk to its parent payroll action and recording the start and end person identifiers that define the work unit.

In Data Vault modeling terms, the heuristic classification derived from the foreign key structure is satellite-leaning. The table describes and qualifies a parent business entity—the payroll action—rather than representing an independent business concept or an associative relationship between two hubs. Its grain is one row per payroll action per chunk, and its attributes are descriptive state (range boundaries and processing status) that change as the parallel run progresses.

Key Information Stored

The table as documented in ETRM 12.2.2 contains nine columns. The composite primary key, defined by constraint PAY_POPULATION_RANGES_PK, consists of PAYROLL_ACTION_ID and CHUNK_NUMBER. Together these form the surrogate key for the table and also serve as the principal business-key candidate, since no separate unique index is documented.

• PAYROLL_ACTION_ID — Foreign key to PAY_PAYROLL_ACTIONS; identifies the payroll action (typically a payroll run or related process) to which the range belongs.
• CHUNK_NUMBER — Sequence number identifying the individual chunk within the payroll action.
• STARTING_PERSON_ID — Lower boundary of the PERSON_ID range assigned to the chunk.
• ENDING_PERSON_ID — Upper boundary of the PERSON_ID range assigned to the chunk.
• RANGE_STATUS — Processing state of the chunk, used to track whether the range is pending, in progress, or complete.
• RAND_CHUNK_NUMBER — Alternate chunk identifier, typically associated with randomized chunking of the population.
• PERSON_ID — A specific person identifier associated with the row, used in the context of the range or its assignment.
• SOURCE_ID and SOURCE_TYPE — Identify the origin of the population definition, allowing ranges to be traced back to the source that generated them.

Common Use Cases and Queries

The primary operational use case is monitoring and troubleshooting parallel payroll runs. Payroll administrators and support teams query this table to confirm how a population was divided, which ranges have completed, and whether any chunk remains outstanding.

• Listing all chunks for a payroll action: SELECT CHUNK_NUMBER, STARTING_PERSON_ID, ENDING_PERSON_ID, RANGE_STATUS FROM HR.PAY_POPULATION_RANGES WHERE PAYROLL_ACTION_ID = :action_id ORDER BY CHUNK_NUMBER;
• Identifying incomplete chunks during a stalled run: SELECT * FROM HR.PAY_POPULATION_RANGES WHERE PAYROLL_ACTION_ID = :action_id AND RANGE_STATUS <> 'C';
• Measuring chunk skew to assess whether the population was evenly distributed, by comparing ENDING_PERSON_ID minus STARTING_PERSON_ID across chunks.
• Confirming the range containing a specific person: SELECT CHUNK_NUMBER FROM HR.PAY_POPULATION_RANGES WHERE PAYROLL_ACTION_ID = :action_id AND :person_id BETWEEN STARTING_PERSON_ID AND ENDING_PERSON_ID;

Reporting use cases include audit of parallel processing configuration, capacity planning for payroll batch windows, and post-run reconciliation of processed headcount against range boundaries.

Related Objects

The documented foreign key relationship ties this table directly to PAY_PAYROLL_ACTIONS, the parent entity governing payroll actions. Additional objects of significance within the payroll processing model include PAY_PAYROLL_RUNS and related action-result tables that record the outcome of each action. The PERSON_ID columns align with PER_ALL_PEOPLE_F, which supplies the person identities bounded by each range. Payroll assignment and process result tables, together with the concurrent program definitions that submit parallel payroll, also depend conceptually on the chunking data held here. Because the metadata provided documents only one explicit foreign key, the remaining relationships should be verified against the specific 12.1.1 or 12.2.2 instance before use in production queries.