SYMPTOM:
After importing an OLAP Cube from SAP BW, the metrics in the cube have unintelligible names, which can be seen in the Cube Mapping tab of the OLAP Cube Catalog, as shown below:
However, when editing the query cube definition in SAP Business Explorer Query Designer, the corresponding key figures have the expected names, as shown below:
CAUSE:
SAP BW presents localized information, including object names, to clients based on the language specified in the client connection. If a cube was created under one language, but was imported into Strategy using a different language, the SAP BW system may not have localized object names for all objects.
If this happens with key figures in the cube, SAP BW reports an internal ID code to ODBO clients as the object name. Strategy Developer 9.4.x-10.x receives no other identifying information for the key figures, so it has no choice but to name the imported objects according to the IDs.
ACTION:
Users should ensure that the language specified in the Strategy database connection to the SAP system matches the language under which the cube was created. The language is specified along with the database connection parameters:
Once a cube has been imported under one language, it cannot be updated with a different language setting. Consequently, if a user changes the language setting and attempts to go back into the OLAP Cube Catalog to update the cube structure, the following error will result.
Importing operations from an external source are no longer allowed when the connection language has been changed (by the Strategy user).
Therefore, a new database instance must be created, with the correct language, and the cubes must be reimported. It is not possible to switch OLAP Cube reports from one database instance to another; thus, care should be taken to insure the proper language setting when initially importing the cube to avoid the need to re-create reports and other supporting objects.
