Skip to Content
avatar image
Former Member

Fast refresh of LOVs in WEBI

HI Guys,

how to fasten the LOV refresh in BO?

Notes: 1. My view is having billions of rows

          2. Distinct LOVs for the specific object is ~ 100 values aprrox.,

Thanks,

Bhaskar 

Add comment
10|10000 characters needed characters exceeded

  • Get RSS Feed

4 Answers

  • avatar image
    Former Member
    Jan 29, 2014 at 07:59 AM

    You can modify the semantic layer, use "distinct" in the select clause.

    Your universe is created using IDT or UDT?

    Thanks,

    Vivek

    Add comment
    10|10000 characters needed characters exceeded

  • Jan 29, 2014 at 09:02 AM

    Hi

    The default list of values associated with the object contains all the distinct Values.

    The first time a list of values is used, it is saved as a .LOV file in the universe sub folder on the file system. This allows the SELECT DISTINCT query to be run only once for an object.


    This folder also stores the .LOV files created in the universe design tool which are used to restrict the list of values returned for objects for which the designer wants to control access to the data.


    The next time that the list of values is required for the object in the universe design tool, the values are returned from the .LOV file and not from the database.

      You can also create a permanent list for values for an object and export this list to the repository. This.LOV file is then always used as the list of values for that object

    Add comment
    10|10000 characters needed characters exceeded

    • Former Member

      Hi


      What is meant by permanent list of values. Is this something like Personal Data values which we can add at universe level.

      Thanks..

  • avatar image
    Former Member
    Jan 30, 2014 at 11:54 AM

    One option is to source your data from elsewhere - is there a smaller table or view that you could use or even create to source the data from?

    Add comment
    10|10000 characters needed characters exceeded

  • Jan 30, 2014 at 05:05 PM

    As far as LOV's best practices is being concerned.

    1. Always reference the Dimension table rather than creating LOV from a fact table or a database view.

    2. If Underlying LOV values are not changing frequently, You can always reference it from a flat file which is inturn accumulated in .LOV files for faster retrival.

    Regards

    Mani

    Add comment
    10|10000 characters needed characters exceeded