0% found this document useful (0 votes)
311 views18 pages

SAF XXXX BO DS Job Stat Collection Technical Spec

This document describes the changes needed to create a new job in BODS that will query internal repository tables to provide reporting on job performance and statistics. A new datastore will be created to access the necessary tables. The new job will contain workflows to extract and transform the data, merge it, and load it into SAP BW. Intermediate tables will be used. The target table and required objects like the datasource and DSO will be created in BW. Testing will be conducted on the new job.

Uploaded by

Debajit Basu
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
311 views18 pages

SAF XXXX BO DS Job Stat Collection Technical Spec

This document describes the changes needed to create a new job in BODS that will query internal repository tables to provide reporting on job performance and statistics. A new datastore will be created to access the necessary tables. The new job will contain workflows to extract and transform the data, merge it, and load it into SAP BW. Intermediate tables will be used. The target table and required objects like the datasource and DSO will be created in BW. Testing will be conducted on the new job.

Uploaded by

Debajit Basu
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
You are on page 1/ 18

Data Warehouse

SAF XXXX

SPRINT
BO DS Job stat collection Report

Version 1.0

21.9.2016
SAF 1297

Table of contents:
1 General ............................................................................................................................................3
2 Business Requirement ..................................................................................................................4
3 IT Description .................................................................................................................................5
3.1 Details of new Job. ......................................................................................................................5
3.1.1 New datastore creation. ........................................................................................................5
3.1.2 Workflow and Dataflow changes. .........................................................................................5
3.2 Intermediate Tables. ................................................................................................................... 11
3.3 Target Table in BODS. ............................................................................................................... 11
3.4 Datasource to be created in BW ............................................................................................. 12
3.5 DSO to be created in BW ......................................................................................................... 12
3.6 Multiprovider to be created in BW .......................................................................................... 12
3.7 Queries( to be decided) ............................................................................................................ 12
3.8 Affected Reports ....................................................................................................................... 12
3.9 Impact to other Reporting tool ................................................................................................ 12
3.10 Portal Role Form (if Required) ....................................................................................... 13
3.11 Process Chain Changes Details ..................................................................................... 13
3.12 Dependent / Impacted Objects ....................................................................................... 13
4. Effort Estimation .............................................................................................................................. 14
5. Implementation Information .......................................................................................................... 15
3.2 Pre Go-Live Activities: ............................................................................................................. 15
3.3 Transport List: .......................................................................................................................... 16
3.4 Post Go-Live Activities: ........................................................................................................... 16
4 Test Scenario .............................................................................................................................. 18
6.1. IT Test ............................................................................................................................................ 18

31.07.2019 2 of 18
SAF 1297

1 General
Approval Status
Role Name (approved by) Date
Author Business Requirement
Responsible Tester
IT Application Manager
Author IT Description

HPSM Change Number


Change Number
Cxxx

Timing Realisation
Step Date
IT Spec 21/09/2016
Implementation
Implementation Check
BAT
Go Live

SAP Solution Manager


Message No Findings No

Document History
Version Author Date Remarks
1.0 Debajit 21/09/2016 IT spec
Basu

Declaration note:
0.x  Version w/o approved BU Specification
1.x  BU Specification
2.x  IT Specification

31.07.2019 3 of 18
SAF 1297

2 Business Requirement

The main objective and purpose is creating a report by querying the BODS internal repository tables
which will provide us info about the Job performance and statistics for all applications.

31.07.2019 4 of 18
SAF 1297

3 IT Description
3.1 Details of new Job.

A new BODS Job will be created which will contain a SQL transform to query tables AL_HISTORY and
AL_STATISTICS, the data extracted will fed into BW system via a info package which will be triggered by
a process chain.

The data fed into BW system via info package which will help us in report creation.

3.1.1 New datastore creation.


Below datastore – BO_REPO_STAT will be created which will provide us access to the tables
AL_HISTORY and AL_STATISTICS which holds the repository metadata:

3.1.2 Workflow and Dataflow changes.

The below job JB_REPO_STAT will be created which will contain four workflows:

31.07.2019 5 of 18
SAF 1297

1) Workflow1 - WF_AL_HISTORY

The first workflow will query the table AL_HISTORY and the data will be loaded in a intermediate
oracle table.

It contains the Dataflows - DF_REPO1_STAT and DF_REPO5_STAT.

DF_REPO1_STAT collects data for Sprint Application and DF_REPO5_STAT collects data for
Elisa Application.

DF_REPO1_STAT:

31.07.2019 6 of 18
SAF 1297

SQL Transform:

Data will be in the below format:

2) Workflow2 - WF_AL_STAT

The second workflow will query the table AL_STATISTICS and the data will be loaded in a
intermediate oracle table.

It contains the Workflows - WF_AL_STAT_SPRINT and WF_AL_STAT_ELISA.

31.07.2019 7 of 18
SAF 1297

WF_AL_STAT_SPRINT collects data for Sprint Application and WF_AL_STAT_ELISA collects


data for Elisa Application.

Workflow WF_AL_STAT_SPRINT contains dataflow DF_REPO1_STAT1.

