31
Atos, Atos and fish symbol, Atos Origin and fish symbol, Atos Consulting, and the fish itself are registered trademarks of Atos Origin SA. May 2006 © 2006 Atos Origin Sheetal Raina 2007 ALE-IDOC Training

ALE IDOC Training-Day 4

Embed Size (px)

DESCRIPTION

Day4

Citation preview

Page 1: ALE IDOC Training-Day 4

Atos, Atos and fish symbol, Atos Origin and fish symbol, Atos Consulting, and the fish itself are registered trademarks of Atos Origin SA. May 2006© 2006 Atos Origin

Sheetal Raina2007

ALE-IDOC Training

Page 2: ALE IDOC Training-Day 4

2 Custom presentation- or document control name

Table of content

• Introduction - ALE Terminologies

• IDOC Segment

• IDOC Components

• IDOC Types

• Message Type

• Partner Profiles

• Port

• Process Codes

• Questions and answers

Page 3: ALE IDOC Training-Day 4

3 Custom presentation- or document control name

Table of content

• Introduction - ALE Terminologies

• IDOC Segment

• IDOC Components

• IDOC Types

• Message Type

• Partner Profiles

• Port

• Process Codes

• Questions and answers

Page 4: ALE IDOC Training-Day 4

4 Custom presentation- or document control name

ALE Training

Terminologies Involved in dealing with Idocs

•Segments •IDoc Type•Message Type•Partner Profiles•Process Codes•Port

Page 5: ALE IDOC Training-Day 4

5 Custom presentation- or document control name

Table of content

• Introduction - ALE Terminologies

• IDOC Segment

• IDOC Components

• IDOC Types

• Message Type

• Partner Profiles

• Port

• Process Codes

• Questions and answers

Page 6: ALE IDOC Training-Day 4

6 Custom presentation- or document control name

ALE Training

IDOC - Segments

Segments: Defines format and structure of a data record. Segment type is version independent name of thesegment. Segment definition is version dependent definition ofsegment which specifies the field which belong to thesegment. Segment documentation gives documentation for

eachfield in segment definition. Data fields used in data segments

Page 7: ALE IDOC Training-Day 4

7 Custom presentation- or document control name

ALE TrainingDefinition (1): Segment

Page 8: ALE IDOC Training-Day 4

8 Custom presentation- or document control name

ALE TrainingDefinition (2): Segment

•A segment comprises SAP release-independent segment type At least one SAP release-dependent segment name

•Segment types are structures in the ABAP repository.

•All fields of a segment are of data type character (CHAR).

Page 9: ALE IDOC Training-Day 4

9 Custom presentation- or document control name

ALE Training

Segment Type/partner/cccccSegment Type/partner/ccccc

Segment Name/partner/ccccc000Segment Name/partner/ccccc000

Segment Name/partner/ccccc001Segment Name/partner/ccccc001

Segment Name/partner/ccccc013Segment Name/partner/ccccc013

Segment TypeE1cccccSegment TypeE1ccccc

Segment NameE2ccccc000Segment NameE2ccccc000

Segment NameE2ccccc001Segment NameE2ccccc001

Segment NameE2ccccc013Segment NameE2ccccc013

Definition (3): SegmentVersion 1e.g. 3.0A

Version 2e.g. 3.0C

Version 14e.g. 7.7x

Page 10: ALE IDOC Training-Day 4

10 Custom presentation- or document control name

ALE Training

• By releasing segments and IDoc types the data structures of the interface are „frozen“ to subsystems and labelled with unique names for

the segments, and the IDoc types

• The IDoc definiton tools control the release feature. Any ongoing development after releasing leads to new versions of either segments or IDoc types.

Definition (4): Segment

Page 11: ALE IDOC Training-Day 4

11 Custom presentation- or document control name

ALE Training

• We distinguish versions for segments as well as for IDoc types.

• In one SAP correction level, e.g. 4.0B, only one current version can exist.

• A new version of the development objects segment and IDoc type is created always, if changes are made after releasing that object.

• Possible changes are strongly restricted to guarantee external compatibility of the IDoc interface.

Definition (5): Segment

Page 12: ALE IDOC Training-Day 4

12 Custom presentation- or document control name

Table of content

• Introduction - ALE Terminologies

• IDOC Segment

• IDOC Components

• IDOC Types

• Message Type

• Partner Profiles

• Port

• Process Codes

• Questions and answers

Page 13: ALE IDOC Training-Day 4

13 Custom presentation- or document control name

ALE TrainingIDOC Components

There are basically two types of IDOCs.

•Basic IDOCs•Extended IDOCs

Extensions are used because –• The standard code of processing is still in use.• Developments and corrections of standard code are available automatically.• Extensions are much less effort than developments.

Page 14: ALE IDOC Training-Day 4

14 Custom presentation- or document control name

ALE Training

• Basic IDoc

Basic IDOC type defines the structure and format of the business document that is to be exchanged between two systems.

Characteristics- Name- Hierarchy of segments- Mandatory vs. Optional segments- Min/Max no. of segments

• Extension IDoc

Extending the functionality by adding more segments to existing Basic IDOCs.

IDOC Components

Page 15: ALE IDOC Training-Day 4

15 Custom presentation- or document control name

ALE Training

The IDoc type requested is available, and matches all requirements:

Nothing to be done !

The IDoc type requested is available, but does not match in all the requirements:

Development as „extension“ !

The IDoc type requested is not available, or matches only in few requirements:

Development as „basis type“ !

What Kind of Development, and When ?

Page 16: ALE IDOC Training-Day 4

