Hierarchy

⤷

⤷

IMG Activity
ID | CM_XX_REGW01 | Set Up Logging of Messages |
Transaction Code | S_KK4_82000774 | (empty) |
Created on | 20011001 | |
Customizing Attributes | CM_XX_204_2_2 | Multiple Use: Non-Critical Optional Activity, IS-HER-CM-AD, ASAP 204 |
Customizing Activity | CM_XX_REGW01 | Maintenance Object: Set Up Logging of Messages |
Document
Document Class | SIMG | Hypertext: Object Class - Class to which a document belongs. |
Document Name | CM_XX_REGW01 |
Use
In this activity, you define whether or not the system should save the message logs at specific callup points.
In Campus Management processes, rule checks can be performed at one or more callup points. If these rule checks are not completed successfully, the system collects the relevant messages in a message log. The system permits you to override this message log if it contains only warnings (type W), information messages (type I), and success messages (type S).
The system enables you to store the original message log so that you can track and subsequently check any overrides. It transfers the relevant message log and stores it permanently.
You must define whether or not the message log should be stored for each callup point. As the system saves the message log as a whole, a message log can also contain messages for other callup points it passes through.
When you override a message log, you can enter a note containing the reasons for the override.
Further notes
The system creates a link to the stored message log in the objects study and student of the infotype Rule Check Results (1748). From this link, you can go directly to the message log. The system sets a separate link for each callup point, even if the message log in question is the same. You can also access the message log from the student file.
The overriding of certain rule check messages is user-specific. These messages can refer to rule validations, fixed checks, BAdI checks, or other checks. You can set this override for each message in the object rule container of the infotype Message Control (1749). In this infotype, you can reduce the priority of a message type user-specifically, i.e. you can change an error message (type E) to a warning (type W).
Requirements
Standard settings
In the standard system, the Save result indicator is not set for any callup point.
Activities
- Determine the callup points for which the system should save the message logs for an override.
- Set the indicator Save result for these callup points.
- Choose Save.
Example
During module booking, checks are performed at the following callup points:
- Callup point 0001 - module booking (general)
- Callup point 0002 - module booking (set)
- Callup point 0003 - module booking (single)
These can be fixed checks and user-defined validations.
Callup point 2 contains checks that fail if the module combination is not correct. As you want the system to log the message log overrides, you must set the indicator Save result for callup point 2.
- Case 1: If messages are available for callup points 1 and 3 of a module booking and the user overrides the message log, the system does not save the message log.
- Case 2: If messages are available only for callup point 2 and you override the message log, the system saves the message log. You can create a note with up to 256 characters for this message log. This note is stored in the system along with the log header (header of the application log). If messages are not only available for callup point 2 but also for callup points 1 and/or 3, the system also saves these. A message log is always saved as a whole.
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 |
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 |
V_T7PIQCHECKTPR | V - View | SM30 |
History
Last changed by/on | SAP | 20011026 |
SAP Release Created in | 464 |