Use
The RFBIKR00 batch input program is used for processing the followingdata:

• Creating and changing vendor master data


• Creating bank master data

Note
Structures:


• Information which affects the entire batch input session is defined in
the session prefix.

• Information which applies to the whole transaction is defined in the
header record. This includes, for example, the transaction code and thekey fields.

• Finally, a batch input structure was created in the Data Dictionary for
every vendor table for which batch input should be possible.
Each structure is identified by the record type and possibly also thetable name.
The structures are in detail:

• BGR00 record type 0 session prefix


• BLF00 record type 1 header data for vendors


• BLFA1 record type 2 general data for vendors


• BLFB1 record type 2 company code data


• BLFB5 record type 2 dunning data


• BLFBK record type 2 bank data (including bank master data)


• BLFBW record type 2 withholding tax data (extended withholding tax)


• BLFEI record type 2 customs tariff preferences


• BLFLR record type 2 supply regions


• BLFM1 record type 2 purchasing data (purchasing organization level)


• BLFM2 record type 2 purchasing data (alternative data retention level)


• BLFZA record type 2 alternative payees


• BWYT1 record type 2 vendor sub-range


• BWYT3 record type 2 partner functions

Country-specific structures:

• BLFAT record type 2 tax categories (South America)

For each field which is transferred in batch input structure, you mustdecide whether the value of the field is initial (for example, thefield should be reset to the initial value) or whether no batch inputat all is necessary for this field.
That means a special character must be specified which has thefunction: "No batch input for this field".
This special character is the character "/" by default.
If the special character "/" is not to be used, you can specify anotherspecial character in the session prefix in field BGR00-NODATA whichwill carry out this function.
Before filling the batch input structure, each field of the structures(with the exception of the session prefix BGR00) must be "prepared" forthe beginning of field with this special character.
The fields of the structures refer to data elements of the fields ofthe original tables. However, numeric and packed fields are anexception. These need separate data elements of category CHAR for batchinput since packed fields cannot be "initialized" with a specialcharacter.
This means that amounts can be transferred to the interface with adecimal point.
End of record marker:
If a batch input structure is later extended, the new end of thestructure is indicated by a special field (SENDE). If you are alreadyworking with the new, extended structure, fill this field with theNODATA special character when "initializing" the structure. As aresult, the system can recognize whether the data is based on the oldor the new structure when importing the structure.
INCLUDE FI_APAR_RFBIDE00_RFBKR00 OBJECT DOKU ID TX
Special fields in the session prefix:
The batch input session name must be entered in the session prefix(BGR00-GROUP). Sending a second session prefix causes the currentsession to be closed and a further session to be opened.
The special character BGR00-NODATA can be transferred in the sessionprefix (see above).
A block date can be transferred in the session prefix (BGR00-START). Ifthis date is set, it must have the format "YYYYMMDD".
Additional address fields:
There are additional address fields available due to linking thecustomer and vendor master and the respective contact persons tocentral address management. This additional address information isstored in central address management's own tables rather than beingkept in the actual master tables (KNA1 for the customer master, LFA1for the vendor master, KNVK for the contact persons).
A separate transfer run via the ALE interface is needed to transferthis additional address information. This run should be before thetransfer run for master data.
See Transfer of address data.
If you use number ranges with internal number assignment when creatingnew customer and vendor masters, the number which is used to identifythe master object in the system must be determined beforehand due toaddress information and master data being transferred separately.
You can determine the numbers using the following BAPIs:

• BAPI_VENDOR_GETINTNUMBER (for the vendor master)


• BAPI_CUSTOMER_GETINTNUMBER (for the customer master)


• BAPI_PARTNEREMPLOYEE_GETINTNUM (for the contact persons)

Master data fields for which there is a counterpart in central addressmanagement (such as name, street, or telephone number) continue to befilled in the actual master tables. The formatting for these fieldswithin central address management is different from the originalformatting of the fields without the link to central addressmanagement. We therefore recommend that you only transfer the data forsuch fields when transferring central address management addressinformation.
Programs:

• RFBIKR00 Executable batch input program


• RFBIKR01 Basic program with processing logic


• RFBIKRG0 Generation program

The RFBIKRG0 generation program uses the basic RFBIKR01 program andwrites the source code contained in it together with the newlygenerated source code to the RFBIKR00 batch input program.
Source code is generated by the generation program for the "fieldtransports" per screen and per input field.
Transactions supported:
The following central transactions are supported in the presentversion:

• XK01 Create vendor


• XK02 Change vendor


• XK05 Block/unblock vendor


• XK06 Set/reset vendor deletion flag

With the creation and change transaction, transferred block fields ordelete flags are also processed. The system then goes to the additionalscreens provided for this.
Only block fields can be processed using block transaction XK05.
Only deletion flags can be processed using delete transaction XK06.
For all bank data which is to be processed, the BLFBK structure must betransferred. If an existing piece of bank data is to be deleted, theBLFBK-XDELE field must be selected.
If the bank master data for bank data is new, the bank can also betransferred in the BLFBK structure. The new bank master data is thencreated when processing the session.
You can change the key fields "Bank country key" BANKS, "Bank key"BANKL, and "Bank account number" BANKN for bank details (table LFBK)only by creating the new bank details and deleting an old set of bankdetails.
By selecting the BWYT1-XDELE field, you delete a vendor sub-range.
By selecting the BWYT3-XDELE field, you delete a partner function.
By selecting the BWYT3-XDEKO field, you delete all partner functions ina data retention level.
By selecting the BLFLR-XDELE field, you delete a supply region.
By selecting the BLFM2-XDELE field, you delete the purchasing data inan alternative data retention level.
By selecting the BLFEI-XDELE field, you delete the customs tariffpreference.
For every withholding tax type to be processed, the structure BLFBWmust be transferred. If an existing withholding tax type is to bedeleted, the BLFBW-XDELE field must be selected.
The alternative payees can be transferred in the BLFZA structure aseither company code-specific or cross-company code. By entering a BLANKin the BLFZA-BUKRS field or by selecting the NODATA indicator, you candefine an alternative payee as cross-company code. By selecting theBLFZA-XDELE field, you can delete the alternative payee.
The following applies for retail users:
You do not have to enter a partner number for contact persons (internalnumber assignment). If however, you do enter a number, this must not beassigned for another contact person as this leads to a programtermination. If you select the field BKNVK-XDELE, the contact person isdeleted.