Hierarchy
SAP_BASIS (Software Component) SAP Basis Component⤷
BC-CTS (Application Component) Change & Transport System⤷
SCTS_TODO (Package) TODO Checks from the Change and Transport System 
Attribute
| Message class |  |
SCTS_TODO | |
| Short Description |  |
Messages for New TODO Checks | |
| Message Number |  |
001 | |
| Documentation status | Space: object requires documentation |
||
| Authorization check Error Message | |||
| Changed On |  |
20031106 |
Message Text
Help Document
Diagnosis
Messages must have a long text, where possible, to explain possible causes to the user and a course of action.
Good long texts help to avoid problems.
Messages that are flagged as "to be documented later" and messages that are flagged as "self-explanatory" are not checked for missing long texts.
System Response
Procedure
Check whether the messages listed here require a long text. If in doubt, mark them as Self-explanatory.
Caution
Do not write message long texts unless it is absolutely necessary. If your text is essential for the usability and understanding of the function, you must first save it in a raw version, and then notify a colleague in Knowledge Management, who will edit the text and save it in an active version.
To create a long text, proceed as follows:
Call transaction SE91 and specify in the start menu the application area for which you want to enter the message long text. Choose "Display".
The following screen displays all messages for the selected application area. Select the message for which you want to enter a long text and choose "Individual maintenance".
The message is highlighted. Choose "Long text". The Editor appears and you are then able to create the long text.
Save the long text as a raw version.
Inform the technical writer responsible so that they can process the long text and save it as an active version.
Delete any messages that are no longer used.
Procedure for System Administration
History
| Last changed on/by | |
20000413 | SAP |
| SAP Release Created in | 46D |
