SAC NAMING CONVENTIONS
1
SAP ANALYTICS CLOUD FOLDER STRUCTURE
Track
Description​
Sub-track
Description
Folders
BIL
Billing
BL
Billing Adjustments
Models
*Stories into Sub-track
BB
Budget Billing
Models
*Stories into Sub-track
CO
Consumption​
Models
*Stories into Sub-track
​DVM
​Device Management
MR
Meter Reading
Models
*Stories into Sub-track
MT
Meter Testing
Models
*Stories into Sub-track
​CSS
Customer Service
CE
Customer Experience
Models
*Stories into Sub-track
2
SAC OBJECT NAMING CONVENTION
 MODELS
The guidance for naming standards for Models in SAC is to use the below convention:
• Name: <Track>_<Sub-Track>_<Source>_<Model Name>
• Description: <Sub-Track>_<NAME>
For Example,
• Track: BIL, DVM, CSS, REV
• Sub Track: BL, BB, CO, MR, MT, CE
• Source: connection name {S4, HANA}
• Model Name: CDS view name, analytical query name or HANA view name
 STORIES
The guidance for naming standards for Stories in SAC is to use the below convention:
• Name: Report/Story title
• Description: <Report description use>
For Example:
• Name: City of Denver Maintenance Billing
• Description: Report for monthly Denver lighting maintenance charges
3
SAC TRANSPORT PROCESS
Prerequisites:
• REMODL Team will be created to temporarily store changes to reports
• Separate folders will be created which will reference different landscapes:
• DEV
• TEST
• PROD (this will be discussed)
• Reports in the respective folders will utilize the corresponding connection.
• For example, report in DEV folder will use the DEV S/4HANA Connection
Transport Process:
1. Changes will be made in the REMODL Team
2. When change is ready, email SAC team (PoC: Carmen Olsen) to update the report in the
target folder
4