Transaction /n/SAPPO/PPO2 (Postprocessing Desktop) comes in handy when fault finding. It can be used in both ECC and SRM. I find it very useful when looking for failed transfers between the two systems. When a requisition is transferred from ECC to SRM for sourcing it is possible to see the reason the requisition did not get created into a SC in the SRM system. The second use for the transaction is when a PO is transferred from SRM to ECC and the PO fails. The brilliant part about using /n/SAPPO/PPO2 is that if the error has been fixed (ie the network has had funds added, or the material has been replicated to SRM) then you can easily just reprocess the failed PO in ECC through this transaction. Follow the below print screens to be able to see all the failed transfers in a system (print screens below are from SRM – Failed requisition transfers):
1. Go to Transaction
2. Fill in the filters (all that really needs to be filled in is Order Assignment as 2 and then the dates you want)
At this point depending on your RFC connection config you might get a warning saying that “No RFC destination saved for logical system”, it is ok you will still get errors displayed.
3. Once executed a list of errors for the filtered selection will be provided. On the left hand side it will provide you a requisition number (ECC requisition number). Then on the right panel it shows you the first error for this requisition. If you expend the requisition it will give you all the issues.
4. If you are happy that all the errors have now been fixed in the receiving system you then can right click and reprocess and push this through using the original request XML.
NOTE: It is a great tool if you see a failed XML in transaction SXMB_MONI to quickly reprocess and find the errors on the transferred document.