Kontakt

Ansicht
Dokumentation

RJGBANKA - IS-M: Changes to Bank Data

RJGBANKA - IS-M: Changes to Bank Data

rdisp/max_wprun_time - Maximum work process run time   RFUMSV00 - Advance Return for Tax on Sales/Purchases  
This documentation is copyright by SAP AG.
SAP E-Book

Description

This program can be used to perform 3 different steps:

  1. Writing to a sequential file (logical file name: ISP_BANK_AEND see the implementation guide on platform-independent file names). The structure for the file is created in the Data Dictionary under 'RJGBDAEND'. To write to the file, you may need to specify a country (bank country) and the old bank number (or possibly several bank numbers). Each record found for these bank numbers is written to the file. The fields SATZART, ANWENDUNG, KUNDENNR, BLZ_ALT, KTONR_ALT, INH_NAME contain entries. The bank (or the user) should now make entries in the additional fields BLZ_NEU and KTONR_NEU. If no entries are made in these fields, the old account number or bank code are retained (when a file is imported).
  2. Importing a sequential file created previously using this program and now containing the additional data (new bank number and account number).
  3. Changing a bank number (for example, bank merger). Specify a bank number (old) and the new bank code. A sequential file is not created when you do this.

Please ensure that existing billing documents are transferred. Existing billing documents that have not yet been transferred are not changed. The same applies to existing bank returns researches: they too are not changed. The bank data is not transferred to Human Resources (carriers may be created there).

Synchronization with a non-SAP system does not take place. This can be performed by processing a file created by this report using a program in the non-SAP system.

Requirements

Caution: To reduce the run time of the program, database indexes should be created before the program is executed (particularly when dealing with a large volume of data - more than 50000 orders with automatic debit). The indexes should always contain the fields BANKL and BANKN. An index should be created for the following tables: knbk, lfbk, jkpa, jfdfs, jgtbkvw, jgtbkez. These indexes must be deleted afterwards since this could otherwise lead to problems in productive processing. The program should not be executed in parallel with normal online operations or in parallel with billing or settlement.

Output

The program outputs a sequential file in step 1.






CPI1466 during Backup   General Material Data  
This documentation is copyright by SAP AG.

Length: 2418 Date: 20240520 Time: 095244     sap01-206 ( 65 ms )