on 05-18-2015 1:36 PM
Hi,
I have an issue while loading the data from source to BW (0employee) through infopackage . Soon after a new change of adding attributes and making time dependent and loading the data i am having an issue.
I hope there was no problem with newly added fields as this are time dependent as i checked with functional team as they change according to from and to date values.
1) In my current settings with info package there was no duplication check enabled but i tried with another infopackage with no duplicates records and loaded the data, the load was successful but for the added time dependent attributes doesn't filled with data but it exist in PSA. Hope there should not be here Duplication enable button in infopackage for 0Employee
2) There was no problem with the code or data in RSA3 and PSA as well . while loading the data from PSA to 0employee i am facing the issue.
Can any advice on this issue.
Regards,
Rahul.
Hi ,
Found the issue, it is due to field of Type in a record.
For an employee based on type it will create a 2 records for an employee with same From and two date values.
when we append the record in cmod to get the 2 similar date intervalsrecords, i got the issue.
Looking to filter records only based on one type to resolve the issue (Excluding the other type)
Will post you if the issue resolves..!!!!
Thanks all you guys with some fast replies...:)
Regards,
Rahul.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi,
Above error you won't get at RSA3/PSA.
while loading into target only we will get that issue.
Issue clearly saying as overlapping. Mean from/to dates will be wrong.
for example:
Employee E102434.
Emp ID From date Todate
E102434 20060401 20080331
E102434 20080401 20121231
E102434 20130101 till date.
above data was correct. if you have below data.
Emp ID Fromdate Todate
E102434 20060401 20080331
E102434 20080201 20121231 - its overlapping, see previous to date and present from date.
Such overlapping issue exist for your data.
So check at source side employe table , see the from date and to date values for employee.
Later ask HR team and ask them to maintain proper date ranges and later you can reload into bw.
Thanks
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Raman,
Thanks for a quick reply,
We have this issue in development soon after the new change its working fine earlier in all systems with no data issue.
Soon after a change for the newly added attributes through code having an issue. Hope there wont be wont be any data issue with std table . may be code that has been written to populate newly added fields may facing the issue.
As i described with the in the earlier post there is no issue while loading the data by using check box of no duplication in infopackage to 0employee but for newly time dependent attrb not populating the data.
The example you mentioned about the previous and current data is same so facing a time overlapping issue. sorry i am missing something here..
Emp ID Fromdate Todate
E102434 20060401 20080331
E102434 20080201 20121231 - its overlapping, see previous to date and present from date.
As i checked with functional team as well there was no issue with that. As this is not for one or two records the issue is for all the records
Can you please help what can we do to resolve the issue.
Hi,
Can you share more error information from logs.
Mean need to know employe id and from/to dates values.
I need the same data from PSA of employee which showed in error,
So that we can anylyse the data and find the cause.
one more thing - Why/where you added code and what is the purpose it?
Thanks
Typical EMPLOYEE extractor will not do the damage described here.
May be you have code in ECC to add extra record into the data package, you need to code the cmod/abap CORRECTLY to avoid the overlap.
Here you need to examine the existing record from standard employee_attr and in your code you might have to split the record dividing across different time periods based on the new fields appended.
Just run RSA3 for one employee and check this scenario.
Gopi
Message was edited by: Eriki Gopi
That's clear. first two records are wrong.
its have same from/to dates of first two records? Why?
How will have one record with same two (from/to)dates?
Note the employee id and check at HR Table.
See there, whether it have two records with same date ranges (01.04.2011 to 20.09.2011) or not.
As said first reply, source may have wrong data. so check it there and rectify the data with help of HR team.
User | Count |
---|---|
93 | |
11 | |
10 | |
9 | |
9 | |
7 | |
6 | |
5 | |
4 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.