Search Results chk_startup_action

Overview

APPS.BEN_XID_BUS is the business-layer PL/SQL package body that supports the Benefits "Extractable Inclusion Data Element" (XID) entity within Oracle E-Business Suite 12.1.1 and 12.2.2. The package encapsulates the validation and persistence logic required to maintain rows in the BEN_EXT_INCL_DATA_ELMT table, which defines which data elements are available for extraction from the Benefits extract framework. This entity determines the composition of extractable benefits data and is therefore central to any downstream reporting, carrier transmission, or data-warehouse load built on the Benefits extract engine.

The package follows the standard Oracle HRMS "B-US" (business) architecture. Business packages sit above the Table Handler (T-H) and Row Handler (R-H) layers and below the user-facing API. The package body carries the private global package name ben_xid_bus. and includes HRMS-specific instrumentation via hr_utility.set_location, which writes entry and exit trace messages to the PL/SQL debug buffer when HRMS trace is enabled. The header comment, $Header: bexidrhi.pkb 115.7 2002/12/16, indicates the file originates from the row-handler implementation naming convention and has been stable since Release 11i, carried forward unchanged into 12.1.1 and 12.2.2.

Key Procedures and Functions

• SET_SECURITY_GROUP_ID — Resolves the business group associated with a supplied ext_incl_data_elmt_id and publishes the corresponding security group identifier into the CLIENT_INFO context. It joins PER_BUSINESS_GROUPS to BEN_EXT_INCL_DATA_ELMT, enforces the mandatory argument through hr_api.mandatory_arg_error, and raises HR_7220_INVALID_PRIMARY_KEY via FND_MESSAGE when the primary key cannot be resolved. This ensures that all subsequent DML executes under the correct multi-tenant security context.
• RETURN_LEGISLATION_CODE — Returns the legislation code applicable to an inclusion data element record. It supports the HRMS legislative filtering model, by which benefits data elements are constrained to the appropriate country or legislative regime.
• INSERT_VALIDATE — Performs the business validation rules required before a new inclusion data element can be inserted. It is the pre-insert hook invoked by the entity's row handler.
• UPDATE_VALIDATE — Performs the equivalent validation checks prior to modifying an existing inclusion data element row, enforcing the same business constraints on the changed attribute set.
• DELETE_VALIDATE — Establishes whether an inclusion data element may be removed, checking for dependencies and referential integrity before allowing the delete to proceed.

Tables Accessed

The package operates directly on BEN_EXT_INCL_DATA_ELMT, referenced through its APPS synonym. This table stores the definition of extractable inclusion data elements, including their identifiers, business group ownership, and associated legislative and extract configuration attributes. The table handler layer (BEN_XID_SHD or equivalent shadow table) is orchestrated by the row handler, while BEN_XID_BUS applies business validation and supplies derived values such as the legislation code before the row handler commits.

Security resolution additionally reads PER_BUSINESS_GROUPS to translate a business group identifier into the security group identifier used by HRMS row-level security. No other application tables are documented as direct references.

Usage Notes

BEN_XID_BUS is not intended for direct invocation by end users or custom code. It is called by the generated row handler and table handler layers, and by the entity's user-facing API, whenever an inclusion data element is created, modified, or deleted. Typical triggers include Benefits Extract configuration forms in the Oracle Forms-based administrator responsibility, and any concurrent or batch process that programmatically maintains extract definitions through the supported Benefits APIs.

The package is referenced by three other packages within the Benefits extract stack, confirming its role as a shared dependency rather than a standalone entry point. Developers maintaining custom extract integrations should invoke the supported public Benefits extract APIs instead of calling BEN_XID_BUS directly, because the business package expects the row handler and security context to have been established first. When diagnosing failures, note that HR_7220_INVALID_PRIMARY_KEY surfaced from SET_SECURITY_GROUP_ID almost always indicates a stale or incorrect ext_incl_data_elmt_id rather than a security configuration defect. This behavior is unaltered between 12.1.1 and 12.2.2.