In the Product Support, we always start the analysis with some basic checklists from past troubleshooting experiences. This means, firstly we are checking the received error messages, or the behavior and if it is a typical issue in the system, then the solution can be simple.
Sometimes, in case the system raises an error message, or the behavior is a well-known issue, even a remote connection might not be needed.
If the reported issue / behavior is not a common problem, then to avoid any misunderstanding as well as to speed up the analysis, a step-by-step document and the opened R/3 and HTTP connection is necessary.
In this post there are 2 separated sections, which contains
typical issues and error messages
good-to-know places / help for the analysis
Typical issues during the transfer
Some of the typical issues / malfunctions during the transfer can be checked in the BBP_PD transaction, but some of them has only a well-known error message
1. Different Follow-on document created during Classic transfer
When a Purchase Order is created instead of Purchase Requisition, the first thing to do, is check the SRM system’s customizing. In this case, you need to check the Node under the SPRO > SAP Implementation Guide > SAP Supplier Relationship Management > SRM Server > Cross-Application Basic Settings > Define Objects in Backend System (Purch. Reqs, Reservations, Purch. Orders).
2. Shopping cart XXXXXXXXX: Error creating the follow-on document
During the classic transfer, the system could not create the Follow-on document in the ECC and the ‘Shopping cart XXXXXXXXX: Error creating the follow-on document’ error message is shown in the RZ20 transaction.
This happens, because the number ranges are not correctly maintained in the SRM and in the ECC environment.
4. Splitting problems: Shopping Cart creates more than one follow-on document
The common root cause of this issue is that, one of the Shopping Cart’s item contains a Preferred Supplier and based on the standard grouping / splitting logic, the one item will be different from the other which results in a separate Purchase Order. The preferred supplier can be determined through a custom BAdI logic, or it can come from the Catalog.
In this scenario, when you check the BBP_PD transaction you can see that the Ordered_Prod value has a lot of zeros before the product number. The field can be seen in the main screen of the BBP_PD transaction under the Items section and inside the item details under the CRMD_ORDERADM_I table.
7. BBP_SOC_APP_01 007 Price could not be translated to standard currency
This error message appears in RZ20, when the user tries to create a Purchase Requisition from the Shopping Cart, but the item currency is different than the assigned vendor’s currency, or the currency conversion rate is not set correctly in the SRM system.
From a Support perspective, the easiest way to trigger a Shopping Cart transfer analysis is when a Shopping Cart has I1112, “Error in transmission” status. In such cases, we can simply retransfer the given document by debugging and check what was failing during the transfer.
In case the Shopping Cart is stuck in transfer process status I1111, the document can be retransferred only with the BBP_SC_AUTO_RETRANSFER standard report.
In any of the above Shopping Cart statuses, you can considerably speed-up the support process by creating two-three Shopping Carts in “Saved” status, that is, without triggering the approval process and transfer. That way, our Support Engineers can immediately trigger transfer on those Saved documents. For this, our engineer will only need an R/3 connection to the affected SRM system.
The standard system is capable to create BAPI test data in the ECC environment. During the RFC call, the system will capture the received data from SRM and store it in a test data. During the analysis, this test data can be run multiple times in testrun, without creating or changing anything in the ECC system. If you need help to create the test data, please go through the Creating test data for ECC backend purchasing documents - https://wiki.scn.sap.com/wiki/x/cIQpFg SAP Wiki page.