DF_REPO1_STAT1 contains sql transform which extracts the data from table AL_STATISTICS,
the data extracted is not in correct format, the data contained in rows has to be rotated in
columns, a Reverse Pivot transform is being utilised to achieve this functionality after the
transform data is loaded in a intermediate Oracle table, apart from this the aggregated data like
the Rows count and total time taken is also calculated.

DF_REPO1_STAT1:

SQL Transform:

31.07.2019 8 of 18
SAF 1297

Reverse Pivot Transform:

Similarly Dataflow DF_REPO5_STAT1 performs the same functionality like DF_REPO1_STAT1


but for the application ELISA.

3) Workflow3 - WF_DATA_LOAD

The third workflow merges the data from the AL_HISTORY and AL_STATISTICS table

It contains the Workflows - WF_DATA_LOAD_SPRINT and WF_DATA_LOAD_ELISA.

31.07.2019 9 of 18
SAF 1297

WF_DATA_LOAD_SPRINT contains Dataflow DF_REPO1_STAT3 and DF_REPO1_STAT4.

Data for from the AL_HISTORY and AL_STATISTICS table is merged along with the aggregated
data.

DF_REPO1_STAT3:

DF_REPO1_STAT4:

4) Workflow4 - WF_FINAL_MERGE

The fourth workflow merges the data from the application Sprint and Elisa and loads the data in
SAP BW.

It contains the Dataflow - DF_FINAL_MERGE and DF_BW_LOAD.

31.07.2019 10 of 18
SAF 1297

DF_FINAL_MERGE:

DF_BW_LOAD

3.2 Intermediate Tables.


Below intermediate tables will be created:

Table Name DB Type


REPO_STAT Oracle
REPO_STAT_FNL1 Oracle
REPO_STAT3 Oracle
REPO_STAT4 Oracle
REPO_STAT6 Oracle
REPO5_STAT Oracle
REPO5_STAT_FNL1 Oracle
REPO5_STAT3 Oracle
REPO5_STAT4 Oracle
REPO5_STAT6 Oracle
REPO_STAT_MERGE Oracle

3.3 Target Table in BODS.

Table Name DB Type


ZTD_DS_MONITORING Sap BW

31.07.2019 11 of 18
SAF 1297

3.4 Datasource to be created in BW

Datasource Name Description


ZTD_DS_MONITORING Monitoring Datasource

3.5 DSO to be created in BW


DSO Name Description Fields to be included
YPYMONIT Monitoring propagation KEY(KEY FIELD)
layer All the rest will come in
data fields.

3.6 Multiprovider to be created in BW


DSO Name Description Fields to be included
YRYMONIT Monitoring reporting layer Object to be included
YPYMONIT

3.7 Queries( to be decided)

Status: NA

3.8 Affected Reports

Status: NA

3.9 Impact to other Reporting tool

31.07.2019
12 of 18
SAF 1297

Status: NA

3.10 Portal Role Form (if Required)


Status: NA

3.11 Process Chain Changes Details

Status: NA

3.12 Dependent / Impacted Objects

Status: NA

31.07.2019 13 of 18
SAF 1297

4. Effort Estimation
(Effort in working days / not the duration  smallest unit 0.5)

Phase: Implementation 13
IT specification 5,0
Job, Workflow and Dataflow 3,0
Datastore and DB tables creation 0,5
Transformations 1,0
Developer Test 1,0
Reports
QA migration 0,5
QA testing 1,0
Phase: GoLive 1,0
Production migration 0,5
After Go Live analysis and 0,5
support

31.07.2019 14 of 18
SAF 1297

5. Implementation Information
5.1. RISKS:
Serial No Risk Mitigation Plan

3.2 Pre Go-Live Activities:

Sl
No. Activity Sub Activity Yes/No Comments

1 Can the transport be done during Business Hrs? Yes Any day of week
a. Downtime required No
Informed Users if the transport is impacting any
2 report? N/A
Can the transport be done while process chains are
3 running? No
Attach screenshot of output of
ZZ_CHECK_INACTIV_OBJECTS for the last 1 day before
4 and after the transport from B1Q

31.07.2019 15 of 18
SAF 1297

3.3 Transport List:

Transport Transport no. Transport description B1Q-Import B1P-Import


order

3.4 Post Go-Live Activities:

Sl No. Activity Sub Activity Yes/No Comments

1 Is the Object being changed central?


2 Check if objects inactivated after import?
3 Data Reload Required?
Reload and Attribute
Change Run required for
Master data?
Reload required for
Transaction data?
4 Reports available after the change?

5 Any Impact/Risk after Go Live?

31.07.2019 16 of 18
SAF 1297

Sl No. Activity Sub Activity Yes/No Comments


If Yes, List them
6 Quick Backout Plan Available?

31.07.2019 17 of 18
SAF 1238

4 Test Scenario
6.1. IT Test

 Include Pre and Post Screenshots of Objects.

6.2. BAT Test

 Include any BAT scenarios wherever available.

Test Acceptance:

O.K. Error

Test Person ..............................................................................................

..............................................................................................
Name Dep. Date Signature

31.07.2019 18 of 18

You might also like