Debugging CRM to R3- Sales Order

Debugging CRM to R3- Sales Order

 

§A) Block the CSA queue on CRM Side .

§B) Create an order and save it.

§C) Go back to the CSA queue and execute your queue in debug mode . Please put a BreakPoint in 385 line of FM   crm_upload_to_oltp. and line 422 of FM crm_r3_salesdocument_upload.

§D) Put a break point on line 385  of  FM   crm_upload_to_oltp and change the destination in parameter lt_actual_recipients-DEST to  a DIALOG destination of R3.

§E) Put a break point on line 422 of FM crm_r3_salesdocument_upload and Set the value of variable gv_synchronous_call  = X  in debug.

§F) Then you will be in R3 - debugging how data flows to R3 .

§G) Then put a breakpoint on Select statement . Basically BTEs are called by selecting on tables like TBE31, TBE32, TBE34 , TPS31, TPS32 and TPS34. These tables contains name of Event/PROCS and FM which you can configure and use an user exit.  The Import parameter of teh FM are stated in TBE01 and TPS01 for each event. While debugging keep the name of the event/procs . The ones which I kept track were  00511074  , 01010001 ,00501020 and 00501021  for TPS31, tps32 and TPS34 . One which I did not track was that of TBE01.  You can configure one FM in these tables to check - if we can do that and use an exit. In case there is already any FM defined, PLEASE DO NOT remove them. So this is a way - you can check which exit you can use.

§H) After all the BTEs are triggerred, system calls Badi BADI_SD_SALES . Put a breakpoint on the Badi implementation as stated above and check, if you have all the value which you can use . 

§I) After the BADI  SAP calls FM SD_SALES_DOCUMENT_INIT which is into the famous Program SAPMV45A