Search Results call_delete_apis

Overview

The APPS.BEN_PLAN_DESIGN_DELETE_API package is a PL/SQL API within the Oracle E-Business Suite Advanced Benefits (BEN) module. Its primary responsibility is to manage the removal of plan design configurations and their associated hierarchical data. In the context of Oracle EBS 12.1.1 and 12.2.2, benefits plan design is a complex structure that defines eligibility, coverage, rates, and enrollment rules. When a plan design or a hierarchy of plan designs is removed, referential integrity across multiple dependent tables must be maintained. This API abstracts that complexity by orchestrating the deletion of dependent records and invoking the appropriate delete APIs for each related entity.

Key Procedures and Functions

The package exposes two documented procedures. CALL_DELETE_APIS is the general-purpose entry point for deleting a plan design and its downstream dependencies. It coordinates the invocation of delete routines for the plan design entity itself and any dependent entities that reference it. CALL_DELETE_APIS_FOR_HIERARCHY performs the equivalent operation for a plan design hierarchy, traversing the hierarchy and invoking delete APIs for each member so that parent-child relationships are unwound in the correct order. Both procedures are intended to be invoked by higher-level BEN processes rather than directly by end users, ensuring that deletion occurs within a controlled transaction and that all related benefits constructs are cleaned up consistently.

Tables Accessed

Based on the documented metadata, the package references two tables through APPS synonyms. BEN_COPY_ENTITY_RESULTS stores the results of copy operations performed on benefits entities. During deletion, this table is consulted and updated so that copy-result records tied to the plan design being removed are reconciled or eliminated. PQH_COPY_ENTITY_TXNS, part of the Public Sector/HR (PQH) copy framework, tracks copy transactions and their statuses. The delete API interacts with this table to ensure that any outstanding or completed copy transactions associated with the plan design are properly handled before the design is removed. Maintaining these two tables is essential to prevent orphaned copy records that could otherwise corrupt subsequent copy or design operations.

Usage Notes

BEN_PLAN_DESIGN_DELETE_API is referenced by several other BEN components, including BEN_PLAN_DESIGN_COPY_PROCESS, BEN_PLAN_DESIGN_WIZARD_API, and PQH_GSP_STAGE_TO_BEN. This dependency pattern indicates that the package is invoked indirectly from the Plan Design Wizard, from the copy process when a copied design must be rolled back or recreated, and from Public Sector staging routines. Developers customizing benefits deletions should call the higher-level processes or, if necessary, invoke these procedures within a properly managed transaction that respects the calling context. The package should not be executed ad hoc against production data, as deletion of plan design records affects enrollment, eligibility, and rate configurations across the benefits subsystem.