2008 Jul 09 10:59 AM
2008 Jul 09 11:06 AM
2008 Jul 09 11:07 AM
Hi Pavan,
Messages are displayed via ALV popup if you post it. These messages contain the posting information(what company it is posted, document number, etc).
These mesages will be captured using this function module.
CALL FUNCTION 'MESSAGE_STORE'
EXPORTING
arbgb =
exception_if_not_active = ' '
msgty =
msgv1 =
msgv2 =
msgv3 =
msgv4 =
txtnr =
zeile = ' '
EXCEPTIONS
message_type_not_valid = 1
not_active = 2
OTHERS = 3.
Hope this helps you.
Regards,
Chandra Sekhar
Edited by: Chandrasekhar Gandla on Jul 9, 2008 12:07 PM
2008 Jul 09 11:07 AM
When the Partner Manager receives a message via tRFC or an XML message that contains a TID (transaction ID), this message is registered in the Message Store. The recipient of the message is determined by Routing Rules. Routing Rules contain information about the sender, recipient, and message type. A message can be directed to:
· An SAP Server (IDocs, RFCs, and BAPIs)
· An SAP BC Service on a local or remote server
· HTTP with a URL as the recipient
· FTP with recipient
· An e-mail recipient
2008 Jul 09 11:08 AM
2008 Jul 09 11:09 AM
Hi,
It Stores message or output directly.
you need pass the input parameters like this :
ARBGB : Message ID
MSGTY : Type of message (I, S, W, E, A).
EXCEPTION_IF_NOT_ACTIVE : X = exception not_active is initialized if
MSGV1 : First variable parameter of message
MSGV2 : Second variable parameter of message
TXTNR : Message Number
ZEILE : Reference line (if it exists).
The output is
Level of current message and Maximum level of severity.
2008 Jul 09 11:24 AM
This is used for Protocol Updates. This is used for Issuing the Output using the Output types.
when there is some error then the below function called.
NAST_PROTOCOL_UPDATE
MESSAGE_STORE is called from the above function to store the Log.