Description
This report transfers data and creates one or more lots for manuallyissued checks.
To do this, it executes the following steps:

• Read the specified application server file and check the data contained
therein

• Create one or more lots for manually issued checks, as long as the data
records are correct

• Close and post the created lots as long as the relevant indicator is set

Data records that contain errors are saved separately, and can betransferred after they have been corrected.

Output
The report outputs the following information in a log:


• The number of data records containing errors, their numbers, and their
lines in the application server file

• List of the lots created for manually issued checks and their status

You can display an extended log.

Preconditions
The report transfers check data from an application server file. Notethe following for this file:


• All fields must have character format.


• Every line can only contain one structure.

The report expects the following for each file (take note of thesequence):

• One file header record (structure BFKKCMGR00) per file


• One lot header (structure BFKKCMK)


• Any number of items (structure BFKKCMP)


• Any number of additional payees for each item (structure
BFKKCMP2P)
You can include data for any number of lots for manually issued checksin a file. However, you have to ensure that you always specify the lotheader first and then the related lot items.
You can generate a test file using reportRFKKCMDG.
You can display or change transfer files using reportRFKKCMDA.

Customer Structures
The name of a customer structure used for the data transfer is createdas follows: Z + name of original transfer structure. Customer structurescan only contain fields of the original structure.
To ensure that the transfer is version-independent, we recommend thatyou use Z structures for the data transfer. Z structures also enable youto remove fields that you no longer require from the structure andtherefore simplify the program for entering the file.
To simplify the generation of customer structures, you can use reportRFKKCMZG or transaction FP55.There you can check the status for eachstructure displayed or generate the structure again.

Procedure


• Analyze the structures specified in the section entitled
"Prerequisites". Determine what required data is transferred from yourlegacy system and what data you have to add.

• Write a program that executes the following steps:

Read data that you get from the legacy system.
Extract data that is relevant for the lot for manually issued checks,transfer it to an application server file and enhance it.
Make sure you have read the notes written in "Prerequisites".

Example


• You enter the information for manually issued checks in your legacy
system. This includes information about the issue and about the masterdata of the business partner to be posted to. You now have to extractthe data relevant for the lot for manually issued checks, enhance it(for example, by specifying a reconciliation key), and save it in theformat described in "Prerequisites".

• Call up the report for transferring payment data
(RFKKCM00, transactionFP51). Fill the required fields and select theProcess Filefield totransfer the data from the application server file to a payment lot.
If the report has determined data records that contain errors (see log),proceed as follows:

• Execute the error processing report
(RFKKCMFA, transaction FP52) andcorrect the data records that contain errors.

• Call up the report for transferring payment data again (RFKKCM00,
transaction FP51). Fill the required fields and select theProcesserrors field to add the corrected data records to the correspondinglot for manually issued checks.
If the report is interrupted, you can restart processing by selectingthe Process File after Interruption field for the report run.Thereport continues processing from the last processed data record.