General presentation

Objective of the application

Describe in a few words the content of application + link with functional or technical specifications (google links) done with during the project or linked with PPMO

Tool Leader + IT leader of the application: Name of project or main leader for the application + reporting coodinator

Contact on ECC side for MM => Henri OLLIVIER

Usage information

How many users? Which user category ? Is there critical period ? Which geographical perimeter? Describe in one sentence: around 50 users, worldwide or 200 users / European Site

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.

NB: The role menu ZR_RCS_ALL_MENU "Role composite with all role Menu and perimeters" gives access to all role menu. When asking for a new role menu, do not forget it is added to that one.

NB: ZR_RCS_SPRINT_A01 & ZR_RCS_SPRINT_A02 are obsolete

Authorization objects

List of autorisation objects mandatory for the application.

See also file maintained by Authorization team : BW Catalog of Roles / link: https://drive.google.com/open?id=10GEfKYqrT1eeTO_uHYAheL1GX7L5y_pvH0KQU64qh5I

Dataflow overview

See SPRINT Dataflow https://drive.google.com/open?id=1G0eplgqwvDwJjtYoziwdE2NPT5YtSjm72fUXXlPcEhM

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 :

Functional and Technical rules on Workbench + Reporting

Rules & Explanations

Masterdata RULE1 on Vendors (C_VENDID) / Class attribut (C_VENCLS)

This rule concerns only Solvay vendors (from PF1) P*, which are employees not existing in PRS.

These vendors are partly created in Solvay PF1 and it is then not possible to set Class = 'X' in Solvay PF1.

For those vendors, the class has to be set to 'X' in BW.

The intervall of vendor is managed in Global Filter (C_GLBFILT). Currently P000000000 to PZZZZZZZZZ

Masterdata RULE2 on Realigned Material Group (C_MATPUR2) 

All realigned material group are existing on Solvay, descriptions are then filled from PF1 only. Only english description are required.

Masterdata RULE3 on Terms of Payment (C_PMNTTRM) 

Terms of Payment on SAP side are managed into 2 tables. TVZBT for sales (customers), T052U for purchasing (vendor). 

Payment terms can be common. On BW there is only one object for Payment Terms. T052U has to be loaded first. The description of common terms will be then TVZBT's one.

Note that keys are differents, no matters, the last description is kept.

ReadSoft DataFlow

SPRINT - Data Mapping - Read Soft https://drive.google.com/open?id=1YV_8OtL4M16bszi1fqVE99O19fPk7EsEYhc9UK4DoP0

Dependencies with other applications

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

Data loadings

Info providers and objects loaded

Main Chains

Slave Chains

Other Chains

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

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.

Main queries

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

Main functionalities

Terms of Payment

MaintenanceBroadcast

No Broadcast implemented

Known bugs

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

Recurring procedure

Variables (TVARV/Global Filters)

Variable (TVARVC)

Global Filters (C_GLBFILT)

FIAP Reloading

FIAP for SPRINT Dsos (CR_PUAP1/2/3), and Cubes (CR_PUAP1/2/3) have been reloaded several times since project golive.

At least is requested : current exercice + 3 previous ones.

Example 2016 => 2016 + 2013 to 2015

See ModOp SPRINT reloadings https://drive.google.com/open?id=1qSUGEl6v1Iftdc9N1CP7ytFxW2ew2lGO0eEmy4Gvwk0

It is important to check image Before/After. Only opened periods could be differents.

FIGL Reloading

Caution, take into account special periods 013 to 016, overwise December figures will be wrong.

Special periods 013 to 016 are at last stored on period 012.

See ModOp SPRINT reloadings https://drive.google.com/open?id=1qSUGEl6v1Iftdc9N1CP7ytFxW2ew2lGO0eEmy4Gvwk0

It is important to check image Before/After. Only opened periods could be differents.

ReadSoft Reloading

See ModOp SPRINT reloadings https://drive.google.com/open?id=1qSUGEl6v1Iftdc9N1CP7ytFxW2ew2lGO0eEmy4Gvwk0

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

Useful transactions / programs