Search Results p_effective_end_date

Overview

The APPS.BEN_PLAN_DESIGN_DELETE_API package body provides the central delete-routing layer for Oracle Advanced Benefits (OAB) plan design entities in Oracle E-Business Suite 12.1.1 and 12.2.2. Rather than issuing physical deletes against each configuration table directly, the package accepts a table alias and primary key identifier, then dispatches the request to the appropriate entity-specific API. This design preserves the datetrack semantics, object version checking, and validation behavior required by the Benefits data model.

The package encapsulates a common signature across many plan design objects. Its central procedure, call_delete_api, carries a p_effective_date parameter that determines the datetrack context of the requested deletion. Additional parameters govern validation-only mode, the target row, and the datetrack mode. Because the caller supplies both a table alias and a primary key, the package functions as a polymorphic delete service used throughout the Benefits configuration layer.

Key Procedures and Functions

• CALL_DELETE_APIS — The primary entry point exposed to callers. It accepts the table alias, primary key, effective date, datetrack mode, object version number, and entity name information, and routes the delete request to the correct underlying Benefits API. It supports a validate-only mode controlled by the process validate flag. Deletion outcomes are reported through output parameters, including the delete-failed indicator and effective start and end dates.
• CALL_DELETE_APIS_FOR_HIERARCHY — A companion entry point that processes delete requests across a hierarchy of related plan design entities. It enables a parent-level delete to propagate to dependent child records while honoring the same datetrack and validation conventions.

The internal call_delete_api procedure, visible in the package source, selects the target API based on the table alias. Documented aliases include EAT, which routes to ben_ACTION_TYPE_api.delete_ACTION_TYPE, and SVA, which routes to BEN_SERVICE_AREA_API.delete_SERVICE_AREA. Both branches pass the effective date through to preserve datetrack behavior.

Tables Accessed

According to documented metadata, the package references the following tables through APPS synonyms:

• BEN_COPY_ENTITY_RESULTS — Stores the outcome of entity copy and delete operations performed across plan design objects. The package consults or updates this table to record processing results for hierarchy-level operations.
• PQH_COPY_ENTITY_TXNS — Tracks entity transaction records associated with copy and delete processing. This table supports the coordination of multi-entity operations managed by the hierarchy procedure.

Usage Notes

The package is typically invoked from the Benefits plan design configuration forms and from concurrent programs that perform bulk configuration maintenance. Custom code should call CALL_DELETE_APIS rather than deleting rows directly from underlying plan design tables, because the wrapper enforces datetrack validation, object version number checking, and row-level security.

Callers must supply a valid p_effective_date consistent with the datetrack mode requested. Passing a date that falls on a datetracked row boundary may cause the underlying entity API to reject the operation. For hierarchy-wide removals, CALL_DELETE_APIS_FOR_HIERARCHY should be used so that dependent entities are removed in the correct sequence. The package is referenced by three other packages within the Benefits schema, confirming its role as a shared low-level delete service. As with all documented APIs, it should be called within a properly managed transaction, and the delete-failed output parameter should be checked before committing.