IDOC settings

[Former Member]

Hi All,

I need to configure a file-IDOC scenario. Can you pls explain me the settings that must be done in XI server(IDX1 & IDX2).

Thanks & Regards,

Jai Shankar.

[Former Member]

Hi Jai,

<b>IDX1</b> is used for Maintaining Ports.

You use the port maintenance in the IDoc adapter to establish an RFC connection to the system that contains the metadata that the IDoc adapter requires to convert IDocs (Intermediate Documents) that have been sent to it to IDoc XML format. This system is defined by the sender port and the client in the IDoc control record. It is either the sender SAP system or an SAP reference system.

The metadata comprises the IDoc structures for the corresponding IDoc types. Using this port you can call this data either directly at runtime or you can load it to the Integration Server (the system with the IDoc adapter) beforehand.

You must maintain a port in the IDoc adapter for all clients in each SAP system that you want to connect to the Integration Server using IDocs.

To create a port, do the following steps:

1.In transaction Port Maintenance in IDoc Adapter (IDX1).

On the left-hand side the system displays a list of ports that are already defined, for example SAPABC_123, and a description.

2.Choose Create a new RFC connection) for the selected system.

The system converts the display area on the right-hand side of the screen into an input area where you can enter the specifications for the new port.

The specifications for Port and Client correspond to the sender port and the client in the IDoc control record.

3.Enter the required data for the new port and save the data.

The system creates the new entry and places it alphabetically in the list of already defined ports. The system displays a corresponding message.

<b>IDX2</b> is used for loading IDOC metadata.

IDoc (Intermediate Document) metadata comprises structures for the corresponding IDoc types that are required by the IDoc adapter to convert these IDocs to IDoc XML format and the other way around.

Using an RFC connection, metadata of this type can be either called directly at runtime or loaded to the Integration Server beforehand.

The system containing the metadata is either the sender or receiver SAP system or, if the sender or receiver system is a subsystem, the SAP reference system where the metadata is saved.

You can display metadata that has already been loaded, or if you are upgrading the application system then you can delete the metadata and reload it.

This step (loading IDOC metadata in IDX2) is optional. When you start to send/receive your first IDOCS then XI will automatically load the metadata from the system.

In outbound scenarios like Idoc to file, it is automatically happening. But for file to Idoc, in many a times I have got "Meta Data doesnot exists error" in the monitor.When i got this error, i went to IDX2 transaction and loaded the metadata.This solved my problem.

Steps to be followed are:

1.To find out what metadata has already been loaded, call the transaction Metadata Overview for IDoc Adapter (IDX2).

The system displays a screen with the directory of all systems connected with the IDoc adapter (including a description) for which metadata has already been loaded. Choose Port Maintenance in IDoc Adapter to call the corresponding transaction and to create additional ports.

2.Expand the individual systems to display the IDoc types and clients including a description for each system. The system displays the metadata for each connected system for which metadata has already been loaded.

3.To apply the metadata structure loaded from a particular system to another system (for example, to an SAP reference system), select the link to the corresponding IDoc type and choose Copy.

The system displays a dialog box in which you can copy the IDoc type description to another system (Target Port).

4.To delete metadata that has already been loaded, select the link to the corresponding IDoc type and choose Delete.

The system asks you if you really want to delete the selected structure.

5.To delete the metadata structure, choose Yes.

6.To load additional metadata, choose Create.

The system displays a dialog box where you can enter the IDoc Type including Extension and the system (Source Port).

7.Make the required entries and choose Continue.

The new structure is inserted in the tree structure as follows:

- If the structure originates from a system from which metadata has already been loaded, it is inserted below the structures already loaded from this system.

- If the structure originates from a system from which no metadata has already been loaded, it is inserted together with the system below the already listed systems.

8.To display details about a metadata structure that has already been loaded, choose the link to the corresponding IDoc type. To display this structure in detail, choose Display. The system displays the structure in a hierarchy tree.

