SAP Datasphere — Don’t Create Your Spaces with These Technical Names

[TuncayKaraca]

While working on SAP Datasphere one of the first tasks is creating spaces. More importantly how you organize the spaces, what’s your strategy and what best practices you may apply, etc. That’s another topic that can be dealt with in details later. Today I would like to tell you “Don’t Create Your Spaces with These Technical Names”

Photo by Benjamin Voros on Unsplash

Let’s start with official definition: Spaces provide a way to partition your SAP Datasphere tenant into independent virtual work environments for departments, LOB’s, data domains, project teams, and individuals.

There are technical names and business names. Technical names are permanent that cannot be changed, business names are just descriptions; change them whenever you’d like. Here we are talking about the technical names of the SAP Datasphere Spaces.

There are rules for technical names, not only for the spaces but also for all other objects in SAP Datasphere. The rules and restrictions apply to the technical names of objects that you create in SAP Datasphere.

SAP Datasphere > Space Management

Space Technical Names

• The maximum length is 20 characters.
• The space ID aka Technical Name can only contain uppercase letters, numbers, and underscores (_).

Don’t Create Your Spaces with These Technical Names

• SYS, CREATE, or SYSTEM
• PUBLIC, DBADMIN, MONITORING, PAL_STEM_TFIDF, SAP_PA_APL, DWC_USER_OWNER, DWC_TENANT_OWNER, DWC_AUDIT_READER, DWC_GLOBAL, and DWC_GLOBAL_LOG.
• Also, the keywords that are reserved for the SAP HANA database cannot be used in a space ID. Check SELECT * FROM RESERVED_KEYWORDS ORDER BY RESERVED_KEYWORD;
• ✔️SAP_CONTENT and SAP_ADMIN — for standard business contents, though you need to create them if you want to import standard business contents. 
• ✔️ BWBRIDGE or BWBRIDGESPACE — I think though there is no specific name reserved for BW Bridge. These can be use for it.

Don’t Use These Prefixes for Your Spaces’ Technical Names

• SAP_*
• DWC_*
• SYS_*

Good examples for Your Spaces’ Technical Names

• ADMINISTRATION
• SYSTEM_ADMIN
• SECURITY
• FINANCE
• SALES
• SUPPLY or SUPPLY_CHAIN
• HR or HUMAN_RESOURCES
• MANUFACTURING or PRODUCTION
• ASSET_MANAGEMENT

References

1. SAP Datasphere > Administering SAP Datasphere > Creating Spaces and Allocating Storage > Rules for Technical Names
2. SAP HANA Platform > SAP HANA SQL Reference Guide for SAP HANA Platform > SQL Reference > Reserved Word > SAP HANA SQL Reference Guide for SAP HANA Platform2.0 SPS 07 > Reserved Words
3. SAP Datasphere > Integrating Data and Managing Spaces in SAP Datasphere > Managing Your Space Integrating Data and Managing Spaces in SAP Datasphere > Managing Your Space
4. SAP Help > Getting Started With SAP Datasphere, SAP BW Bridge
5. SAP > SAP Datasphere — First Guidance: Development Guidelines and Naming Conventions
6. SAP Datasphere — Don’t Create Your Spaces with These Technical Names at medium.com/@tncykarc