BusinessObjects Universe Designer – Sysdate Value Object

| Posted by watashii | Filed under BusinessObjects, Database, Software

universe_sysdate

Creating SYSDATE value objects in a Universe (via Oracle connection) can simply be done as shown above.   I have simply created a single-value dimension object, which can be used anywhere within a query (result/condition/sort).  Having sysdate values allows the flexibility to create dynamic time-based reports.  For example you can schedule a weekly report to extract data from the past 7 days starting from the current time the report was run.

Note, when parsing the object against the database (Oracle), an error will appear. ORA-00903: Invalid table name.

You can just ignore this error and press ok.

Share:

  • Digg
  • del.icio.us
  • Facebook
  • Google Bookmarks
  • Print
  • email

Related Posts:

  1. Oracle SQL Loader – Importing CSV files to a table
  2. BusinessObjects – Delete Universes in CMC
  3. BusinessObjects – Internal Error when connecting Windows clients
  4. Starting / Shutdown Oracle Database in Unix
  5. BusinessObjects InfoView LDAP Authentication Error

Tags: , , ,

Permalink | June 5th, 2009

3 Responses to “BusinessObjects Universe Designer – Sysdate Value Object”

  1. Aditya Says:
    September 14th, 2010 at 11:13 am

    After I am creating an object with sysdate in the universe, when I using that universe in desktop Intelligence, I am getting an error “The query does not reference a table QP0007″.. Kindly help. I need to have a object which returns sysdate.
    The DB is oracle 10g and I am using BO XI R2
    Kindly assist

  2. watashii Says:
    September 15th, 2010 at 1:38 pm

    I havent tested this on deski. You could try recreating the same query in the “Query Panel” within Designer to make sure your SQL is valid and can run against your database.
    As an alternative method to this post, you could also create a derived table in Universe with the SQL: “select sysdate from dual“, however you need to make sure the joins to your normal tables are ok to avoid cartesian joins. This may have performance issues depending in your design.

  3. Hernan Del Valle Says:
    November 17th, 2010 at 9:35 pm

    If you do click on the parse button it’s going to show you that error but if you write SYSDATE then click on the ok button and it’s going to work fine.

    also you can use TRUNC function

    Thanks A lot!!

Leave a Reply