topic Re: message vs IDOC in Application Development and Automation Discussions

message vs IDOC

Former Member — Sun, 18 Dec 2005 05:44:40 GMT

dear consultant,

how a message in IDOC, different from a message from message-class,

thanks& regards in advance,

kcc

Re: message vs IDOC

Former Member — Sun, 18 Dec 2005 07:11:35 GMT

Hi,

IDOC has a basic type which consists of segments(ALE).This basic type is attached to an upper layer called message type.

However message in message-class is used purely for displaying messages in R/3 for user interaction.

Hope this makes it clear.

Thanks & Regards,

Vanita

Please assign points for useful answers.

Re: message vs IDOC

Former Member — Sun, 18 Dec 2005 09:20:58 GMT

Hi KC,

It is not clear what you are asking, but I presume two things and here are the answers for the same,

1. Message Type & message classes

The message type of the IDoc will help you to identify the business message/ data that you are transmitting across systems. Whereas the message classes contain a set of informative message that can be used to reflect the outcome of a process/ operation you do.

2. IDoc Status & message classes

In the IDoc status we can provide meaning information to reflect the status of the operation we performed. Here we can use the existing standard message classes.

Go through this link for some more information,

http://www.sapgenie.com/faq/ale.htm

Thanks

Kathirvel

Re: message vs IDOC

Former Member — Sun, 18 Dec 2005 09:23:41 GMT

Hi Kc,

Some of your threads are answered, please check the same and reward points if they are helpful or solves your problem.

Please have a look at the below link to award points,

https://www.sdn.sap.com/irj/sdn/crphelp

Thanks in advance

Kathirvel

Re: message vs IDOC

Former Member — Sun, 18 Dec 2005 11:31:02 GMT

dear consultants,

how to reward the respondents,

someone,please,help me

thanks& regards,

kcc

Re: message vs IDOC

Former Member — Sun, 18 Dec 2005 19:09:15 GMT

Hi,

Here is the link between message vs idoc

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.

This is how the data actually come from SAP to the IDoc as follows:

You need a function module or another self-written program that creates the data to send.

If the triggering transaction supports customizable NAST messaging, then you can create a NAST message that supports ALE or IDoc. The link between the message and IDoc is defined via the process code in the partner profile WE20. Whenever the NAST message is processed it will make a call to ALE_PROCESSING in program RSNASTED or EDI_PROCESSING in program RSNASTED, which does the job for you and eventually will call the function module that fills the data hive.

If a program does not support messaging via NAST then you need to create the IDocs with your own routine and then call MASTER_IDOC_DISTRIBUTE.

Thanks,

Naga