Beruflich Dokumente
Kultur Dokumente
Disha Jain
Mumbai,24th September, 2007
Atos, Atos and fish symbol, Atos Origin and fish symbol, Atos Consulting, and the fish itself are registered trademarks of Atos Origin SA. November 2006
2006 Atos Origin
Table of Contents
Outbound
Sending out the data from our system, any IDoc which is sent out from the
system is called as Outbound.
Inbound
Receiving the data in the system is termed to be inbound
Each system in the system landscape must have a logical system name.
The name should be unique throughout the whole system landscape. This name can then be
assigned to one client of an SAP system. To guarantee that the name is unique and to
simplify the assignment, SAP recommends the naming convention <System
name>CLNT<Client number>.
To view the existing names of logical systems, choose the following in the
IMG: Application Link Enabling (ALE) Sending and Receiving Systems Logical Systems
Define Logical System.
To view the assignments to clients, choose the following in the IMG:Application Link Enabling
(ALE) Sending and Receiving Systems LogicalSystems Assign Logical System to a
Client.
Port Definition
Transaction WE21
A port defines the medium in which the data is exchanged between the two systems.
The tRFC port used in the ALE process can be generated automatically when you generate
the partner profiles or it can be maintained manually.
For port definitions to be generated automatically, the RFC destination name must be the
same as the logical system name.
Cross system reporting RBDSTATE- run periodically on destination system, reports status of incoming IDocs to
the sending system using ALEAUD message.
RBDAUD01 executed on sending system, analyzes the audit log and displays the
output as report.
10
11
Distribution Model
12
Distribution Model
13
Partner Profile
14
Partner Profile
For every message type, you need to make the outbound processing settings in
the sending system, and the inbound processing settings in the receiving system.
In every system, the settings are made for each partner in the partner profile.
To view the partner profile, choose the following in the IMG: Application Link
Enabling (ALE) Modeling and Implementing Business Processes Partner
Profiles and Time of Processing Maintain Partner Profile Manually.
This is transaction WE20.
15
16
Interface Adviser
For more information on the distribution of master data, see the Implementation Guide documentation (IMG) under:
Application Link Enabling (ALE) Modeling and Implementing Business Processes Master Data Distribution.
17
18
EDI Configuration
19
20
Message Control
21
Condition Elements
22
23
24
The condition records are nothing but the combination of fields that you want to
control in the output determination.
Access Sequence is nothing but a four digit Alpha-Numeric Key which is used by
the SAP as the search criterion to search the condition records.
25
26
27
28
29
After the above screen, you select Generate Port Name radio button. It will
automatically generate the port. Then it will show the following screen where
you have to fill in the information like the RFC Destination for the Port and short
description etc
30
31
32
Partner Profile
Execute the transaction WE20 for generating the partner profile.
Once this screen appears, we have to fill in the required information like Message
Type, Receiver Port, the IDoc transfer packet size, basic type for corresponding
message type etc
33
EDI configuration
At this point, our configuration for EDI system is over. Now we have to actually
generate the sales order and we need to create the IDoc associated with it. So go
to the transaction
VA01 Create Sales Order. Enter in to the required fields of sales order and save
it. It will generate the document number.
34
EDI Configuration
35
Display IDoc
After that you can go to the transaction WE02 Display IDoc List.
36
As the purchase order is created in MM, outbound processing has to take place using
Message Control. The master data for the vendor therefore contains a condition record which
uses the order to find the corresponding EDI message and writes an MC record.
The key fields in the MC record are assigned to the corresponding key fields in the partner
profile (outbound processing using Message Control). They determine the process code,
which in turn defines the outbound processing (generating an outbound IDoc using a function
module).
The key fields in the partner profile (outbound processing using Message Control) are
assigned to the corresponding key fields in the partner profile (general outbound processing).
This determines the IDoc type (ORDERS01) and the port.
The IDoc Interface now knows which IDoc type to generate with which function module. The
IDoc is created. The partner profile specifies that the IDoc is immediately sent to the port.
37
38
39
The MM master data must contain certain parameters which are sent to the order recipient
via IDoc:
Apart from the partner number and type, the vendor master record must contain the
partner function. The partner function is a required field entry in the additional outbound
partner profile using Message Control (MC).
The vendor master record should contain the name which appears as the partner number
in the recipient partner profiles as the "account with vendor" (field LFB1-EIKTO). This field
is compared with the partner number value in the recipient inbound partner profile. If this
field is not maintained, additional conversions are required in the recipient system.
The vendor material information must contain the material name for the vendor, because
the recipient determines from the contents of a segment of type E1EDP19 which material
has been ordered.
The MC condition record must contain a transmission medium "6 (EDI). The recipient
cannot see this value. If another transmission medium is entered, the IDoc Interface will
not be activated.
40
41
The SD master data must contain EDI-specific parameters which are compared with the data
from the order IDoc:
Partner number, type and function of the sender are assigned according to the data in the
partner profile. This data must also exist in the SD master data.
The material number is transferred in a segment of type E1EDP19. This material must
exist in the material master record. The qualifier 002 in the segment shows that this is the
material number for the vendor.
If the EDI subsystem does not assign the combination of customer and vendor to a sales
organization via segments of type E1EDK14 (document header organizational data), you
must maintain this assignment yourself using the customizing transaction (VOED).
More on EDI
WE82 - Linking the message type with the basic IDoc type.
42
EDI- RECAP
43
EDI Configuration-RECAP
44
Information Sources
https://websmp207.sap-ag.de/int-adviser
Interface Adviser
45
Thank You
Atos, Atos and fish symbol, Atos Origin and fish symbol, Atos Consulting, and the fish itself are registered trademarks of Atos Origin SA. November 2006
2006 Atos Origin