Regards,

Abhy

[Former Member]

Hi Jai,

Look at this also..

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

Will be useful

cheers,

Prashanth

P.S Please mark helpful answers

[Former Member]

Hi ,

For SAP XI you need to do following settings:

1. Create RFC destination in SAP XI pointing to SAP R/3 application system.

2. Create a port and add the RFC destination create in first step.

3. Import the IDoc that you want to use for the Interface in IDX2 (this step is not mandatory)

4. Create LS for the SAP XI system

Regards

Vijaya

[bhavesh_kantilal]

Jai,

This document is for IDOC to IDOC. Just use the part that is applicable to your scenario,

https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/cdded790-0201-0010-6db8-beb...

Regards,

Bhavesh

[former_member91687]

Hi Jai,

<b>IDX1 is for port maintenance for IDOC adapter</b>, for steps on how to create ports the steps given here will help:

http://help.sap.com/saphelp_nw04/helpdata/en/3b/beb13b00ae793be10000000a11402f/frameset.htm

<b>IDX2 gives info about the meta data</b>. for more on it:

http://help.sap.com/saphelp_nw04/helpdata/en/8a/b8b13bb3ace769e10000000a11402f/frameset.htm

Regards,

Chandra

[Former Member]

These are steps to follow:

STEPS IN DESIGN

1. Import idoc from the SAP System (SAP02) through imported objects.

2. Create Data Type, Message Type, Message Interface for the Outbound File.

3. Create Message Mapping with file Message and idoc (Matmas04)

5.Create Interface mapping between File Interface and the idoc.

Steps to be followed in Creation of Technical and Business System

Technical System

In SLD, click on technical landscape->New Technical System->WebAS ABAP.

Business System.

1.Goto Business Landscape->New Business System->Name the business system.

2. Choose the technical system that needs to be attached->WebAS ABAP->Technical System Name.

Preconfiguration steps for transfer of data to IDOCS

1.Create a RFC Destination in SM59 of XI Server of type.

2.In transaction IDX1 ,create a port for the client of XI server.

3. The port has to be displayed in the idx2 transaction and we should be able to view the idoc’s which we imported through integration repository.

Steps in Configuration

1. Goto service without party, right click->Assign a business system.

2. Choose the business system to be added.

3. Create a File Sender Service with communication channel for the same.

4. Create an idoc receiver channel under the business system. Mention the RFC Destination and the port created for the same.

5. Mention the logical Name in the Service->Adapter Specific Parameters of both the File Sender Service as well as the business system.

6. Make the Sender Agreement for theFile Sender with communication channel.

7.Create the Receiver Determination and Interface Determination for the business system.

8.Create the Receiver Agreement for the Business system.

TCODES for File>XI>IDoc

SM59-rfc destination on recving side

IDX1-port on recving side

IDX2-load metadata

Bus. service adapter specific Identifiers-->Logical sys name (check this blog:/people/michal.krawczyk2/blog/2005/03/29/xi-error--unable-to-convert-the-sender-service-to-an-ale-logical-system )

we05-IDoc status records

BD54-Create Partner Number

We20-Create Partner Profile

and also go thru this blog on

File to IDOC

and also these links:

https://websmp201.sap-ag.de/nw-howtoguides

http://help.sap.com/saphelp_nw04/helpdata/en/6a/e6194119d8f323e10000000a155106/frameset.htm

In R/3 Side, Partner profiles should be created.

Have a look into this document for the same...

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

And also since the Blog on File to Idoc looks quite complecated... I thought of giving you more info...

You can take a look at this document.

https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/cdded790-0201-0010-6db8-beb...

It is IDOC to IDOC.All you will have to do is ignore the first half of it.

Also, create an XSD of your IDOC , import it as an external definition and use it as the data type for the file.

Apart from that other details like SLD , R3 config etc you can look into the document and the info i have given.