Question:
The InfoPackage we had before BW3.0b upgrade was working fine, now the 3.0 is here and I can't load any data that has the same employee number even though the cost center or other keys are different. Why did this change and what should I do to get around this? Has anyone had this problem? Please let me know, thanks!
Answer:
does it say you have duplicates ?>?
if so.. go to the IP and in the processing tab.. select only PSA and update subsequently in DT.. then select ignore double records..
Answer:
Hi Schalasani,
Thanks! When I go into PSA, the 2nd dup emp no. has a red sq on the left instead the normal green circles. It should allow dup emp no with diffenent cost center or job etc. I checked the PSA of our BWProd that still 2.0b, there are many duplicate emp no with different cost center or jobs. This is the way we track the employee's history within the company, so I can't skip the dup records.
Answer:
The document 'SAP BW 3.0 - Functions in Detail' includes a section 'Handling Double Data Records'. If you search for this exact phrase at http://service.sap.com you will find the document.
Answer:
How about you just use the only PSa and update subsequently in data targets.. this might do what u want.. do not select ignore doubel data records..
Answer:
Thanks everyone. I tried to load into PSA only and it went fine. When I tried to manually process, it did not go. I then ran PSA only again then load InfoObj only and got eroor messages.
Looking at the 'Detail' in monitor I got green lites for Requests & Extraction; Error in datapkg 1 under Transfer: arrived in BW; error rcds written to application log.
Processing (data Packet): Errors Occured ;
Transfer rules (14673->14673 Records):No errors.
Update (0 new/0changed) : Errors occured ....
ZEMPNO: Data record 3 ('0000004E): Duplicate data record
Basically the data that were fine in 2.0b are flagged as duplicate records now and won't let me load into InfoObj, frustrating! No one else had the same problem???
''
Answer:
Had the same problem here... amongst others, while everything worked fine in 2.0B.
One of the things I tried was to reinforce the ALPHA conversion exit again (although SAP adviced me not to, it worked just fine afterwards). For some (the problem only occured for old data from our R/3 system) I created a routine in the transfer rules.
Another one was to delete the "old" master data that wasn't used anymore.
Also with COPA hierarchies I got the weirdest error messages... the trick was to just delete the master data and upload it again. Worked just fine.
cheers,
El Belgio
Answer:
there are some oss notes around this alpha conversion stuff, dates are in november december, so I guess we(cause I also had kind of the same) will face such things again for some time.
Ch
_________________
_
There are only 10 types of people in the world :
those who understand binary and those who don't.
Answer:
El Belgio,
Thanks for your input, it made me feel better that I am not the only one. I know how to delete the Master Data (MD) using se14, I wonder if you can give me a step-by-step instructions on how to reinforce the ALPHA conversion exit? Thanks so much!
Answer:
Go to your transfer rules (in the actual Transfer Rules tab)
On the left side of the screen you have the actual mapping of an InfoObject and a transfer rule
The far left column there (scroll with the scroll bar on the bottom) is called "Conversion". Check the box for the corresponding InfoObject that gives you all the problems.
cheers,
El Belgio
Answer:
El Belgio,
I deleted the MD of ZEMPNO, that is when I go to Maintain MD context I only see the Employee numbers, no data in any other column. I then went to Transfer rules tab, scroll to the far right and found Conversion. There are only 3 IO 0langu, Zempno and 0Txtmd, the conversion boxes are greyed out for ZEmpno and 0Txtmd so my only choice was 0Langu. I checked the 0langu even though I did not think it would help, reload, same duplicate Employee number error. Thanks so much for everyone's help. We may have to get a consultant in to see if the upgrade was properly installed etc....
Guest99
Answer:
Hi Guest99,
check the error in more detail... does it say in which record the actual error occurs? If not, make sure to load in to PSA first. Analyze the first error record (i.e. check the values). If that doesn't help, post the details here.
cheers,
El Belgio
Answer:
Thanks everyone! I resolved my problem by adding the 'time-dep' in the InfoObject Zempno. Time-dep is very important in HR data handling, I think 3.0B is more strict than 2.0b. Hope this help next person who has the same problem. Thanks again!!!!!