How to deal with recieved IDoc's ?

[Former Member]

Hello,

I have the following scenario here within a workshop:

We have a SAP R/3 IDES System sending IDoc for Materials and Debitors to a 3rd party system (e.g. if material is updated on r3-side). This so far works fine and the 3rd party system also recieves all the IDoc's sent.

Now my question:

What do I have to do to see wheter this 3rd party product has sent IDocs to the R/3 ( e.g. orders ) specifically:

a) where can I find these Idocs ? TC WE05 ?

b) How can I define what has to be done ( e.g. executing order ) if the R/3 recieves an IDoc and I don't wan't to use Workflows ( because theyre out of scope of this workshop ).

Thanks for any advice,

Clemens

[Former Member]

Hello,

yes .You can check whether system has received any new IDocs from 3rd party system which must be defined as logical system in We20.

Check IDocs in we02/we05.

You need to define partner profile inbound paramters to identify message type & use the relevant process code (to process the required data ) in parameters .& also set parameter whether you want to process IDocs immediately or collectively later at scheduled timing.

This setting will take care of processing incoming data from 3rd party.

Thanks.

[Former Member]

Hi Rushali,

Thank you for your answer! That was helpful though I have one additional question ( just for own understanding):

The same way I set the options for outbound parameters for the message type ( MATMAS and DEBMAS ) I have to set the inbound parameters for ORDERS etc. and just assigning a process code that has to be executed ? That easy ? Is it also possible to start a specific transaction if a specific IDoc arrives ? The plan is to process IDocs immediately as they arrive.

Thank you!

[Former Member]

Hello,

Yes..you hv to set inbound parameters with process code which will be linked to Inbound function module.

In case of orders you need to set relevant proces code.& set the indicator for process immediately.

Thanks.

[Former Member]

if ur received idoc has message TYPE ORDERS and process Code ORDE

then when the idoc is received (inbound) then standard inbound is triggered executing fm IDOC_INPUT_ORDERS and when the idoc is success then a sales order is created .

regards,

vijay

[Former Member]

Helllo,

Thanks for your advice, that helped a lot - I set the process code for the IDoc to ORDE. Now, when the order is created after IDoc comes in - do I have to confirm it manually somehow or does it execute automatically ? If not, how to achieve that ?

Thanks,

[Former Member]

It will be done in the EDI mapping <b>and it picks the function module automatically</b> .

u can check the same in the WE20 partner profiels for the inbound and outbound parameters.

regards,

vijay.

[Former Member]

Hello,

You need not confirm it manually.

if you have setup process idoc immediately,then data will get processed immedaitely.

& if you have chosen other option of processing later(collect idocs ),then you need to look at scheduling RBDAPP01 program at certain timings.

this program processes inbound IDocs in the system.

Thanks.

[Former Member]

Hi clemens,

1. Based on Message type ,creation date ,Idocs type You can check in Tcode

WE02 / we05.

Here you will find different status of idocs.

2.Generally if you are receiving idocs for standard idoc type there will be some program which will process these idocs.

OR if you are receiving enhanced idoc type you need to develop a program to process those idocs and schedule that program based on your frequency of idocs.

Pls. reward points for helpful answers

[ferry_lianto]

Hi Clemens,

If you setup the inbound partner profile (WE20) to be trigger immediately (under processing by function module) then the IDoc will post automatically to the application.

Otherwise, if you setup to trigger by background job then you need to schedule/run standard program RBDAPP01 to post the IDoc.

Please ensure you have setup the variant correctly that corresponding to your message type prior to run above program.

Also you can process manually the IDoc(s) via transaction code BD87.

Hope this will help.

Regards,

Ferry Lianto