Oracle Discoverer End User Layer Table Names
From: Mikey V <odinjmu_at_hotmail.com>
Date: 10 Jun 2004 14:23:03 -0700
Message-ID: <dddef76f.0406101323.c015697_at_posting.google.com>
When creating the End User Layer, Discoverer creates cryptic tablenames that consists of mostly numbers. For example, STATE.STATE_NAME is now O100691.STATE_NAME in the End User Layer. Is there a way for the source tablenames to stay intact? My client has large SQL scripts used to generate reports from the transactional database, and would like to import this SQL into Discoverer Plus.
Date: 10 Jun 2004 14:23:03 -0700
Message-ID: <dddef76f.0406101323.c015697_at_posting.google.com>
When creating the End User Layer, Discoverer creates cryptic tablenames that consists of mostly numbers. For example, STATE.STATE_NAME is now O100691.STATE_NAME in the End User Layer. Is there a way for the source tablenames to stay intact? My client has large SQL scripts used to generate reports from the transactional database, and would like to import this SQL into Discoverer Plus.
Another question is, is there a way to use Discoverer's reporting capabilities against the transactional database? I know that the many perks of Discoverer is not allowing users to modify OLTP data and to hide the underlying complexity from end users--but I'd like to know if it's possible. It seems that is is NOT possible, and that you require an EUL. If I have to create an EUL that's fine I guess, but at least I would like to maintain the table names.
Thanks in advance. Received on Thu Jun 10 2004 - 23:23:03 CEST