Idocs configuration

(1)

Applies to:

This document applies to SAP version ECC 6.0. This document applies to SAP version ECC 6.0.

Summary

This document explains about inbound

This document explains about inbound and outbound Idoc configuration with simple and outbound Idoc configuration with simple steps.steps. Author(s):

Author(s): Renuka SrinivasanRenuka Srinivasan Company:

Company: Applexus Technologies (P) LtdApplexus Technologies (P) Ltd Created on:

Created on: 15 January 201115 January 2011

Author Bio

Renuka Srinivasan Is working as SAP Technology Consultant with Applexus Technologies Renuka Srinivasan Is working as SAP Technology Consultant with Applexus Technologies (P) Ltd. Completed Bachelor of Engineering in Sri Shakthi Institute of

(P) Ltd. Completed Bachelor of Engineering in Sri Shakthi Institute of Engineering andEngineering and Technology.

(2)

T

able of

1. What is Idoc?

IDocs are struct

IDocs are structured ASCII filured ASCII files (or a virtual equies (or a virtual equivalent). They are tvalent). They are the file format he file format used by SAP R/used by SAP R/3 to 3 to ex- ex-change data with foreign systems.

(3)

IDocs is the acronym for

IDocs is the acronym for Interchange Document. This indicates a set Interchange Document. This indicates a set of (electronic) information whichof (electronic) information which builds a logical entity. An IDoc is e.g. all the data of a

builds a logical entity. An IDoc is e.g. all the data of a single customer in your customer master data file,single customer in your customer master data file, or the IDoc is all the data of a

or the IDoc is all the data of a single invoice.single invoice.

The information which is exchanged by IDocs is called a message and the IDoc is

The information which is exchanged by IDocs is called a message and the IDoc is the physical represen-the physical represen-tation of such a message. The name “messages” for the information sent via IDocs is used

tation of such a message. The name “messages” for the information sent via IDocs is used in the samein the same ways as other EDI standards.

ways as other EDI standards.

2. Why Idoc Configuration?

To exchange IDoc data between systems and partners that are completely independent or between To exchange IDoc data between systems and partners that are completely independent or between same systems we need to configure.

same systems we need to configure.

3. Steps in Idoc Configuration

Consider we have to exchange data between two di

Consider we have to exchange data between two different clients. fferent clients. Following are the configuraFollowing are the configuration stepstion steps common for Interchange Documents in both

common for Interchange Documents in both the clients.the clients. 3.1. Create segment

3.1. Create segment

a.

a. Go to transGo to transactioaction WE31 -> Givn WE31 -> Give your segme your segment name -> Prent name -> Press Createss Create.e.

b.

b. Type your fiType your field name and eld name and data element adata element and press save nd press save then segment defithen segment definition winition will be createdll be created automatically.

automatically.

3.2 Create Idoc

3.2 Create Idoc TypeType

Go to Transaction WE30 Go to Transaction WE30 a.

(4)

b.

b. Then selThen select the IDOect the IDOC option to crC option to create and preeate and press Entess Enter. Give segr. Give segment namment name, minie, minimum andmum and maximum number for and save it. Check if this is mandatory segment.

maximum number for and save it. Check if this is mandatory segment.

c.

c. If you wIf you want Heaant Header and der and Item cItem creatreate the sege the segment trment tree accoee according rding to thatto that, you ca, you can view n view as folas followslows then press Save.

then press Save.

d.

d. Then go back anThen go back and set relead set release the IDOse the IDOC type for usiC type for using it furtng it further. Idher. Idoc type wiloc type will be createdl be created successfully once we release that status. We have to release the segments (in W

successfully once we release that status. We have to release the segments (in W E31) and IDOCE31) and IDOC type as well.

(5)

3.3

3.3 Create Create Message Message TypeType

Go to transaction WE81 for new message type. Go to change mode a

Go to transaction WE81 for new message type. Go to change mode a nd click New Entries for nd click New Entries for creating our own message type.

creating our own message type.

3.4

