IDOC Configure

8/2/2019 IDOC Configure

1/14

How-to Guide

SAP NetWeaver 04

How ToConfigure theIDoc Adapter

Version 1.00 March 2005

Applicable Releases:SAP NetWeaver 04

XI 3.0 SR1 and above


2/14

Copyright 2005 SAP AG. All rights reserved.

No part of this publication may be reproduced ortransmitted in any form or for any purpose without the

express permission of SAP AG. The information

contained herein may be changed without prior notice.

Some software products marketed by SAP AG and its

distributors contain proprietary software components of

other software vendors.

Microsoft, Windows, Outlook,and PowerPoint

are

registered trademarks of Microsoft Corporation.

IBM, DB2, DB2 Universal Database, OS/2, Parallel

Sysplex, MVS/ESA, AIX, S/390, AS/400, OS/390, OS/400,

iSeries, pSeries, xSeries, zSeries, z/OS, AFP, Intelligent

Miner, WebSphere, Netfinity, Tivoli, and Informix are

trademarks or registered trademarks of IBM Corporation

in the United States and/or other countries.

Oracle is a registered trademark of Oracle Corporation.

UNIX, X/Open, OSF/1, and Motif are registered

trademarks of the Open Group.

Citrix, ICA, Program Neighborhood, MetaFrame,

WinFrame, VideoFrame, and MultiWinare trademarks

or registered trademarks of Citrix Systems, Inc.

HTML, XML, XHTML and W3C are trademarks or

registered trademarks of W3C, World Wide Web

Consortium, Massachusetts Institute of Technology.

Java is a registered trademark of Sun Microsystems, Inc.

JavaScript is a registered trademark of Sun Microsystems,Inc., used under license for technology invented and

implemented by Netscape.

MaxDB is a trademark of MySQL AB, Sweden.

SAP, R/3, mySAP, mySAP.com, xApps, xApp, SAP

NetWeaver, and other SAP products and services

mentioned herein as well as their respective logos aretrademarks or registered trademarks of SAP AG in

Germany and in several other countries all over the

world. All other product and service names mentioned

are the trademarks of their respective companies. Data

contained in this document serves informational

purposes only. National product specifications may vary.

These materials are subject to change without notice.

These materials are provided by SAP AG and its affiliated

companies ("SAP Group") for informational purposes

only, without representation or warranty of anykind, and SAP Group shall not be liable for errors or

omissions with respect to the materials. The only

warranties for SAP Group products and services are those

that are set forth in the express warranty statements

accompanying such products and services, if any.

Nothing herein should be construed as constituting an

additional warranty.

These materials are provided as is without a warranty

of any kind, either express or implied, including but not

limited to, the implied warranties of merchantability,

fitness for a particular purpose, or non-infringement.

SAP shall not be liable for damages of any kind including

without limitation direct, special, indirect, or

consequential damages that may result from the use of

these materials.

SAP does not warrant the accuracy or completeness of

the information, text, graphics, links or other items

contained within these materials. SAP has no control

over the information that you may access through the

use of hot links contained in these materials and does not

endorse your use of third party web pages nor provide

any warranty whatsoever relating to third party webpages.

SAP NetWeaver How-to Guides are intended to

simplify the product implementation. While specific

product features and procedures typically are explained

in a practical business context, it is not implied that those

features and procedures are the only approach in solving

a specific business problem using SAP NetWeaver. Should

you wish to receive additional information, clarification

or support, please refer to SAP Consulting.


3/14

1 Scenario............................................................................................................1

2 Introduction....................................................................................................1

3 The Step By Step Solution ......................................................................23.1 Use transaction SM59 on the Integration Server to establish communication

with the SAP backend system....................................................................................2

3.2 On the Integration Server, configure the port for IDoc communication........33.3 Create or verify the logical system name on the SAP backend system. ........4

3.4 Create or verify the business system in the SLD. ..........................................4

3.5 Verify the logical system name of the business system.................................5

3.6 Verify or add the logical system name for the sender business system.........6

3.7 Create/configure the communication channel for the receiver IDoc adapter.8

4 Appendix...........................................................................................................84.1 Transaction IDX2...........................................................................................8

4.2 Acknowledgments should not be requested...................................................9

4.3 Configuring IDocs for user management.....................................................10


4/14

- 1 -

1 ScenarioThis guide describes how to configure an IDoc adapter in SAP Exchange Infrastructure 3.0 (XI 3.0) to send

an IDoc from the Integration Server to an SAP backend system.

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

system configurations. To complete the IDoc adapter configuration, these configurations have to be

made first, or information on these configurations has to be retrieved.

2 IntroductionConfiguring an IDoc adapter in XI 3.0 requires some configuration steps on both the Integration Server

and the SAP backend system where the IDoc message is to be sent. These steps are often forgotten or

performed incorrectly, thereby causing the delivery of messages to fail.

Since the IDoc adapter uses the ABAP stack, the configuration requirements are mainly in ABAP.

To set up an IDoc adapter, the Integration Server must be able to communicate with the SAP backend

system, and the logical system name used when posting IDocs must exist in the latter.


5/14

- 2 -

3 The Step By Step SolutionThe basic steps for the IDoc configuration are outlined below:

1. On the Integration Server, call transaction SM59 to establishcommunication with the SAP backend system.

2. On the Integration Server, configure the port for IDoc communication.3. On the SAP backend system, create or verify the logical system name.4. In the SAP System Landscape Directory (SLD), create or verify the

