Trouble shooting of SRM-PO transfer error.

What is the problem ?

There is a backend error when process SRM PO. In BBP_PD there is status I1132 “Transfer failed”. In the transaction RZ20, there is an error log. 

Trouble shooting steps:

1, How to get the backend error message number for SAP Note searching?

• 1) Take a note of the error description in the transaction RZ20.
• 2) Go to the backend system -> Transaction SE16 -> Table T100 ->Search the message text with “* a part of the error message description *”. Then push F8. In the list of the searching result, find the correct message number. Record the message number, then start note searching with the 5 digital message number.

2, If you cannot find the Note , how can you start investigation in the backend system?

• 1) In the SRM system, go to the transaction SM59 and find the correct backend system, then double click on the RFC destination. In the next screen click on the “remote logon” (The RFC user must be a dialog user).

• 2) When you are in the backend system, go to the transaction SU3. In the parameter tab, add the parameter FBGENDAT =X.

• 3) Go to the backend transaction SE38 to run report FBGENDAT for Function module BAPI_PO_CREATE1 or BAPI_PO_CHANGE with mode is A or B. For more information regarding this report, please check SAP NOTE 539978.

• 4) Start to create a SRM PO which will be transferred to the backend system.
• 5) Once you have a new entry in the SM13 in the backend system, please deactivate the generation of test data in the report FBGENDAT. Then delete the parameter in Step 2).
• 6) Go to the backend transaction SE37 and run the FM BAPI_PO_CREATE1, in the test data directory, you may find the generated test data by step 4).

• 7) In the transaction SE37, run the FM BAPI_PO_CREATE1 again with the created test data. In the return table, you will get the error issued from the MM program.

• 8) Set a watch point with “sy-msgno = error number” ,you could debug the error issuing code in the FM BAPI_PO_CREATE1.

Please note you could debug in the FM BAPI_PO_CREATE1 again and again untill you find the root cause, because there is no commit work in the FM.