Results for “ben_pd_copy_to_ben_five”
50+ results
AI-generated from documented ETRM metadata — verify critical details on the linked pages.
Overview
APPS.BEN_PD_COPY_TO_BEN_FIVE is a PL/SQL package body within the Oracle E-Business Suite Advanced Benefits (BEN) module. It forms part of a numbered family of copy utilities — the naming convention BEN_PD_COPY_TO_BEN_ONE through BEN_PD_COPY_TO_BEN_FIVE indicates a partitioned or staged design in which a large set of benefits plan design records is split across several packages to keep individual program units within compilable and manageable size limits. The "PD" prefix denotes Plan Design, and the object's responsibility is to orchestrate and execute the copying of benefits plan design configuration data from source entities to target entities during plan duplication, plan-year rollover, or template-based plan creation.
The package is classified as OTHER in the ETRM repository, meaning it is not an end-user callable API in the same sense as a public BEN business API; it is internal infrastructure invoked by higher-level benefits copy processes rather than directly by customers.
Key Procedures and Functions
The documented metadata identifies one callable program unit:
- CREATE_RATE_ROWS — the principal documented procedure. Its purpose is to generate rate rows in the benefits rate tables when plan design data is copied. In the benefits model, rates are date-effective, flexfield-qualified, and frequently attached to variable rate profiles, activity base rates, benefit pool rollover requirements, and premium definitions. This procedure materialises those rate definitions against the newly created target plan design.
The package body excerpt also exposes internal helper logic that supports this work. A private get_fk function resolves a source primary key value into its corresponding target primary key by scanning a cached collection (ben_pd_copy_to_ben_one.g_pk_tbl) of old-to-new identifier mappings, allowing foreign key relationships to be re-pointed after a copy. A private get_dt_modes procedure derives the appropriate date-track mode (for example, insert versus update handling) based on the effective start date, effective end date, and DML operation being performed.
Collectively these units implement the standard benefits copy pattern: read source rows, translate surrogate keys via the shared key-mapping table, and re-insert with corrected date-track and rate semantics.
Tables Accessed
The package references a broad set of BEN plan design and rate tables through APPS synonyms, including:
- Rate and activity tables: BEN_ACTY_BASE_RT_F, BEN_ACTY_BASE_RT_CTFN_F, BEN_ACTY_RT_PTD_LMT_F, BEN_ACTY_RT_PYMT_SCHED_F, BEN_ACTY_VRBL_RT_F
- Actual premium tables: BEN_ACTL_PREM_F, BEN_ACTL_PREM_VRBL_RT_F, BEN_ACTL_PREM_VRBL_RT_RL_F
- Variable rate tables: BEN_BNFT_VRBL_RT_F, BEN_BNFT_VRBL_RT_RL_F
- Pool and coverage configuration: BEN_APLCN_TO_BNFT_POOL_F, BEN_BNFT_POOL_RLOVR_RQMT_F
- Delivery and trigger setup: BEN_CM_DLVRY_MED_TYP, BEN_CM_DLVRY_MTHD_TYP, BEN_CM_TYP_TRGR_F
These are read to source the original configuration and written to when the copy creates the corresponding target rows, with _F suffixed tables representing the date-effective (datetrack) base tables.
Usage Notes
BEN_PD_COPY_TO_BEN_FIVE is referenced by four other packages, confirming its role as a subordinate unit in a larger copy framework rather than an entry point. It is normally invoked indirectly when a user runs plan copy, plan design duplication, or plan-year rollover from the Benefits Plan Design forms (such as the Plan Configuration and Plan Design Copy windows), or through the associated Benefits concurrent programs that process large-scale plan replication.
Developers writing custom benefits migration or configuration-cloning scripts should not call this package directly. Instead, they should invoke the supported parent copy routine, which guarantees that all five partitioned packages execute in the correct sequence and that the shared key-mapping collection in BEN_PD_COPY_TO_BEN_ONE is populated before foreign key translation occurs. Any direct invocation risks unresolved surrogate keys and inconsistent datetracked rate rows.