Loading data from various source systems to BW characteristics can result in errors due to conversion exists. This page gives some information on how conversion exits can affect master data loading.
Conversion Exits are used to ensure that values stored in BW are consistent. You can specify the conversion exit that will be used for each characteristic and convert the data to the correct format during the loading process.
What is a conversion exit
First a definition of a conversion exit. A conversion exit or conversion routine is defined in SAP help as follows;
“Non-standard conversions from display format to SAP-internal format and vice versa are implemented with so-called conversion routines. Conversion routines are identified by a five-position name and are stored as a group of two ABAP function modules. The function modules have a fixed naming convention. The following ABAP function modules are assigned to the conversion xxxxx:
These routines are run automatically each time an entry is made in a screen field when the screen field refers to a domain with a conversion exit. So the data can be displayed in a user friendly format regardless of how it is stored internally.
However, these routines are important in data loading, as a characteristic can be assigned a conversion routine. This means that the characteristic value stored by the infoobject must always be in the internal format specified by this conversion routine.
Loading from datasource
In the datasouce there are two conversion routines specified, one that is entered on the SAP source system which is used in the value help when entering selections for the infopackage. See "SS Conv. Rout." above. The other conversion routine is in the BI system and this is executed on loading depending on the setting you make for “format”. See "Conv. Routine" above. The format field allows you to specify if the data is delived in the internal format or in an external format which must be converted before it can be stored in BW. If the source system is an SAP system, all fields will be set to “internal”.
In most cases, it is useful to have the conversion routine of the datasource field assigned to the mapped infoobject. The conversion routine is automatically assigned to the transformation when the fields are mapped.
As you can see above, the infoobject 0MATERIAL has the same conversion exit assigned in RSD1 as in the datasource field.
It is important to remember that just because the conversion routine is assigned to an infoobject, this does not mean that the data will be converted to the internal format when it is loaded. The conversion should take place at the datasource level or in the transformation.
So, if you are loading data from a source which does not deliver the data in Internal format, you have two options
1 Execute the conversion routine at the datasource level by specifying the format as “External” and the correct routine in the field “Conv. Routines”. This way the data will already be converted when it reaches the PSA.
2. Choose to execute the conversion routine in the transformation.