Hello,
I am using SRM 5 in classic mode, connected to ECC 6.0.
I have an error message in the administrator monitor that tells me a transfer a shopping cart to ECC has failed.
"Shopping cart 1000000123: Error creating the follow-on document"
(Message is BBP_PU 367)
This is located in the "local errors" section of the administrator monitor.
The follow on doucment will be a PO in ECC.
This message does not tell me the cause of the problem therefore I need to retrnsmit the cart and debug to find the error message that is being returned from ECC.
I have browsed the forum and there are various answers about debugging but but have not found exact instructions on how to debug, and it is now always clear on whether the instructions apply to classic or extended classic.
I have seen reference to the method in note 539978 that creates test data with FBGENDAT for the ECC BAPI. However this method does not seem suitable for a production system because it will interfere with all shopping carts being transferred while the shoppign cart with the problem is being debugged.
Therefore I would like to debug in SRM just for the shoppign cart with the problem.
Hopefully this thread will become the defintiive poitn of reference for debuggin a classic shopping cart transfer to ECC in SRM 5.
I propose to use function module BBP_PD_SC_TRANSFER to transfer the shopping cart again by entering the shopping cart GUID.
Question 1) Can this error message be returned by checks in SRM before the BAPI is called in ECC? If so, where do I place a breakpoint to find the error determined by the checks in SRM?
Question 2) If the system is getting as far as calling the BAPI in ECC, is it possbile to find the error message passed back from ECC by this approach, given that the actual transfer is carried out by the spooler?
Question 3) If this approach is valid, in which method/function module do I need to place a breakpoint, at which statement is the error message passed back to SRM from ECC?
Your help would be appreciated,
Reagrds