Google Cloud Cortex Framework for SAP

Data Foundation Demand Sensing

What does this Looker Block do for me? Provides several different dashboards showing variations of weekly demand plan with forecasts from weather, promotion and customer trends.

• Demand Sensing Summary Dashboard - This dashboard provides weekly sales quantity and weather forecasts outside the statistical range for a select time frame, location, product and customer in a tabular format.

• Demand Sensing Temperature - This dashboard provides weekly sales quantity and temperature details for a select time frame, ship-to location, product and customer.

• Demand Sensing Trends - This dashboard provides weekly sales quantity and customer trends details for a select time frame, ship-to location, product and customer.

• Demand Sensing Forecast Outside Statistical Range - This dashboard provides weekly sales quantity and weather forecasts outside the statistical range for a select time frame, ship-to location, product and customer.

• Demand Sensing Promo Differential - This dashboard provides weekly sales quantity and promo differential for a select time frame, ship-to location, product and customer. Promo Differential details include the retail prices of products per unit in Syndicated Point-of-Sale Data.

Required Data

The datasets required by this block can be obtained by following the installation and configuration instructions for both:

• Google Cloud Cortex Framework
• Google Cloud Cortex Demand Sensing Solution (available for download through Google Cloud Marketplace)

The related LookML Block also leverages many of the same datasets.

• Google Cloud Cortex Framework for SAP

Installation Instructions

This LookML model can be manually installed following the steps below.

Option A: Marketplace Install via Git

Refer to the Looker Docs for installing a tool from Marketplace. Provide values for the required prompts as outlined in next section Required Parameters.

Option B: Manual Install via Fork of this Repository

• Fork this GitHub repository
• Create a blank LookML project with any name (e.g., cortex_demand_sensing)
• Connect the new LookML project to the forked repository
• Update the values of constants in the manifest.lkml file as described in the next section Required Parameters
• Commit and deploy changes to production

Required Parameters

> ❕ These required values are configured during the Marketplace Installation process, or if this Block was installed from a forked Git repository, you will update the values for these constants in the `manifest.lkml` file for the project.

• Connection: In the manifest.lkml file, update the value of the CONNECTION_NAME

• GCP Project ID: The GCP project where the SAP reporting dataset resides in BigQuery (i.e., GCP project ID). Identifying Project ID.

• Reporting Dataset: The deployed Cortex Data Foundation REPORTING dataset where the SAP views reside within the GCP BigQuery project.

• K9 Reporting Dataset: The deployed Cortex Data Foundation K9_REPORTING dataset where the HolidayCalendar, Trends, Weather and Weather views reside within the GCP BigQuery project. If using Cortex Data Framework 4.2 and earlier, REPORTING_DATASET and K9_REPORTING_DATASET constants can use the same dataset name.

• Client: Input the Client ID from the dataset.

• Years_Past_Data: Control the number of years of data displayed on the dashboard.

• (Optional) Unhide additional dimensions and measure: Most dimensions and measures have been hidden to simplify reporting and data understanding. However should you find anything valuable missing, simply update the hidden parameters to No in the relevant views.

Additional Resources

To learn more about LookML and how to develop visit:

• Looker Best Practices
• Looker/Google Cloud Training