Reduced IDOC: Generating Inbound function module for IDOC

[Former Member]

Created a reduced IDOC based on message type MATMAS called ZMATMAS.

When I send IDOC to receiver IDOC has status 51:

'Incorrect function module IDOC_INPUT_MATMAS01 called up'

This is because process code used is MATM which uses function module IDOC_INPUT_MATMAS01.

How do I generate an inbound function module IDOC_INPUT_ZMATMAS01 for custom process code ?

[Former Member]

Hi ,

Please do this stting for custom Idocs.

1.Make the entries in we57 for the new fucntion module

2.Create a process code in inbound -WE42 .

TO maintain entries follow the below example

A process code needs to be maintained on each client. It then needs to be linked to the message via the partner profiles on each client. This allows the various clients to use a unique function module for the same message type.

To maintain the process code follow these steps:

• Log on to the appropriate receiving system client

• Execute WE42 (ALE -> Extensions -> Inbound -> Maintaining process codes inbound)

• Choose Inbound with ALE service

• Choose Processing with function module

• Click on Processing with function module and choose create icon

• Click on New Entries

• Type in process code ZINR and give it a description and save

• Now you are asked to Please maintain codes added in ALE entry methods, enter and choose Z_IDOC_INPUT_FIRVSL and copy it. You should choose a FM similar to your one.

• Enter your process code ZINR

• Enter your function module Z_IDOC_INPUT_ZINVRV

NOTE: The next 6 steps are used in workflow error handling.

• Enter IDPKFIDCMT in object type

• Enter MASSINPUTFINISHED in End event

• Enter IDOCINVOIC in IDoc object type

• Enter INPUTERROROCCURREDFI in IDoc start event

• Enter INPUTFINISHEDFI in IDoc End event

• Enter IDOCINVOIC in Application object type

You will need to determine the task associated with object IDOCINVOIC, and then assign the appropriate position to it. This position will then receive the application error messages via workflow.

3.make the Function module as the Inbound function module -BD51

Define FM settings (BD51) Client independent

Enter transaction BD51 (ALE -> Extensions -> Inbound -> Define settings for input modules)

Click on New entries

Type in the name of the new function module IDOCINPUT_ZINVRV

• Enter 0 for mass processing in the output column

• Save and Exit

Please let me know if u have any Queries

Rgds

Sree M

[Former Member]

Hi,

Inbound IDOC

Creation of Function module: SE37

Assigning the characteristics for FM: BD51

Assigning FM with IDOC type: WE57

Creation of process code: WE42 88

Creating partner profile for Inbound parameter: WE20

Processing of Inbound IDOC manually: WE19

Viewing processed Inbound IDOC: WE02

If you have followed all these steps then easily you can achieve the requirement.

In WE19 you can process already generated IDOC once again or you can add segments, even you can create new IDOC and click on button standard Inbound if this gives popup with message partner profile found then you can go for testing.

To debug you can click on button Inbound FM and give FM and carry on debugging.

I think this will resolve your issue.

Use of WE19 is very imprtant for Inbound IDOC.

Please reward if useful

Regards,

Ramesh