Process Management: New Functions for Message Processing


As of Release 4.0A, you can use the following new functions with regard to process message processing:

Message processing if destination errors occur

In Customizing, you can specify for every message category how a message is treated if one of the following errors occurs:

The following processing types are available:

This type of message processing is identical to that of previous releases. It is predefined in the standard system.
The message is sent to all destinations that can process it even if an error has occurred in one destination. Once the message has been sent to a destination, it can no longer be changed in the message monitor although it cannot be processed by another destination due to incorrect message data.
In this case, the message is not sent to any destination at all if an error occurs at one destination at least. Thus, the message can still be corrected in the message monitor and then sent to all destinations.
Use this processing type if:
This applies to all message destinations predefined by SAP except for PI01.
To improve system performance, do not use this processing type if:

The processing type is documented in the message log.

Individual processing of process messages

In Customizing, you can specify that messages are always processes individually for each message destination. If you have set this indicator for at least one destination of a message category, the system always processes messages of this category in a separate runtime environment.

Use this processing type for message destinations of type R/3 function module that carry out complex functions such as order confirmation or goods movement posting. Otherwise, destination errors might occur when several messages are processed.
The processing type is documented in the message log.

The following function modules contained in the standard system are always processed individually irrespective of settings you make in Customizing:

Additional check for destination PI01 "process message record"

When archiving a batch record, the system transfers all those process messages to the log that have been sent to destination PI01 (process message record) and contain the number of the relevant process order.

When you send a message to the process message record, the system therefore checks whether the relevant process order already has status Batch record archived . If this is the case, the process message receives status Sent with warning and a corresponding system message is generated in the message log.

Uploading process messages from external systems

In the PI-PCS interface, you can now also call function module PROCESS_MESS_UPLOAD with a transactional remote function call (tRFC). You can thus use the tRFC to transfer process messages from external systems to the R/3 System. The tRFC ensures that:

Message transfer via the synchronous RFC is still supported in the system. Existing links to control systems can still be used. In future however, new links will only be certified if the control system supports message transfer via tRFC.

Change system parameters in customizing

Settings for message processing if destination errors occur

If process messages are not to be sent to any of its destinations when a destination error occurs, you must set the SndA indicator in Customizing for the message category.

Set up process message categories

Settings for individual processing of process messages

If a message destination is to process every process message in a separate runtime environment, you must set the Indiv indicator in Customizing for the message destination.

Set up message destination