General presentation

Objective of the application

The Objectif for this application is the give to Authorisations team reports from ST03N t-code in BW with OLAP and way to manage report with reporting tool instead t-code in ECC.

Usage information

By infoproviders since January 2015 :

	Calendar Year/Month	JAN 2015	FEB 2015	MAR 2015	APR 2015	MAY 2015	JUN 2015	JUL 2015	AUG 2015	SEP 2015	OCT 2015	NOV 2015	DEC 2015	JAN 2016	FEB 2016	MAR 2016	APR 2016	MAY 2016	JUN 2016	Overall Result
InfoProviders Used		Query Access Counter	Query Access Counter	Query Access Counter	Query Access Counter	Query Access Counter	Query Access Counter	Query Access Counter	Query Access Counter	Query Access Counter	Query Access Counter	Query Access Counter	Query Access Counter	Query Access Counter	Query Access Counter	Query Access Counter	Query Access Counter	Query Access Counter	Query Access Counter	Query Access Counter
Overall Result		62	30	19	18	6	135	19	88	17	23	44	18	29	7	12	19	7	6	559
CUBE/A/CUB_GRC01	Cube - GRC Transactions Usage	57	28	18	17	6	92	19	80	16	20	44	18	29	7	12	18	7	6	494
ODSO/A/DSO_GRC6	DSO - GRC Transactional Usage Daily	2					15		4		1									22
ODSO/A/DSO_GRC5	DSO - GRC Transactional Usage Weekly	0					14		3		1									18
ODSO/A/DSO_GRCL	DSO - GRC Tcode linked to Role Composite/Simple	0	0				14		1		1									16
CUBE/A/CUB_GRC1A	Cube - GRC Transactions Usage - APO	3	2	1	1					1					0		1			9
ODSO/A/DSO_GRC4	DSO - GRC Users			0																0

By infoproviders since January 2016 :

	Calendar Year/Month	JAN 2016	FEB 2016	MAR 2016	APR 2016	MAY 2016	JUN 2016	Overall Result
InfoProviders Used		Query Access Counter	Query Access Counter	Query Access Counter	Query Access Counter	Query Access Counter	Query Access Counter	Query Access Counter
Overall Result		29	7	12	19	7	6	80
CUBE/A/CUB_GRC01	Cube - GRC Transactions Usage	29	7	12	18	7	6	79
CUBE/A/CUB_GRC1A	Cube - GRC Transactions Usage - APO		0		1			1

By Queries since January 2016 :

	Calendar Year/Month	JAN 2016	FEB 2016	MAR 2016	APR 2016	MAY 2016	JUN 2016	Overall Result
Query		Query Access Counter	Query Access Counter	Query Access Counter	Query Access Counter	Query Access Counter	Query Access Counter	Query Access Counter
Overall Result		29	7	12	19	7	6	80
ELEM/A/BW_QRY_CUB_GRC01_0001	BW GRC - User Usage	28	6	11	17	4	5	71
ELEM/A/BW_QRY_CUB_GRC01_0001_BCAST	BW GRC - User Usage (Broadcast)	1	1	1	1	3	1	8
ELEM/A/BW_QRY_CUB_GRC1A_0001	BW GRC - User Usage APO		0		1			1

History

Provide some history of the application : When was it created ? What was the initial project ? Who was the original requestor ? If possible provide link to the project information

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
ZBI_RCS_AU_A02	Authorization transactions follow-up - End User Role	Applications
ZR_RCS_CA_M34	AU - Authorization transactions	Menus

Authorization objects

List of autorisation objects mandatory for the application.

Authorization object	Explanation

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

Detail of main topics with explanations of the rules and only the main + special rules about queries to run and use in the correct way

Dependencies with other applications

Dependencies with other application (BW, QV, Externals tools like PVelocity or Dynasis etc...

Data loadings

Info providers and objects loaded

Detail of process chain, list + link between or special event done for the loading

Loading frequency

Detail of frequency : monthly; weekly or else

Average performance

if possible, give some information on average process chain duration, amount of data loaded and total data volume example: daily process chain loaded in 30 min, weekly chain loaded in 1h15, with around 2k to 10k lines in DELTA mode for a total of 10M lines in cube. The purpose is to give a general overview of the volume of data managed y the application

Key Figure	Estimation
~ Average Process Chain Runtime
~ Average nb of rows loaded per load
~ Total nb of rows loaded (if full)
~ Average Runtime for 10k lines

Record Keeping

Give details if any historisation is done, example: keep only data greater than beginning of Y-3

Reporting

Queries End User Documentation

Query end user documentation should be created in the public "Customer Support Wiki" space under the corresponding BW application page : BW - Application. Technical query query documentation, if necessary should be added as a sub-page of this documentation using the BW Technical Query Documentation template.

The workbook below is the most used :

TECHNO - BI TEAM > BW Global - Authorization transactions > image2016-7-27 23:15:17.png

TECHNO - BI TEAM > BW Global - Authorization transactions > image2016-7-27 23:16:2.png

Main queries

List the most important and complex queries only with a link to the documentation

Main functionalities

Give detail on all complex functionalities: list most important and/or complex KPI, query jump, alerts

Broadcast

Indicate if there are broadcasts and give some details on the broadcast settings.

Maintenance

Known bugs

Give the list and explanation on the known, not-solved, bugs.

Recurring procedure

List recurring procedures

Planned Evolution

Detail planned major evolution if already known. Example: complete decommissioning of application is planned in 2017 / Extension to solvay perimeter planned in 2nd semester of 2016