Search Results ben_batch_parameter




Overview
Explore in AI Chat

Overview

BEN_BATCH_PARAMETER is a configuration table within the Oracle Advanced Benefits (BEN) module of Oracle E-Business Suite, documented as valid in both release 12.1.1 and 12.2.2. The table stores the runtime parameters that govern batch execution processes for benefits processing, and it exists to allow administrators to control how concurrent batch programs behave, including the degree of parallelism, error tolerance thresholds, and the granularity with which records are processed. Each row in the table represents a discrete combination of batch execution code and business group, ensuring that batch behavior can be tailored per legislative data group or operating unit.

The ETRM metadata classifies BEN_BATCH_PARAMETER heuristically as standalone from a Data Vault perspective. In practice this suggests the table is best modeled as a satellite attached to a business-group hub or as a reference/lookup satellite, since it carries descriptive and control attributes (thread counts, chunk sizes, error limits) rather than participating in many-to-many relationships. It does not appear to act as a junction or link table.

Key Information Stored

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

  • BATCH_PARAMETER_ID — the surrogate primary key, enforced by the unique index BEN_BATCH_PARAMETER_PK. This is the only documented unique index and therefore the only column explicitly marked as a business-key candidate at the schema level.
  • BATCH_EXE_CD — the batch execution code that identifies which concurrent program or batch routine the parameter row applies to.
  • BUSINESS_GROUP_ID — scopes the parameter set to a specific business group, enabling per-organization configuration.
  • THREAD_CNT_NUM — the number of worker threads or parallel processes permitted during execution.
  • MAX_ERR_NUM — the maximum number of errors tolerated before the batch is aborted.
  • CHUNK_SIZE — the volume of records processed in a single commit or fetch cycle, affecting memory and rollback behavior.
  • OBJECT_VERSION_NUMBER — the optimistic locking column used by the Oracle Application Framework (OAF) to detect concurrent updates.
  • LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN, CREATED_BY, CREATION_DATE — standard EBS audit WHO columns tracking creation and modification metadata.

Common Use Cases and Queries

Administrators query BEN_BATCH_PARAMETER to diagnose performance or failure issues in benefits batch runs. A frequent pattern retrieves the active parameters for a given batch code:

  • SELECT BATCH_EXE_CD, BUSINESS_GROUP_ID, THREAD_CNT_NUM, MAX_ERR_NUM, CHUNK_SIZE FROM BEN.BEN_BATCH_PARAMETER WHERE BATCH_EXE_CD = :p_code AND BUSINESS_GROUP_ID = :p_bg_id;
  • Reporting on audit history: selecting LAST_UPDATED_BY and LAST_UPDATE_DATE to determine who last tuned a parameter set.
  • Tuning exercises that compare THREAD_CNT_NUM against actual concurrent manager load to right-size parallelism.

Because the table is small and configuration-oriented, queries are typically simple single-table lookups rather than complex analytical joins.

Related Objects

Given its standalone classification, BEN_BATCH_PARAMETER has limited declared foreign-key dependencies in the documented metadata. The most relevant related objects include:

  • BEN_BATCH_PARAMETER_PK — the primary key index that enforces uniqueness on BATCH_PARAMETER_ID.
  • FND_CONCURRENT_PROGRAMS — the concurrent program definitions that the BATCH_EXE_CD values ultimately drive.
  • FND_BUSINESS_GROUPS — referenced through BUSINESS_GROUP_ID to resolve the owning legislative or business group.
  • BEN_BATCH_* runtime tables — the transactional tables populated when a batch executes, which consume the parameter values stored here.
  • FND_USER — joined via CREATED_BY, LAST_UPDATED_BY, and LAST_UPDATE_LOGIN for audit reporting.