
Processing Different Notification Data
To call up the individual functions in the list, call up the notification in create or change mode. Since the notification screen can be configured differently, the functions in your system may be located on other tab pages.
Function |
Tab Page/Menu Path |
What You Should Know: |
Specifying system availability and condition |
System availability |
Here, you can make entries regarding system availability before and after the problem occurs, as well as before and after the task is performed. If the problem has an effect on other systems or system parts, enter the affected object and key for the effect. You can also expand the structure list using This information is not relevant for maintenance requests. |
Entering breakdown data and duration |
Notification orMalfunction, breakdown |
Refer to Entering Breakdown Data and Downtimes |
Calling up location and account assignment data |
Notification orLocation data |
The location and account assignment data originates from the reference object. It is copied from the master data to the notification, where you can make changes if required. The advantage of this is that a change to the master data for the reference object does not automatically change the notification. |
Calling up the scheduling overview |
Notification orScheduling overview |
The scheduling overview, for example, contains the required start and end dates for the notification. These dates can also be calculated automatically on the basis of priorities. |
Changing the reporter of the problem |
Notification orScheduling overview |
Here, you enter the name of the person who reported the malfunction. |
Calling up administrative data |
Goto ® Administrative data |
The administrative data records who created the notification, when, who last changed it and when. |