Knowledgebase: Enterprise
Extracted Data Lines are not all Converted correctly by Selected Entity Conversion Table
Posted by Priya Doyle on 16 February 2011 11:47 AM

Extracted Data Lines are not all Converted correctly by Selected Entity Conversion Table

 Modified 13-OCT-2010     Type PROBLEM 

Applies to:

Hyperion Enterprise - Version: and later   [Release: 5.1 and later ]
Information in this document applies to any platform.


When a Data Extract is made using an old Entity Conversion Table not all lines of  the extract are converted properly i.e. they are not converted at all. Some lines do convert correctly.

During past maintenance of the application entities within the Entity conversion tables were deleted. Prior to deletion of Entities, the Entity Conversion Tables were not purged of the redundant Entities.


The Entity Conversion Tables contain Entities that are no longer in the Application and which were never purged for the Conversion Tables.


The cause of the instability of the Entity conversion table showed that there were previously deleted entities in some Conversion tables that were not visible in the Oracle Hyperion Enterprise GUI but manifested themselves as 'Invalid Enterprise Entity' messages when the extract of Conversion Tables was loaded.

Two solutions to this problem are available.

Before proceeding ensure no users are working in the application and you have a valid back-up.

Solution A delete and re-create existing conversion tables

A1, Navigate to the Application Module from the Oracle Hyperion Enterprise Desktop.
A2, Select TASK
A4, Deselect the 'ENTIRE APPLICATION Check Box of the Extract Application Window.
A6, Back at the FILE tag , give the file a suitable name.
A7, Select OK and allow the extract to run.
A8, Access the Extract file and open in a suitable TXT file editor (Notepad.exe  or similar)
A9, The format of the file will be as follows for an extract conversion table . 
NOTE  For an import conversion table the External/Internal conversion is reversed.

[Econv=conversion table name   !Description

External Entity  !Enterprise Entity 
External Entity2 !Enterprise Entity2

etc etc.

The second column after the delimiter contains the entities that MUST be available in the Application. If they are not the error is produced.

Each of these 'Missing Enterprise Entities' need to be corrected and changed to valid Enterprise Entities or removed.

Hint :- To test the file for non existed Entities, load the Extract file of Conversion Tables file and trap the errors that are generated from the error.log file.

A10, Once the extract file is cleaned proceed as follows.
A11, From the Entities Module
A12, Select NAVIGATE
A13, Select Entity Conversion Tables.
A14, Open Any Table by highlighting it and pressing OK
A15, From the File Menu , Select and delete all Entity Conversion Tables. (Removing them from Database Formats they are attached to if needed)
A16, Return to the Application Module 
A17, Select Task,  Load Application 
A18, Re-load the  corrected extract file of Conversion tables to re-create the Conversion Tables.
A19, If the Conversion Table names were removed form Database Formats..Re-add them at this point.

Verify the Conversion Tables are working by running an Extract or Load of Data using the Formats that apply them.

Solution B  Create New Entity Conversion Tables

Follow the same steps as solution path A but

B1 While editing the Conversion Table Extract, Adjust the conversion table NAME field to a new desired name.
B2, Negate step A15, the deletion step.

If new Conversion Tables are created, the Database Formats calling these tables Must to changes to the NEW Conversion Table Names.

B3, Enter the Database Module
B4, Select FILE
B6, Open each Format in turn and change the Entity Conversion Table to the newly created appropriate Entity Conversion Table.
B7, Again as in Solution A, verify the Conversion Table works as expected.

(0 vote(s))
Not helpful

Comments (0)
Post a new comment
Full Name: