Search Results ben_batch




Overview
Explore in AI Chat

Overview

BEN.BEN_BATCH_BNFT_CERT_INFO is a transactional staging table within the Oracle E-Business Suite Benefits (BEN) schema. It stores benefit certification related data that results from running concurrent manager processes. The BEN_BATCH family of tables is designed to capture concurrent manager output so that results remain available for inclusion in reports such as the activity summary report and the audit log. Critically, this information is persisted regardless of whether the originating process is run in validate (rollback) mode or commit mode, which allows administrators and auditors to review what a process would have done before, during, or after the actual commit.

Under the heuristic Data Vault classification mined from its foreign key structure, this table is modeled as a standalone structure — that is, it neither functions as a hub, link, nor satellite in the strict Data Vault sense. Its role is instead that of a batch results or audit staging entity keyed on a system-generated identifier. In Oracle EBS 12.1.1 and 12.2.2, the table resides in the APPS_TS_TX_DATA tablespace with a PCTFREE of 10, and its indexes reside in APPS_TS_TX_IDX.

Key Information Stored

The table is anchored by the surrogate primary key BATCH_BENFT_CERT_ID (NUMBER(15)), which is defined by the unique index BEN_BATCH_BNFT_CERT_INFO_PK. This column is system-generated and serves as the single documented unique business-key candidate; no composite natural key is documented for this table. The most significant business columns are:

Common Use Cases and Queries

Because the table stores batch output independent of commit or rollback, its primary use cases center on reconciliation, audit, and exception reporting. A typical query joins the table to BEN_BENEFIT_ACTION and PER_PEOPLE_F to report on certification results per person per action:

  • Audit reporting: retrieve all rows for a specific benefit action to confirm what the concurrent process recorded, regardless of commit status.
  • Exception analysis: identify rows where ENRT_CTFN_RECD_DT is null or where TYP_CD indicates an unexpected classification.
  • Staging reconciliation: compare batch rows against committed enrollment data to detect discrepancies between validate and commit runs.

Sample pattern: SELECT b.BATCH_BENFT_CERT_ID, b.PERSON_ID, b.ACTN_TYP_ID, b.ENRT_CTFN_RECD_DT FROM BEN.BEN_BATCH_BNFT_CERT_INFO b WHERE b.BENEFIT_ACTION_ID = :action_id;. Joins to BEN_ACTN_TYP_F via ACTN_TYP_ID allow action type description lookup, and joins to PER_PEOPLE_F via PERSON_ID resolve the person's name.

Related Objects

  • BEN.BEN_BENEFIT_ACTION — Referenced by BENEFIT_ACTION_ID; the parent action for the batch result.
  • BEN.BEN_ACTN_TYP_F — Referenced by ACTN_TYP_ID; provides action type definition and description.
  • PER.PER_PEOPLE_F — Referenced by PERSON_ID; supplies person-level identity data.
  • BEN.BEN_BATCH_* (sibling tables) — Share the batch staging pattern for other concurrent process outputs.
  • FND.FND_USER / FND.FND_LOGINS — Referenced by the Who columns for user and login attribution.
  • Activity Summary Report and Audit Log — Consume this table's rows as reporting sources.