Results for “contact_typ_cd”

42 results




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

Overview

BEN_BATCH_DPNT_INFO is a table within the BEN schema (Advanced Benefits module) in Oracle EBS 12.1.1 and 12.2.2. As its description states, it stores dependent information created during a batch run. When the Benefits batch process executes — for example, a Life Events batch, open enrollment batch, or a dependent eligibility refresh — the system generates dependent-level records and stages them in this table. Each row captures a single dependent's benefit-relevant context as produced by that batch execution, tying the dependent to the originating benefit action so the batch results can be processed, audited, and reconciled afterward.

From a dimensional modeling perspective, the documented FK structure suggests a satellite-leaning classification. This is a heuristic mined from the single foreign-key relationship to BEN_BENEFIT_ACTIONS, meaning the table primarily holds descriptive, event-scoped attributes that surround a driving transaction rather than acting as an independent hub or a pure associative link.

Key Information Stored

The table contains 18 documented columns in the 12.2.2 physical schema. The most significant include:

Common Use Cases and Queries

Typical uses include auditing the effect of a batch benefit run, validating which dependents were created or modified, and reconciling coverage dates against actual enrollment records. Because the table is batch-staged, a common pattern is to join to BEN_BENEFIT_ACTIONS to reconstruct the triggering event.

  • Locate an action's generated dependents: SELECT d.* FROM ben.ben_batch_dpnt_info d WHERE d.benefit_action_id = :action_id;
  • Dependents for a participant: SELECT * FROM ben.ben_batch_dpnt_info WHERE person_id = :person_id;
  • Reconstruct action context: SELECT d.batch_dpnt_id, a.action_id, d.dpnt_person_id, d.enrt_cvg_strt_dt FROM ben.ben_batch_dpnt_info d JOIN ben.ben_benefit_actions a ON d.benefit_action_id = a.benefit_action_id;
  • Plan-scoped reporting: filter by pgm_id or pl_id to analyze dependent enrollments created across a batch cycle.

Related Objects

  • BEN_BENEFIT_ACTIONS — referenced via BEN_BATCH_DPNT_INFO.BENEFIT_ACTION_ID; the parent benefit action driving each row.
  • BEN_BENEFIT_ACTION related detail/audit tables in the BEN module, commonly joined for action-level context.
  • PER_ALL_PEOPLE_F — resolved through PERSON_ID and DPNT_PERSON_ID for participant and dependent names.
  • BEN_PGM_F and BEN_PL_F — benefit program and plan definitions joined on PGM_ID and PL_ID.
  • BEN_PRTT_ENRT_RSLT — actual enrollment results, useful for reconciling batch-created dependents.
  • FND_OBJECTS / audit views — supporting who-columns such as LAST_UPDATED_BY and CREATED_BY.