Syndication error from XI to R3

[Former Member]

We are getting a IDOC error with status 51 when we are syndicating changes from XI to SAP R3. The error is - The function module IDOC_INPUT_DEBITOR_MDM, which was called for the application input, was not able to process the IDoc. A possible cause is that the IDoc has wrong message type or IDoc type.

We have configured the basic type of IDOC to DEBMDM05 & message type to DEBMDM.

Can anyone suggest corrective actions.

[Former Member · Accepted solution]

Hi Arvind,

As Michael also Suggested there is really no standard process code for inbound for DEBMDM . You will have to Split DEBMDM to DEBMAS and use Process Code APLI.

It is really not necessary to have ARDMAS populated unless untill you are sure you are maintaining data for the ARDMAS structure.Usually in SAP most clients do not maintain data for this structure. So if you just MAP DEBMAS as input then it should work fine.

Same holds for CREMDM : It has to be split to CREMAS and ARDMAS for inbound to SAP.

Sagar : If you know of any standard process code for DEBMDM please let us know the name. That will definitely solve the development effort in XI but as to my knowledge ther is none till now.

Regards,

Prashanta

[Former Member]

Arvind,

We had a thread on this topic 6 month back also. You can search under Forum- MDM

with search string "Jagathi Bondalapati" .

It will give you more insight into the solution.

Thanks

Prashanta

[Former Member]

Hi all.

I can see in IDOC_INPUT_DEBITOR_MDM function call that the first thing that is checked is:

• check IDOC

IF IDOC_CONTRL-IDOCTP NP 'DEBMAS*'.

RAISE WRONG_FUNCTION_CALLED.

ENDIF.

So, only idoc DEBMAS can be processed inbound.

DEBMDM could not be processed directly in R/3. It should be splitted earlt in DEBMAS + ADRMAS.

Regards.

AJ.

[Former Member]

Hi ArvindH,

For Message Type DEBMDM just check if standard process codes and corr. function modules are available for these Message types..

If not you have to create an inbound process code(we42) and attach a function module to it(se37). Then Specify this Process code in partner profile's inbound Parameters(we20).

We have taken this approach.

To create a new function module for DEBMDM just refer any function module for an existing process code in inbound parameters of we20

Thanks and Regards,

<b>Sagar Sonje.

Mark Helpful Answers. </b>

[michael_theis]

Hello Sagar,

like mentioned above, DEBMDM is intended for the message distribution from R/3 to XI. There is no standard function module for the inbound processing of DEBMDM available in R/3!

Kind regards

Michael

[Former Member]

Hello Sagar,

As you have mentioned that you have copied standard FM and assigned it to the Process code, could you please let me know the Standard FM which you have copied for this scenario and are there any changes that has to be made to this copied FM.

[Former Member]

Hi Arvind,

By referring to Standard Function Module i meant suppose in your partner profile settings; for Basic Type <b>CREMAS04</b> you have a specified an inbound process code and a Function module is associated with it.

You have to<b> refer </b>this function module and <b>create </b>your own function module right from scratch to <b>populate</b> <b>sdata</b>.

Assign this function module to your process code.

Now specify this process code in your partner profile settings.

Please Revert if any Queries.

Thanks and regards,

<b>Sagar Sonje</b>

<b>Mark Helpful Answers</b>

[michael_theis]

Hi Arvind,

IDoc Type DEBMDM can only be used for sending messages from R/3 to MDM. DEBMDM is mass enabled which means there's one or more debitor in an IDoc. The mentioned function module can NOT handle this in the R/3 inbound. The R/3 inbound expects a single DEBMAS IDoc. That's we SAP delivers a IDoc split on XI within the XI content. You can syndicate DEBMDM from MDM to XI, but XI has to split those DEBMDM messages into ADRMAS and DEBMAS thus R/3 is able to store the data.

Kind regards

Michael