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

Roles


In SAP HANA, as in most of SAP's software, authorizations are grouped into roles.

A role is a collection of authorization objects, with their associated privileges. It allows us, as developers, to define self-contained units of authorization. In the same way that at the start of this book we created an attribute view allowing us to have a coherent view of our customer data which we could reuse at will in more advanced developments, authorization roles allow us to create coherent developments of authorization data which we can then assign to users at will, making sure that users who are supposed to have the same rights always have the same rights. If we had to assign individual authorization objects to users, we could be fairly sure that sooner or later, we would forget someone in a department, and they would not be able to access the data they needed to do their everyday work. Worse, we might not give quite the same authorizations to one person, and have to spend valuable time correcting...

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