Kontakt

Ansicht
Dokumentation

Account Balancing After Legacy Data Transfer ( RELNBANK_402_BKK_KTOABSC )

Account Balancing After Legacy Data Transfer ( RELNBANK_402_BKK_KTOABSC )

BAL Application Log Documentation   rdisp/max_wprun_time - Maximum work process run time  
This documentation is copyright by SAP AG.
SAP E-Book

Short text

Account Balancing After Legacy Data Transfer

Description

In general, account balancings of the legacy system are unknown to the Bank Customer Account system.

The following changes apply as of release 4.02 A, to ensure a smooth transition from the legacy system to the Bank Current Account system:

  • If you choose Account -> Additional data in the account master in the section on legacy data transfer, you will find two new fields: the go-live date and the balance transfer date. These fields must contain entries during legacy data transfer. If the accounts were already transferred or manually created, you do not have to retrospectively make entries in these fields. For this, a report (RFBKCPBL) is available. Balancings that occur in the time period from 'Balance transfer date' to 'Go-live date' are not posted.
  • Payment items for time periods in which value dates in the past before the 'Go-live date' are to be permitted, must be transferred. If there is a large number of items, these can also be summarized per posting date and value date. If there are item charges or dispatch expenses, you have to set up the corresponding counters before the items are transferred. If the items are summarized and transferred per posting date and value date, the counters are updated for less items accordingly. This would mean that the item charge in BCA inevitably differs from that in the legacy system. However, this is not critical, as no adjustment postings for charges are made.
  • For balancing, the field 'Next date' must show the end date of the oldest period for which a balancing without posting is to be executed. Assuming legacy data transfer is planned for October 1, the third quarter is to be balanced without posting. In this case, you must enter September 30 in 'Next date'.
  • You must also maintain the conditions for the time period from the balance transfer date to the go-live date. You must ensure that the conditions in BCA coincide exactly with those in the legacy system, as only in this way will the calculation results be identical.
  • The balancings before the 'Go-live date' must be executed. The system recognizes that these balances are before the go-live operation and therefore does not post the balancing. The account balancing before the go-live updates the account balancing tables required for an adjustment of this period. No legacy date transfers take place before account balancings and value date transaction figures.

This solution means that it is not absolutely necessary to execute an account balancing in the legacy system before the go-live date. However, you will normally execute an account balancing in the legacy system before going live with BCA.






Vendor Master (General Section)   CL_GUI_FRONTEND_SERVICES - Frontend Services  
This documentation is copyright by SAP AG.

Length: 2978 Date: 20240426 Time: 073410     sap01-206 ( 79 ms )