Results for “ben_bri_bus”

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

Overview

BEN_BRI_BUS is the business-layer PL/SQL package body in the Oracle E-Business Suite Advanced Benefits (Oracle Benefits) module. Its name derives from the BEN module prefix combined with "BRI," which refers to Batch Rate Information, the Benefits subsystem that stores and processes rate and cost information for benefit offerings, plans, and programs. The package encapsulates the server-side business rules that govern the manipulation of batch rate information records, providing a controlled, validated interface between the Benefits forms and concurrent processes and the underlying BEN_BATCH_RATE_INFO table.

As a "BUS" (business) package, BEN_BRI_BUS sits above the corresponding shadow (SHD) package, BEN_BRI_SHD, which performs the physical row-level inserts, updates, and deletes. This layering is a standard Oracle Application Object Library pattern in which the shadow package handles data manipulation and the business package enforces validation, derives context values such as legislation code and business group, and maintains audit information in BEN_BENEFIT_ACTIONS. In Oracle EBS 12.1.1 and 12.2.2 the package is deployed in the APPS schema with VALID status, and the ETRM repository records it as an "OTHER" API classification, indicating it is an internal business-layer component rather than a formally published public API.

Key Procedures and Functions

The ETRM documentation records four procedures or functions within this package body:

• RETURN_LEGISLATION_CODE — A function that returns the legislation code applicable to the current batch rate information transaction. It resolves the legislative context, typically from the business group or a related plan/program record, so that downstream validations and date-effectivity logic apply the correct country-specific rules.
• INSERT_VALIDATE — Performs validation logic in advance of inserting a new batch rate information row. It verifies that required attribute combinations are consistent with the parent plan, program, or offering before the shadow package commits the row.
• UPDATE_VALIDATE — Applies equivalent validation for modifications to existing batch rate information records, ensuring that changes do not violate Benefits configuration or legislation rules.
• DELETE_VALIDATE — Validates that a batch rate information record may be removed, preventing deletion where dependent or referenced data would be left inconsistent.

The ETRM metadata does not publish formal parameter lists for these units, and none are restated here. Their naming follows the standard insert/update/delete validation convention used throughout the BEN business packages.

Tables Accessed

The package references the following tables through APPS synonyms:

• BEN_BATCH_RATE_INFO — The primary subject table holding batch rate information rows; accessed for insert, update, and delete validation.
• BEN_BENEFIT_ACTIONS — Records action/audit history for benefit configuration changes, consistent with the business layer's responsibility for action tracking.
• BEN_OIPL_F — The offering/plan relationship table, used to confirm that rate information is associated with a valid offering-to-plan linkage.
• BEN_PGM_F and BEN_PL_F — Program and plan definition tables, consulted to resolve the legislative and configuration context used by RETURN_LEGISLATION_CODE and the validation routines.
• PER_ALL_PEOPLE_F — The person table, referenced for the user or contact context attached to the transaction.

Additional dependencies include BEN_BRI_SHD, BEN_BRI_BUS itself (recursive reference), and the standard utilities FND_MESSAGE, HR_API, and HR_UTILITY.

Usage Notes

BEN_BRI_BUS is not referenced by any other database object according to the ETRM metadata, confirming that it is invoked directly rather than being embedded in a dependency chain. It is referenced by three other packages, and in practice is called from Benefits setup forms and from concurrent programs that load or maintain batch rate information. Customizations should treat it as an internal business-layer component: rather than calling its validation routines directly, integrations should use the supported Benefits APIs or interface tables, invoking BEN_BRI_BUS only where the standard form or concurrent process flow already does so. Because the validation units carry no documented parameter interface, direct invocation from custom code is not advisable without source inspection.