Results for “control_type”

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

Overview

PAY_BATCH_CONTROL_TOTALS is a Payroll (PAY) module table owned by the HR schema in Oracle E-Business Suite 12.1.1 and 12.2.2. It holds user-defined control totals that support the Batch Element Entry (BEE) process, the mechanism by which large volumes of element entries are loaded for a payroll run through spreadsheets or interface files. Each row defines a validation threshold that the Batch Element Entry process checks against the aggregated values uploaded for a given batch, allowing payroll administrators to detect discrepancies before entries are committed to the payroll.

From a Data Vault modeling perspective, the mined classification suggests this table is satellite-leaning. It carries a surrogate primary key (BATCH_CONTROL_ID) and a foreign key to PAY_BATCH_HEADERS, so it functions as a descriptive child record attached to a parent batch header rather than as an independent hub or a pure link table. In dimensional terms, it behaves as a dependent detail table whose grain is one row per control total definition per batch.

Key Information Stored

The table contains six documented columns. The most significant are:

• BATCH_CONTROL_ID — The surrogate primary key, uniquely defined by the PAY_BATCH_CONTROL_TOTALS_PK index. It is the sole documented unique index and therefore the only business-key candidate identified in the metadata.
• BATCH_ID — Foreign key to PAY_BATCH_HEADERS, associating the control total with its parent batch. This is the principal join column in the model.
• CONTROL_TYPE — Identifies the category of control total being defined, indicating what aspect of the batch the total is intended to validate.
• CONTROL_TOTAL — Stores the expected or threshold aggregate value against which uploaded batch data is compared.
• CONTROL_STATUS — Records the processing state of the control total, for example whether it has been satisfied, breached, or is still pending evaluation.
• OBJECT_VERSION_NUMBER — The standard Oracle EBS optimistic locking column used to manage concurrent updates through the OA Framework.

The presence of OBJECT_VERSION_NUMBER and the surrogate key pattern is consistent with tables maintained through the Oracle Applications Framework, so direct DML should be undertaken with caution.

Common Use Cases and Queries

Typical scenarios include validating a batch before submission, auditing which batches failed control checks, and reporting on configured totals. A representative query joining the control totals to their parent batch header follows:

• Pre-submission validation: SELECT b.batch_id, c.control_type, c.control_total, c.control_status FROM pay_batch_control_totals c, pay_batch_headers b WHERE c.batch_id = b.batch_id AND c.control_status = 'FAILED';
• Configuration review: List all control totals defined for a specific batch to confirm expected thresholds before a Batch Element Entry run.
• Audit reporting: Aggregate control totals by CONTROL_TYPE across batches to identify recurring discrepancies or misconfigured thresholds.

Because control totals exist primarily as pre-commit validation aids, most operational use occurs before payroll processing rather than after.

Related Objects

The following objects are most closely associated with PAY_BATCH_CONTROL_TOTALS:

• PAY_BATCH_HEADERS — The parent table, joined on PAY_BATCH_CONTROL_TOTALS.BATCH_ID = PAY_BATCH_HEADERS.BATCH_ID. This is the only documented foreign key relationship.
• PAY_BATCH_LINES — Batch element entry line detail, representing the data the control totals are designed to validate.
• PAY_ELEMENT_ENTRIES and PAY_ELEMENT_ENTRY_VALUES — The underlying element entry records created once a batch is successfully processed.
• PAY_BATCH_CONTROL_TOTALS_PK — The primary key index enforcing uniqueness on BATCH_CONTROL_ID.

No additional foreign keys or dependent views are documented in the ETRM metadata, so the relationship to PAY_BATCH_HEADERS is the primary structural dependency to observe when querying or extracting this data.