C4C Integration – Debugging remote calls into ERP / CRM

[Kinsbrunner]

Introduction

When working with system integration, it sometimes happens that initial customizing fails, especially when you are under your first C4C related projects. So, as we are not able to debug on source system (C4C) it is extremely useful to be able to debug on target system (in my case ERP).

Purpose

The aim of this document is to explain how to debug ERP calls from C4C side in order to be able to understand issues and troubleshooting. Be aware that same procedure applies for CRM system.

STEP 1: Finding error message

When testing ERP External Pricing, I was facing specific issues which didn’t sound to be C4C-related, even more, taking into account the scenario I was testing it sound to me more like an external message received from ERP. So, I decided to try researching and debugging over ERP system. On C4C, I was getting error message “ËRP: No pricing procedure could be determined” so, on ERP side, I entered into T100 table in order to find the corresponding message:

Once found that it was message type V1 and message number 212, I went into SE91 transaction and made a Where-Used list search for that specific message in order to find from where was it being triggered and, finally found it:

STEP 2: Finding ERP integration user

So, next step was to determine the ERP user created for the integration; in case you have followed Marketplace Integration guide (on the ERP Preparation section), it should be CODINTEG.

STEP 3: Activating remote ABAP debugging

As the debugging to be done is from a remote call, it is required to activate it for specific user through transaction SRDEBUG.

STEP 4: Setting integration user as debugging user

Afterwards, it is necessary to set an external breakpoint for the INTEGRATION user. For doing so, go to Utilities menu and then, into Settings in order to set the debugging user to the integration one:

The reason why this is required is since the user that reacts to Web Service is the one defined for integration so, that is the user that needs to be activated for debugging.

Final step (solving the issue) depends on you… Happy Debugging!