Solved: IDoc to XI u0096 Outbound IDoc

hi Experts,

Please let me know how to post IDOC to XI in R/3 Sender System?

Please help

Sourabh

SAP Managed Tags:
SAP Process Integration

You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.

Comment

Accepted Solutions (1)

Identify Message type and Basic type to be used for posting the IDoc . Create RFC Destination (SM59) to Receiver XI system .Create PORT for IDoc processing (WE21) and assign the RFC Destination created above to this PORT . Create Logical System (LS) for the IDoc (BD54) to be sent to the XI receiver system Create Partner Profile with outbound parameter (WE20) to be send to the XI receiver system.

Create Partner Profile with outbound parameter (WE20) to be send to the XI receiver system.

Hope this will help you.

You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.

Comment

Answers (8)

Create Inbound Function Module – Transaction SE37

In the receiving system, create a function module Z_IDOC_INPUT_ZRZSO_MT using SE37. Below, I have described the logic for the same:

Add Include MBDCONWF. This include contains predefined ALE constants

Loop at EDIDC table

Check if the message type is ZRZORDER. Otherwise raise WRONG_FUNCTION_CALLED exception

Loop at EDIDD table

Append data from the segments to appropriate internal tables

For example: append data from ZRZSEG1 segment to the internal table of type ZCUSTOMERS

Update the DDic tables from internal tables

Depending on the result of the update, fill the IDoc status record (type BDIDOCSTAT) and append it to the corresponding table.

Status 53 => Success

Status 51 => Error

You can download the sample ABAP code for the above function module here.

Assign Function Module to Logical message – Transaction WE57

Create a new entry

Specify name of the Function Module as Z_IDOC_INPUT_ZRZSO_MT

Also, specify Type as F, Basic IDoc type as ZRZORDER, Message type as ZRZSO_MT and Direction as 2 (Inbound)

Save the entry

Define Input method for Inbound Function Module – Transaction BD51

Create a new entry

Provide Function Module name as Z_IDOC_INPUT_ZRZSO_MT

Specify the Input method as 2

Save the entry

Create a Process code – Transaction WE42

Create a new Process Code ZPCRZ

Select Processing with ALE Service

Choose Processing type as Processing by function module

Save the entry

On the next screen, select your function module from the list

Save the changes

On the next screen, select your function module from the list

Save the changes

Define Logical system for the partner - Transaction SALE or BD54

Define a Logical system LOGSYS100 using transaction SALE or BD54 to identify the partner business system

Regards

Abhishek

You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.

Comment

Dear sourabh

In R3, go to the transaction Sm58. This is the transctional RFC log and will contain entires if there was any error while sending the IDOC to your XI system.

Next, in XI, go to SXMB_MONI and monitor for processed messages. This will display all the messages processed by XI.

Also, if no business system is assigned to the R3 system in XI, then I think the IDOC would not have reached XI and you would be able to see this error in SM58.

Plz go thru this link....It will be of some help

http://www.riyaz.net/blog/index.php/2008/01/25/xipi-settings-in-r3-partner-system-to-receive-idocs/

Regards

Azahar

You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.

Comment

we have standard report program to process all selected iodc's i.e RSEOUT00 ,to process inbound idoc's we have RSEINB00,both programs you can schedule in back ground accoring to Business requirement,or we can use WE19 t.code to test idoc.

Identify Message type and Basic type to be used for posting the IDoc . Create RFC Destination (SM59) to Receiver XI system

.Create PORT for IDoc processing (WE21) and assign the RFC Destination created above to this PORT . Create Logical System

(LS) for the IDoc (BD54) to be sent to the XI receiver system Create Partner Profile with outbound parameter (WE20) to be

send to the XI receiver system.

Create Partner Profile with outbound parameter (WE20) to be send to the XI receiver system.

IDoc Adapter converts the incoming IDoc to XML and XML messages to outgoing IDoc. The IDoc adapter resides on the ABAP

stack of the integration server and hence no Sender Agreement is necessary in order to setup the sender adapter. A point

to note is that using IDoc adapters, we can only have asynchronous (tRFC) processing. Apart from using Runtime Workbench

and transaction SXMB_MONI, IDoc messages can be monitored using transaction IDX5.

