cancel
Showing results for 
Search instead for 
Did you mean: 

Sending IDOC...

Former Member
0 Kudos

Hello,

trying to understand IDOCs seems complicated. You need to use ports, logical

system names, destinations and so on.

Following the most linked blog

/people/ravikumar.allampallam/blog/2005/02/23/configuration-steps-required-for-posting-idocsxi

I am able to configure the infrastructure of IDOCs.

But I couldn't find a tutorial how to use an IDOC? Can anyone guide me how

to fill an IDOC with data and send it to XI?

Certainly no big job, but I couldn't find a how-to guide.

Also it is difficult to know which IDOCs exist and can be used or when you have

to create your own one

thx

chris

Accepted Solutions (0)

Answers (6)

Answers (6)

Former Member
0 Kudos

Hi Christian Riekenberg ,

The following websites contain PDF docs explaining how to use an IDoc:

A Step-by-Step Guide on IDoc-to-File Using Business Service in the XI Integration Directory

https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/e07dcaa0-a92b-2a10-3a96-b3d942bd...

How to convert an IDoc-XML structure to a flat file and vice-versa in XI 3.0

https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/46759682-0401-0010-1791-bd1...

Introduction to IDoc-XI-File scenario and complete walk through for starters.

/people/prateek.shah/blog/2005/06/08/introduction-to-idoc-xi-file-scenario-and-complete-walk-through-for-starters

IDOCs (Multiple Types) Collection in BPM

/people/pooja.pandey/blog/2005/07/27/idocs-multiple-types-collection-in-bpm

cheers!

gyanaraj

****Pls reward points if u find this helpful

Former Member
0 Kudos

Hi Christian,

In order to send or receive IDOC you have to perform the following ALE settings as well.

Steps for ALE settings:-

Steps for XI

Step 1)

Goto SM59.

Create new RFC destination of type 3(Abap connection).

Give a suitable name and description.

Give the Ip address of the R3 system.

Give the system number.

Give the gateway host name and gateway service (3300 + system number).

Go to the logon security tab.

Give the lang, client, username and password.

Test connection and remote logon.

Step 2)

Goto IDX1.

Create a new port.

Give the port name.

Give the client number for the R3 system.

Select the created Rfc Destination.

Step 3)

Goto IDX2

Create a new Meta data.

Give the Idoc type.

Select the created port.

Steps for R3.

Step 1)

Goto SM59.

Create new RFC destination of type 3(Abap connection).

Give a suitable name and description.

Give the Ip address of the XI system.

Give the system number.

Give the gateway host name and gateway service (3300 + system number).

Go to the logon security tab.

Give the lang, client, username and password.

Test connection and remote logon.

Step 2)

Goto WE21.

Create a port under transactional RFC.(R3->XI)

Designate the RFC destination created in prev step.

Step 3)

Goto SALE.

Basic settings->Logical Systems->Define logical system.

Create two logical systems(one for XI and the other for R3)

Basic settings->Logical Systems->Assign logical system.

Assign the R3 logical system to respective client.

Step 4)

Goto WE20.

Partner type LS.

Create two partner profile(one for XI the other for R3).

Give the outbound or inbound message type based on the direction.

Step 5)

Goto WE19

Give the basic type and execute.

fill in the required fields.

Goto IDOC->edit control records.

Give the following values.(Receiver port,partner no.,part type and sender Partner no. and type)

Click outbound processing.

Step 6)

Go to SM58

if there are any messages then there is some error in execution.

Goto WE02.

Check the status of the IDOC.

Goto WE47.

TO decode the status code.

Step 7)

Not mandatory.

Goto BD64.

Click on Create model view.

Add message type.

BD87 to check the status of IDOC.

In case if not authorized then go to the target system and check in SU53, see for the missing object

and assign it to the user.

SAP r3

sm59(status check)(no message)

WE02(status check)

WE05(status check)

BD87(status check)

Xi

IDx5(Idoc check)

SU53(authorization check)

After these steps you can trigger an IDOC from WE19

Plz reward points

Prashant

Edited by: Prashant Menon on May 8, 2008 8:19 AM

Former Member
0 Kudos

Hi,

Use WE19 IDOC Test tool to fill the IDOC field values for test purpose and trigger the IDOC from there it self

Goto we19

Select the basic type and give the name of the idoc

