ALE IDOC Training-Day 3

24
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 ALE / IDoc Training Disha Jain Mumbai,24 th September, 2007

description

Day3

Transcript of ALE IDOC Training-Day 3

Page 1: ALE IDOC Training-Day 3

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

ALE / IDoc Training

Disha Jain

Mumbai,24th September, 2007

Page 2: ALE IDOC Training-Day 3

2 ALE./IDOC Technical Training

Table Of Contents

» Introduction to IDocs and Types

» IDoc Structure

Page 3: ALE IDOC Training-Day 3

3 ALE./IDOC Technical Training

IDocs Type (WE30)

» MATMAS- MATMAS01/02/03/04

» CREMAS-CREMAS01/02/03/04

» ORDERS-ORDERS01/02/03/04/05

» DELVRY- DELVRY01/02/03

» WE60

Page 4: ALE IDOC Training-Day 3

4 ALE./IDOC Technical Training

Structure of an IDoc

Page 5: ALE IDOC Training-Day 3

5 ALE./IDOC Technical Training

IDoc Definitions-IDoc Type

Page 6: ALE IDOC Training-Day 3

6 ALE./IDOC Technical Training

IDoc Definition: Basic Type and Extensions

Page 7: ALE IDOC Training-Day 3

7 ALE./IDOC Technical Training

IDoc Definitions : Segment (1)

Page 8: ALE IDOC Training-Day 3

8 ALE./IDOC Technical Training

IDoc Definitions : Segment (1)

Page 9: ALE IDOC Training-Day 3

9 ALE./IDOC Technical Training

IDoc Definitions : Segment (1)

» All fields in the Segment are of type Character, which means all SAP data types are permitted if they represent a character data type.Examples of such SAP data types: CHAR, NUMC, CLNT.

» Naming convention:

» SAP segment types start with ”E1”

» SAP segment names start with ”E2”

» Customer segments start with ”Z1” or ”Z2” or use the prefix technique (Concept of longer names).

» Partner name areas can only be used through prefix technique (Concept of longer names )

Page 10: ALE IDOC Training-Day 3

10 ALE./IDOC Technical Training

IDoc Definitions : Segment (2)

Page 11: ALE IDOC Training-Day 3

11 ALE./IDOC Technical Training

IDoc Definitions : Segment (2)

» A segment consists of one version independent segment type and version dependent segment names.

» The segment type (internal definition) is used in the SAP system and represents the connection to the SAP development environment (Workbench and Repository).

» External systems, ie; EDI Subsystem, can recognize the version of the current segment by the segment name.

» Segment types are a maximum of 27 digits. Segment names are derived out of the segment types, by adding 3 digits (starting with 000).

» SAP segments differ from this norm by using an additional 2 digit prefix “E1” for segment types and “E2” for segment names.

» The naming conventions are preserved through the IDoc definition tools.

Page 12: ALE IDOC Training-Day 3

12 ALE./IDOC Technical Training

Segment Type-(WE31)

Page 13: ALE IDOC Training-Day 3

13 ALE./IDOC Technical Training

Structure of a Master IDoc

Page 14: ALE IDOC Training-Day 3

14 ALE./IDOC Technical Training

Structure of Communication Award

Page 15: ALE IDOC Training-Day 3

15 ALE./IDOC Technical Training

Change Documents and Change Pointers

Page 16: ALE IDOC Training-Day 3

16 ALE./IDOC Technical Training

Generating IDoc from Change Pointers

Page 17: ALE IDOC Training-Day 3

17 ALE./IDOC Technical Training

IMG :Activate Change Pointers

Page 18: ALE IDOC Training-Day 3

18 ALE./IDOC Technical Training

IDoc Structure: Technical Background

Page 19: ALE IDOC Training-Day 3

19 ALE./IDOC Technical Training

IDoc Structure: Technical Background

» The figure below shows the basic structure of an IDoc and which parts are transferred to and from the external system. The parent-child segment hierarchy is shown here as a tree structure. A total of 3 hierarchy levels can be seen.

» An IDoc type is defined through its permitted segments. Segments can be dependent on each other (parent and child segments).

» For example, segment E1EDPT1 (document item text identification) is a child segment of segment E1EDP01 (document item data, general) in IDoc type EXPINV01 (export billing) and a child segment of E1EDP07 (order data shipping notification) in IDoc type DESADV01 (shipping notification).

» The segment, therefore, is used in several contexts and is the "child" of several "parents".

Page 20: ALE IDOC Training-Day 3

20 ALE./IDOC Technical Training

IDoc Structure: Technical Background

IDocs are archived in three database tables in SAP - one for the control record, one for the data records, and one for the status records.

» The control record is identical for all IDocs and contains the administration information, for example, sender, recipient and message. Note that the control record also contains the last processing status ( STATUS field).

» The data records contain the segments and administration information for the segments (for example, a parent segment to which it is attached).

» The status records contain all of the previous processing statuses, as well as the corresponding administration information. This information is not sent between systems as part of the IDoc but rather as a separate data packet.

Page 21: ALE IDOC Training-Day 3

21 ALE./IDOC Technical Training

IDoc Structure: Technical Background

Page 22: ALE IDOC Training-Day 3

22 ALE./IDOC Technical Training

IDoc Structure: Technical Background

» The parent-child structure of the segments is realized by the PSGNUM field, which contains the number of the parent segment (if applicable).

» In addition, the HLEVEL field also contains the hierarchy level. The actual application data, that is, the actual segment, is located in the SDATA field.

» This field, in turn, is subdivided into individual application fields. The maximum length of SDATA is 1000 bytes.

» The SEGNUM field in the status record is used to identify segments which have caused syntax errors.

» SEGFLD fulfills the same function at the lowest level of the segment fields.» A segment is defined as a required segment in the IDoc type, but was not filled when the

actual IDoc was generated. For this reason, the relevant IDoc does not contain this required segment - the syntax check returns an error; the missing segment is marked in the SEGNUM field.

Page 23: ALE IDOC Training-Day 3

23 ALE./IDOC Technical Training

More Info.

» See FM - IDOC_INPUT_ORDERS

Page 24: ALE IDOC Training-Day 3

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

Thank You