Hi,
For a customer I am investigation an issue with business partner synchronization between CRM and ECC on a quality environment.
A CRM address change leads to a short dump in ECC - MESSAGE_TYPE_UNKNOWN (the change itself seems to be correctly transferred to ECC).
Debugging tells me that the dump is (indirectly) caused by include LVV02F0M line 66-68.
IF SY-BATCH IS INITIAL.
MESSAGE I012 WITH GROUP_COUNT NODATA
ENDIF.
In other words, the system thinks it should present the message in foreground whilst the process is running in background. Only the values for variables GROUP_COUNT and NODATA are transferred to the middleware message table. Since it cannot handle the message without a message type a dump occurs. The route to this dump is:
1. FM PI_BP_CUSTOMER_ALE_INBOUND_RI - variable IV_KNVK_MASS_SWITCH is initial
2. FM IDOC_INPUT_DEBITOR
3. FM ERP_IDOC_INPUT_DEBITOR - PERFORM FILL_APPL_STRUCTURES..
4. Include LVV02F3N - PERFORM call_transaction..
5. Include LVV02F3J - CALL_FUNCTION 'DEBITOR_BDCDATA'
6. FM DEBITOR_BDCDATA - PERFORM MAPPE_PRUEFEN-OEFNEN
7. Include LVV02F0M
Regarding point 4: the variable INPUT_METHOD is initial which corresponds to no display mode. I have checked the CRM RFC destination to ECC and the RFC user (which is not a dialog user) but could not find a setting that is responsible for SY-BATCH being initial.
Any ideas?
Kind regards,
Miguel Ruijsenaars