what is MESSAGE TYPE and purpose?

[former_member206396]

what is message type. and why it is used eventhough there is idoc type..? tell me its purpose?

waiting for reply..

thanking you

Rama krishna S

[Former Member]

Check out this thread in the forum.

Hope this will be of some help to you

[Former Member]

Hi Rama

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.

Hope u find this helpful

Regards

Alok Pathak

[former_member188685]

Message type

Use

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.

Example

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

and for getting info of message type and what for they used check this message type text table<b> EDIMSGT</b>

Regards

vijay

[vinod_gunaware2]

The message type defines the context under which an IDoc is transferred to its destination. It

allows for using the same IDoc file format for several different applications

A message type represents the group in which every basic IDoc types must belong. A message type is conceptually the nature of the data transmitted within an IDoc.

For example, the MATMAS message type is related to material master data, Material Master. To this MATMAS message type is associated several basic IDoc types: MATMAS01, MATMAS02 , MATMAS03, MATMAS04 et MATMAS05. Each basic IDoc type is able to contain essential data on material master data. MATMAS01 is the first version, each subsequent version increments the sequence number ( MATMAS02, etc.) and adds fields comparing with the previous version.

By convention, each basic IDoc type which follows the ascending numbering can not remove a field or change the applicative meaning of a field comparing with the previous version of the basic IDoc type. The standard message types and basic IDoc types in SAP R/3 respect this convention, and it is preferable to do so for all the new types to be created.

An IDoc file requires a minimum of accompanying information to give sense to it. These are the

message type and the IDoc type. While the IDoc type tells you about the fields and segments of

the IDoc file, the message type flags the context under which the IDoc was sent

A receiver of an IDoc must know the exact syntactical structure of the data package

received. Naturally, the receiver only sees a text file with lines of characters. In

order to interpret it, it is necessary to know which segment types the file may

contain and how a segment is structured into fields. SAP sends the name of the IDoc

type in the communication header.

The IDoc type describes the file structure. The IDoc type is defined and viewable

with transaction WE30.

Examples of IDoc types are MATMAS01, ORDERS01, COND_A01 or CLSMAS01.

The message type is an identifier that tags the IDoc to tell the receiver how the IDoc

is meant to be interpreted. It is therefore the tag for the semantic content of the IDoc.

Examples of message types are MATMAS, ORDERS, COND_A or CLSMAS.

The combination of IDoc type and message type gives the IDoc the full meaning.

Theoretically, you could define only a single IDoc type for every IDoc you send.

Then, all IDocs would have the same segments and the segments would always have

the same field structure. According to the context some of the record fields are

filled; others are simply void. Many antiquated interfaces are still working that way.

regards

vinod

[Former Member]

Hai Ramakrishna

01 Error --> Idoc Added

30 Error --> Idoc ready for dispatch(ALE Service)

then goto SE38 --> Execute the Program RBDMIDOC

29 Error --> ALE Service Layer

then goto SE38 --> Execute the Program RSEOUT00

03 Error --> Data Passed to Port ok

then goto SE38 --> Execute the Program RBDMOIND

12 Error --> Dispatch ok

Inbound Status Codes

50 Error --> It will go for ALE Service Layer

56 Error --> Idoc with Errors added

51 Error --> Application Document not posted

65 Error --> Error in ALE Service Layer

for 51 or 56 Errors do the following steps

goto WE19 > give the IDOC Number and Execute>

Press on Inbound function Module

for 65 Error --> goto SE38 --> Execute the Program RBDAPP01 then your getting 51 Error

Thanks & regards

Sreenivasulu P