Ansicht
Dokumentation

_ISUAMI_000006 - Define Text Messages

ABAP Short Reference   rdisp/max_wprun_time - Maximum work process run time  
This documentation is copyright by SAP AG.

In this activity, you make the settings for messaging.

Some entries have been predefined by SAP.

1. Message category

Check the predefined entries and if necessary define additional message types using namespace 5*, 6*, 7*, 8*, and 9*.

1. Message attribute determination group

Here you make the entries for the message attribute determination group of a device category. The message attribute determination group is used in the device or device info record to determine the message attribute. A message attribute determination group can have more than one message attribute.

• Message attribute

Here you define the length of the message and the message category, for example.

1. Message Types

Check the predefined entries and, if necessary, define additional message types using the namespaces 5*, 6*, 7*, 8*, and 9*.

1. Message source

Check the predefined entries and if necessary define additional sources from which to send the message using namespace 5*, 6*, 7*, 8*, and 9*.

1. Validity for messages

Here you define the number of days for which the message is valid.
The system uses the following logic to determine the message validity:

• If a number of days is specified in Customizing for the message template and the agent has selected this template in the application, the system calculates the validity date by adding the specified number of days to the system date.

• If no number of days is specified in Customizing for the message template or if the agent has not selected a template in the application, the system calculates the validity date by adding the number of days specified in Customizing for the message source to the system date.

If no number of days has been specified in Customizing for the message source either, the system uses the system date as the validity date.

• If the agent has authorization to change the message template or to write the message, they can enter or overwrite the validity date directly when saving or sending the message.

1. Message object type

Check the predefined entries and if necessary define additional message object types using namespace 5*, 6*, 7*, 8*, and 9*.

1. Parameters for template

Check the predefined entries and if necessary define additional parameters using namespace X*, Y*, Z*.

You can also use these parameters as placeholders in the text of message templates. The parameters are filled as soon as the agent selects the template in the application when saving or sending the message.

For example, if you use the parameters &DEVICE_CATEGORY& and &DEVICE_NO& in the text of the message template, they are replaced by the device category and the device serial number respectively when the message template is used in the application.

To allow the system to fill parameters defined in the customer namespace, you have to implement method REPLACE_PARAMETERS_TEMPLATE.

For more information, see the documentation for interface IF_EX_ISU_AMI_MSG.

1. Message templates

If you edit a message template, you can assign a template ID.

You can enter messages in multiple languages for a template ID.

1. Assign template to dunning activity

rdisp/max_wprun_time - Maximum work process run time   Vendor Master (General Section)  
This documentation is copyright by SAP AG.

Length: 4031 Date: 20240523 Time: 154729     sap01-206 ( 62 ms )