OK, I'm starting to see why people don't like Data Export. I'm trying to export a particular set of data to a relational table and for some reason, one of the dimensions is not showing up in the table. If I change the export to write to a file, the column is there. It is interesting that the order of the row members is different in the flat file than in the relational export. What appears to be happening is it is taking one of my two dense dimensions which shows up as the last row member before my data vailes in my flat file and is moving(or perhaps overlaying) what is my second row member in the flat file. I know that is clear as mud so to show you an example a row my flat file export looks like:
Actual,r1,aaa1,bbb1,ccc1,ddd1,eee1,Tier1,123456.789
In the relational it looks like:
Actual,Tier1,aaa1,bbb1,ccc1,ddd1,eee1,blank,123456.789
so it is shifting or overwriting the R1 with Tier1 and where tier1 should be is blank.
If anyone has figured a workaround for this other than to export to a file and load it into relational, let me know. In the meantime I'm opening a SR with Oracle and se eif they have a fix
Strategic Deployment Models for Oracle EDM: From Metadata Steward to Master
Creator
-
By now, most of the world knows what EDM is and what it does. Even though
EDM has been out for several years at this point, I believe its strategic
potenti...
5 days ago