IDOC Inbound Processing

[Former Member]

Hi friends,

i am testing an idoc in inbound processing with direct function module call, while running it in foreground the idoc is processed successfully and posted to the application, but while running this in back ground , we are getting the error,

1) the material no couldnot be identified for the

item 000010.

2) conditions in E1EDKT1 has been changed check the data ?

how to rectify this one ?

[Former Member]

Hai Joseph

There are two ways to process inbound IDoc. It depend on your business requirement. You could process immediately or background.

This process is controlled in your partner profile setup (WE20)-> Inbound parameters -> inbound options -> Processing by Function Module -> Trigger by background program or Trigger immediately.

If you want to trigger by background program, please maintain variant in program RBDAPP01 and schedule a job to execute. Please select appropriate values for your variant based on your condition.

If you set trigger immediately, SAP will take care the process. You only need to monitor for any error occured via WE02.

Well ... hope you have a good time and enjoy working with IDoc stuff. Let me know if you need an extra help.

Thanks & Regards

Sreenivasulu P

[naimesh_patel]

Hello Joseph,

If you are processing your IDoc in Background than, please check the Inbound paratmeters for Processing by function module of the Partner in Partner Profile (we20).

If you select Trigger by Background program than it might work.

Regards,

Naimesh

[Former Member]

Hi Joseph,

Go to WE19

Create an Idoc

Populate all the segments with the mandatory data

Click on Inbound function module

Enter the function module name which does the processing of the Idoc and select the check box call in debug mode.

You can debug and find out where it is giving the error and correct it accordingly.

Regards,

Sameena

[Former Member]

Hi Joseph,

1) Is there any code in the function module that is checking if the progam is running in foreground or background mode (sy-binpt I think). Maybe the code is behaving differently in foreground and background based on that value.

2) If you can use SE30 (ABAP Runtime Analysis) for both the foreground job and the background job, you can compare the call stack from each run and see where they diverged.

Cheers,

Tony.