16 Custom presentation- or document control name

Table of content

• Introduction - ALE Terminologies

• IDOC Segment

• IDOC Components

• IDOC Types

• Message Type

• Partner Profiles

• Port

• Process Codes

• Questions and answers

Page 17: ALE IDOC Training-Day 4

17 Custom presentation- or document control name

ALE Training

• An IDoc type is defined by the corresponding:

» Segments

» Attributes of these segments(for example, maximum number, hierarchical sequence, segment status) Go to transaction code WE30

• Enter the Object Name, select Basic type and click Create icon

• Enter a description for your basic IDOC type and press enter

Create IDOC Type

Page 18: ALE IDOC Training-Day 4

18 Custom presentation- or document control name

ALE Training

• Select the IDOC Name and click Create icon

• The system prompts us to enter a segment type and its attributes

• Choose the appropriate values and press Enter

• The system transfers the name of the segment type to the IDOC editor.

• Follow these steps to add more number of segments to Parent or as Parent-child relation

• Save it and go back

• Go to Edit -> Set release

Create IDOC Type Cont…

Page 19: ALE IDOC Training-Day 4

19 Custom presentation- or document control name

Table of content

• Introduction - ALE Terminologies

• IDOC Segment

• IDOC Components

• IDOC Types

• Message Type

• Partner Profiles

• Port

• Process Codes

• Questions and answers

Page 20: ALE IDOC Training-Day 4

20 Custom presentation- or document control name

ALE Training

• Go to transaction code WE81

• Change the details from Display mode to Change mode

• After selection, the system will give this message “The table is cross-client (see Help for further info)”. Press Enter

• Click New Entries to create new Message Type

• Fill details

• Save it and go back

Create Message Type

Page 21: ALE IDOC Training-Day 4

21 Custom presentation- or document control name

ALE Training

• Go to transaction code WE82

• Change the details from Display mode to Change mode

• After selection, the system will give this message “The table is cross-client (see Help for further info)”. Press Enter.

• Click New Entries to create new Message Type.

• Fill details

• Save it and go back

Assign Message Type to IDoc Type

Page 22: ALE IDOC Training-Day 4

22 Custom presentation- or document control name

Table of content

• Introduction - ALE Terminologies

• IDOC Segment

• IDOC Components

• IDOC Types

• Message Type

• Partner Profiles

• Port

• Process Codes

• Questions and answers

Page 23: ALE IDOC Training-Day 4

23 Custom presentation- or document control name

ALE Training

• The partner profile links system 1 with system 2, e.g. the SAP business application with an EDI subsystem.

• The process code points to a business process. The business process controls the creation of an IDoc in outbound, or the processing of an IDoc to post a business document in inbound.

• The port takes all the technical properties to address system 2.

IDOC Configuration Terms

Page 24: ALE IDOC Training-Day 4

24 Custom presentation- or document control name

ALE Training

– A partner profile is an identifier for a system used for communicating messages.

– There are 4 basic types of partner profiles

•KU for customer•LI for vendor•B for Bank

•LS for Logical System

Partner Profile

Page 25: ALE IDOC Training-Day 4

25 Custom presentation- or document control name

ALE Training

• A partner profile defines the parameters of communication between 2 or more systems.• A partner profile specifies various characteristics of data exchanged with a business partner.• The parameters also determine the mode of processing and error handling.• Three views of a partner profile

1. General parameters view: Data stored in EDPP1

2. Inbound parameters view: Data stored in EDP213. Outbound parameters view: Data stored in EDP13

except message control parameters are stored in EDP12.

Partner Profile

Page 26: ALE IDOC Training-Day 4

26 Custom presentation- or document control name

ALE Training

• The main parameters are Message types, IDOC types, process codes, partner functions, message function, output types and port.

• Can be viewed as a gateway for ALE and EDI communications. It routes the specified messages through the defined IDOC types to the given port, after invoking the appropriate function modules for outbound processing

• For Inbound it receives IDoc of a specific type and identifies modules to post data to the application databases.

• Linking the process code to the function module for Outbound interface with message control and always for inbound interface.

Partner Profile(Contd).

Page 27: ALE IDOC Training-Day 4

27 Custom presentation- or document control name

Table of content

• Introduction - ALE Terminologies• IDOC Segment • IDOC Components• IDOC Types• Message Type• Partner Profiles• Port• Process Codes• Questions and answers

Page 28: ALE IDOC Training-Day 4

28 Custom presentation- or document control name

ALE Training

• A port is a logical representation of a communication channel in SAP with the data communicated being IDocs.

• There are 4 main types of portsFileTransactional RFCR/2Internet port.

• EDI typically uses file-based ports, which specifies directory location, file name and name of subsystem (if installed).

• In ALE the port of the type tRFC.

Ports

Page 29: ALE IDOC Training-Day 4

29 Custom presentation- or document control name

Table of content

• Introduction - ALE Terminologies• IDOC Segment • IDOC Components• IDOC Types• Message Type• Partner Profiles• Port• Process Codes• Questions and Answers

Page 30: ALE IDOC Training-Day 4

30 Custom presentation- or document control name

ALE Training

– Process code are used in ALE/EDI to identify the function module or API to be invoked for subsequent processing.

– Each process code is associated with a message type.

Process Code

Page 31: ALE IDOC Training-Day 4

31 Custom presentation- or document control name

Table of content

• Introduction - ALE Terminologies• IDOC Segment • IDOC Components• IDOC Types• Message Type• Partner Profiles• Port• Process Codes• Questions and Answers