Bank directoy method to choose

[Former Member]

Hi Experts,

As per project reauirement, i need to import bank directory. I am seeing two options.

1/. Using BAPI_bank_create and BAPI_bank_change. through this i can import bank directory.

2:. is SPRO, through RFBVBIC2 or RFBVALL_0.

The reauirement is the bank directory is coming from middleware and not directly from bank.

Please suggest which one to use for importing bank directory from the mentioned methods.

Regads,

CV

[ivor_martin]

Hi CV,

I would suggest have the middleware place the file on the Application server for RFBVBIC_0 to pick up from a pre-defined directory. It has robust validations in place. The file path can be specified in the parameters for RFBVBIC_0.

Note your middleware must format the file in the format specified in the documentation for RFBVBIC_0.

Regards,

Ivor M

[Former Member]

Hi,

Thanks for the quick response. Please share field selection to be made for running this by T.code BIC2 / RFBVBIC2

Regards,

CV

[ivor_martin]

Hi,

You have better instructions if you use transaction BAUP (Thats program name RFBVALL_0).

Here are the instructions with the file format and sample function module as well (see below).

Regards,

Ivor M.

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 is restricted to a maximum of 1023 bytes. The following formats are supported:

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 countries also. You can use the sample function module FILL_BNKA_FIELDS_SAMPLE from the function group BAUP as a template.

1. Copy the function module FILL_BNKA_FIELDS_SAMPLE.

2. Write your own statements in the copied function module. Note that as a useful part of the module, the UPLOAD_FILES function module must be called up.

3. Save and activate your module.

4. Enter the required Customizing settings (transaction BA01).

You receive a bank directory from your house bank. If this is not possible, SAP note 132012 provides addresses for finding bank directories.

Features

The report compares the data from the input file with the existing data in the R/3 System. The following activities take place:

5. If the bank data does not exist in the R/3 System, the data is taken from the input file. Not all data fields are transferred fully, but normally, the field lengths used are sufficient and field contents are not lost.

The following information is transferred:

a) Bank name (the first 60 bytes) to the BNKA-BANKA field.

b) Town and postal code (the first 35 bytes) to the BNKA-ORT01 field.

c) Street (the first 35 bytes) to the BNKA-STRAS field.

d) Bank key (complete) to the BNKA-BANKL field.

e) Bank number (complete) to the BNKA-BNKLZ and BNKA-BANKL fields.

f) SWIFT Code (complete) to the BNKA-SWIFT field.

g) Branch (the first 40 bytes) to the BNKA-BRNCH field.

h) Region (3 bytes) to the BNKA-PROVZ field.

6. If there is a bank in the input file, that has a deletion flag in the R/3 System, the deletion flag is reset.

7. If there are banks in the R/3 System (BNKA table) that are not in the input file, these are assumed to no longer exist. If the Set Deletion Flag parameter has been activated, these are assigned the deletion flag and 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 BNKA table) or in the update mode (this does update the BNKA table).

You can restrict the number of records imported from the file for test purposes. The data is then only imported up to the selected number.

Output

The system displays statistics that show how many banks were created or changed.

A detailed list is output if you have requested this on the selection screen. This contains all the banks that were successfully changed or inserted.

Importing the data to a unicode system ('Codepage' parameter)

When a text file is uploaded into a unicode system, it is assumed that the character set (code page) of the text file is the same as the character set used in the system. If this is not the case, the data needs to be recoded during the import. The information on the character set for the file must then be specified in the codepage parameter. In most cases, you can specify the codepage 1100 (or a similar one) that corresponds to the 7 bit ASCII coding. The list of the character sets defined in the system is provided in the input help (F4) for the codepage parameter.

There are three options for importing the text file correctly to a unicode system:

1. Direct uploads from the presentation server are recommended only for smaller datasets.

2. Upload from the application server, to which the file was transferred in unconverted form (for example, using FTP with the BINARY parameter).

3. Upload from the application server, to which the file was transferred and converted to the target codepage - in this case, you do not use the codepage parameter.

If the data import is interrupted with a message that the file is not correct, or if certain special characters such as umlauts are incorrectly displayed, or if unusable data is imported, then the specified character set is incorrect. The correct character set for the file must then be requested from the file author for example.

Do not use the codepage parameter in a non-unicode system.

[Former Member]

hi,

thanks for the responce.