Search icon CANCEL
Subscription
0
Cart icon
Your Cart (0 item)
Close icon
You have no products in your basket yet
Save more on your purchases now! discount-offer-chevron-icon
Savings automatically calculated. No voucher code required.
Arrow left icon
Explore Products
Best Sellers
New Releases
Books
Videos
Audiobooks
Learning Hub
Conferences
Free Learning
Arrow right icon
Arrow up icon
GO TO TOP
Creating Universes with SAP BusinessObjects

You're reading from   Creating Universes with SAP BusinessObjects Create and maintain powerful SAP BusinessObjects Universes with the SAP Information Design Tool

Arrow left icon
Product type Paperback
Published in Sep 2014
Publisher
ISBN-13 9781782170907
Length 310 pages
Edition 1st Edition
Languages
Arrow right icon
Author (1):
Arrow left icon
Taha Mahmoud Taha Mahmoud
Author Profile Icon Taha Mahmoud
Taha Mahmoud
Arrow right icon
View More author details
Toc

Table of Contents (12) Chapters Close

Preface 1. Introduction to BI and the Semantic Layer FREE CHAPTER 2. Aligning BI Solutions with Business Demands 3. Creating Our First Universe 4. Creating the Data Foundation Layer 5. Creating the Business Layer 6. Testing Your Universe 7. The Data Foundation Layer – Advanced Topics 8. The Business Layer – Advanced Topics 9. Data Security and Profiles 10. A Multiuser Development Environment Index

List of values


A list of values is used when the end user is prompted to select a value for a specific dimension such as region, for example. Usually, LOVs are assigned with a dimension because they are used in filters. The LOV will generate a query to display the distinct values for the associated dimension.

Tip

We should create LOVs for dimensions with less than 100 distinct values in order to make sure that they are user friendly and easy to navigate.

It is not recommended that you create an LOV for any business object based on the fact table. We should use the dimension table instead. For example, if you have the country code, which is stored in the Customers fact table as a foreign key and in the Country dimension as a primary key, we should then build an LOV on top of the country code stored in the Country dimension table.

It is not recommended that you build an LOV for attributes or measures because it will generate a nonsense LOV, for example, a list of PO box numbers is nonsense while...

lock icon The rest of the chapter is locked
Register for a free Packt account to unlock a world of extra content!
A free Packt account unlocks extra newsletters, articles, discounted offers, and much more. Start advancing your knowledge today.
Unlock this book and the full library FREE for 7 days
Get unlimited access to 7000+ expert-authored eBooks and videos courses covering every tech area you can think of
Renews at €18.99/month. Cancel anytime