Search Results update_mapping_target_data

Overview

APPS.BEN_PLAN_DESIGN_TXNS_API is a public API package within the Oracle E-Business Suite Advanced Benefits (Oracle HRMS) module. Its principal business function is to manage the transactional processing associated with plan design copy operations. In Oracle Benefits, administrators frequently define a plan design configuration in one business group or effective period and then copy that design to another target. The copy operation is not a simple row duplication; it involves the coordinated migration of plan records, plan types, options, eligibility configurations, and their dependent mappings across multiple base tables. BEN_PLAN_DESIGN_TXNS_API encapsulates this multi-step, transactionally sensitive process, exposing a controlled procedural interface (rather than direct DML) so that callers inherit validation, logging, and result tracking.

The package is classified as an API, and its source header (becetapi.pkb 120.7) confirms a shipping, supported component maintained by Oracle. Internally it declares package-level variables such as g_package and g_debug (bound to hr_utility.debug_enabled), indicating built-in debug diagnostics used for troubleshooting copy requests. The package maintains state through cooperating global structures, notably ben_pd_copy_to_ben_one.g_pk_tbl, which carries copy reuse metadata used to reconcile source and target rows during post-processing.

Key Procedures and Functions

The package exposes 21 documented procedures and functions. The core transaction lifecycle is handled by CREATE_PLAN_DESIGN_TXN, UPDATE_PLAN_DESIGN_TXN, and DELETE_PLAN_DESIGN_TXN, which create, maintain, and remove the plan design copy transaction record identified by a copy_entity_txn_id. Parallel result-level operations are provided by CREATE_PLAN_DESIGN_RESULT, UPDATE_PLAN_DESIGN_RESULT, and DELETE_PLAN_DESIGN_RESULT.

Mapping and configuration logic is handled by UPDATE_MAPPING_TARGET_DATA, AUTO_MAPPING, GET_MAPPING_INFO, GET_MAPPING_COLUMN_NAME, and GET_REQUIRED_MAPPING_COMPLETED, which determine how source entities map to destination entities and whether mandatory mappings are satisfied before a copy proceeds. Submission and orchestration are handled by SUBMIT_COPY_REQUEST and PDW_SUBMIT_COPY_REQUEST, with WRITE_TXN_TABLE_ROUTE recording the table routing path for the transaction and GET_USER_BUSINESS_GROUP_IDS resolving the security scope. Row-selection state is captured by UPDATE_HGRID_CHILD_SELECTION and UPDATE_DOWNLOAD_STATUS. Logging and diagnostics are served by CREATE_LOG and GET_LOG_DISPLAY, while PURGE_PLAN_DESIGN_PROCESS removes obsolete process data. The private helper update_cer_with_target seeds target information into BEN_COPY_ENTITY_RESULTS, illustrating the package's internal reconciliation of old and new values.

Tables Accessed

The package reads and writes BEN_COPY_ENTITY_RESULTS, which stores per-row copy outcomes and target detail (information columns are populated with copy reuse type and new value). Core benefits definition tables include BEN_PL_F (plans), BEN_PL_TYP_F (plan types), and BEN_OPT_F (options), representing the design objects being copied. Payroll and balance structures — PAY_ELEMENT_TYPES_F, PAY_ELEMENT_TYPES_F_TL, PAY_BALANCE_TYPES, PAY_BALANCE_DIMENSIONS, PAY_DEFINED_BALANCES, and PAY_ALL_PAYROLLS_F — are referenced where copied designs reference payroll elements and balances. HR_ALL_ORGANIZATION_UNITS and HR_ALL_ORGANIZATION_UNITS_TL supply organization context, HR_ASSIGNMENT_SETS support eligibility scope, FND_USER provides actor identity, and FND_NEW_MESSAGES supports message/token retrieval for user feedback.

Usage Notes

This package is invoked whenever a plan design copy is initiated from the Oracle Benefits administrative interface, and it may also be called programmatically by concurrent programs and custom extensions needing to drive or validate a copy transaction. The presence of SUBMIT_COPY_REQUEST and PDW_SUBMIT_COPY_REQUEST indicates it is designed to be called from a form or controller that submits a copy job, with the API handling transaction creation, mapping verification, submission, logging, and cleanup. In 12.1.1 and 12.2.2 the interface is consistent; Oracle recommends calling the documented API procedures rather than performing direct DML on the underlying benefits tables. Debug output is controlled by the standard HR_UTILITY debug flag, and users specifically seeking a "create_process_log" mechanism will find the equivalent logging entry point in CREATE_LOG and the diagnostic display routine GET_LOG_DISPLAY.