Click on Execute

provide the Control record values like partner number and port , msg type.

Give the field values also there.

Click on standard outbound process.

Use the Transaction ocde WE30 to view the IDOC's.

If the standard IDOC's are not satisfying your requirement means you need to go for Custom IDOC creation

Steps To Create Custom IDOC

1.Create Segment Type (WE31)

Go to Transaction code WE31

Enter Segment type, click on Create

Give Description

Enter the Necessary Fields & Data Elements for those Fields.

Save the Changes.

2.Create Idoc Type (WE30)

Go to transaction code WE30

Enter the Object Name, select Basic type and click Create icon

Select the create new option and enter a description for your basic IDOC type and press enter

Select the IDOC Name and click Create icon

The system prompts us to enter a segment type and its attributes

Choose the appropriate values and press Enter

The system transfers the name of the segment type to the IDOC editor.

Follow these steps to add more number of segments to Parent or as Parent-child relation

Save it and go back

Go to Edit -> Set release

3.Create Message Type (WE81)

Go to transaction code WE81

Change the details from Display mode to Change modenAfter selection, the system will give this message “The table is cross-client (see Help for further info)”. Press EnternClick New Entries to create new Message Type

Fill details

Save it and go back

4.Assign Idoc Type to Message Type (WE82)

Go to transaction code WE82

Change the details from Display mode to Change moden After selection, the system will give this message “The table is cross-client (see Help for further info)”. Press Enter.

Click New Entries to create new Message Type.

Fill details

Save it and go back

Regards

Seshagiri

Former Member
0 Kudos

Thanks for this answers. Points will be assigned.

Now I try following tutorial:

https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/e07dcaa0-a92b-2a10-3a96-b3d942bd...

But there will be create a Business Service in Directory. But I already

have a Business System with adapter specific I should use in tutorial.

This caused an error: "No receiver could be determined"

Why do they use a Business Service? Is this necessary for IDOC communication?

Or can I do this also in Business System?

thx

chris

gopalkrishna_baliga
Participant
0 Kudos

Hi Chris,

I am also facing the "No receiver could be determined" error in my IDOC to File scenario. How did you solve this?

I am using a business system for sender IDOC system. Should this be a business service?

Kindly help me. I will be really greatful to you if you can help me.

Thanks & Regards

Gopal

Former Member
0 Kudos

Hi,

Its not like that we shld only use the Business Service for this type of scenarios

We can use Businss system in Idoc---File scenarios

The error which u r getting is No Receiver could be determined is because of your Receiver determination may be wrong

Cross check it once aigan

Regards

Seshagiri

Former Member
0 Kudos

Hi,

You can fill IDOC with data in WE19 in SAP R/3.

In the Initial Screen of WE19:

Select Radio Button of via message Type and specify the Message Types such as ORDERS05 or any Z* Message Types and press F8.

You will enter into another screen where IDOC with Segments will be dispalyed. Here you can fill teh data into respective segments.

Follow below steps:

Edit the Control Record Fields and Specify the Sender and Receiver Port,Partner No and Partner Type and finally Message Type.

Fill the segments with the data as per your requirement.

After filling the data, press on Standard outbound Processing for triggering IDOC. IDOC will be triggered and will reach XI.

Check the IDOC in SXI_MONITOR in XI System.

Thanks,

Kishore.

Edited by: Kishore on Mar 12, 2008 5:51 AM

Former Member
0 Kudos

Hello,

for testing purposes their exist transaction WE19 like described here:

/people/swaroopa.vishwanath/blog/2007/01/22/ale-configuration-for-pushing-idocs-from-sap-to-xi

https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/e07dcaa0-a92b-2a10-3a96-b3d942bd...

In a 'real life' scenario your IDoc will be created by a program (already existing or written by yourself) or by change pointers.

> Also it is difficult to know which IDOCs exist and can be used or when you have to create your own one

It depends from your scenario. For most standard scenarios like sending an invoice their exists already an IDoc (in this case INVOIC). You first have to know which data you want to transfer and then you can look for example in WE60 and search for existing IDocs.

Regards

Patrick

Former Member
0 Kudos

Hi chris,

best is to create a IDOC type SYSTAT01 with transaction WE19.

Use the button "outgoing". After that check WE02. See status for errors

This is a good way for the understanding.

Regards Mario