on 11-29-2012 1:49 PM
Hi,
We've just moved to SRM 7.0 from SRM 5.0 and moved from the BAPI for creating the self service purchase orders to an XI interface solution. Since the upgrade RZ20 is not providing any information about the failure but the text "Shopping cart XXX: Item Y: has Errors. Before, in SRM 5.0, the transaction was providing all the information needed to understand the root cause.
We're creating more than 1000 shopping carts per day, the average of failure is 7 - 10% (all due to master data issues) so we cannot go to the MONI transaction in XI and look for the failure of each message as it is not an escalable solution. We need to have a solution such as the RZ20 in which on a glance you see all the shopping cart that fails and the reason of the failure.
We are on a classic scenario.
Thanks in advance.
Regards,
RR
Hi Richard,
Hope this below thread would be little helpful in resolving your query -
http://scn.sap.com/thread/1773727
http://scn.sap.com/thread/3278177
http://scn.sap.com/thread/1345622
http://scn.sap.com/thread/2137681
Thanks.
From RBEI,
Snehal
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi RR,
I am quite puzzled with your question. You guys are not capturing any error in RZ20? Did you try exploring solution of providing SRM Admin roles? SRM Admin role also have Application monitor similar to SRM 5 where you can view failed shopping cart and its reason. Please see screen shot below from SRM 7 EHP1 solution.
Hope this helps.
Thank you
Ritesh
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi RR,
The First screen shot which you have attached is what you are seeing in SRM 7.0 correct? And 2nd one which you have referred in what you used to see in SRM 5.0 older version?
The SRM 5.0 one looks like customized as it provides resolution steps and vendor information. This does not look standard. Do you check while upgrading do you guys missed some customized report or BADI which used to provide such a detail error analysis?
Thank you
Ritesh
Hi Ritesh,
Thanks but there was no BADI implemented for the same in SRM 5.0, it was like that since the beggining. So, there was nothing missing.
My view is that there should be a transaction/report that should provide as our RZ20 before. Our volumes (no. of shc created/day) are high and then we cannot based our RCA on individual analysis.
Thanks a lot for your quick responses.
RR
Hi Ricard:
This document might be able to help you, please check it out:
You may also want to look at this:
You mentioned that you are in Classic Scenario and using PI. I would like to know how do you get messages (XML) from ECC > PI > SRM. We can create a SC and PO in ECC, but not returning the message back to SRM that the PO and PO number is created in ECC.
Thanks,
Mike
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Mike,
The FEH is based on monitoring in ECC. Through FEH you can see the reason why a PO failed but surprisingly, you are not able to see the shopping cart number that is related to the failed purchase order. Also, FEH does not provide in a glance, as RZ20, all the failures but you need to go PO per PO to get it.
In regards to the return, one of the issues we had in the past was that by standard, professional purchase orders are also trying to send a purchase order creation confirmation to XI and SRM . This should not happen. Due to this, cues were blocked and then shopping carts created multiple self service purchase orders as SRM never recieved the confirmation that the self service purchase order was created.
Thanks but unfortunately FEH is not providing the information we need.
Thanks a lot for your fast reply.
Ricard.
User | Count |
---|---|
1 | |
1 | |
1 | |
1 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.