Message Processing Rules

You use message processing rules to determine how you want to process incoming remote function calls (RFC), IDocs, and HTTP messages. Messages are processed based on their type.

For more information, see Message Services.

Features

The following table describes the properties for message processing rules:

Property	Description
Name	Name of the message processing rule.
Description	Description of the message processing rule.
Message Listener	Name of the message listener server to which the rule applies.
Message Type	The types of messages you want the server to accept, including the following: RFC IDoc Web Service (for the HTTP) message
Message Name	Name of the RFC, IDoc, or Web Service message. The message name is automatically part of the inbound JRA message; however, for the HTTP service interface, the message name must be specified in the HTTP request URL.
Processing Type	Determines how messages are processed. Transaction Messages are immediately passed to a transaction. Category Messages are stored in a persistent queue. You can use the Message Services actions to retrieve them.
Category	If you select a Processing Type of category, this field is available. Grouping in which the message is saved in the buffer for sequential processing. If a message maps to a category, it is assigned to that category and works like a virtual queue. Messages may be processed out of order. You can run a scheduled transaction against the queue using actions to read the incoming messages.
Category Description	If you select a Processing Type of category, this field is available. Description of the message category.
Transaction	If you select a Processing Type of transaction, this field is available. Name of the transaction used to process the message.
Persist Transaction	If you select a Processing Type of transaction, this field is available. The following options determine when the system writes to the database: Always On Error Never
Log Level	If you select a Processing Type of transaction, this field is available. Select one of the following debugging levels: Unknown None Debug Info Warn Error Fatal
Parameters	If you select a Processing Type of transaction, the input properties of the transaction is available as parameters. These parameters can be mapped to the following message fields: ReceivedMessageXML MessageUID MessageID Transaction input parameters are for the RFC, IDoc, or HTTP.

If no processing rule is associated with a message type, the generic rule "*" is used to process the message.

Messages are written to the system database. You also use the Message Monitor to forward received messages manually to a transaction for processing. The messages are passed to the specified transaction input parameter as defined in the processing rule for the message type and name.

Activities

To access the message processing rules, on the SAP MII administration menu, choose Message Services Message Processing Rules .