1. Overview of ALE / EDI / IDOCs

4. Typical EDI/IDOC Scenario

8. Complete EDI/ ALE scenario

11. ALE Objective

14. ALE Scenario Document SAP System R/3 SAP System R/3 IDoc EDI Subsystem EDI Subsystem IDoc IDoc

16. Components of ALE Services: Application Services Distribution Services Communication Services

17. Application Services Services: Application Services Distribution Services Communication Services This is where the SAP applications ( SD, FI, MM etc. ) generate their data and documents

20. Determine Receipients Filter/Convert Data, Create IDOC Application Functions Filter/Convert Data Carrier Application Layer Distribution/ ALE Layer Communication Layer Application In a Nut Shell Application Data Master IDOC Comm. IDOC Comm. IDOC

24. Control record Data Record Status Record IDOC “ Intermediate Document”

25. Control Record The very first record of an IDoc package is always a control record. The structure of this control record of the structure EDIDC and describes the contents of the data contained in the package. The control record goes to table EDIDC

26. Message Type Message Type indicates How to Know what the data Means Data Exchanged by IDOC and EDI is known as Messages Message of same kind belong to the same message type. Message types are stored in table EDMSG

27. Data Record All records in the IDoc, which come after the control record, are the IDoc data. They are all structured alike, with a segment information part and a data part, which is 1000 character in length, filling the rest of the line. Data & Segment info is stored in EDID4 for release 4.x and EDID3 for release 2.x and 3.x.

28. Status Record Information about the IDoc status like: IDoc identification number Status number - table verified IDoc type Direction Data and time stamp; Structure: EDIDS

30. Idoc Segments TCODE: WE31

31. Idoc Types TCODE: WE30

32. How to Attach Segments

33. Message Types WE81 WE82

34. IDOC Type/ Message Type/ Processing Function Module Valid combination of Message type and IDOC type are stored in table EDIMSG Combination of message type and IDOC type determine the processing algorithm. This is usually a function module and is set up in table EDIFCT.

36. Outbound Processing

37. Outbound processing: direct Application posting ALE layer Database Application document posted simultaneously with IDOCs Comm. layer asynch. RFC or EDI System call FM ( INBOUND_ IDOC_ PROCESS ) On destination Comm. layer Need to create IDOC? Create master IDOC Customer Distribution Model Receiver determination Segment filter Field value conversion Version change Dispatch control M C Links C

43. Filling an EDIDD structure MOVE “Z1SEG” to EDIDD-SEGNAM MOVE “10” to Z1SEG-FIELD1 MOVE “ABC” to Z1SEG-FIELD2 MOVE Z1SEG to EDIDD-SDATA Header (55bytes) SDATA (1000bytes) … . SEGNAM …. EDIDD Z1SEG Field1 Field2 Field3 Field4 “ 10” “ ABC”

48. Maintaining RFC Destinations TCODE: SM59

49. Displaying and Maintaining Ports A port is a logical representation of a communication channel in SAP with the data communicated being IDocs . TCODE: WE21

50. Partner Profiles TCODE: WE20

51. Partner Profiles-Inbound

52. Partner Profiles-Outbound

53. ALE For Transactional data ---- Output Determination NACE

54. Output Determination -- Output Types

55. Output Types -- Details

56. Inbound Processing

57. Inbound Processing. Application posting ALE layer Input control Database Simultaneously update IDOC's status Field value conversion A Comm. layer asynch. RFC or EDI Version change Segment filter C A Post application document Process IDOC Serialization

61. FM Assignment to Message Type and IDoc type TCODE: WE57

62. Process Codes WE41 WE42

63. Process Codes in Inbound and Outbound TCODE: WE64

64. FM For Inbound EDI TCODE: BD67

72. List Of All IDocs Created. (Default, Additional, EDI)-- WE02/ WE05

73. Selection Program For Issuing Output -- WE15

74. Test Tool For Idoc Processing (WE19)

75. Idoc Search For Business Contents (Database). WE09

76. Questions