Results for “ben_bdi_upd”

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

Overview

BEN_BDI_UPD is an Oracle Applications (APPS) PL/SQL package belonging to the Oracle Advanced Benefits (BEN) module. Its object name reflects its role as an update driver for Benefits Dependent/Beneficiary Data Information (BDI) records. In the Oracle E-Business Suite R12.1.1 and R12.2.2 data model, the "BDI" entity corresponds to the batch dependent information structures used during benefits processing, particularly as they relate to the Dependent and Beneficiary designation batch processes. BEN_BDI_UPD provides the programmatic layer used to apply updates against these staging records.

The package is classified in the ETRM as an "OTHER" API type, indicating that it is not part of the formal public interfaces (such as the HR_API or BEN public APIs) but rather an internal utility package. Its status is VALID in the APPS schema, meaning it compiled successfully and is available for internal invocation by other Benefits objects.

Key Procedures and Functions

The documented ETRM metadata lists one primary procedure within BEN_BDI_UPD:

• UPD — The sole documented program unit. As the name implies, this procedure performs update processing against the BDI data set. It is designed to modify existing dependent/beneficiary batch information records rather than insert or delete them. Because the ETRM metadata does not publish the formal parameter list, the exact signature (typically including identifiers for the batch, person, or dependent records plus context parameters) should be confirmed through the package specification in the database or via the "show dependent code" link referenced in the ETRM dependency listing.

The ETRM documentation records two total program units (procedure and/or function) for the package, with UPD being the documented entry point. The package body encapsulates the procedural logic, while the specification exposes the callable interface.

Tables Accessed

The ETRM documents exactly one table referenced by BEN_BDI_UPD through APPS synonyms:

• BEN_BATCH_DPNT_INFO — This table stores batch dependent information. BEN_BDI_UPD modifies rows in this table as part of its UPD processing. In the Benefits batch architecture, this table acts as a staging/working store for dependent data associated with a benefits batch run, and the update package applies changes to those staged records prior to final downstream processing (for example, validation or transfer into the live dependent tables).

No other base tables are documented as being directly referenced, although the package may rely on the BEN_BDI_SHD shadow (history) mechanism for audit purposes, as indicated by its dependency on BEN_BDI_SHD.

Usage Notes

BEN_BDI_UPD is classified as an internal package rather than a supported public API. Its documented dependencies confirm that it operates within the Benefits batch-processing framework:

• Depends on: BEN_BDI_SHD (the shadow/audit record package for BDI data) and HR_API (the Human Resources public API layer). The dependency on HR_API suggests that updates performed here may cascade into or synchronize with HR person/dependent data.
• Referenced by: BEN_BATCH_DPNT_INFO_API, the higher-level API for batch dependent information, and by itself (indicating possible recursive or multi-pass internal calls).

Because it is referenced by BEN_BATCH_DPNT_INFO_API, the package is most commonly invoked indirectly during Benefits batch processing—typically through concurrent programs that run dependent/beneficiary batch jobs, or through the batch dependent information API when Oracle's delivered batch flows execute. It is not intended for direct invocation from Oracle Forms or user-facing concurrent programs.

Customization guidance: given its internal status and the narrow documented surface (a single UPD procedure over a single staging table), developers should avoid calling BEN_BDI_UPD directly from custom code. Instead, invoke the supported BEN_BATCH_DPNT_INFO_API, which layers on validation and audit handling. Any direct usage risks violating the batch integrity model, since updates bypass the higher-level API's safeguards. Always confirm the effective signature via the package specification in the target environment, as R12.1.1 and R12.2.2 may carry minor patch-level differences.