[Home] [Help]
882: /* 8716870: Imputed Income Enhancement */
883: --if the Imputed income enrollment row is in future compared to the effective date use
884: --effective date associated with the enrollment row rather than one being passed to the api.
885: l_eff_date_for_enrt date:=null;
886: p_global_env_rec ben_env_object.g_global_env_rec_type;
887: /* 8716870: Imputed Income Enhancement */
888:
889: begin
890: --
1615: --Environment objects. We have just called a heavy duty api (ben_election_information/ben_prtt_enrt_result_api)
1616: --with an effective date different from what was supposed to be used. This may have stored this date in the
1617: --env objects. This date is not required for any other modules so we query to see if this value was written and
1618: --if so we will overwrite it with the original effective date.
1619: ben_env_object.get(p_rec => p_global_env_rec);
1620:
1621: hr_utility.set_location('l_eff_date_for_enrt:'||l_eff_date_for_enrt,1234);
1622: hr_utility.set_location('p_effective_date:'||p_effective_date,1234);
1623: hr_utility.set_location('p_global_env_rec.effective_date:'||p_global_env_rec.effective_date,1234);
1623: hr_utility.set_location('p_global_env_rec.effective_date:'||p_global_env_rec.effective_date,1234);
1624:
1625:
1626: if (p_global_env_rec.effective_date = l_eff_date_for_enrt) then
1627: ben_env_object.init
1628: (p_business_group_id => p_global_env_rec.business_group_id
1629: ,p_effective_date => p_effective_date
1630: ,p_thread_id => p_global_env_rec.thread_id
1631: ,p_chunk_size => p_global_env_rec.chunk_size
2201: --
2202: -- Fidelity calls this routine from CTRL M which runs it as a concurrent
2203: -- program. In this case they need the environment setup for them.
2204: --
2205: ben_env_object.init(p_business_group_id => p_business_group_id,
2206: p_effective_date => p_effective_date,
2207: p_thread_id => 1,
2208: p_chunk_size => 1,
2209: p_threads => 1,