Idoc process

[former_member653171]

Hi

some external system creating sales order

as per XI team I have added two message types Inbound as ORDERS & o/b parmtr as INVOIC

for existing partner profile in WE20 and one more setting customer SH & PY in VOE4

I don't have any Idoc knowledge is any more settings need to be done

sudha

[Former Member · Accepted solution]

Hi Yo can follow below for basic config for IDOC settings.

Define a new internal RFC destination INTERNAL

Explore both the transactions WEDI and SALE and adjust the settings as necessary

Use transaction BALE to generate an arbitrary IDoc

You can access most of the transactions used in the example below in the menu

WEDI and SALE.

We will assume, that we want to send material master data from the current system

to a remote system

. To simulate this scenario we do not need to have a second

system. With a little trick, we can set up the system to send an IDoc back to the

sending client.

We will set up the system to use an RFC call to itself. Therefore we need to define

an RFC remote destination, which points back to our own client. There is a virtual

RFC destination called NONE which always refers to the calling client.

RFC destinations are installed with the transaction SM59. Create a new R/3

destination of type "L" (Logical destination) with the name INTERNAL and the

destination NONE.

Note: Do not use RFC type internal. Although you could create them manually, they

are reserved for being automatically generated. However, there is the internal

connection "NONE" or "BACK" which would do the same job as the destination we

are creating now.

The next step is defining a data port, which is referenced by the IDoc sending

mechanism to send the IDoc through. Declaring the port is done by transaction

WE21.

We will now declare an ALE connection from our client to the partner INTERNAL.

ALE uses IDocs to send data to a remote system. There is a convenient transaction

to send material master data as IDocs via the ALE.

The set up is done in transaction SALE. You first create a new ALE model, to avoid

interfering with eventual existing definitions. Then you simply add the IDoc

message MATMAS as a valid path from your client to INTERNAL.

In order to send the IDoc, you call the transaction BALE and choose the distribution

of material master data (BD10). Choose a material, enter INTERNAL as receiver

and go.

To see, which IDocs have been sent, you can use the transaction WE05. If you did

everything as described above, you will find the IDocs with an error status of 29,

meaning that there is no valid partner profile. This is true, because we have not

defined one yet.

Regards

Yepuri