General Texts as Text Modules

Procedure

If you want to be able to use a section of text more than once, you can store it in the class "General texts". You can then insert it wherever you require with an INCLUDE statement. General texts are documents which are not linked to any object. They are stored in the system as independent system objects and are also transported as such. Proceed as follows:

Select document class "General texts" in the documentation maintenance transaction initial screen.
Enter a name. Proceed as follows:
- 1. position: "Y" or "Z" (indicates customer's own "General texts").
- 2. 2nd and 3rd position: Abbreviation of the document class
- 4. position: underscore "_"
- from the 5th position onwards: meaningful name for the contents of the document.
Example

NA_CHECK_ENTRY

The umlaut or other special characters, apart from the underscore "_", may not be used.

Note

General text modules can be used by anyone. You should give your text modules meaningful names as this will enable them to be used effectively.
Enter your text and save the document.
Include the document you have created at the relevant place in your text:
- Position the cursor on the desired location.
- Choose Include Text Documentation.
- Enter the name of the module in the dialog box.
- Check that the text was correctly included by displaying the screen with Documentation Screen Output.
  
  Note
  
  Avoid using headings as this restricts the general usability of the text.

If you work in a multilingual system and documentation must be translated, note that general texts are translated as independent units, so they should contain no reference to the text that precedes or follows them.

General texts must be independent logical units of information. Avoid using headings as this restricts the general usability of the text. Generally, texts stored in text modules must therefore be logical units of information which can stand on their own.