sap abap middleware_debugging
DESCRIPTION
sap Middle ware debuggingTRANSCRIPT
Before creating the order in CRM:
Set external break-point in FM CRM_R3_SALESDOCUMENT_UPLOAD in CRM in both dc-22 & dc1-20 instances. (Keep both instances open)
In ECC side do the same thing for FM BAPI_SALESDOCU_PROXY_UPLOAD. Keep both instances open in ECC as well.
Now create an order in CRM and save it. It’ll stop in CRM_R3_SALESDOCUMENT_UPLOAD FM.There in Line#381 make gv_synchronous_call = ‘X’ in debug modeAnd change lv_rfc_dest to ECC_DR1CLNT230_TRUSTED in Debug mode as well.
Then cursor will come to Line464. Then press F5 it’ll direct go into ECC (BAPI_SALESDOCU_PROXY_UPLOAD). Then you can continue from there.
Function Modules for various Orders:
Enter /h and set a breakpoint at one of the following function modules:
1. CRM_R3_ACCOUNTING_UPLOAD passes Controlling information for serviceContracts and service orders
2. CRM_R3_SERVICECONF_UPLOAD passes Controlling information for serviceConfirmations.
3. CRM_R3_SRV_RESERVATION_UPLOAD is called for material reservations.4. CRM_R3_SALESDOCUMENT_UPLOAD is called for sales relevant
information (for example, if you have sales items in a service document).
5. CRM_R3_SERVICE_BILLING_UPLOAD for billing of service orders in R3.
Reprocess the BDOC:
Set a breakpoint at the line IF lv_synchronous_call IS INITIAL or IFgv_synchronous_call IS INITIAL. F8 brings you to this breakpoint.
Set lv_synchronous_call/gv_synchronous_call to X and with F5 you'll enterR3 debugging. Make sure that the RFC user used for communicating betweenthe systems is defined as a dialog user.
Important: you should not set a BDOC to debug status in a productive system, as this can lead to inconsistencies.
In this case, you should deregister the queues via transaction SMQR. The queue name is CSA_ORDER_ followed by the no. of the service document.