business system.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 Use transaction SM59 on the Integration Server to establishcommunication with the SAP backend system.

1. Using transaction SM59, create an RFC

destination of connection type 3.

In this example, the RFC destination

name is CU6CLNT800.


6/14

- 3 -

2. Enter the logon information:

The logon language must be the same as

the language of the payload content, forexample, for Japanese payload the

language must be JA. Otherwise, the

content will be corrupted in the target

system.

3. Test the connection by choosing Test

connectionand Remote logon. Both

tests must be successful.

If the user in the target system is a

background user or does not havesufficient authorization no logon screen

will be displayed.

3.2 On the Integration Server, configure the port for IDoccommunication.

1. Call transaction IDX1 to create a port. In

this example, the Portname is SAPCU6.The Portname must have the format

SAPxxx, where xxxis the system ID ofthe SAP backend system.

The Clientmust be the client number of

the SAP backend system.

Select the RFC Destinationthat was

created in the previous step.

IDoc metadata is client-independent.

Therefore, only the smallest client is

used.


7/14

- 4 -

The fields Partner No. and Partn. Type

are not used; leave them empty.

3.3 Create or verify the logical system name on the SAP backendsystem.

1. Either call transaction SALE on the SAP

backend system and choose Define

Logical System or call transaction BD54

directly without going through the

Implementation Guide (IMG).

2. Create or verify the logical system name.

In our example, the name CU6CLNT800

is verified.

3.4 Create or verify the business system in the SLD.The business system name for the SAP backend system must contain a validLogical System Name. This Logical System Name is the one that was verified

or created in the previous step.


8/14

- 5 -

1. In the SLD, select the SAP backend

business system, or create one if none

exist. Verify the Logical System Name.

3.5 Verify the logical system name of the business system.

1. In the Integration Directory, choose the

business system CU6CLNT800, for

example.

In the menu, choose Service Adapter-

Specific Identifiers.

If the information is empty or incorrect,

you have to synchronize it with the

content of the SLD. Follow the steps

below for synchronization.


9/14

- 6 -

2. (Optional): Synchronization of the

business system in the Integration

Directory with the business system in the

SLD.

Choose the business system in theIntegration Directory.

Switch to Editmode.

In the menu, choose Service Adapter-

Specific Identifiers.

3. (Optional): In the dialog box, choose

Compare with System LandscapeDirectoryto re-synchronize.

4. (Optional): If the data expected from the

SLD is not updated, the SLD cache may

need to be cleared first.

3.6 Verify or add the logical system name for the sender businesssystem.If the sender system is a third-party business system, repeat steps 3.4 and 3.5for the sender system. The sender business system must have a logical systemname. Otherwise, the IDoc cannot be delivered.

If the sender business system already exists, but does not have a logical systemname, the name can be added using the SLD.


10/14

- 7 -

1. In the SLD, navigate to the business

system and choose Change.

2. Enter the Logical System Nameand

choose Save.

3. Re-synchronize the Integration

Directory by following the

synchronization instructions in section

3.5.

(intentionally left blank)


11/14

- 8 -

3.7 Create/configure the communication channel for the receiver IDocadapter.

1. In the Integration Directory, create an

IDoc receiver communication channel.

The RFC Destinationis the one from

section 3.1.

The Portis the one from section 3.2.

The Segment Versionis either empty or

smaller than the SAP Release.

If you want to use IDoc parties as senders

or receivers with a party type other than

LS, select the check box Apply Control

Record Values from Payload.

NOTE:There is no need to create a communication channel for the IDoc sender. Instead, theSAP backend system must be configured to send the IDoc to the Integration Server.

4 Appendix4.1 Transaction IDX2

There are a couple of situations where transaction IDX2 can be useful on the IntegrationServer.

1. When you want to test the connection between the Integration Server andthe SAP backend system.

2. When an IDoc has changed and the metadata stored on the IntegrationServer needs to be updated.

When an IDoc is sent from the SAP backend system to the Integration Server, thesystem first checks whether the metadata for this IDoc is already in its persistent cache.If not, it uses the configuration made with transaction IDX1 to retrieve the IDoc metadatafrom the backend system. If the metadata is already in the cache, it will NOT be retrievedfrom the backend system. Therefore, when an IDoc has been changed, it is important

that you manually update the metadata on the Integration Server or delete it from thecache, so that the latest version can be retrieved. IDX2 is used for this purpose.


12/14

- 9 -

1. Call transaction IDX2 and choose

Create.

Enter the IDoc Typeand the Source

Portas defined in section 3.2.

Choose Continue.

2. If successful, a corresponding dialogbox appears. If an error occurs, the

IDX1 configurations need to be re-

checked.

3. Verify that the IDoc type is present.

4.2 Acknowledgments should not be requested

If the Integration Server receives an IDoc, it creates a message and requests anacknowledgment for delivery and application processing. This feature can be switchedoff with the report IDX_NOALE. The acknowledgment request can be switched off forevery system/client and message type.


13/14

- 10 -

4.3 Configuring IDocs for user management

If you are using user management, IDocs sent to the Integration Server should not beprocessed by the IDoc adapter. Insert the relevant IDoc types into the corresponding

exception table.

1. Execute report

IDX_SELECT_IDOCTYP_WITHOUT_IS

to insert all the IDoc types meant for

ALE processing.


14/14

www.sap.com/netweaver

IDOC Configure

Documents

Transcript of IDOC Configure