Search Results ben_ext_incl_chg




Overview
Explore in AI Chat

Overview

BEN_EXT_INCL_CHG is a table in the BEN (Advanced Benefits) schema of Oracle E-Business Suite. Its documented description is "Extract changes inclusion criteria," which positions it within the benefits extract framework that produces outbound data files for carriers, payroll systems, and third-party benefit providers. In release 12.2.2 the object is documented with 14 columns and is registered as VALID in the ETRM repository; the same physical definition applies to 12.1.1 implementations, where the extract engine operates against the same BEN schema objects.

Functionally, the table stores the inclusion criteria that determine which record changes are captured when a benefits extract is executed. Each row associates a change event with the extract record definition and the data element within that record, allowing the extract process to filter the population of changed records that qualify for transmission.

Under the heuristic Data Vault classification derived from the foreign-key structure, this object is best modeled as a link. It resolves the relationship between a data element within a record and a record in a file, qualified by a change event, rather than holding descriptive attributes of a single business entity. This classification is a modeling suggestion, not a property of the delivered EBS table.

Key Information Stored

The surrogate primary key is EXT_INCL_CHG_ID, enforced by the unique index BEN_EXT_INCL_CHG_PK. In the documented 12.2.2 schema this index is defined over (EXT_INCL_CHG_ID, ZD_EDITION_NAME), reflecting the editioning mechanism used by the online patching architecture; the business-key candidate is therefore the composite of the surrogate identifier and the edition name rather than the identifier alone.

Common Use Cases and Queries

The principal use case is diagnosing extract output: when a changed record fails to appear in a generated extract file, the inclusion criteria rows for the affected record and data element are inspected. Administrators also review these rows when configuring new extracts or when a change event is added to an existing record definition.

A typical query joins the criteria to their parent record-in-file definition:

  • SELECT c.ext_incl_chg_id, c.chg_evt_cd, c.chg_evt_source, c.legislation_code, r.record_name
  • FROM ben.ben_ext_incl_chg c, ben.ben_ext_rcd_in_file r
  • WHERE c.ext_rcd_in_file_id = r.ext_rcd_in_file_id
  • AND c.business_group_id = :p_bg_id;

To trace a single data element across all applicable change events, filter on EXT_DATA_ELMT_IN_RCD_ID. Reporting extracts commonly restrict on LEGISLATION_CODE and CHG_EVT_CD to reconcile which change events drive file generation for a given legislative context. Because the table is editioned, queries that must read the run-time edition should either rely on the editioning view or filter ZD_EDITION_NAME = 'ORA$BASE' when inspecting seed data.

Related Objects

  • BEN_EXT_DATA_ELMT_IN_RCD — referenced through EXT_DATA_ELMT_IN_RCD_ID; defines the data element contained in an extract record.
  • BEN_EXT_RCD_IN_FILE — referenced through EXT_RCD_IN_FILE_ID; defines the extract record and its position within the output file.
  • BEN_EXT_DATA_ELMT_IN_RCD_D and BEN_EXT_RCD_IN_FILE_D — corresponding translated/denormalized companion tables used by the extract definition pages.
  • BEN_EXT_DATA_ELMT_IN_RCD_CR and BEN_EXT_RCD_IN_FILE_CR — change-history or criteria tables that participate in the same extract definition model.
  • The Advanced Benefits extract concurrent programs, which read these criteria at run time to select changed records for file generation.

Because the table functions as a link between record definitions and data elements, referential integrity is maintained entirely through the two documented foreign keys; any deletion or redefinition of an extract record or data element must be preceded by removal of the associated inclusion-criteria rows.