Ansicht
Dokumentation

CRM_MESSAGES - Set message-relevant parameters

Addresses (Business Address Services)   SUBST_MERGE_LIST - merge external lists to one complete list with #if... logic for R3up  
This documentation is copyright by SAP AG.

Purpose

You can use this report to influence the following parameters:

• degree of usage (degree of detail)

The degree of detail specifies which user user receives what range of messages. The F4 help provides you with the possible values for selection.

• Trace mode

In trace mode, messages are not deleted physically, but logically. They are then displayed further in status "deleted" in the application log.

• Tax parameters for breakpoints when collecting and deleting messages

In order to determine from which program a specific message should be collected or deleted in the application log, the command "breakpoint for instruction message" is, as a rule, unsuitable, as it stops at every triggered message, and even at messages that only stop a function module, in combination with the ABAP command RAISING, and never appear on the user interface. The command is also too vague, as it does not allow you to only stop when you a specific message is triggered.

With the report, you can specify:

• the message ID and/or

• the message class and/or

• the CRM subobject that allows the message to be collected

to trigger the (hard programmed) breakpoint when collecting or deleting this message. This allows you to track how specific messages are set up and archived in the application log for the business transaction. The breakpoint is unspecific - other users are therefore not affected.

The hard programmed breakpoints are found in the function modules CRM_MESSAGE_COLLECT and CRM_MESSAGES_DELETE.

Activities

• Set trace mode and degree of usage

Set the values you require for trace mode and degree of usage, and choose "Copy values". The values are then copied into the global user- specific memory, and are used for the duration of your terminal session.

If you want to change the settings permanently, that is, beyond the duration of your terminal session, you must set the corresponding parameters CRM_TRACE and CRM_USER_LEVEL in the user maintenance (transaction SU01). Note that no F4 help or value validation can be offered for the parameter maintenance, due to technical reasons.

• Reset trace mode and degree of usage

If you choose "Recreate standard", the standard values are recreated for degree of usage and trace mode.

• Set debugging parameters

Enter your selection criteria for message ID (message class), message number and subobject being called. You can also work with wildcards, for example, by entering the special characters '+' and '*'.

The debugging parameters remain valid for the current user and the current date. As they are updated in the database table INDX, they are available beyond the current session.

• Delete debugging parameters

Here, you deactivate the debugging parameters.

Example

1. Maximum degree of usage
   Trace mode = 'X'
   Degree of usage = '9'

When you choose 'Copy values', you have the highest possible degree of usage. You have all collected and displayed all the messages in the business transaction. Deleted messages (with status "deleted") also continue to be displayed.

1. Trace mode, but normal degree of usage
   Trace mode = 'X'
   Degree of usage = '3' (office-based sales employee)

All the messages occuring in transaction processing are collected, but not all are displayed. The scope of display remains on the level 'office-based sales employee'.

This setting is useful for examining problems occuring in the productive operation, which cannot be reproduced. The productive user is not bothered by the messages collected additionally. They can, however, be evaluated later, and possibly provide hints regarding the cause of the error.

1. Stop at a specific message
   Message ID = 'CRM_ORGMAN'
   Message no. = '010'

If you choose 'Update debugging parameters', the system always stops while processing the CRM business transaction when the message CRM_ORGMAN010 is copied into the message buffer, or is deleted from it.

1. Stop at specific messages that are deleted from a subobject
   Message ID = 'CRM_ORGMAN'

If you choose 'Update debugging parameters', the system always stops while processing the CRM business transaction when any message is copied from message class CRM_ORGMAN into the message buffer, or is deleted from it.

1. Stop at specific messages that are triggered by a subobject.
   Message ID = 'CRM_ORGMAN'
   Calling object = 'ORGMAN'

If you choose 'Update debugging parameters', the system always stops while processing the CRM business transaction if any message from message class CRM_ORGMAN is copied from the business transaction subobject ORGMAN into the message buffer, or is deleted from it.

CL_GUI_FRONTEND_SERVICES - Frontend Services   General Data in Customer Master  
This documentation is copyright by SAP AG.

Length: 5907 Date: 20240520 Time: 081659     sap01-206 ( 93 ms )