Checking Hypertext Structures
You can check hypertext structures with Report RSDOKU01.
Selection screen
You must enter the name of the hypertext structure in the fieldStructure_name. You can enter a specific structure or a valuerange (e.g. SIMG_* or * to check all structures).
Field Checklanguage represents the languages in which thestructures should be checked.
There are three variants:
Explicitly enter one or more languages, e.g. E for English.
Enter * to check each structure in all languages in which it exists.
Leave the field empty to check each structure in its master language.
To check a translation, specify a reference language. The masterlanguage is set as the default value for the reference language. If youare not translating from the master language (e.g. French fromEnglish), you can choose the second option and define English as thereference language.
To simply get the errors with the highest priority (error class 1, seebelow), 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 ofa structure. As default only the faulty documents are output.
Some structures are linked into other structures (e.g. SIMG_ALL). Tocheck all structures and documents that are used in the next higherstructure including the linked structures, you must select the checkboxfor expanding linked structures.
Caution: This is meaningless if you are checking all structures anyway.The documents and structures would then be checked more than once.
NEW-PAGE

Output list

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

List of errors
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 linkedstructure.
Short text - the text line that appears directly in the structuredisplay (text title)
Long text - the actual text. This object is checked most carefully.Most error codes refer to the long text (document).

Error codes (error class 1)
Short text does not exist
Document title missing.
Obsolete link type
A structure is still linked with the obsolete ID TOCX, which is nolonger allowed.
Document does not exist
Long text does not exist in any language.
Document ex.only in x y z
The long text does not exist in the check language but the documentexists in languages x y z.
Document does not contain any text.
The long text has been created, but does not contain any text.
Syntax error in line XY:
The formatting statements in the document are not allowed. Either acharacter is missing at the beginning of a format <. .> or an endformat character <(><)> is missing.
IF/ENDIF error in line XY
The number of IFs and ENDIFs should be the same, but they are not.
Link USJSIMGSKSK incorrect
In the document a link should refer to another object, but the link issyntactically incorrect and cannot be created.
Glossary definition incorrect
Either the glossary term is linked incorrectly or it does not exist inthe glossary.
Include DSSIMGAKSKS incorrect
The included text could not be found. Either there is a typing error orthe text does not exist.
Transaction XXXX does not exist
In the document there is a link to a transaction that does not exist.
Report RSXXXXXX does not exist
A link in the document points to a report that does not exist.

Error code (error class 2 - error comparing with the referencelanguage)
Document is obsolete
The version of the check document is smaller than the version of thedocument in the reference language.
Difference in the text volume
The number of text lines in the two documents differs by more than 30%.
Number of links 01 of 10
The number of links in the document is different from the number oflinks in the master language.

Error code (error class 3 - warnings)
Document has no master language
No language was defined as master language.
Hidden paragraph in line xxx
The comment statement <(><)> may not be used in texts that wereconverted to WinHelp.