3.4 Associate Associate Message TyMessage Type with pe with Basic IdBasic Idoc Typoc Typee

Go to transaction W

Go to transaction W E82 for associating the message type with E82 for associating the message type with basic IDOC type.basic IDOC type.

3.5 Create Logical System

Go to transaction SPRO and press SAP Reference IMG for creating the logical system for source and Go to transaction SPRO and press SAP Reference IMG for creating the logical system for source and

(6)

destination. destination.

Click the node define

Click the node define logical system from SPRO -> SAP Reference IMG -> logical system from SPRO -> SAP Reference IMG -> SAP customizingSAP customizing Implementation Guide -> SAP xApp Resource and

Implementation Guide -> SAP xApp Resource and Portfolio Management (SAP xRPM) -> BasePortfolio Management (SAP xRPM) -> Base system Interfaces -> SAP Human Capital Management Integration ->

system Interfaces -> SAP Human Capital Management Integration -> Common system configurationCommon system configuration and SAP HCM ALE setup ->

and SAP HCM ALE setup -> Application link enabling (ALE) -> Basic Settings -> Logical Application link enabling (ALE) -> Basic Settings -> Logical Systems ->Systems -> Define Logical System

Define Logical System

Else go to transaction SALE then

Else go to transaction SALE then go to Basic settings-> logical system go to Basic settings-> logical system then Define logical system.then Define logical system. We can create the same.

We can create the same.

3.6 Create Logical Connection

a.

(7)

b. Then Click Connection test

b. Then Click Connection test icon after marking the current user checkbox iicon after marking the current user checkbox in logon and security tab.n logon and security tab.

c. Then Destination client will automatically open c. Then Destination client will automatically open

(8)

3.7 Create Ports

Go to transaction WE21 for

Go to transaction WE21 for creating ports. WE21 -> Transactional IR -> creating ports. WE21 -> Transactional IR -> CreateCreate

4. Steps to be done in Source client

1.Go to

1.Go to transaction SE11 -> create a table with entries.transaction SE11 -> create a table with entries. 2.Go to

2.Go to transaction WE31 -> create segments as shown before. Here you have to mention all thetransaction WE31 -> create segments as shown before. Here you have to mention all the fields mentioned in the database table.

fields mentioned in the database table. 3.Go to

3.Go to transaction WE30 -> create basic IDOC type and release the segments and basic type.transaction WE30 -> create basic IDOC type and release the segments and basic type. 4.Go to

4.Go to transaction WE81 -> create message type.transaction WE81 -> create message type. 5.Go to

5.Go to transaction WE82 -> assign message type to basic Idoc type.transaction WE82 -> assign message type to basic Idoc type. 6.Go to

6.Go to transaction BD64 -> Click on Display/change buttontransaction BD64 -> Click on Display/change button

7.

(9)

8.Specify description and technical name and press

8.Specify description and technical name and press continue.continue.

9.Select your model view -> click edit

9.Select your model view -> click edit -> Add message type-> Add message type

10. In dialog box specify sender, receiver, and message type and

10. In dialog box specify sender, receiver, and message type and continue. Now the model view locontinue. Now the model view look ok ss Like

Like

11. Click on environment menu -> generate partner profile 11. Click on environment menu -> generate partner profile

(10)

12. It will show the following screen. Select your model view and click on execute. 12. It will show the following screen. Select your model view and click on execute.

13. It will show the partner profile log in next screen. 13. It will show the partner profile log in next screen.

14. Click on back button 2 times it will take to distribution model screen. 14. Click on back button 2 times it will take to distribution model screen. 15. Click on Edit ->

15. Click on Edit -> Model view -> DistributeModel view -> Distribute

16. In displayed dialog box select the partner system and continue. 16. In displayed dialog box select the partner system and continue. 17. Then it will show the log of model view distribution.

17. Then it will show the log of model view distribution. 18. To check partner profile go to transaction WE20. 18. To check partner profile go to transaction WE20.

19. Then write the report program in SE38 to create IDOC control records and transfer it to destination 19. Then write the report program in SE38 to create IDOC control records and transfer it to destination partner system.

