Results for “ben_abr_info_types”

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

Overview

BEN_ABR_INFO_TYPES is a configuration table in the Oracle Advanced Benefits (BEN) module of Oracle E-Business Suite, documented in ETRM 12.2.2 and equally applicable to 12.1.1. Its description — "Activity base rate extra information types" — indicates that the table defines the set of extra information types available for capture against Activity Base Rate (ABR) records. Activity Base Rates are used within Advanced Benefits to derive rates from activities, and the extra information types defined here govern which supplemental, flexfield-backed attributes can be associated with those rate definitions.

The table functions as a reference or lookup entity rather than a transactional table. Rows are typically seeded or configured during implementation to control the selectable values presented to administrators when maintaining activity base rate information. The Data Vault classification mined from its foreign key structure is standalone. In Data Vault modeling terms, this suggests the object is best treated as an independent reference hub with no parent link dependencies, with its descriptive attributes modeled as satellite data. Retention and historization policies should therefore be applied at the hub level.

Key Information Stored

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

• INFORMATION_TYPE — the primary key and business-key candidate, uniquely identifying each extra information type. The unique index BEN_ABR_INFO_TYPES_PK is defined on this single column, making it both the surrogate and the natural key.
• DESCRIPTION — the user-facing name or explanation of the information type.
• ACTIVE_INACTIVE_FLAG — controls whether the type is available for selection in ABR configuration.
• MULTIPLE_OCCURENCES_FLAG — indicates whether more than one instance of the information type may be captured per activity base rate.
• LEGISLATION_CODE — legislative jurisdiction that qualifies the availability of the information type, supporting country-specific benefits rules.
• OBJECT_VERSION_NUMBER — optimistic locking column used by the Oracle Applications framework.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN, CREATION_DATE, CREATED_BY — standard WHO audit columns recording creation and modification metadata.
• REQUEST_ID, PROGRAM_APPLICATION_ID, PROGRAM_ID, PROGRAM_UPDATE_DATE — concurrent program and request context columns populated when the row is created or updated by a batch process.

Common Use Cases and Queries

Typical usage centers on configuration validation and reporting. A developer or analyst may query active information types for a given legislation:

• SELECT information_type, description FROM ben.ben_abr_info_types WHERE active_inactive_flag = 'Y' AND legislation_code = :p_leg;
• Determine whether an information type supports multiple occurrences: SELECT multiple_occurences_flag FROM ben.ben_abr_info_types WHERE information_type = :p_type;
• Audit recently modified configuration: SELECT information_type, last_update_date, last_updated_by FROM ben.ben_abr_info_types WHERE last_update_date > SYSDATE - 30;

These queries support implementation validation, migration verification, and troubleshooting when expected extra information types do not appear in the ABR setup UI.

Related Objects

The ETRM relationship data classifies this table as standalone, with no inbound or outbound foreign keys documented. Consequently, dependent objects are identified through the INFORMATION_TYPE value rather than through referential constraints. The most significant associated objects include:

• BEN_ABR_INFO_TYPES_PK — the unique index enforcing uniqueness on INFORMATION_TYPE.
• Activity base rate definition tables in the BEN schema that consume INFORMATION_TYPE as a lookup value during rate configuration.
• Flexfield/DFF definition tables (FND_FLEX_VALIDATION) that may back the extra information segments.
• Concurrent program and request tables (FND_CONCURRENT_REQUESTS) joined on REQUEST_ID for population lineage.

Because no enforced foreign keys exist, joins must be constructed on INFORMATION_TYPE with appropriate validation of active status and legislation code to avoid ambiguous results.