Description
Program RFFBWG10 transfers failed payment transaction data from UNIX,DOS or OS/2 files and writes them into a table for further processingusing report RFBITB01.

File types:
The report distinguishes between several country-specific andapplication-specific file types. You specify the file type on theselection screen. The specified file which is to be transferred mustcorrespond exactly to the predefined structure. If none of the filetypes specified are suitable, then you must define a new file type.This can only happen within the framework of a modification.

UNIX file or DOS or OS/2 disk:
Via the selction screen you also determine whether the file is to befound in the UNIX file system (UNIX file) or on disk (OS/2 or DOSfile).
If the file is on disk, the report must be started on a PC where therelevant disk must have been inserted into the drive. You specify thedrive and the file name with the path on the selection screen.
You must always enter a UNIX file name (with path). If the file is aUNIX file, the file is to be found under this name. Otherwise the filefrom the disk is stored temporarily under this name. The file is alwaysstored temporarily in this case with line separation (text mode).

Line separation:
Using this switch on the selection screen, you specify whether thecurrent file is with or without line separation. If this is not known,you should look at the file in the system editor or carry out test runswithout transferring data. You can easily tell by looking at theprintout of the file whether the correct option was chosen for the testruns.

Precondition
If you transfer data from disk, then you should start the report on aPC.

Output
As well as the optional output of the file, the report also lists allincorrect and non-transferred lines.
The number of records read generally corresponds to the number ofrecords transferred since header and footer records are nottransferred.