partner system.

20. Go to Transaction WE02 to check the generated IDOC control records. 20. Go to Transaction WE02 to check the generated IDOC control records.

5. Steps to be done in Destination client

1.

1. Go to trGo to transactansaction SEion SE37 to crea37 to create the funte the function mction module fodule for updator updating the ting the table frable from IDOom IDOCC segments.

segments. 2.

2. SpeSpecifcify impoy import, exrt, exporport and tabt and table parle parameameterters.s. 3.

3. Go to transGo to transactioaction WE57 for assn WE57 for assigninigning the FM to logig the FM to logical systcal system. Cliem. Click on Displck on Display/ changay/ change buttone button..

4. Specify FM name, function type, basic type(IDOC ), message type and direction then save it. 4. Specify FM name, function type, basic type(IDOC ), message type and direction then save it. 5. Go to transaction BD51 to define input method for inbound function module and click on

(11)

6. Specify your function module and input type by clicking the new entries. 6. Specify your function module and input type by clicking the new entries. 7. Go to transacti

7. Go to transaction WE42 and on WE42 and create process code.create process code.

8. Go to transaction BD64 and generate the partner profile again. 8. Go to transaction BD64 and generate the partner profile again.

9. Got o transaction SE 38 and execute the transaction in source system (client100). 9. Got o transaction SE 38 and execute the transaction in source system (client100).

10. Check in destination system (client 800). Go to Transaction WE02 and check your table in SE11. 10. Check in destination system (client 800). Go to Transaction WE02 and check your table in SE11. (You can get the transferred entries in that table).

(12)

Copyright

No part of this publication may be reproduced or transmitted in anpublication may be reproduced or transmitted in an y form or for any y form or for any purpose without the express permission of SAP AG.purpose without the express permission of SAP AG. The information contained herein may be

The information contained herein may be changed without prior notice.changed without prior notice. Some software products marketed by SAP AG and its

Some software products marketed by SAP AG and its distributors contain proprietary software components of other software vendors.distributors contain proprietary software components of other software vendors. Microsoft, Windows, Excel, Outlook, and PowerPoint are

Microsoft, Windows, Excel, Outlook, and PowerPoint are registered trademarks of Microsoft Corporation.registered trademarks of Microsoft Corporation.

IBM, DB2, DB2 Universal Database, System i, System i5, System p, System p5, System x, System z, System z10, System z9, z10, IBM, DB2, DB2 Universal Database, System i, System i5, System p, System p5, System x, System z, System z10, System z9, z10, z9,z9, iSeries, pSeries, xSeries, zSeries, eServer, z/VM, z/OS, i5/OS,

iSeries, pSeries, xSeries, zSeries, eServer, z/VM, z/OS, i5/OS, S/390, OS/390, OS/400, AS/400, S/390 Parallel S/390, OS/390, OS/400, AS/400, S/390 Parallel Enterprise Server,Enterprise Server, PowerVM, Power Architecture, POWER6+, POWER6, POWER5+, POWER5, POWER, Open Power, PowerPC, Batch

PowerVM, Power Architecture, POWER6+, POWER6, POWER5+, POWER5, POWER, Open Power, PowerPC, Batch Pipes, BladePipes, Blade Center, System Storage, GPFS, HACMP, RETAIN, DB2 Connect, RACF,

Center, System Storage, GPFS, HACMP, RETAIN, DB2 Connect, RACF, Redbooks, OS/2, Parallel Sysplex, MVS/ESA, AIX, IntelligentRedbooks, OS/2, Parallel Sysplex, MVS/ESA, AIX, Intelligent Miner, Web Sphere, Netfinity, Tivoli and Informix are

Miner, Web Sphere, Netfinity, Tivoli and Informix are trademarks or registered trademarks of IBM Corporation.trademarks or registered trademarks of IBM Corporation. Linux is the registered trademark of Linus

Linux is the registered trademark of Linus Torvalds in the U.S. and Torvalds in the U.S. and other countries.other countries. Adobe, the A

