regarding message types

[Former Member]

what mean by message type and Idoc type?????

difference between them??????

[former_member194669]

Hi,

The messages exchanged between systems are of various message types. The message type depends on the data contained and the process involved. It determines the technical structure of the message, the IDoc type. For example, the FIDCMT message type is used for journal messages.

The IDoc type indicates the SAP format that is to be used to interpret the data of a business transaction.

An IDoc type consists of the following components:

· a control record

This is identical for each IDoc type.

· several data records

One data record consists of a fixed key part and a variable data part. The data part is interpreted using segments, which differ depending on the IDoc type selected.

· several status records

These are identical for each IDoc type and describe the statuses an IDoc has already passed through or the status an IDoc has attained.

aRs

[Former Member]

Hi Subash,

<b>Message type</b>. A message type represents the application message exchanged between R/3 systems and R/3 and an external system. A message type characterizes the data sent across systems and relates to the structure of the data called an IDOC type (see below). For example, MATMAS is a message type for Material Master, and INVOIC is a message type for an Invoice (Billing Document). ALE supports over 200 message types in R/3 and about 200 application areas.

<b>IDOC type</b> and IDOC. An Intermediate Document (IDOC) type represents the structure of the data associated with a message type (DEBMAS02 for message type DEBMAS — Customer Master, and WMMBID02 for message type WMMBXY— Goods Movements), while an IDOC is an object containing the data of a particular message type. IDOCs are data containers with intelligence built in. Each IDOC contains one and only one business object. For example, an IDOC of type SHPMNT01, message type SHPMNT, will contain data only of one Shipment Document. Generally, the architecture of an IDOC is independent of the message type by virtue of ALE’s ability to redefine it for any message type.

<b>Reward points if answer is helpful.</b>

With Thanks,

Chinmay

[varma_narayana]

Hi..

These are the two important components based on which as IDOC is generated.

IDOC TYPE : Defines the Structure based on which the Data of an IDOC has to created (i.e Data Records)

Eg: MATMAS03, ORDERS03

Tcode: WE30

Message type : Determines the Processing logic to Generate IDOC in Outbound and to Post(Update) Idoc Data in inbound.

Eg: MATMAS, ORDERS, ORDRSP.

Tcode: WE81

<b>Reward if Helpful</b>

[Former Member]

hI

The basic IDOC type is defined by the applications. it defines the structure and format of the data of the application document

it is just a information documents consisting of all fields data in specific format

Message Type:

An IDoc type can be implemented for various "logical" messages; one message can also be assigned to different IDoc types (m:n relationship).

The message is defined by the values for message type (required), message code (optional) and message function (optional). These three fields belong to the key fields in the partner profiles, which are used, for example, to determine inbound processing. If the 'Message type' field is not maintained (e.g. in the case of a control record from Release 2.1, in which MESTYP did not exist), the IDoc Interface uses the value from STDMES (EDI message type).

If possible, the descriptions of the message type should be linked to the corresponding EDI message type.

The message ORDERS (= message type) identifies purchase orders (outbound) and sales orders (inbound).

<b>Reward points for useful Answers</b>

Regards

Anji