SAP Data Warehouse Cloud contentDocumentationRelease Date: May 21st, 2022Last Update: May 21st, 2022EXTERNAL
Table of Contents1General Remarks . 62Release Notes SAP Data Warehouse Cloud Content . 7Content Innovation Q2 2020 – June 3, 2020 . 7Content Innovation Q4 2020 – November 15, 2020 . 7Content Innovation Q1 2021 – Februar 22, 2021 . 7Content Innovation Q2 2021 – May 31, 2021 . 7Content Innovation Q1 2021 – Feburary 21, 2022 . 7Content Innovation Q2 2021 – May 21, 2022 . 73Install and how to use content . 9General Information . 9Setup Information . 10Update existing content . 11Activate Time Data in the SAP Content Space. 124Lines of Business (LoB) . 13SAP Ariba: Enterprise Analytics for Procurement . 14Architecture and Abstract . 14Stories . 15Models . 220.127.116.11.18.104.22.168.22.214.171.124.4Invoice Line View (SAP PROC RL INVOICES). 16Strategic Savings - SAP PROC RL STRATEGIC SAVINGS . 16Orders and Requisitions - SAP PROC HL ORDERS AND REQS . 17Requisitions Orders and Invoices - SAP PROC RL REQ ORD INV . 17Setup Instructions: . 18Configuration for Single Realm Ariba . 19Configuration for 2 Realm Ariba . 21Modifying the RL View . 23SAP Ariba: Spend Analysis . 26Architecture and Abstract . 26Stories . 27Models . 2126.96.36.199.188.8.131.52.3.3Time Data Associations Tables . 28Reporting layer . 28Inbound and Harmonization layer . 35Finance for S/4 HANA Cloud . 37Architecture and Abstract . 37Stories . 38Models . 3184.108.40.206Financial Data of the Last Three Years (SAP FI GLDataOverTime) . 38
220.127.116.11Financial Data with Semantic Tag (FI) (SAP FI GLAccountSemanticTag). 39Sales and Distribution: Sales Analysis for SAP S/4HANA on-premise . 42Prerequisites for SAP S/4HANA release 2020 . 418.104.22.168.4.1.2Transaction Data . 42Master Data (Release OP2020) . 43Architecture and Abstract . 45Stories . 48Models . 422.214.171.124.126.96.36.199.4.3Master data . 49Currency Conversion. 52Transaction data. 54Statistical Process Control (SPC) . 95Architecture and Abstract . 95Stories . 96Models . 9188.8.131.52.184.108.40.206.220.127.116.11.4Control Chart - Consumption layer to SAP Analytics Cloud . 97Nelson rules and merged view of data . 97Source data and Source separation . 97Control Chart (SPC) (SAP X SPC OUT CONTROL CHART) . 98Setup content with local dataset. 1015Industries . 103Automotive (AUT) . 103Prerequisites for SAP S/4HANA release 2020 . 1035.1.1.15.1.1.2Transaction Data (Release OP2020) . 103Master Data (Release OP2020) . 103Architecture and Abstract . 105Stories . 106Models . 1075.1.4.15.18.104.22.168.22.214.171.124.126.96.36.199Master Data . 107Currency Conversion. 109Sales Document Item . 110Purchase Orders . 111Manufacturing Orders. 113Consumer Products (CP) - Revenue Growth . 115Prerequisites for SAP S/4HANA release 2020 . 1188.8.131.52.2.1.2Transaction Data . 115Master Data (Release OP2020) . 116Architecture and Abstract . 118Stories . 118Models . 118SAP Intelligent Real Estate . 119SAP S/4HANA Cloud Connection . 119BTP SAP Cloud for Real Estate Connection in Data Intelligence . 119Architecture and Abstract . 121Stories . 121Models . 122
184.108.40.206.220.127.116.11.18.104.22.168.22.214.171.124C4RE Building Report (RL) (SAP RE C4RE BuildingReportTL) . 123C4RE Building Area Detail (RL) (SAP RE C4RE BuildingAreaDetailTL) . 128RE CLM Occupancy Report (RL) (SAP RE CLM OccupancyReportTL) . 130CLM Land Site Areas Parcels Report (RL) (SAP RE C4RE LandSiteReportTL) . 135CLM Cost Reporting Semantic Tag (RL) (SAP RE CLM CostSemTagReport). 137POS Analysis for Retail . 141Architecture and Abstract . 141Stories . 141Models . 142Setup content with local dataset. 147Supply Chain Management for Life Sciences (SCM-LS) . 148Prerequisites for SAP S/4HANA release 2020 . 14126.96.36.199.5.1.2Transaction Data (Release OP2020) . 148Master Data (Release OP2020) . 149Architecture and Abstract (SCM-LS) . 151Stories . 152Models . .7Master Data . 153Currency Conversion. 155Sales Document Item . 156Billing Document Item . 156Purchase Orders . 157Transportation Orders . 159Manufacturing Orders. 161Telecommunication: Customer Value Management (CVM) . 163Architecture and Abstract . 163Stories . 165Models . 16188.8.131.52.184.108.40.206.3.3Inbound Layer . 166Harmonization Layer . 168Reporting Layer . 174Setup content with local dataset. 176Utilities – Meter To Cash scenario . 178Prerequisites: Data Sources in source system . 179Architecture and Abstract . 179Stories . 180Models . 18220.127.116.11.18.104.22.168.22.214.171.124.126.96.36.199Harmonized View on Meter Reading Data (SAP UTL HL MeterReadings) . 181Harmonized View on Maintenance Items (SAP UTIL HL CDS IMAINTITEMDATA) . 184Harmonized view on Billing Orders (SAP UTL IL Billing Orders) . 186Harmonized view on Payments (SAP UTL IL Payments) . 187Harmonized view on Business Partner Items (SAP UTL HL BPItem) . 189Overview content Data Sources . 1916Cross Applications . 194Financial Analytics Dashboard for SAP Analytics Cloud . 194SAP Monitoring Content (Data Integration Tasks) . 195
Sustainability Control Tower. 1967Known Issues. 197
1GENERAL REMARKSThis documentation covers the following topics: Chapter 3 describes how to get the content and install it in the system.As of the Q4 2020 release, SAP Analytic Cloud content corresponding to the SAPData Warehouse Cloud models is provided in separate packages in the SAP AnalyticCloud Content Network. You need to import and setup both SAP Data WarehouseCloud and SAP Analytics Cloud packages for an End-2-End content experience.Please read this chapter carefully, even if you have installed content before. Chapter 4 describes the detailed documentation of the Line(s) of Business (LoB) andIndustries is described in chapter 5. Cross Application content is described in chapter6. Find information about known issues and their resolution in chapter 7.Further information is available on the following web sites: SAP Community blog,the product web sitefind an overview of all content packages in the SAP Business Content Center.This documentation assumes that the reader is familiar with SAP Data Warehouse Cloud.It does not substitute SAP Data Warehouse Cloud documentation, which can be foundhere: Help Portal: SAP Data Warehouse Cloud.The content does not include any predefined roles or permissions.
2RELEASE NOTES SAP DATA WAREHOUSE CLOUD CONTENTHere you can find an overview of the content per Content release.CONTENT INNOVATION Q2 2020 – JUNE 3, 2020-Industry Content for Retail: SAP Consumer Sales IntelligenceCONTENT INNOVATION Q4 2020 – NOVEMBER 15, 2020-Financial analytics dashboard for SAP Analytics CloudIndustry Content for Automotive (AUT): Responsive Supply Network, Sales andInventoryIndustry Content for Consumer Goods (CP): Revenue Growth Management FoundationIndustry Content for Utilities (UTL): Meter to CashCONTENT INNOVATION Q1 2021 – FEBRUAR 22, 2021-SAP Ariba: Enterprise Analytics for ProcurementFinance for S/4HANA CloudStatistical Process Control (SPC) ToolkitTelecommunication: Customer Value ManagementCONTENT INNOVATION Q2 2021 – MAY 31, 2021-SAP Ariba: Spend AnalysisFinancial Analytics Dashboard for SAP Analytics Cloud (Updates)SAP Retail: POS Analysis for RetailSAP Supply Chain Management: Life SciencesCONTENT INNOVATION Q1 2021 – FEBURARY 21, 2022-Intelligent Real EstateSales and Distribution: Sales Analysis for SAP S/4HANA on-premiseSustainability Control TowerCONTENT INNOVATION Q2 2021 – MAY 21, 2022-Automotive (AUT): Responsive Supply Network, Sales and Inventory (update)Consumer Goods (CP): Revenue Growth Management – Foundation (update)Intelligent Real Estate
--Sales and Distribution:o Sales Analysis for SAP S/4HANA on-premise (update)o Sales Conditions for SAP S/4HANA on-premise (new)o Sales Quotations for SAP S/4HANA on-premise (new)Supply Chain Management: Life Sciences (Update)
3INSTALL AND HOW TO USE CONTENTGENERAL INFORMATIONBusiness content is available from the Content Network. Please refer to the onlinedocumentation for details:Importing from the Content Network.The first SAP and Partner content packages released in June 2020 (Content Innovation 1)contained both SAP Data Warehouse Cloud objects and the SAP Analytics Cloud stories(as part of a Space) in one content package.With the release of November 2020 (Content Innovation 2), this has changed:To simplify and optimize the SAP Analytics Cloud to SAP Data Warehouse Cloudconnectivity, a SAP Data Warehouse Cloud live connection with the name “SAPDWC”is used from now onwards. This connection needs to be created manually in the SAPAnalytics Cloud system. Read the SAP Analytics Cloud documentation if you need help tocreate a SAP Data Warehouse Cloud live data connection.Consequently, SAP Analytic Cloud content is delivered in separate packages starting withQ4 2020. This adds the flexibility to import the content in any SAP Analytic Cloud systemof choice and connect to any Data Warehouse Cloud system of choice.There will no longer be content packages, that include SAP Analytics Cloud content andSAP Data Warehouse Cloud content, instead two separate packages will always exist inthis optimized setup. Both packages should always be installed together for an end-to-endexperience.Please understand that new or updated package will only be support for the optimizedsetup going forward.The SAP Analytic Cloud content and the SAP Data Warehouse Cloud content can beinstalled independently. Before you can run the SAP Analytics Cloud stories, a liveconnection to SAP Data Warehouse Cloud has to be setup. This is a one-time effort foreach SAP Analytics Cloud system.Follow the SAP Analytics Cloud documentation how to setup the live connection betweenSAP Analytics Cloud and SAP Data Warehouse Cloud here. (SAP Analytics Cloud Help
Connections Live Data Connections Live Data Connections to SAP Data WarehouseCloud)SETUP INFORMATIONBefore you can import any SAP or partner content package, the space into which thecontent will imported, needs to be created upfront. The same holds true for theconnections to any source system as well as the openSQL schemas.The description of each content package also contains the necessary information so thatno important task that is required before importing a content package will be missed.SAP Content is always imported into the space SAP CONTENT. Thus, please create aspace with the technical name “SAP CONTENT” once before you can import any contentpackage. Please use the description “SAP Content”. In addition, you need to assign theuser who will import the content to the space SAP CONTENT.Each partner content is imported into a dedicated space, please follow the instructions atpackage level in the Content Network to create the required space. Do not forget to assignthe user who will import the content to the partner content space.For the creation of the connections or openSQL schemas, follow the instructions atpackage level.In case further activities are required, they will be either mentioned in the Content Networkfor each package or as part of the content documentation.
UPDATE EXISTING CONTENTWhenever using the “Overwrite” option during the content import, this could result inunintended loss of customer enhancements, customer data or changes to content objects.Should you have imported content before, some or all objects included in the package-tobe-installed might already exist in your system. Content packages are not free of overlap,so content objects may be delivered in more than one package. They might get overwrittenaccidentally even if you choose a different package. Please read the following paragraphcarefully to avoid accidental loss of customer enhancements and data:If you have a second tenant that you do not use productively, e.g. for development ortesting, you may check the new content first to ensure it fulfils your needs before moving itto the productive tenant.It is recommended to copy the artefacts, before you change or enhance them. Typically,references to other objects will stay in place. A copy will still reference the same objects asthe original: A copy of a view will still refer to the original objects (views, remote tables,tables).
ACTIVATE TIME DATA IN THE SAP CONTENT SPACEBefore importing any content package, the Time Data needs to be setup in the SAP &Partner Content Space (SAP CONTENT).Please follow the SAP Data Warehouse Cloud documentation “Create Times Dimension”here or use the In-App Help directly in SAP Data Warehouse Cloud in case furtherassistance is required:As a result, the Time Tables and dimension are created as follows:
4LINES OF BUSINESS (LOB)The Industry and cross-application packages offer selective access to line-of-businessinformation already to the degree that this is required for the scenarios to work. Here inparticular finance information from S/4HANA and HR information from SuccessFactors areavailable.The line-of-business connections, e.g. to SAP S/4HANA Cloud or SAP SuccessFactors,and the data models on top may be re-used even without an industry or cross-applicationfocus.
SAP ARIBA: ENTERPRISE ANALYTICS FOR PROCUREMENTThe Enterprise Analytics for Ariba Procurement package is one integrated solution thatprovides analytics based on Ariba Data. It measures Compliance, Sourcing Savings,Process Efficiency and Working Capital to reduce spend by following establishedprocurement processes, payment terms and the most efficient processing methods withinan organization.Architecture and AbstractThe SAP Analytics Cloud stories are created using 3 SAP Data Warehouse Cloud models: Invoice Line View (SAP PROC RL INVOICES) Strategic Savings (SAP PROC RL STRATEGIC SAVINGS) Requisitions Orders and Invoices (SAP PROC RL REQ ORD INV)These views are built on top of Ariba tables brought in by an ETL Partner. In this particularpackage, SAP Ariba REST API’s are accessed by these ETL platforms and brought toData Warehouse Cloud as Database User tables.
StoriesThe following story is included in the content package:SAP PROC PROCUREMENT ANALYTICSPlease navigate to the SAP Analytics Cloud content documentation for details.ModelsThree layers are used for all of objects in this package:Inbound Layer (IL) ObjectsThese objects represent tables that are brought in to SAP Data Warehouse Cloud. Eachtable represents data related to a specific Ariba template.Harmonization Layer (HL) ObjectsThese objects join together tables brought into SAP Data Warehouse Cloud, but are notdirectly used on the dashboard/reporting level. For example, the Commodity HL viewcombines commodities found on the Orders table, and joins it with the CommodityDimension table from Ariba.Reporting Layer (RL) ObjectsThese objects are meant for use on a reporting/dashboard level. In this package, the SAPAnalytics Cloud story is using these RL objects to build charts and tables. These RLobjects are created by connecting 2 or more IL or HL objects. The data model appliesdifferent joins between tables, calculations, and data harmonizing steps to make it readyfor use on SAP Analytics Cloud.
188.8.131.52Invoice Line View (SAP PROC RL INVOICES)12Invoice Line View model is used directly in the SAP Analytics Cloud story. It builds from 4invoice related sources, and a payment terms table. Combining these tables together addsadditional attributes to each invoice.Calculations in (1) are for trimming and concatenating text strings to allow for joins. Ie. forinvoice names, ID’s and source system names.Some KPI’s are calculated here at the view level (2): PO and Non-PO Spend Invoice Due dates Discount Days Potential Discounts On and Off Contract Spend & Invoice Counts Compliant and Non-Compliant Spend184.108.40.206Strategic Savings - SAP PROC RL STRATEGIC SAVINGSThe Strategic Savings model is used directly on the SAP Analytics Cloud story. This viewuses the Savings Allocation table from Ariba. Using the “Associations” feature in DataWarehouse Cloud, it connects to various dimension tables ie. Region, Organization andCost Centres. These data tables have a hierarchy structure that allows users to performdrill-down analysis. Ie. Within organizational groups in the company.
220.127.116.11Orders and Requisitions - SAP PROC HL ORDERS AND REQSThe Orders and Requisitions view is not directly in the SAP Analytics Cloud story. It actsas an intermediary model that performs the joins and calculations between tables. In thismodel, Order tables and Requistions are joined.Calculations for Data Harmonization: Date conversions Concatenations for order numbersKPI Calculations: Order Count Order Line Count18.104.22.168Requisitions Orders and Invoices - SAP PROC RL REQ ORD INVThe Requisitions, Orders and Invoices model is used directly on the SAP Analytics Cloudstory. This view joins the Invoice Line View, with the Orders and Requisitions view.
Setup Instructions:1. Creating / Uploading a Payment Terms table1. Open the Payment Terms table in the Data Builder.2. Use the data editor to add each individual payment term record to the table.3. Alternatively, you can use the Upload Data from CSV option. To do this,prepare a payment terms CSV file with the following columns:Column NameDescriptionExampleDescription enText description for the60 days NET frompayment termInvoice ReceiptPayment terms ID used in yourNT60UniqueNameAriba systemValueDays (or months) to pay invoice60PeriodSpecify period in Days (D) orDMonths (M)Discount daysDays to qualify as earlypayment (if applicable)10
Discount PercEarly payment discount %2(if applicable)CSV Table example:Configuration for Single Realm AribaThe data models in this content package are designed to be compatible with both singleand dual realm Ariba systems. For single-realm Ariba systems, we need to delete portionsof the HL views listed below.Invoice (HL)ERP Order (HL)Invoice Line Items (HL)ERP Order LineRequisition Line Items (HL)Items (HL)Invoice Line Items Spli
The SAP Analytic Cloud content and the SAP Data Warehouse Cloud content can be installed independently. Before you can run the SAP Analytics Cloud stories, a live connection to SAP Data Warehouse Cloud has to be setup. This is a one-time effort for each SAP Analytics Cloud system. Follow the SAP Analytics Cloud documentation how to setup the .