Access Management

Role Code

Role Description

Explanation



In order to access the tcode ZBW_SD_PC

ZR_*_CA_P05

GBU

In order to load content of data base on GBU

ZR_*_CA_P01

Company Code

In order to load content of data base on Company code

List of authorization objects mandatory for the application.

Authorization object

Explanation

Z*P05

GBU

Z*P01

Company Code

Data flow 

Overview

The objective of the application is to upload forecast data (BFR and Budget) using an excel file. Data are later combined into Global Sales.

The data flow is based on the LSA method. The data visualization is done on the multiproviders MVSDSO61 (SO: Financial Forecast) .

How to use the program:

How to upload Forecast

  1. Access the program via transaction code  ZBW_SD_PC

  2. Inform GBU / Year / Version and select the forecast file on your PC, which has to be excel and with correct format (template below).

  3. Click on  Preview  in order to check the authorization of content and data correction. It may take some time.      
  4. Click on  Check File  to get the summary of the data correction. 
    1. If data is incorrect, it will tell how many error and what line is incorrect on the file. Correct the file and try step 2 again.
    2. If data is OK, the Load File button will be available
  5. Click on  Load File, it will save the data into BW system and run process chain PC_GL_SALES_PROP_99 in order to load from file to PSA and DSO DPSDFC01

How to download Forecast from BW system

In case, user wants to see the last forecast in order to make the next forecast. User can download the file that already loaded into BW to his PC in order to revise and upload again.

Guidelines to upload the BDG / MTP  (Update Feb 2021)

However, in order to download the file, user must be the owner of the file (perform upload the file).

  1. Access the program via transaction code  ZBW_SD_PC
  2. Click on  History in order to see the list of the file that loaded into BW (it will display only last 10 files)
  3. After click on History, there are 2 input fields available:
    1. Source Filename is to enter name of the system file that  user want to download. It can be seen at the first column. It is  case sensitive.
    2. Target Filename is the path and file name that user want to save into the PC. For example, C:\Users\th30085\Downloads\Test .xls .
      1. The folder to download, user must have authorization to save file as well (eg. C:\   or C\WINDOWS  do not allow normal user to save the file)
      2. Filename must end with .xls   If save to .xlsx, the file may not be opened.
  4. Click on  Download
  5. In order to upload again, it is recommend to:
    1. Save as to format excel 2010 (.xlsx)
    2. Change the format of the Calmonth to YYYYMM
    3. Close excel before loading

Note: The user who upload the file can download the file only. It is checked by user ID. Therefore, other users will not allow to download other user file to see the content.

File Template for Upload.

Forecast Template.xlsx

Core Rules 

  1. Authorization of file content will be checked base on GBU and Company code, which get from roles of user on BW system. 
  2. The data will be replaced with the same keys (combination of all fields). If the same key are in the same file, it will be replaced by the last record.

  3. If a user is loading data and it is not completed yet, another user will not allow to click on 'Load Data'.  The user need to wait until the process chain loading complete.

Reporting

Core queries

The core queries are based on the multiproviders MVSDSO61:

Workbook


Query


Financial ForecastBW_WBK_MVSDSO61_0001Financial ForecastBW_QRY_MVSDSO61_0001

Data loadings

Main Process ChainFinal Info ProviderFrequencyStart TimeDuration
PC_GLOBAL_SALES_FORECASTCRSDFC01Daily~3:00am CET~3 minutes
PC_GL_SALES_PROP_99AASDFC01triggered by ZBW_SD_PC

Data Quality Controls

Data comes from SAP system. To compare data between BW and sources systems, check propagation layers.

Operational Documentation

Procedures

<Describe the recurring procedures needed to operate the application (eg. start/pause/terminate/restart the app processes, data preparation, data ingestion, ETL, data visualization, data export, other manual activities)>

Scheduling

<Describe the scheduling in place for the application (eg. existing jobs, trigger time/event based, dependencies)>

Monitoring

<Describe the monitoring checks to confirm the application is performing well (eg. check the overall status, check performance metrics like runtime/data volume/memory/disk/CPU, maintain and react to alerts/notifications)>

Error Handling

<Describe how to handle errors (eg. error codes, description and respective resolution, alert users)>

Known Bugs

<List the existing bugs, its criticality, workarounds and resolution plan.>

Roadmap

<List past & future evolutions for the application (including links to MED/FSD/TSD)>