Results for “fetch_drvd_factor_result”
8 results
AI-generated from documented ETRM metadata — verify critical details on the linked pages.
Overview
APPS.BEN_PDW_COPY_BEN_TO_STG is a PL/SQL package body that supports the Benefits copy-entity framework used by Oracle EBS Advanced Benefits during the "PDW" (Person/Data Warehouse staging) copy process. Its central responsibility is to read source Benefits configuration and enrollment rows and mirror them into the staging/result structures that drive the generic copy-engine mechanism. The package collaborates with the underlying copy transaction infrastructure — notably PQH_COPY_ENTITY_TXNS and BEN_COPY_ENTITY_RESULTS — to record each DML operation performed during a copy run, so that downstream processing can identify which entity instances were reused, created, or displayed.
In Oracle EBS 12.1.1 and 12.2.2, the package is catalogued with API classification OTHER, indicating it is an internal, non-public interface rather than a supported API. The header identifies a build at the 12.2.0 code line (bepdwstg.pkb 120.20.12020000.2), confirming its relevance across both documented releases.
Key Procedures and Functions
The package exposes 37 documented procedures and functions. Their purposes are summarized below.
- PRE_PROCESSOR — Entry-point logic that prepares a copy transaction before entity rows are processed.
- GET_TXN_DETAILS — Retrieves source effective date and business group context for a given copy entity transaction; it drives the effective-dating used throughout the copy.
- COPY_PLN_RECORD_PCP, COPY_PL_TYP_RECORD, COPY_BNFT_BAL, COPY_DRVD_FACTOR — Copy individual Benefits entities (plan, plan type, benefit balance, derived factor) into staging, recording each as a copy-entity result.
- CREATE_ELIG_PRFL_RESULTS, CREATE_ELIG_CRTR_RESULTS, CREATE_DEP_ELIG_CRTR_RESULTS, CREATE_DEP_ELPRO_RESULTS, CREATE_VAPRO_RESULTS, CREATE_YRP_RESULT — Build result rows for eligibility profiles, eligibility criteria, dependent eligibility criteria and program results, variable/activity rate results, and yearly period results.
- DUMP_ELIG_PRFLS — Emits diagnostic output for eligibility profiles during copy processing.
- GET_PRFL_NAME, GET_DPNT_PRFL_NAME — Resolve profile and dependent profile names.
- GET_BALANCE_NAME, GET_CURRENCY, GET_STAGE_OBJECT_NAME — Return descriptive attributes (balance name, currency, staging object name) for the entity being copied.
- INTERIM_COVERAGE_LOOKUP — Looks up interim coverage data used in benefits calculations.
- FETCH_DRVD_FACTOR_RESULT — Retrieves derived-factor result rows following copy.
- MAX_SEQUENCE — Derives the next sequence value for generated staging keys.
- Additional helper and utility routines complete the reported set of 37 documented procedures/functions.
Tables Accessed
The package reads and writes the following tables via APPS synonyms:
- BEN_PL_TYP_F, BEN_PL_F, BEN_PGM_F, BEN_OIPL_F, BEN_PTIP_F, BEN_PL_TYP_OPT_TYP_F — plan, program, option-in-plan, plan type, and plan type/option type configuration rows copied into staging.
- BEN_ELIGY_PRFL_F — eligibility profile definitions.
- BEN_PER_INFO_CHG_CS_LER_F and BEN_PER_INFO_CHG_CS_LER_F_S — person information change life-event-reason rows and their shadow table.
- BEN_BNFTS_BAL_F — benefit balance definitions.
- BEN_BENFTS_GRP — benefits groups.
- BEN_POPL_YR_PERD and BEN_POPL_YR_PERD_S — plan year period definitions and shadow rows.
- BEN_PSTL_ZIP_RNG_F — postal ZIP range data used in eligibility determination.
- BEN_COPY_ENTITY_RESULTS — the copy-engine result table where the package records the outcome of each copied or reused entity instance.
Usage Notes
BEN_PDW_COPY_BEN_TO_STG is invoked internally by the Benefits copy framework, not directly by end users. It is referenced by three other packages, which call its copy routines as part of a larger entity-copy transaction. Typical invocation paths include the Benefits configuration copy concurrent programs and related forms that initiate copying of a plan, program, or eligibility setup across business groups or effective dates.
Because the package is classified as OTHER and carries an internal header, it must not be called from custom code as if it were a supported API; its signature and behavior are subject to change between patch levels. Where custom development requires similar functionality, supported Benefits APIs or the standard copy forms should be used. The presence of the string "cconn" in user searches likely reflects an internal connection or session identifier associated with this package rather than a documented object name.