A <b>message type</b> represents the application message exchanged between R/3 systems and R/3 and an external system. A message type characterises the data sent across systems and relates to the structure of the data called an IDOC type.
Example: MATMAS is message type for Material Master
The <b>Intermediate Document, or IDoc</b>, is the main component of all interface functionality in SAP
An IDOC is simply a data container that is used to exchange information between any two processes that can understand the syntax and semantics of the data.
An IDOC is created as a result of execution of an outbound ALE or EDI process. In an inbound ALE or EDI process, an IDOC serves as an input to create application document
<b>An IDoc type specifies the structure of the data.
A message type specifies the meaning of the data</b>
==================================================
An IDoc type is the definition of a specific data structure.
An IDoc is an actual instance of data based on an IDoc type. Therefore, there can be many IDocs created from a single IDoc type.
====================================================
A <b>segment</b> defines the format and structure of a data record.Segments are reusable components, which means they can be used
in more than one IDOC type. A segment consists of various fields that represent data in a data record.
=================================================
Segment Components
<b>Segment type</b> This is version independent name of the segment.
<b>Segment definition</b> This is version dependent definition of a segment where you specify the fields that belong to the segment
<b>Segment documentation</b>
=================================================
IDOC Creation
Create new segments (We31)
Create new IDOCs (WE30)
Create a new message type (we81)
Link message type with IDOC type (we82)
=====================================
ALE Settings
Create and allocate Logical System
Define RFC Destinations
Define Ports
Maintain Customer Model
Create Partner Profiles
Bluesky
