on 10-23-2008 4:46 PM
Hi
We are in the process of implementing the MDM R/3 integration via PI. PI is splitting the incoming DEBMDM xml structure into ADRMAS and DEBMAS and posting it to R/3 as IDocs. What is the best way to achieve error handling in R/3 if one of them fails? For instance if ADRMAS succeeds and DEBMAS fails then the data for that record is not just outdated but it is also wrong to be partially updated.
Pls let us know how you have handled in your implementations
Thanks
Arvind
Hi Arvind,
You can use Transaction WE05 to check the failed idocs and you can also edit the data if error is due to data error.
To reprocess the failed idocs use transaction BD87.
Regards
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Arvind
Re-check your requirements - also any operational requirements.
If the inconsistent partial update leads to problems in the business processes or you cannot introduce the manual check procedure, you might consider designing some custom IDoc handling in ECC to ensure consistent updates.
Regards,
Thomas
Hi Arvind,
We had faced a similar issue wherein the ADRMAS was getting posted while the DEBMAS was failing.
Yes it is a fact that, this will result in partial updations which is not what we expect.
But there is no automated way to ensure the correctness of the same and this has to be handled manually.
You need to execute transaction we02 and see for the error code and the status of the IDOC.
Also refering to the data segment may help you to find out where could be the exact problem.
Hope it helps.
Thanks,
Minaz
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
85 | |
10 | |
10 | |
10 | |
7 | |
6 | |
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.