One way to debug CRM Middleware is by disabling the inbound queue in ECC or outbound queue in CRM. This was causing great inconvenience to others working on the same server trying to create similar documents in ECC. This blog is about debugging the CRM middleware without disabling the queue. The example used here is of a DMR request created in ECC once a service confirmation is saved and completed in CRM.

  • Place an external break point in function module CRM_R3_SERVICECONF_UPLOAD.

Image3.jpg

  • Create a service confirmation in CRM, fill the mandatory fields, complete and save the confirmation.
  • By default gv_synchronous_call  is initial and function ‘BAPI_SERVICECONF_PROXY_UPLOAD’ is called as a background task. Once GV_SYNCHRONOUS_CALL is set to ‘X’, function ‘BAPI_SERVICECONF_PROXY_UPLOAD’ is called in foreground task and can be debugged all the way in ECC.

Image2.jpg

 

  • Function module CRS_SERVICE_BILLING_PROCESS processes the service confirmations.

 

   Image1.jpg

To report this post you need to login first.

3 Comments

You must be Logged on to comment or reply to a post.

  1. Samantak Chatterjee

    Hi Vanita,

    Thanks for a good article.

    I have query regarding this topic. I would like to know how to get the Function Module name for other kind of scenarios for example Sales Order creation, Business Partner creation/modification or Product Master modification. Is there any method available by which we can get to know the name. This will help to debug those applications without blocking any queues in the middleware from CRM end.

    Any pointers in this respect will be really very helpful.

    Many thanks in advance.

    Best Regards,

    Samantak Chatterjee.

    (0) 

Leave a Reply