API = pay_element_entry_api.create_element_entry
Package Name = pay_element_entry_api
File Name = pyeleapi.pkh
Business Process = create_element_entry
API's versions:
$Header: pyeleapi.pkb 115.27 2007/11/16 13:14:24 ayegappa ship $
PAY_ELEMENT_ENTRY_API
$Header: pyeleapi.pkh 115.11 2005/10/24 04:59:30 susivasu noship $
PAY_ELEMENT_ENTRY_API
We now cannot create element entries for Adjustment only elements using the API pay_element_entry_api.create_element_entry with the p_entry_type input parameter = 'E'.
Error produced is:
" ORA-20001 : These element entries are not valid for an Adjustment Only element.
Cause: Either the entry type is incorrect, or the adjustment entry is not defined.
Solution: Supply an entry type that is in 'A','R' or 'B',and ensure that the target_entry_id (for A or R type) or original_entry_id (for B type) parameter is not null."
Steps to Reproduce:
Use pay_element_entry_api.create_element_entry to create an Adjustment Only element with p_entry_type='E'
---> The API is called from package code within the custom library form, the pl/sql block looks like:
begin
pay_element_entry_api.create_element_entry
(p_validate
=> false
,p_effective_date
=> ld_paaf_eff_start_date
,p_business_group_id
=> ln_business_group_id
,p_assignment_id
=> p_assignment_id
,p_element_link_id
=> ln_cost_element_link_id
,p_entry_type
=> 'E'
,p_input_value_id1
=> ln_cost_input_value_id
,p_entry_value1
=> ln_cost_balance_value
,p_effective_start_date => ld_ee_effective_start_date
,p_effective_end_date
=> ld_ee_effective_end_date
,p_element_entry_id
=> ln_ee_element_entry_id
,p_object_version_number => ln_ee_object_version_number
,p_create_warning
=> lb_ee_create_warning);
exception
when others then
omhr_log_msg('OMPAY_LEGAL_ENTITY_TRANSFER','Create adj element error for person_id '||ln_person_id||' and element name: '||c_let_default_elements.element_name,SQLERRM);
end;
---> Samples values:
Ld_paaf_eff_start_date
= 01-MAY-08
Ln_business_group_id
= 21
P_assignment_id
= 94355
ln_cost_element_link_id = 14434
ln_cost_input_value_id
= 9118
ln_cost_balance_value
= 14072.5
Friday, May 23, 2008
18-24 May-08 Oracle Payroll (FEB Payroll Run Validation)
Today we adjusted the income tax inconsistencies in the FEB-08 Payroll Run with the Legacy Payroll Income Tax details.
For eg:
Total Tax for 3 months(JAN-FEB-MAR) is 12000 then, Oracle Payroll spilts it in 3 equals Parts of 4K each.
if Feb tax is 4000 and Mar is 4000 in ERP system and
if Feb tax is 4050 and Mar is 3950 in Legacy Payroll system then
we need to balance the Adjustment element created for (edu_cess or IT etc) on the last date of the previous payroll period (here 31-Jan-2008) with the difference of the addition of the 2 Payroll Systems
adjust 50 Rs in cess adjustment element on 31-jan-2008
and run the quickpay for that employee for FEB-08
firstly delete the quickpay or payroll run and then do the above steps
in this way INcome tax mismatch can be adjusted
For eg:
Total Tax for 3 months(JAN-FEB-MAR) is 12000 then, Oracle Payroll spilts it in 3 equals Parts of 4K each.
if Feb tax is 4000 and Mar is 4000 in ERP system and
if Feb tax is 4050 and Mar is 3950 in Legacy Payroll system then
we need to balance the Adjustment element created for (edu_cess or IT etc) on the last date of the previous payroll period (here 31-Jan-2008) with the difference of the addition of the 2 Payroll Systems
adjust 50 Rs in cess adjustment element on 31-jan-2008
and run the quickpay for that employee for FEB-08
firstly delete the quickpay or payroll run and then do the above steps
in this way INcome tax mismatch can be adjusted
Subscribe to:
Posts (Atom)