Structural Authorizations with Nakisa
- by Prashant Rastogi, Associate Manager, Accenture
- February 15, 2012
Learn how to implement structural authorizations for Nakisa. Understand the concepts and activities required to make structural authorizations work with Nakisa components.
The concept of structural authorization helps SAP ERP HCM users to define the population of the organizational structure that they can access. These kinds of authorizations use evaluation paths to determine all the objects under the root object in an organization structure. Because Nakisa components are mostly visualization tools, structural authorizations play a vital role in helping users by optimally visualizing data.
Although the general concept of structural authorizations is well known by most SAP ERP HCM users, one relatively unexplored area is its use in Nakisa applications. I explain how to use SAP Talent Visualization applications by Nakisa (SAP Talent Visualization by Nakisa [STVN] and SAP Organizational Visualization by Nakisa [SOVN]) with structural authorizations.
Nakisa, one of SAP’s partnership products, is fully integrated with SAP ERP HCM back-end data. This integration ensures that all security-related (authorization) operations that are implemented on back-end data are also valid for visualization solutions in SOVN and STVN.
For some of Nakisa STVN’s components, such as succession planning, however, Nakisa uses TREX search indexes between the SAP ERP HCM data in the back end and its presentation layer. Therefore, restrictions for data searching for end users should first appear in these indexes for these components. For all other components (e.g., organizational charting and organizational modeling) structural authorizations are directly picked from the SAP ERP HCM back end.
Structural authorization plays a vital role in implementing STVN or SOVN functionality because it directly affects the possibility of displaying objects, such as organizational unit and position, to the user. In addition, the standard SAP ERP HCM system doesn’t provide STVN or SOVN functionality with specific authorization profiles in the SAP ERP HCM back end. This limitation complicates the process further because users implementing basic Nakisa functionality do not get any guidance about how to build structural authorization profiles or which objects to include.
Would you like to see this full item?