General presentation

Objective of the application

Tool Leader + IT leader of the application: 

Usage information

History

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

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. It is then not possible to set Class = 'X' in ERP.

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

Data loadings

Info providers and objects loaded

Main Chains

Slave Chains

Other Chains

Loading frequency

Average performance

Record Keeping

Reporting

Queries End User Documentation

Main queries

Main functionalities

Terms of Payment

MaintenanceBroadcast

No Broadcast implemented

Known 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

Useful transactions / programs