Data which was previously loaded successfully may result in errors after the upgrade to BW 7.3. This page provides some of the reasons why this can happen, and how to resolve the issue.
Conversion exits are used to convert values from external to internal format and vice versa. Their purpose is to make sure the values are stored in a consistent format to avoid ambiguity, and to present the data in a user friendly way to the front end.
Changes in BW 7.3
With 7.3 systems, the values are checked before the master data tables are updated. Therefore it is no longer possible to update incorrect values which do not comply with the conversion exit. The following are examples of errors that can occur
How the check is implemented
The master data is checked as follows;
internal-1 --> external -- > internal-2
1. The data is loaded from the datasource say it is "internal-1".
2. This value "internal-1" is passed to CONVERSION_EXIT_PRIDB_OUTPUT and the external format value "external" is output
3. This "external" format value is passed to CONVERSION_EXIT_PRIDB_INPUT to again get the internal format value say "internal-2"
4. If internal-1 <> internal-2, then the error message occurs
How to solve the problem
You must load the data in the correct format. You have two options to convert the data if it arrives in BW in the external format
- In the datasource
- In the transformation
Please see the following page for more details on this;
Please note that only the following conversion exits are supported in
alpha, gjahr, numcv, peri6, peri7
If you are using a different conversion exit, you would have to do the conversion in a routine.
You can check the existing data for compliance with the conversion exit using following check in RSRV ; "Check Characteristic Values with Conversion Exit". This is found under the section "All Elementary Test" --> "Master data".