Setting up new IDOC message type.

[Former Member]

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?

[Former Member]

Hi James,

If I understand it correctly, you want to use standard message <b>MBGMCR</b>. To do this you do not need to create a new process code, you can just use standard process code <u><b>BAPI</b></u>.

This ALE message is created from BAPI, for all these messages (created from BAPI) you need to use process code BAPI. Which process code checks for the entry in TBDBA. Entries in TBDBA are created at time of creation of ALE interface for BAPI (Txn code BDBG).

Hope this helps.

Cheers,

Sanjeev

[Vinod_Chandran]

Please check the following menu

From the SAP menu

Tools -> Business Communication -> IDoc Basis -> Development -> Inbound processing settings -> Message/application object

You can get more information from here

http://help.sap.com/saphelp_470/helpdata/EN/dc/6b7e0b43d711d1893e0000e8323c4f/frameset.htm

Thanks

Vinod

Message was edited by: Vinod C

[Former Member]

Hi james

Try to add the message type inth transaction we20 and double click on the message type that will take you to partner profile inbound where you assign your process code to the message type. And then generate the partner profile.This should work.

If you your query is answered please let me know.

Bye

karthik

[Former Member]

Hi James,

If I understand it correctly, you want to use standard message <b>MBGMCR</b>. To do this you do not need to create a new process code, you can just use standard process code <u><b>BAPI</b></u>.

This ALE message is created from BAPI, for all these messages (created from BAPI) you need to use process code BAPI. Which process code checks for the entry in TBDBA. Entries in TBDBA are created at time of creation of ALE interface for BAPI (Txn code BDBG).

Hope this helps.

Cheers,

Sanjeev

[Former Member]

Hi Sanjeev,

In our system MBGMCR is not assigned to process code BAPI. I therefore created a new process code and linked MBGMCR to the new function code. MBGMCR is linked to object BUS2017.

The questin I have is, do I need to copy BUS2017 and what are the steps for assigning my new message type to a busines object?

Rgds,

James.

[Former Member]

Hi James,

What system do you have ? Have you tried using process code BAPI in your partner profile ? Can you post here what error are you getting when you try to use it ?

Cheers,

Sanjeev

[Former Member]

Hi Sanjeev,

Message type MBGMCR which I have linked to my new process code works fine. It's my new message type ZITRANS which I am having problems with.

I am getting further now by using transation BDBG to generate the ALE interface. I have taken a copy of the business object BUS2017 to zBUS2017 and tried to link my new message type to the creatfromdata method of the object. When I try and do this tells me that my IDOC type MBGMCR01 already exists. This message type is already linked to message type MBGMCR. Is it not possible to link two message types to the 1 IDOC type and generate the interface. Do I need to generate the IDOC interface for each new inbound message type? Am I on the right track?

Thanks for your help so far.

Rgds,

James.

[Former Member]

Hi James,

Did you get answer to your question? Is there any way to use custom message with standard IDOC?