Kontakt

Ansicht
Dokumentation

RJBR_GENTRANS_DBERBIS - Migration Report for Generic Transactions

RJBR_GENTRANS_DBERBIS - Migration Report for Generic Transactions

Vendor Master (General Section)   General Material Data  
This documentation is copyright by SAP AG.
SAP E-Book

Purpose

The "calculate to" date (DBERBIS field) in the cash flow table for generic transactions is interpreted as an inclusive value (calculate through).

When you upgrade your system, or change the release, you can use the migration report RJBR_GENTRANS_DBERBIS to check the date field DBERBIS, and if required correct the existing generic transactions.

If corrections are required, the system takes into consideration all the relevant interest flows (cash flow indicator 1, 8, or 9). Date field DBERBIS is then changed to DBERBIS-1.

Integration

In addition to correcting the flow data of generic transactions, you can also use this migration report to correct the flow data of the versions of the generic transactions or of the datasets in the data pool. Versions and datasets in the data pool are corrected in the same way as the generic transactions.

Prerequisites

Table JBRDBKOMIG is provided for the migration of existing generic transactions.,,

You must first fill this table with the existing generic transactions by means of the initialize activity. If this table is already filled, then the migration status is frozen. This means that this migration report ignores any transactions that have since been created in the system.

Features

Selection

You can select the generic transactions either by their internal or external numbers. If you do not enter any selection criteria, then the system selects all relevant generic transactions.

Standard Variants

We recommend that you perform migration inclusive of versions and data pool datasets. Therefore this is the default setting. However, if you do not want to migrate versions and data pool datasets, you must deselect these indicators. You cannotthen migrate versions or data pool datasets at a later point in time.

The default package size for processing is 100. If required, you can change the package size to suit your system environment. If your generic transactions contain a lot of cash flows (for example, over 200), then you should choose a package size of less than 100.

Output

The system displays a list that contains the number of generic transactions that were selected and processed.

If the check process results in errors or warnings, then the system displays the relevant internal numbers of the generic transactions affected. You must then check these transactions manually, and change them as required. To display generic transactions for which errors were found or warnings generated, double click on the transaction in the results list.

Activities

  • Initialize
This is the first step, which can be performed once only. The system fills the migration table JBRDBKOMIG with the current position of generic transactions. If the selection criteria include internal or external numbers, then these are ignored.
The system sets the migration status in table JBRDBKOMIG to 'I' (= initialized).
If initialization aborts, contact SAP.
  • Check and Correct
The report checks whether the interest rate periods in the cash flow table for generic transactions overlap by 1 day (see the example below). If this is the case for all the relevant interest flows in thecash flow table for the generic transaction, then the migration report corrects field DBERBIS to DBERBIS-1.
The system sets the migration status in table JBRDBKOMIG to 'C' (= corrected).
If the generic transaction is already correct, then the system confirms this by setting the migration status to 'S' (= confirmed).
If the cash flow table contains only one interest flow, then the system issues a warning. In this case, and if an error occurs, the generic transaction is not corrected. The migration status is not changed.
If the "Ignore Warning and Correct" indicator is set in the process flow control section, then the system ignores the warnings and corrects the transactions. The system sets the migration status in table JBRDBKOMIG to 'C' (= corrected).
  • Correct without Checking
The selected generic transactions are corrected without any additional checks being made. This means that the field DBERBIS is always set to DBERBIS-1 in the interest flows.
The system sets the migration status in table JBRDBKOMIG to 'C' (= corrected).
  • Confirm without Changing
If the generic transactions are already correct, then these can be confirmed without being corrected so that they are no longer selected in the migration process.
The system sets the migration status in table JBRDBKOMIG to 'S' (= confirmed).
  • Reverse
You can reverse the migration if required. However, the initialize activity cannot be reversed, though you can reverse the other activities. If you reverse the migration, the system initializes the affected generic transactions automatically so that these can be migrated again.

Example

If both the end of the interest rate period of the first cash flow, and the start of the interest rate period of the next cash flow both fall on 12/31/2003, then the periods overlap by 1 day.






CL_GUI_FRONTEND_SERVICES - Frontend Services   BAL Application Log Documentation  
This documentation is copyright by SAP AG.

Length: 5895 Date: 20240520 Time: 061943     sap01-206 ( 158 ms )