Skip to main content

SAP CRM/ERP: Handy places for (Business Partner) Middleware Debugging

Submitted by Stefan Barsuhn on

If you have a problem in your ERP/CRM middleware, here are some handy places that you can set your breakpoints in:

ERP

  • Upload from CRM starts in CRM_UPLOAD_TRIGGER (ERP function module!)
  • Upload to CRM is triggered in CRM_SEND_DATA
  • check TX SM30 table COM_BUPA_CALL_FU to see all function modules that are processed during BP inbound/outbound

CRM

  • BP upload to CRM passes through BUPA_OUTBOUND_TRANSMIT_BP
  • Inbound confirmation of ERP replication (in CRM) happens in FM BUPA_MWX_BDOC_DOWNLOAD_R3A 
  • BDoc is created in BUPA_MWX_BDOC_CREATE_MAIN
  • check TX SM30 tables CRMC_BUT_CALL_FU in CRM to see all function modules that are processed during BP inbound/outbound replication
  • check the filters maintained in TX R3AC1, here the tabs Mapping R/3 -> CRM and CRM -> R/3 contain the relevant function modules
  • Other places for filtering are TXs R3AR2 (initial load settings) and SMOEAC (subscriptions)
  • In order to debug the outbound queue from CRM to ERP, follow this blog.  Make sure to set the breakpoint in CRM_UPLOAD_TRIGGER on the ERP side, not the CRM side!

Note

  • On the sender side, you need to set a session breakpoint (SAP GUI) or an external breakpoint (CRM WebUI) for your own user.
  • On the receiver side, you need to set an external breakpoint for the RFC user.

Tags