Diagnosis
There are two typical known causes that lead to corrupt DART extractfiles.
Moving DART extract files between different operating systems
DART extract files are stored as text files. Unix and Windows NT use adifferent number of record termination characters in text files. Ifextract files are copied between such systems via ftp in text mode, thefiles are converted to the standard of the target file system, i.e.,record termination characters are either added or removed. Theconsequence is that file offsets that are stored within the extractfiles are not valid anymore, and DART cannot query such files.
Data segment text fields that include line break characters
When documents are posted via batch input or other automatic processes,text fields may include line break characters. If these characters arenot removed during extraction, the data record is effectively splitinto two records in the extract file, which in turn leads to problemswhen querying the extract.

Procedure
If the problem that has occured is related to a file transfer, you canconfirm that such a conversion took place by comparing original andtarget file sizes. After a conversion, file sizes will be different. Tocorrect the problem, ftp the extract files in binary mode, or copy themdirectly. Make sure that file copies have exactly the same number ofbytes as the original files.
If the problem is one of additional line break characters in a segmenttext field, run the report RTXWCHK3 to locate the first such record. Tocorrect the problem, either alter the line-item or report to SAP thesegment which requires a filter on the text fields. Currently, DARTremoves line break characters for FI and CO document items.
Run report RTXWCHK3