General presentation

Objective of the application

To upload forecast data (BFR and Budget) from non-SAP data, which is excel file to combine data into Global Sales.

Tool Leader + IT leader of the application: Anon Kasemvilas + Sandra Silveira

How to use the program:

How to upload Forecast

Access the program via transaction code ZBW_SD_PC
Select the forecast file on you PC, which has to be excel and the correct file format (the total length must shorter than 121 characters)
Click on Preview in order to check the authorization of content and data correction. It may take some time
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
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
The data from DSO will go to the cube automatically every 1 hour base on process chain PC_GL_SALES_PROP_01

TECHNO - BI TEAM > Forecast > image2017-3-15 19:21:30.png

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.

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

Access the program via transaction code ZBW_SD_PC
Click on History in order to see the list of the file that loaded into BW (it will display only last 10 files)
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.
Click on Download
In order to upload again, it is recommend to:

Save as to format excel 2010 (.xlsx)
Change the format of the Calmonth to YYYYMM

TECHNO - BI TEAM > Forecast > image2017-3-15 19:29:10.png 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

Roles & Access

Roles and access

List of application role + menu role and explanation if we have several applications role with specials rules.

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

Authorization objects

List of autorisation objects mandatory for the application.

Authorization object	Explanation
Z*P05	GBU
Z*P01	Company Code

Dataflow overview

Use the google presentation below as a template. This google presentation must be saved in the Reporting GDrive folder under the corresponding application. Then post the link to the document here.

Reporting documentation drive folder:

https://drive.google.com/drive/folders/0B0qn89R0RGdqYkZZOFZyYXlXVkE

Exemple of dataflow overview :

Template Application name DataFlow

Functional and Technical rules on Workbench + Reporting

Rules & Explanations

Authorization of file content will be checked base on GBU and Company code, which get from roles of user on BW system.
The data will be replace with the same keys, which are combination of version, GBU, Company, Sales Employee, Distribution Chanel, Ship-to, Source system, and material. Although if the same key are in the same file, it will be replaced by the last record.
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.
The file content will check by following criteria:

Object	Description	Check by comparing to
0VERSION	Version	No Checking
0LOGSYS	Source System	Table TBDLST
0CALMONTH	CalMonth YYYYMM	YYYY > 2000 or YYYY < 2999 MM >=01 or MM <=12
CPFCTR1_2	BFC GBU	Table /BIC/MCPFCTR1_2 (GBU Master data)
C_COMPCDE	Company Code	Table /bic/pc_company (Company code Master data)
C_DISTCHN	Distribution Channel	Table /BIC/TC_DISTCHN (Distribution Master data)
C_SHIPTID	Ship to code	Table /bic/pc_customr (Customer Master data)
C_SALEMP	Sales Rep	Table /BIC/MC_SALEMP (Sales Rep. Master data)
C_MATNR2	Material Code	Table /bic/pc_matnr2 (Material Master data)
0BASE_UOM	Unit Quantity	Table T006
K_FCT_QTY	BFR Quantity	Contain number and '-' sign only
0LOC_CURRCY	Currency	Table /bi0/scurrency
K_FCT_SAL	BFR Sales	Contain number and '-' sign only
K_FCT_CM	BFR Contribution Margin	Contain number and '-' sign only

Data loadings

Info providers and objects loaded

PC_GL_SALES_PROP_01 execute every 1 hour to load data from propagation layer to cube

PC_GL_SALES_PROP_99 trigger by ZBW_SD_PC from user to load from file to PSA and DSO DPSDFC01

Loading frequency

Depend on users to load via T-Code ZBW_SD_PC. However, this loading will be load only upto propagation layer.

Process chain PC_GL_SALES_PROP_01 will run every hour In order to load data from propagation layer to reporting layer.

Average performance

The step 'Preview Data' mayl take time (less than 1 minute) in order to check the content of the data comparing to the master data.

The step 'Load File' may take time around 1 - 5 minutes.

Record Keeping

Log of loading data will be kept on DSO DPSDFC02 with the detail of filename, username, date and time that load data, the status of loading and GBU. However, it will display on the tcode only last 10 records.

Reporting

There is no query base on the forecast only. The data will combine with the global sales multi-provider