Inbound function module for IDoc type INFRECMASS01

[roland_spindler]

Hello everybody,

What is the inbound function module for IDoc type INFRECMASS01?

I tried IDOC_INPUT_INFREC (as for IDoc INFREC01), but I got the following message (B1 044): Incorrect function module IDOC_INPUT_INFREC called up

Thanks in advance

Roland

[Manohar2u]

Look at the FM in we42 tcodes tables.

Regds

Manohar

[roland_spindler]

There is only one entry INFR which refers to IDOC_INPUT_INFREC (which did not work). It does not distinguish between INFREC01 and INFRECMASS01.

Any other ideas?

[Manohar2u]

You can get FM for idoc type and message type from WE57.

Regds

Manohar

[roland_spindler]

I want to enter the correct function module at WE57, that's why I need to know it.

[Former Member]

The only difference between INFRECMASS01 and INFREC01 is that repitition of the same segments. However, the standard function module is hardcoded with IDOC type INFREC01, so if you want to use the MASS IDOC copy the standard one and put in the logic to loop around and process the info records one by one.

There is no standard funtion that can process mass idoc of the info record.

Regards,

Ravi

Note: Please mark the helpful answers

[roland_spindler]

Is there a way to use ME18 to create type INFREC01 messages instead of INFRECMASS01?

[christianpunz]

fast track: SE16N on table EDIFCT.

[Former Member]

Hi Roland,

IDoc type INFRECMASS01 is used usually for outbound.

You can use standard program RBDSEINF (ME18) to generate purchasing info record IDoc via FM MASTERIDOC_CREATE_REQ_INFREC.

For inbound, please use IDoc type INFREC01 instead.

Hope this will help.

Regards,

Ferry Lianto

[roland_spindler]

Thanks.

For many other message types (customers, material, etc.) I can create IDocs with transactions similar to ME18. I can import those IDocs easily into the target system.

However, the IDocs I created with ME18 produce the mentioned error message on importing. Where is my mistake?

best regards

Roland

[Former Member]

Hi Roland,

Please chcek your partner profile setup (WE20) perhaps it was not configured properly.

Hope this will help.

Regards,

Ferry Lianto

Please reward points if helpful.

[roland_spindler]

Thanks Ferry!

After changing the outbound message type at the partner profile, it did work!