On the XI system, create a RFC destination of type R/3 connection, pointing to the source SAP Application system. Also, create a port for the source system using transaction IDX1. Mention the above created RFC destination in the IDX1 port configuration. This is required as XI uses this configuration to read the IDoc metadata from the source system. Once you have done this, your XI system is ready to receive IDocs from the source SAP system.

The metadata for an IDoc is loaded in the Integration Server when the first message for the particular IDoc is processed by the Integration Engine. You can see the IDoc metadata using the transaction IDX2. If you dont see the metadata for your IDoc in transaction IDX2, you can manually load it using the Menu options in IDX2. You need to specify the port and the IDoc type before you can import the IDoc metadata

You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.

Comment

Hi Nirmal,

we have standard report program to process all selected iodc's i.e RSEOUT00

to process inbound idoc's we have RSEINB00.

both programs you can schedule in back ground accoring to Business requirement.

or we can use WE19 t.code to test idoc.

regards

mahesh.

You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.

Comment

Hi,

WE19 is the testing tool for the INBOUND and OUTBOUND Idocs,it will not post the data into XI.

What type of idoc ur using,To post the data into XI u have to trigger the IDOC in the transaction.

Suppoce u have to post the production order details then u have to go to CO02 TC code there u have to give the production order details and release the IDOC .

Before release the IDOC make sure u have done the ALE settings then the Data will be posted into XI.

Chech the ALE settings.

IDOC

http://msdn2.microsoft.com/en-us/library/ms942196.aspx

Idoc configuration Required~

in R/3

1) RFC destination pointing to XI

2) WE20 Partner Profile entries

in XI

1) RFC destination pointing to R/3

Go thru this -

Go thru these for Idoc to XI scenarios-

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

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

These will be the Configurations needed in your R3,

1. SM 59 - Create an RFC destination for your XI .

2. We21 -- Create a port for XI

3. We 20 -- Create a partner profile entry for the Outbound IDOCs for XI.

Configuration on XI

1. IDX2 - Import IDOC metadata.

For eg : Lets assume the R/3 system and Xi system are QZA and X7A.

In XI :

Step 1 : In SALE Tcode :

a)Create Logical systems for R/3 and XI.

EG : (QZACLNT100) and (X7ACLNT100).

b) Assign the logical system of XI to Client.(X7ACLNT100)

Both the above options u can find in SALE transaction under SENDING and RECEIVING SYSTEMS tab

Step 2 : In SM59 create RFC destination in XI pointing to R/3(i.e IP address of R/3) (This RFC Destination name shd be same as the Sender LS name)=> QZACLNT100 is my RFC destination.

Step 3: Create the PORT in XI for the Sender system and assign the RFC destination.

In R/3 :

Step 1:

In SALE Tcode :

a) Create Logical systems for R/3 and XI for

b) Assign the logical system of R/3 to Client.(QZACLNT100)

Step 2 : In SM59 create RFC destination in R/3 pointing to XI(i.e IP address of XI) (This RFC Destination name shd be same as the Receiver LS name)=> X7ACLNT100 is my RFC destination.

Step 3: In SALE Tcode under Modelling and Implementing Bussiness Processes-> maintain Disribution Model and Distribute Views.

a)Click on that ,it shall take to Tcode BD64 ,where u can create a Distribution Model.

b)Once you create that ADD MESSAGE type(You have the button at the top), there it shall ask for Receiver and Sender LS and Message type.

c)In Menu Bar EDIT->Generate Partner Profile.

Click on that and press Execute .

This shall create 2 partner profile X7ACLNT100 and QZACLNT100 ,X7ACLNT100(this is the partner number for QZA system) shall have the outbound parameter as CREMAS, and QZACLNT100 is created with no parameters ,you need not worry .

d) Click EDIT->MODEL VIEW->Distribute.

This shall distribute the model and you can see the distribution mode aslo getting created in XI system.

This configuration shall surely help u out as it worked out for me.

Configurations required for IDocs in R/3

In your XI system, you need to do the following.

1. Create a RFC destination to your R/3 system

2. Create a port in IDX1 of your XI system and use the RFC destination in step1.

3. Try importing a idoc metadata thru idx2 transaction to check whether the configuration is correct.

4. In your SLD configure the technical system and business system. The technical system should hold the logical system name you have in your R/3 system client.

5. Import the business system and you can use it in your configuration scenario.

Please also refer below links for details.

Go thru this-

https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/877c0d53-0801-0010-3bb0-e38...

Regards,

Phani