Beruflich Dokumente
Kultur Dokumente
2011 SAP AG
Enter Title Here: Do not exceed space provided - Title automatically appears in page header
Table of Contents
1. What is Idoc?............................................................................................................................................. 3
2. Why Idoc Configuration?............................................................................................................................3
3. Steps in Idoc Configuration3
3.1. Create segment3
3.2 Create Idoc Type...4
3.3 Create Message Type..5
3.4 Associate Message Type with Basic Idoc Type...6
3.5 Create Logical System.6
3.6 Create Logical Connection..7
3.7 Create Ports...8
4. Steps to be done in Source client.8
5. Steps to be done in Destination client11
Related Content..13
Copyright..14
Enter Title Here: Do not exceed space provided - Title automatically appears in page header
1. What is Idoc?
IDocs are structured ASCII files (or a virtual equivalent). They are the file format used by SAP R/3 to
exchange data with foreign systems.
IDocs is the acronym for Interchange Document. This indicates a set of (electronic) information which
builds a logical entity. An IDoc is e.g. all the data of a single customer in your customer master data file,
or the IDoc is all the data of a single invoice.
The information which is exchanged by IDocs is called a message and the IDoc is the physical
representation of such a message. The name messages for the information sent via IDocs is used in the
same ways as other EDI standards.
b. Type your field name and data element and press save then segment definition will be created
automatically.
Enter Title Here: Do not exceed space provided - Title automatically appears in page header
b. Then select the IDOC option to create and press Enter. Give segment name, minimum and
maximum number for and save it. Check if this is mandatory segment.
c.
If you want Header and Item create the segment tree according to that, you can view as follows then
press Save.
Enter Title Here: Do not exceed space provided - Title automatically appears in page header
d. Then go back and set release the IDOC type for using it further. Idoc type will be created
successfully once we release that status. We have to release the segments (in WE31) and IDOC
type as well.
Enter Title Here: Do not exceed space provided - Title automatically appears in page header
Else go to transaction SALE then go to Basic settings-> logical system then Define logical system.
We can create the same.
Enter Title Here: Do not exceed space provided - Title automatically appears in page header
b. Then Click Connection test icon after marking the current user checkbox in logon and security tab.
Enter Title Here: Do not exceed space provided - Title automatically appears in page header
Enter Title Here: Do not exceed space provided - Title automatically appears in page header
9.Select your model view -> click edit -> Add message type
10. In dialog box specify sender, receiver, and message type and continue. Now the model view looks
Like
Enter Title Here: Do not exceed space provided - Title automatically appears in page header
12. It will show the following screen. Select your model view and click on execute.
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 Display
change button
Enter Title Here: Do not exceed space provided - Title automatically appears in page header
6. Specify your function module and input type by clicking the new entries.
7. Go to transaction WE42 and create process code.
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).
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).
Enter Title Here: Do not exceed space provided - Title automatically appears in page header
Related Content
You must include at least 3 references to SDN documents or web pages.
http://forums.sdn.sap.com/thread.jspa?messageID=10041344#10041344
http://forums.sdn.sap.com/thread.jspa?messageID=9949613#9949613
http://forums.sdn.sap.com/thread.jspa?messageID=9932294#9932294