Search Results ben_pgm_extra_info




Overview

BEN.BEN_PGM_EXTRA_INFO is a table within the Oracle Advanced Benefits (BEN) module of Oracle E-Business Suite, available in both 12.1.1 and 12.2.2. As its name implies, the table stores supplementary, descriptive information associated with benefit programs that does not fit within the core program definition. Benefit programs are the top-level containers used to group plan offerings, eligibility rules, and enrollment periods; BEN_PGM_EXTRA_INFO provides an extension point for capturing configuration metadata, flexfield-based attributes, and other non-standard program details referenced during program setup and processing.

The table is documented with 65 columns and a primary key constraint named BEN_PGM_EXTRA_INFO_PK. The ETRM Data Vault classification for this object is standalone, meaning it is not heavily integrated into a foreign-key mesh with other business entities in the mined relationship model. From a modeling perspective, this suggests it behaves as a satellite-like or descriptive extension table, holding attributes that qualify a parent program rather than serving as a transactional hub or link between multiple entities. The object status is VALID, indicating it is an active, supported schema component.

Key Information Stored

The table is anchored by its surrogate primary key, PGM_EXTRA_INFO_ID, which uniquely identifies each extra-information record. The documented unique index BEN_PGM_EXTRA_INFO_PK is built on this column, making it the single business-key candidate surfaced by the metadata. Notable columns include:

Common Use Cases and Queries

Because the table is a descriptive extension of benefit programs, it is most commonly queried in program-setup and configuration reporting. A typical retrieval joins the extra information back to the parent program by PGM_ID. For example, to list all extra-information records for a specific program:

  • SELECT PGM_EXTRA_INFO_ID, PGM_ID, INFORMATION_TYPE, PGI_ATTRIBUTE1, PGI_INFORMATION1 FROM BEN.BEN_PGM_EXTRA_INFO WHERE PGM_ID = :p_program_id;
  • Audit reporting: filter on LAST_UPDATE_DATE or CREATED_BY to trace who configured program metadata and when.
  • Flexfield extraction: select the PGI_ATTRIBUTE* or PGI_INFORMATION* columns for downstream data warehouse loads, since these hold client-specific configuration not exposed elsewhere.
  • Concurrent request reconciliation: join on REQUEST_ID to identify records generated by a specific concurrent program execution.

Reports typically treat this as a lookup-style table, filtered by program and information type rather than scanned in bulk.

Related Objects

The metadata documents the object as standalone, with no foreign-key relationships surfaced in the mined structure. The most significant logical relationships are derived from its column set:

Because the object is standalone, joins should be validated against the actual constraint definitions in a given 12.1.1 or 12.2.2 instance before being relied upon in high-volume reporting.