Question:
Hello,
Environment : 3.0B
I am trying to skip a duplicate record from being updated in Master data using transfer rules , setting the value of RETURNCODE = 4 .
The Load monitor shows a status of RED and stops the whole load. Is there any other way to skip the record in the Transfer rules and avoid getting a status of RED as it stops the whole the whole load .
This is as good as setting ABORT = 4.
In 3.0B , you can use option of storing in PSA and selecting the option of "Ignore Duplicate Records " . I am trying to avoid storing the records in PSA .
Answer:
I think that you need to use the "error handling" button in the scheduler.
Ch
_________________
_
There are only 10 types of people in the world :
those who understand binary and those who don't.
Answer:
you can use the start Routine to remove the duplicates first.
-Ravi.
Answer:
The system is figured in such a way that as far as master data is concerned it terminates the update if it finds a duplicate record in the transfer structure itself.
I suspect that the load is from a flat file. In that case a sort/filter could bring out the duplicates. There is no way you could have duplicates if the master data is transferred from R/3 into BW by means of the updates.
_________________
Keep smiling
Answer:
Thank you for the quick responses
- Loads are from R/3 and the records are unique in R/3 , but in BW I am trying to extract portion of the data. Hence the logic is need to skip records.
I used the Start routine and worked . For some reason I had tried that before and did not seem to work but anyways ...
question : Returncode = 4 is supposed to ignore the records and move onto the next one ,. Why does the load turn itself to RED and flag as error ?
Thanks to you all .
Answer:
My experience is that you can only use RETURNCODE=4 in update rules, not in transfer rules .
Answer:
In version 3, if you set the return code to 4 in a transfer rule, it will create an infopackage that will contain only the records that were skipped via the routine, and let you have more possibilities under the button "error handling" in the scheduler.
via this button "error handling", you can force the system to dump anyway if there are "too much" records skipped, and this is the default option
as by default, "too much" is more than 1...
'hope this helps clarifying
Ch
_________________
_
There are only 10 types of people in the world :
those who understand binary and those who don't.
Answer:
Also just to calrify,, u can use any of those options (automatic erro handling) if you are not loading via PSA..
Answer:
CAN SOMEBODY PLEASE TELL ME HOW R/3 ALLOWS DUPLICATE MASTER DATA TO BE PASSED THROUGH THE EXTRACT STRUCTURE, OR FOR THAT MATTER, SAVED?
_________________
Keep smiling
Answer:
it could be a manual delta you are trying to load
mostly it is a wrong key in BW than the key in R3.. for example a sales view being loaded without the correct compunding.. or something like that..
Answer:
Why not just use an Option in InfoPackage under Processing Tab Strip:
Ignore Double Data Records
N.G