Hierarchy
SAP_APPL (Software Component) Logistics and Accounting⤷
MM-PUR-SSP (Application Component) Self-Service Procurement⤷
/SRMERP/OL_CFG (Package) Configuration Data Access
IMG Activity
| ID | /SRMERP/MSG_HANDLING | Configure Message Handling |
| Transaction Code | /SRMERP/44000216 | (empty) |
| Created on | 20101115 | |
| Customizing Attributes | /SRMERP/MSG_HANDLING | Configure Message Handling |
| Customizing Activity | /SRMERP/MSG_HANDLING | Configure Message Handling |
Document
| Document Class | SIMG | Hypertext: Object Class - Class to which a document belongs. |
| Document Name | /SRMERP/MSG_HANDLING |
Use
For messages, you can define whether an application log entry is written and whether a CCMS alert is triggered.
You can access the application log using transaction SLG1, application log object /SRMERP/.
Requirements
Standard settings
SAP delivers a system table with default settings. By default, logging is active for all message types (E, A, and X). You can display the system table using table view /SRMERP/V_MSG_S. If you do not define any settings in this Customizing activity, the system uses the default settings.
Activities
The settings you define in this Customizing activity are stored in a Customizing table. To specify the messages that an entry applies to, you use the following columns: Message class, Msg.no., Message Type. You can make entries in several ways:
- Entry for a specific message of a specific type: Enter the message class, the message number, and the message type.
- Entry for a specific message: Enter the message class and the message number.
- Entry for a specific message type in a specific message class: Enter the message class and the message type.
- Entry for all messages in a message class: Enter the message class and leave the message number and the message type empty.
- Entry for messages of a certain type in all message classes: Enter the message type and leave the message class and message number empty.
- Entry for all messages: Leave all three fields empty and select the Log and Alert checkboxes as required.
When a message is generated, the system checks for matches in the Customizing table in the following order:
- Entry exists for this message class, message number, and message type
- Entry exists for this message class and message number
- Entry exists for this message class and message type
- Entry exists for this message class
- Entry exists for this message type
- Generic entry exists for all message classes, message numbers, and message types
As soon as a matching entry is found, the corresponding setting is used for the message.
If no match is found in the Customizing table, the system table is used.
Example
Business Attributes
| ASAP Roadmap ID | 204 | Establish Functions and Processes |
| Mandatory / Optional | 2 | Optional activity |
| Critical / Non-Critical | 2 | Non-critical |
| Country-Dependency | A | Valid for all countries |
Assigned Application Components
| Documentation Object Class | Documentation Object Name | Current line number | Application Component | Application Component Name |
|---|---|---|---|---|
| SIMG | /SRMERP/MSG_HANDLING | 0 | /SRMERP/EBS0000022 | Self-Service Procurement |
Maintenance Objects
| Maintenance object type | C | Customizing Object |
| Assigned objects | ||||||
|---|---|---|---|---|---|---|
| Customizing Object | Object Type | Transaction Code | Sub-object | Do not Summarize | Skip Subset Dialog Box | Description for multiple selections |
| /SRMERP/V_MSG_C | V - View | SM30 |
History
| Last changed by/on | SAP | 20101115 |
| SAP Release Created in | 606 |
