Unable to import IDoc into IR

[Former Member]

Hi - For no reason i can't import the IDoc into XI.

The problem seems to be that in backend system is a problem. The basis-type and the segments are all released - to me because i released and de-released them. The Idoc was developed in client 010 and i want to import ist from 011 - of course there was some kind of transport!

In WE20 of backend system i am not able to pick this IDoc for Incoming parameter, no idea why.

In XI i am able to import MetaData via IDX2 but i am still not able to import the IDoc!!

can somebody help?! br Jens

[MichalKrawczyk · Accepted solution]

Hi Jens,

>>>>In WE20 of backend system i am not able to pick this IDoc for Incoming parameter, no idea why.

can you see this new IDOC in WE60 ?

and We30/We31 all segments ?

if not then maye the transport was not successful

Regards,

michal

[Former Member · Accepted solution]

Hi Michael!

Ok, WE60 says its not released. But in WE30 and WE31 everything looks fine!

What to do?!

[Former Member · Accepted solution]

Hi,

1 Scenario

This guide deals with all the configurations required to create an IDoc adapter in Exchange Infrastructure

3.0 to send an IDoc from XI to the SAP backend system.

Unlike other types of adapters, the IDoc adapter has dependencies on the XI 3.0 ABAP configurations and

the backend SAP system configurations. Those configurations information will have to be either created

first or retrieved in order to complete the IDoc adapter configuration.

2 Introduction

Configuring IDoc adapter in Exchange Infrastructure 3.0 requires some configuration on the SAP

systems, for both XI and the backend system where the IDoc message is to be sent. These steps, although

simple, are many times missed or mis-configured, causing the delivery of messages to fail.

Since IDoc adapter uses the ABAP stack, instead of J2EE, the configuration requirements are mainly in

ABAP.

Setting up IDoc adapters requires the XI integration server to be able to communicate with the backend

SAP system, and also to make sure that the Logical System Name used when posting IDoc exists on the

backend SAP system.

3 The Step By Step Solution

The basic steps for the IDoc configuration are outline below:

1. Configure SM59 on XI to communicate to SAP backend system.

2. Configure port on XI for IDoc communication.

3. Create or verify the Logical System Name on the SAP backend system.

4. Create or verify business system in XI’s System Landscape Directory.

5. Verify the Logical System Name of the business system.

6. Verify or add the Logical System Name for the sender business system.

7. Create/configure the Communication Channel for the IDoc receiver adapter

3.1 Configure SM59 on XI to communicate to SAP backend system.

1. Using transaction SM59, create an RFC destination with Connection Type = “3”.

In this example, the RFC destination name is “NDVCLNT510”.

2. Enter the logon information:

3. Test the connection by clicking on “Testing connection” and “Remote logon”.

Both must be successful.

3.2 Configure port on XI for IDoc communication.

4. Go to transaction IDX1 on XI, and create a port. In this example, the Port name is “SAPNDV”.

• The Port name must be in the form of “SAPxxx”, where xxx is the system ID of the backend SAP

system.

• The Client must be the client number of the backend SAP system.

• Select the RFC Destination which was created in the previous step.

3.3 Create or verify the Logical System Name on the SAP backend system.

5. Enter transaction SALE on the SAP backend system.

6. Create or verify the Logical System Name. In our example, NDVCLNT510 is verified.

3.4 Create or verify business system in XI’s System Landscape Directory.

The business system name for the SAP backend system must contain a valid Logical System Name. This Logical System Name is the one verified or created in the previous step.

7. In the System Landscape Directory, select the SAP backend business system. If one does not exist, then create the business system. Verify the Logical System Name.

3.5 Verify the Logical System Name of the business system.

8. In the Integration Directory, doubleclick on the business system (in our example, it is NDVCLNT510).

Navigate the menu:

Service • Adapter Specific Identifiers.

If information is empty or incorrect, then it will have to be synchronized with the content of the System Landscape Directory. Follow the steps below for synchronization.

9. (Optional) Synchronization of the business system in Integration Directory to the business system in System

Landscape Directory.

• Double-click on the business system in the Integration Directory.

• Switch to Edit mode.

• Select menu: Service • Adapter-Specific Identifiers

10. (Optional) Within the dialog box, click on the button as indicated below to resynchronize.

11. (Optional) If the expected data from the System Landscape Directory is not updated, then the SLD cache may need to be cleared first.

3.7 Create/configure the Communication Channel for the IDoc receiver adapter.

15. In the Integration Directory, create an IDoc receiver communication channel.

• The RFC Destination is from step 3.1.

• The Port is from step 3.2.

NOTE:

There is no need to create an IDoc sender Communication Channel for XI. Instead, the backend SAP system must be configure to send the IDoc to XI.

4 Appendix

Transaction: IDX2

There are a couple of situation where IDX2 can be useful on the XI system.

1. When we want to test connection between the XI and SAP backend system.

2. When an IDoc has changed, and the meta data stored in XI needs to be update. When an IDoc is sent from the SAP backend system to XI, XI will first check to see if the meta data for the IDoc is already in its persistent cache. If not, then XI will use the configuration in IDX1 to retrieve the IDoc meta data from the backend system. If the

meta is already in cache, then it will NOT do so. Therefore, when an IDoc has changed, it is necessary to manually update the new meta data on XI, or delete it from the cache, so that the latest version can be retrieved. IDX2 is used for this purpose.

Go to transaction IDX2 and click on “Create”.

Enter the IDoc Type and the Source Port as defined in step #2. Click “Continue”.If successful, the following will show up. If error occurs, then the IDX1 configurations will need to be re-checked.

Regards

Hemant

Award point if find helpful

[udo_martens · Accepted solution]

oh, no, my nightmare...

[Former Member]

got it, please also use TX WE81 & WE82!

[udo_martens]

Hi Jens,

you can import it from 010 as well, result would be the same.

Regards,

Udo

[Former Member]

Hi Udo, i already did this but without a success because the IDoc isn't there either!

[Former Member]

Hi Guys,

still i have the problem that i am not able to import the necessary IDoc.

I already de-released and released it again, did a new metadata.load via IDX2, Cache-Refresh for no reason but nothing changed!!!

Please help!

br Jens