Page tree


1.0 Overview




Business Context and Application Overview

The data admin reports in the global sales folder of BW serves specific functions related to customer data, customer group retrieval, end-use mapping, and material conversion within the SAP BW system.

Target Users:

Data Admin of GBUs

VERSION

DATE

MODIFIED BY 

DESCRIPTION

0.01

20.12.2023

Azadeh Nasiri

Initial draft









Application Type


Data Product Type 
  • Dashboard
  • Report
  • Advanced analytics
  • AI 
  • Others <specify which one>
Technologies
  • BW
  • Tableau
  • Qliksense
  • Talend
  • Dataiku
  • Others <specify which one>

Data Sources 

Note: list of all applications and various environment

  • SAP PF1 (Production environment)
  • SAP WP1
  • SAP PI1
  • BW (versions)
  • iCare CRM 
  • CORE CRM
  • Others <specify the name of the source> 

2.0 Business Process


Not applicable


3.0 Application Feature Overview


Workbooks Technical names 
Data Admin - Customer Corporate GroupBW_WBK_SD_CPSDSO54_0001
Data Admin - Customer GroupBW_WBK_SD_ADM_0002
Data Admin - Customer Master DataBW_WBK_SD_MVSDAD02_0005
Data Admin - End UseBW_WBK_SD_ADM_0001
Data Admin - Material Master DataBW_WBK_SD_MVSDAD02_0006
Data Admin - Material not ConvertedBW_WBK_SD_MVSDSO44_SD0009
Data Admin - Ship-to KABW_WBK_SD_MVSDSO44_SD0002_ADMIN

4.0 Functional Specification


4.1 General Data/Calculations 


4.2 Process Detail 

4.2.1.  Report/Process Definition 

GBR* Data Mapping control

This report provides data to control the mapping done for 2 axis recorded in GBR(*) and was developed to help the data mapping for the CRM Analytics tool (depending of the GBU’s decision to use it or not). The axis are:

  • CORPORATE END USE
  • GBU Customer Group (Group, Sub-Group, Account Type, Customer Classification)

Both are available in the BW WBP reports and in the CRM Analytics.

For the Billing date we suggest to use always 1 year period.

Tabs in the report:


For the END USE mapping always use the Corporate end use TO LINK, to identify easily the customers and products to update in Quikload (GBR).

 (*)GBR - It is a global data repository for the data mapping done in the Quikload Tool

Data Admin - Customer

This workbook works directly with Customer's Master-Data, whether or not the customer has sales.
It is possible to control the GBR(*) customer Corporate group, even if the customer still has no sales in SAP. This report works directly with master data and for that reason the GBU can't be used in prompts (GBU defined only when the customer has sales).

Data Admin - Customer Group
This report retrieves all customers' groups (Corporate and GBU), for customers with sales in SAP. It is possible to be refreshed by GBU.

Data Admin - End Use
This report provides data to control the mapping done for 2 axis recorded in GBR(*) and was developed to help the data mapping for the CRM Analytics tool (depending of the GBU’s decision to use it or not).
The axis are:

  • CORPORATE END USE
  • GBU Customer Group (Group, Sub-Group, Account Type, Customer Classification)

Both are available in the BW WBP reports and in the CRM Analytics.

Tabs in the report:

  • END USE and SALES
  • END USE link
  • END USE axis
  • Application
  • Market
  • Segment

For the Billing date we suggest to use always 1 year period.
For the END USE mapping always use the Corporate end use TO LINK, to identify easily the customers and products to update in Quikload (GBR).

Data Admin - Material not converted

It’s not possible to convert sales unit into prompted quantity unit (PUQ) when that conversion don't exist in SAP.
After choosing the PUQ the report retrieves all materials that are not converted in that unit.

Tip! To convert most quantities in Tonnes or Kilograms, you can use “VTN” (for tonnes) or “VKG” (for kilogram) in the “Prompt Unit Quantity”



5.0 Non-functional Descriptions 


Please populate the relevant section and delete those that are not applicable.

5.1 Usability

5.2 Regulatory Compliance

5.3 Security

5.4 Performance

5.5 Reliability

5.6 Scalability

5.7 Compatibility

5.8 Availability

5.9 Refresh of the Data

Data loaded in GBR at day D it will be updated in BW at D+1.