Programme SAP RFBVALL_0 - Country-specific transfer of bank data

Purpose
This report is used for transferring a bank directory to the R/3 System(BNKA table) that was stored in a country-specific file.

Prerequisites
The report imports a file in the ASCII format. The length of a line isrestricted to a maximum of 1023 bytes. The following formats aresupported:

  • Austria - AT1, AT2

  • Canada - CA1

  • Great Britain - GB1

  • South Africa - ZA1

  • Denmark - DK1

  • Spain - ES1

  • Switzerland - CH1, CH2

  • Germany - DE1, DE2,
    • DE3, DE4
    • Italy - IT1

    • USA - US1

      • You can use this report to import other file formats for other countriesalso. You can use the sample function moduleFILL_BNKA_FIELDS_SAMPLEfrom the function group BAUP as a template.
      Copy the function moduleFILL_BNKA_FIELDS_SAMPLE.
      Write your own statements in the copied function module. Note that as auseful part of the module, the UPLOAD_FILES function module must becalled up.
      Save and activate your module.
      Enter the required Customizing settings(transaction BA01).
      You receive a bank directory from your house bank. If this is notpossible, SAP note 132012 provides addresses for finding bankdirectories.

      Features
      The report compares the data from the input file with the existing datain the R/3 System. The following activities take place:
      If the bank data does not exist in the R/3 System, the data is takenfrom the input file. Not all data fields are transferred fully, butnormally, the field lengths used are sufficient and field contents arenot lost.
      The following information is transferred:
      Bank name (the first 60 bytes) to the BNKA-BANKA field.
      Town and postal code (the first 35 bytes) to the BNKA-ORT01 field.
      Street (the first 35 bytes) to the BNKA-STRAS field.
      Bank key (complete) to the BNKA-BANKL field.
      Bank number (complete) to the BNKA-BNKLZ and BNKA-BANKL fields.
      SWIFT Code (complete) to the BNKA-SWIFT field.
      Branch (the first 40 bytes) to the BNKA-BRNCH field.
      Region (3 bytes) to the BNKA-PROVZ field.
      If there is a bank in the input file, that has a deletionflag in the R/3 System, the deletion flag is reset.
      If there are banks in the R/3 System (BNKA table) that are not in theinput file, these are assumed to no longer exist. If theSet Deletion Flagparameter has been activated, these are assigned the deletion flagand can then be reorganized.
      No banks are deleted. The following programs are used for this purpose:
      Reset Bank Data (SAPF023)
      Archiving of Bank Master Data (SAPF061)
      Selection
      You can start the report in the test mode (without updating the BNKAtable) or in the update mode (this does update the BNKA table).
      You can restrict the number of records imported from the file for testpurposes. The data is then only imported up to the selected number.
      Output
      The system displays statistics that show how many banks were created orchanged.
      A detailed list is output if you have requested this on the selectionscreen. This contains all the banks that were successfully changed orinserted.
      Importing the data to a unicode system ('Codepage'parameter)
      When a text file is uploaded into a unicode system, it is assumed thatthe character set (code page) of the text file is the same as thecharacter set used in the system. If this is not the case, the dataneeds to be recoded during the import. The information on the characterset for the file must then be specified in the codepage parameter. Inmost cases, you can specify the codepage 1100 (or a similar one) thatcorresponds to the 7 bit ASCII coding. The list of the character setsdefined in the system is provided in the input help (F4) for thecodepage parameter.
      There are three options for importing the text file correctly to aunicode system:
      1. Direct uploads from the presentation server are recommended only forsmaller datasets.
      2. Upload from the application server, to which the file was transferredin unconverted form (for example, using FTP with the BINARY parameter).
      3. Upload from the application server, to which the file was transferredand converted to the target codepage - in this case, you do not use thecodepage parameter.
      If the data import is interrupted with a message that the file is notcorrect, or if certain special characters such as umlauts areincorrectly displayed, or if unusable data is imported, then thespecified character set is incorrect. The correct character set for thefile must then be requested from the file author for example.
      Do not use the codepage parameter in a non-unicode system.

380410RFBVALL_0: BC numbers with leading zeros