Search icon CANCEL
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
Software Development on the SAP HANA Platform

You're reading from   Software Development on the SAP HANA Platform Written by a SAP HANA expert, this book takes you from installation to running your own processes in no time. By the end of the course you'll have awesome data retrieval and analytical powers to call on.

Arrow left icon
Product type Paperback
Published in Jul 2013
Publisher
ISBN-13 9781849689403
Length 328 pages
Edition Edition
Arrow right icon
Author (1):
Arrow left icon
Mark Walker Mark Walker
Author Profile Icon Mark Walker
Mark Walker
Arrow right icon
View More author details
Toc

Table of Contents (19) Chapters Close

Software Development on the SAP HANA Platform
Credits
About the Author
About the Reviewers
www.PacktPub.com
Preface
1. So, What Is This SAP HANA Thing Anyways? FREE CHAPTER 2. SAP HANA Studio – Installation and First Look 3. Your First SAP HANA Development – An Attribute View 4. Painting with Numbers – An Analytic View 5. Let's Get Graphical – Graphical Calculation Views 6. You Talking to Me? – Scripted Calculation Views 7. Hey! That's My Data! – Authorizations in SAP HANA 8. On Another Level – Hierarchies in SAP HANA 9. Deploying Your Reporting Application to Reporting Software 10. Data Provisioning Using Data Services 11. Application Development Using the XS Engine So Long and Thanks – Where To Go from Here Index

Package privileges


The last tab in the role definition screen concerns Package Privileges. These allow a given user to access those objects in a package.

In our example, the package is called book, so if we add the book package to our role in the Package Privileges tab, we will see the following result:

Assigning package privileges is similar to assigning SQL privileges we saw earlier. We first add the required object (here our book package), then we need to indicate exactly which rights we give to the role. As we can see in the preceding screenshot, we have a series of checkboxes on the right-hand side of the window. At least one of these checkboxes must be checked in order to save the role.

The individual rights have names which are fairly self-explanatory. REPO.READ gives access to read the package, whereas REPO.EDIT_NATIVE_OBJECTS allows modification of objects, for example.

The role we are creating is destined for an end user who will need to see the data in a role, but should not need...

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