Description
This report transfers and posts documents from an external system toContract Accounts Receivable and Payable (FI-CA). To do this, itexecutes the following steps:

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

• Reserve and open a reconciliation key
for each program run.
All documents transferred by the program run are posted with thisreconciliation key. After the transfer has been completed thereconciliation key is automatically closed for further postings.

• Post the correct documents.

Data records that contain errors are saved separately, and can betransferred after they have been corrected.
During the test run the program checks the data in the applicationserver file and creates a log; however, no document is posted.

Output
The report outputs the following data in a log:


• Opened reconciliation key


• Number of incorrect documents, their documents, and the lines in the
file

• Number of posted documents and the document numbers created

You can select an extended log.

Preconditions
The document data is transferred by the report from an applicationserver file. Note the 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 (BFKKGR00 structure)


• One document header (structure BFKKKO or ZFKKKO)


• One or more object relation items (structure BFKKOPREL)
(optional)

• One or more card supplement items (structure BFKKOPC) (optional)


• Any number of items or offsetting items from the structures
BFKKOP/ZFKKOP or BFKKOPK/ZFKKOPK

• Several items with locks (structure BFKKOPLS) can follow each
item

• An item with CO-PA data (structure BFKKCOPA) can follow
each offsettingitem (optional)

• Several items with deferred revenues (structure BFKKDEFREV)

can followeach offsetting item (or item with CO-PA data, if used)
You can generate a test file using report RFKKBIBG.
You can include any number of documents in a file. However, you have toensure that you always specify the document header and then the relatedline items.
Each BFKK structure has application and customer includes: SI_BFKK* andCI_BFKK*. These includes enable you to insert application-specificand/or customer-specific fields.
You can display or change transfer files using report
RFKKBIT0.

Customer Structures


• With ZFKK structures you can transfer smaller data structures than the
standard structures.

• Each ZFKK structure may only contain some of the fields of the
corresponding BFKK structure.

• Z* structures do not change with a release change. This means that you
can use the same structure when the standard transport structureschange.

• To generate and check Z* structures, use transaction
FPB9.

• The names of all fields in the customer structure must agree with the
field names of the original structure. All fields must have characterformat.

Number assignment for documents
You can transfer documents with internal or external document numberassignment. Note the following:
Documents with internal document number assignment


• Field BFKKGR00-XEXTBL must be empty.


• Field BFKKKO-OPBEL must be empty.


• Field BFKKKO-BLART must have a document type that is assigned to
number range for mass processing. The document numbers are thengenerated automatically.
Documents with external document number assignment

• Field BFKKGR00-XEXTBL must be "X".


• Field BFKKKO-OPBEL must have an entry.


• Field BFKKKO-BLART must have a document type that is assigned to
number range for individual processing. The document numbers mustcorrespond to the number range.
Documents with external and internal number assignment must not becombined within a file.

Work Breakdown Structure Element (WBS Element)
There are two ways to import the work breakdown structure element in theBFKKOPK record. You either specify the internal form of the number inthe field PS_PSP_PNR or you specify the24 character text form in thefield BFKKOPK-PS_PSP_PNR_TXT. If both fieldsare filled, the fieldPS_PSP_PNR_TXT overwrites the value of PS_PSP_PNR.

Procedure
Analyze the structures specified in the section entitled"Prerequisites". Determine what required data is contained in yourdocuments and what data you have to add.
Write a program that extracts your document data, adds SAP-specific data(if necessary), and exports the data in a sequential application serverfile. Make sure you have read the notes about the data structure writtenunder "Prerequisites".
Call up the report for transferring the document data(RFKKBIB0). Fillthe required fields and select the Process Datafield to transfer thedata from the application server file to Contract Accounts Receivableand Payable.
If the report has determined data records that contain errors (see log),proceed as follows:
Execute the error processing report (RFKKBIBE) and correctthe datarecords that contain errors. Proceed
Call up the report for transferring the document data(RFKKBIB0) again.Fill the required fields and select theProcess Errors field to addthe corrected data records to the appropriate reconciliation key.
If the report is interrupted, you can restart processing by selectingthe Process File after Interruptionfield for the report run. Thereport continues processing from the last data record processed.

Note
You can check and convert the data to be transferred using your ownfunction modules. You can use events910(convert document data) and920(check document data). For more information see the Implementation Guidefor Contract Accounts Receivable and Payable underProgram Enhancements.