6 Replies Latest reply: Aug 29, 2005 9:08 PM by James Mandikos RSS

Setting up new IDOC message type.

James Mandikos
Currently Being Moderated

Hi All,


I have created a new process code (ZMBGMCR) and linked message type MBGMCR to the process code and configured the process code to use function BAPI_IDOC_INPUT1. The reason I have created a new process code is because the standard message MBGMCR is not linked to a process code. 


I have also created a new mesage type based on a reduced version of MBGMCR that. I have also link to the new process code. I have gone through all the interface customising to setup the new message type. I have linked an IDOC type (MBGMCR02) to the new message type (WE82), assigned the function module to the message type/ Idoc type (WE57), added the message type to the new process code ZMBGMCR (WE42) and configured the partner profile. 


In testing the new message type, the IDOC is failing with an IDOC Interface is not complete message in the IDIC status record. In debugging function module BAPI_IDOC_INPUT1, the function fails in the check for an entry in TBDBA.   There is an entry for the standard message MBGMCR which is why the standard message works.


Does anyone know how this entry in TBDBA is created?