Like any SAP solution, the Nakisa solutions have a variety of specific terminology that is banded about in the public domain or when working directly with the solution experts or Nakisa themselves. Nakisa and SAP’s marketing folks have also created their own terminology for the Nakisa solutions.
In this blog I have attempted to cover a number of key terms and definitions used in the Nakisa world. No doubt I will have missed a few, so feel free to suggest anything I may have forgotten to add. Some terminology has been missed intentionally, like non-Nakisa specific terminology or abbreviations not used by Nakisa or SAP. I’ve also tried to pick the most important or widely-used terms to keep the list readable in one go.
Suite Abbreviations
Term | Definition |
VSN | Visualization Solutions by Nakisa |
SOVN | SAP Organizational Visualization by Nakisa |
STVN | SAP Talent Visualization by Nakisa |
SP | Service Pack |
CDS | Corporate Directory Services – the original name for Nakisa’s solutions |
Architectural
Term | Definition |
Authentication | Authenticate the user against an authentication source |
Authorization | Allow the user to access different functionality, depending on their application role |
Concurrent sessions | the number of sessions that are open at the same time |
Concurrent users | The number of users who may access the system at the same time |
Custom RFC | Functionality to use SAP function modules to retrieve data from SAP |
Extractor | Nakisa’s extract tool to retrieve data from SAP and write to a Staging database |
Hybrid | A combination of Live (structure & data) and Staged (analytics) |
Live | Retrieving/writing data live from/to SAP |
NakisaRFC | Nakisa’s customizable Live SAP data extractor |
Role-based security | Application roles provide the user with the ability to access restricted functionality, such as a search listing or view |
Single Sign-on (SSO) | Authentication method used for integrating VSN solutions into the NetWeaver Enterprise Portal, authenticating the user using their login credentials from the MYSAPSSO2 ticket |
Staged | Using a database as the data source |
Writeback | Wiring data back to the SAP system |
Application Specific Features & Functionality
Term | Definition |
AdminConsole | The Administrator Console used to configure Nakisa’s applications |
Build | The delivery of an entire application or A set of configuration |
Cds.log | Log file where information, warnings and errors are logged by the application |
Chartbook | A booklet that shows an orgchart over a number of pages |
Connection string | A string to specify the connection to a data source |
Details Panel | Panel of details about a selected object |
Direct count | Analytic counts for a single OrgUnit |
Directory | Asearch listing that also displays details of a selected object simultaneously |
Flex | Adobe Flex module – used for rendering sexy-looking graphics using Adobe Flash Player |
HCMD | HCM Dashboard – the old name for TalentDashboard |
Hierarchy | A set of same-type objects that form a basic structure or part of a structure when linked to another hierarchy |
Indirect count | Analytic counts for an OrgUnit and its child OrgUnit’s |
Node | A box that represents an object, such as an OrgUnit or Position |
Orgchart | A object-orientated chart of objects from a number of hierarchies linked together by relationships |
Profile | “Flat” details panel designed to be printed or exported |
Publish | Moving a build’s configuration files to the runtime folders so that the configuration is the “active” configuration used |
Scenario | A "what-if" situation created in OrgModeler to help manage organizational changes |
Scenario module | Where OrgModeler scenarios are managed |
Search Listing | Facility to search for objects of a given type by certain criteria |
Selected Items | The panel that displays flagged orgchart boxes in the orgchart or selected listing records in searches |
Silo | A function that displays an orgchart from the selected object up to the top object in a direct line |
SocialLink | OrgChart module that allows users to maintain their own profile in a similar way to the SAP Talent Profile for Employees |
Style | The layout of the nodes |
Subcategory | A grouping of similar employees or positions that can be displayed in one org chart box |
Task | A pop-up window in which the user performs an activity to add, modify or delete (delimit) data |
View | A selection of information/images/icons shown in the nodes for a particular object |
Wizard | A step-by-step, option-based method of performing bulk tasks quickly and easily |
Security
Term | Definition |
Attribute scope | A method of defining the scope of security using only the values of attributes in the target object |
Derives and below | A type of dynamic security where the user can see information for their OrgUnit (OrgUnit, positions and/or employees) and for child OrgUnit’s (e.g. a departmental manager) |
Dynamic Filters | Allows the entire orgchart above the user who is logged in to be blocked |
Dynamic Security | A type of security that allows access to features or data depending on specific conditions (e.g. a manager seeing restricted data for their employees) |
Hierarchy Scope | Allows specific data for the orgchart to be blocked, depending on the user logged into the system |
Keyword | Used for a dynamic security role to recognize that security rules should be applied |
Restricted data | Sensitive data that has been restricted to a security role (so it is not available to all end-users) |
Role-based security | Use of application roles to secure data and/or functionality, rather than or in addition to SAP-based authorization(s) |
Role mapping | Mapping an SAP role to an application role so that a user can be mapped to a role during authentication |
Scope | The range of conditions to which security applies |
Security Role | An application role that allows the user to see particular data and/or have access to certain functionality |
Self and Below | A type of dynamic security where the user can see information for themselves and for those below them only (e.g. direct reports) |
Start from Self / One Level Above | A type of dynamic security where the user can see information for themselves, for those below them only (e.g. direct reports) and for their manager |
Static Security | A type of security that allows all users of a security role “all or nothing” access to functionality or data |
Customization and configuration files
Term | Definition |
Data element | Defines the data source for a set of fields |
Detail | Represents various sections throughout the application, such as data sections on a details panel or a view detail configuration |
Detail data | Detail data contain the data definitions (fieldsets) used by sections of a detail and are linked to a single data element |
Details presentation | Layout of the details panels and, prior to 3.0 SP1, views |
Directory | Master configuration for search listings |
Hierarchy | Each level of objects in an orgchart (e.g. OrgUnits, Positions, Employees etc) |
Link | Link between details panels and other objects (tasks, orgcharts etc) |
Listing | The display and sort fields of a search listing |
Module | The main modules in each application (e.g. directory, orgchart or myreports) |
Search control | The search fields (including Advanced search) of a search listing |
Selection value set | Source of values for drop-down lists |
Selector | A directory for selecting objects (like the OrgUnit selector used when creating an OrgModeler scenario) |
Theme | Application themes available |
Validation | Validations for input fields (e.g. number, dates and names) |
Associated Terminology
Term | Definition |
JVM | Java Virtual Machine |
J2EE | Java Platform, Enterprise Edition |
NWCE / CE | NetWeaver Composition Environment |
