Search Results create_copy_entity_results




Overview
Explore in AI Chat

Overview

The APPS.BEN_COPY_ENTITY_RESULTS_API package body is a server-side PL/SQL API within the Oracle E-Business Suite Advanced Benefits (Oracle Benefits) module. Its business purpose is to manage the persistence of copy entity result records — the outcome data generated when a Benefits administrator copies configuration entities (such as plans, programs, eligibility rules, or related setup objects) from one context to another. The package encapsulates the insert, update, and delete operations against the underlying BEN_COPY_ENTITY_RESULTS table, exposing a controlled API layer rather than permitting direct DML from calling code. The object resides in the APPS schema and carries a status of VALID in both the 12.1.1 and 12.2.2 releases. It is classified as an API in the ETRM repository, and although the package body itself is not referenced by any other database object, the corresponding specification and the CPE (copy entity) supporting packages rely on this API to record and maintain copy results.

Key Procedures and Functions

The documented interface exposes three procedures, each modelling a standard DML operation on the copy entity results data:

  • CREATE_COPY_ENTITY_RESULTS — Inserts a new copy entity results row. This procedure is invoked when a copy operation produces a result entry that must be persisted, capturing the outcome of copying a given entity between source and target contexts.
  • UPDATE_COPY_ENTITY_RESULTS — Modifies an existing copy entity results record. It supports changes to previously stored result data, for example when the status or attributes of a completed or in-progress copy need to be revised.
  • DELETE_COPY_ENTITY_RESULTS — Removes a copy entity results record, allowing the cleanup or reversal of entries no longer required.

These procedures are wrappers around the BEN_CPE_INS, BEN_CPE_UPD, and BEN_CPE_DEL packaged routines respectively, which handle the actual row-level processing and validation logic. Parameter lists are not reproduced here; the ETRM metadata documents purpose only, and callers should reference the package specification for exact signatures.

Tables Accessed

The package operates against the following documented tables, reached through APPS synonyms:

  • BEN_COPY_ENTITY_RESULTS — The primary transactional table holding the results of copy entity operations. All three procedures read from or write to this table.
  • PQH_TABLE_ROUTE — Referenced in the dependency chain, this table participates in the routing or workflow mechanics associated with entity processing, supporting the copy operation context.

Dependencies also include BEN_CPE_SHD, HR_API, and HR_UTILITY, which provide shared row-handling, error, and utility services. The package body is referenced by 15 other packages, confirming its role as a shared results-management layer within Oracle Benefits.

Usage Notes

BEN_COPY_ENTITY_RESULTS_API is not intended for direct end-user invocation; it is a programmatic API called from within Benefits configuration flows. Typical invocation contexts include the Benefits copy entity user interface (Oracle Forms), concurrent programs that perform bulk entity copying, and custom or extension code that needs to persist copy results consistently with the standard product. Because the package delegates to the BEN_CPE_* routines, callers automatically inherit validation and the standard HR_API error-handling behaviour, including the return of a standard API error table. Developers extending copy functionality should call these procedures rather than issuing direct DML against BEN_COPY_ENTITY_RESULTS, ensuring row-level audit, validation, and downstream integration remain intact across both 12.1.1 and 12.2.2 environments.