Adobe, the Adobe logo, Acrobat, dobe logo, Acrobat, PostScript, anPostScript, and Reader are either d Reader are either trademarks or regtrademarks or registered trademarks istered trademarks of Adobe Syof Adobe Systemsstems Incorporated in the United States and/or other countries.

Incorporated in the United States and/or other countries. Oracle is a registered trademark of

Oracle is a registered trademark of Oracle Corporation.Oracle Corporation.

UNIX, X/Open, OSF/1, and Motif are registered trademarks of the Open UNIX, X/Open, OSF/1, and Motif are registered trademarks of the Open Group.Group.

Citrix, ICA, Program Neighborhood, MetaFrame, Win Frame, Video Frame, and MultiWin are trademarks or

Citrix, ICA, Program Neighborhood, MetaFrame, Win Frame, Video Frame, and MultiWin are trademarks or registered trademarks of registered trademarks of Citrix Systems, Inc.

Citrix Systems, Inc.

HTML, XML, XHTML and W3C are

HTML, XML, XHTML and W3C are trademarks or registered trademarks of W3C®, World Wide Web Consortium, Massachusettstrademarks or registered trademarks of W3C®, World Wide Web Consortium, Massachusetts Institute of Technology.

Institute of Technology.

Java is a registered trademark of

Java is a registered trademark of Sun Microsystems, Inc.Sun Microsystems, Inc.

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

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

Netscape.

SAP, R/3, SAP Net Weaver, Duet, Partner Edge, By Design, SAP Business By

SAP, R/3, SAP Net Weaver, Duet, Partner Edge, By Design, SAP Business By Design, and other SAP products and services mentionedDesign, and other SAP products and services mentioned herein as well as

herein as well as their respective logos are trademarks or registered trademarks of SAP AG their respective logos are trademarks or registered trademarks of SAP AG in Germany and other in Germany and other countries.countries.

Business Objects and the Business Objects logo, Business Objects, Crystal Reports, Crystal Decisions, Web Intelligence, Xcelsius, and Business Objects and the Business Objects logo, Business Objects, Crystal Reports, Crystal Decisions, Web Intelligence, Xcelsius, and other Business Objects products and services mentioned herein as well

other Business Objects products and services mentioned herein as well as their respective logos are trademarks or as their respective logos are trademarks or registeredregistered trademarks of Business Objects S.A. in the United States and

trademarks of Business Objects S.A. in the United States and in other countries. Business Objects is an in other countries. Business Objects is an SAP company.SAP company. All other product

All other product and service names and service names mentioned are thmentioned are the trademarks of e trademarks of their respective their respective companies. Data ccompanies. Data contained in this documontained in this documentent serves informational purposes only. National

serves informational purposes only. National product specifications may vary.product specifications may vary. These materials are subject to change

These materials are subject to change without notice. These materials are provided by SAP without notice. These materials are provided by SAP AG and its affiliated companies ("SAPAG and its affiliated companies ("SAP Group") for informational purposes only, without representation or warranty of any

Group") for informational purposes only, without representation or warranty of any kind, and SAP Group shall kind, and SAP Group shall not be liable for not be liable for errors or errors or omissions with respect to the materials. The only

omissions with respect to the materials. The only warranties for SAP Group products and services are warranties for SAP Group products and services are those that are set forth in those that are set forth in thethe express warranty statements accompany

express warranty statements accompanying such products and services, if ing such products and services, if any. Nothing herein should be any. Nothing herein should be construed as constituting anconstrued as constituting an additional warranty.

Idocs configuration

Applies to:

Applies to:

Summary

Summary

Author Bio

Author Bio

T

T

able of

able of

Contents

Contents

1. What is Idoc?

1. What is Idoc?

2. Why Idoc Configuration?

2. Why Idoc Configuration?

3. Steps in Idoc Configuration

3. Steps in Idoc Configuration

4. Steps to be done in Source client

4. Steps to be done in Source client

5. Steps to be done in Destination client

5. Steps to be done in Destination client

Copyright

Copyright