Kontakt

Ansicht
Dokumentation

RSDOKU21 - OBSOLETE: Check Report: Check Structure and Long Texts

RSDOKU21 - OBSOLETE: Check Report: Check Structure and Long Texts

Fill RESBD Structure from EBP Component Structure   General Material Data  
This documentation is copyright by SAP AG.
SAP E-Book

You can check hypertext structures with Report RSDOKU01.

Selection screen
You must enter the name of the hypertext structure in the field Structure_name. You can enter a specific structure or a value range (e.g. SIMG_* or * to check all structures).

Field Checklanguage represents the langauges in which the structures should be checked.
There are three variants:

  1. Explicitly enter one or more language, e.g. E for English.
  2. Enter * to check each structure in all languages in which it exists.
  3. Leave the field empty to check each structure in its master language.

To check a translation, specify a reference language. The master language is set as the default value for the reference language. If you are not translating from the master language (e.g. from French to English), you can choose the second option and define English as the reference language.

To simply get the errors with the highest priority (error class 1, see below), you can switch off the check against the reference language. The documents are only checked within the check language in this case.
There is no comparison check (error class 2).

You can also set a further check parameter to output all the objects of a structure. As default only the faulty documents are output.
Some structures are linked into other structures (e.g. SIMG_ALL). To check all structures and documents that are used in the next higher structure including the linked structures, you must select the checkbox for explanding linked structures.
Caution: This is meaningless if you are checking all structures anyway. The documents and structures would then be checked more than once.

A header that specifies how many errors were found in the structure is created for each structure and each check language. The errors are divided into levels: level 1 is always the structure itself, i.e. if you create a structure with Transaction SO70 and link document CHAPSTEFAN, this document is in the 1st level of this structure. All the documents in the other levels are either linked to a document of the 1st level as a link or as include. You can see which document this is - you must be able to trace the path to the error - from how the document name is indented.
The number of incorrect lines is only a rough guide and specifies approximately how many text lines must be revised.

The output list has 5 columns: The columns contain the document name, type (how and in which line the document is linked L-link, I-include), master language of the document, number of lines, and the error code.


There are the following objects:

Structure - this can be the hypertext structure itself or a linked structure.

Short text - the text line that appears directly in the structure display (text title)

Long text - the actual text. This object is checked most carefully. Most error codes refer to the long text (document).

  1. Short text does not exit
    Document title missing.
  2. Obsolete link type
    A structure is still linked with the obsolete ID TOCX, which is no longer allowed.
  3. Document does not exist
    Long text does not exist in any language.
  4. Document ex. only in x y z
    The long text does not exist in the check language but the document exists in languages x y z.
  5. Document does not contain any text.
    The long text has been created, but does not contain any text.
  6. Syntax error in line XY:
    The formatting statements in the document are not allowed. Either a character is missing at the beginning of a format <. .> or an end format character &lt;/&gt; is missing.
  7. IF/ENDIF error in line XY
    The number of IFs and ENDIFs should be the same, but they are not.
  8. Link USJSIMGSKSK incorrect
    In the document a link should refer to another object, but the link is syntactically incorrect and cannot be created.
  9. Glossary definition incorrect
    Either the glossary term is linked incorrectly or it does not exist in the glossary.
  10. Include DSSIMGAKSKS incorrect
    The included text could not be found. Either there is a typing error or the text does not exist.
  11. Transaction XXXX does not exist
    In the document there is a link to a transaction that does not exist.
  12. Report RSXXXXXX does not exist
    A link in the document points to a report that does not exist.
  1. Document is obsolete
    The version of the check document is smaller than the version of the document in the reference language.
  2. Difference in the text volume
    The number of text lines in the two documents differs by more than 30%.
  3. Number of links 01 of 10
    The number of links in the document is different from the number of links in the master language.
  1. Document has no master language
    No language was defined as master language.
  2. Hidden Paragraph in line xxx
    The comment statement &lt;ZV&gt; may not be used in texts that were converted to WinHelp.

Description

Requirements

Output

Example






rdisp/max_wprun_time - Maximum work process run time   ABAP Short Reference  
This documentation is copyright by SAP AG.

Length: 5591 Date: 20240520 Time: 141248     sap01-206 ( 125 ms )