
Generate Flow Data
Use
This report program copies the transactions with Order and Posted settlement status to the new transaction management functions. It does not convert transactions that have been reversed and deleted. The program creates a new transaction with a new number for each 'old' transaction and saves the number assignment. You have the option of branching from the new transaction to the old transaction.
Integration
This report program is part of the conversion program for the new securities transaction for Release 4.6A. This conversion program consists of five report programs. We recommend that you run them in the following order:
Prerequisites

We recommend that you settle and/or delete these transactions before you upgrade to 4.6A.
After upgrading to 4.6A, the following restrictions apply to the old functions:
Features
Selection criteria
Test run |
Carry out a test run first. A test run executes the report program, but does not make any changes to the database. The test run allows you to recognize errors and correct them before you execute the update run. |
Update run |
Only execute the update run if no errors occurred in the test run. |
Show log details |
If you set this indicator, a detailed log is displayed showing how the old transaction numbers have been assigned to the new ones. |
Output
When you convert a transaction, the system first determines the flows for the existing activities and then creates a new transaction with a new number for each old transaction. It saves the assignment of the old and new number.
The historic status is also displayed for each transaction. Existing transactions and orders are converted according to the following logic:
Transactions with 'old' status |
are transferred to activity categories |
Order |
Order |
Expired order (expiration indicator set) |
Order - Expiration |
Settlement |
Contract - Settlement |
Order - Settlement |
Order - Contract - Settlement |
Execution - Settlement |
Contract - Settlement |
Order - Execution - Settlement |
Order - Contract - Settlement |
If a settlement exists, the payment details are derived from the payment-relevant data of the main flow. If no settlement exists, the payment details are not filled.
The detailed log shows you how the old transaction numbers have been assigned to the new numbers.
An error log is displayed if any errors occurred during the conversion. We recommend that you perform a test run first. If errors occur during the test run, you can correct them using the error log. Only perform the update run when you have successfully completed the test run.

Use the report program Individual Conversion of a Transaction (RFVW_FWTR_VTBPHA_SINGLE) to check whether the transactions you corrected can now be converted successfully. Using this report program, you can carry out a test run for the corrected transaction (it does not convert the transaction)
Once you have corrected all the errors and carried out the individual check for the corrections, we advise you to perform a test run before the update run to make sure all the errors have been eliminated.
Result
All the existing settled transactions and all the orders have been migrated to the new transaction management functions. You can now only edit the transactions using the new transaction management functions.
The display function from the 'old' transaction management function is the same. When you call up a converted transaction using the new transaction management function, the 'old' transaction number is displayed in the status row. From the display screen for the new transactions, you can branch to the underlying old transaction by choosing Environment ® Display old transaction.
Memos and change documents are not converted. However, you can access them using the data from the old transaction.