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

 Name of project or main leader for the application + reporting coodinator

SPRINT stands for Solvay Purchasing Reporting INTelligence

SPRINT is a project launched early 2014, with the main purpose to build and deliver a reporting application to cover both the Purchasing and the PtP reporting needs.

It is hosted in WBP server, collecting information from PF1-050 (PRS), PF1-020 (Solvay legacy ERP), WP1-400 (Rhodia legacy ERP) and RHO-020 (Acetow ERP).

SPRINT application is available for the two “family” of users

• Purchasing & Supply Chain function
• SBS PtP

each one having a dedicated Menu in WBP with the respective queries.

The Sprint reporting is also including queries based on following projects :

• PUNCH (QM Notification - Task/Activity/Causes/Item)
• SRM7 (Shopping Cards)
  
  SRM7 is used by Rhodia and by Solvay (SMILES program is rolling out SRM7 for Solvay; first rollout for NAM and LATAM went live on July 1st 2014, next rollouts for APAC and EMEA planned go-live for 2015).The SRM7 system is shared by both legacies and is connected to both ERP systems.

Tool Leader + IT leader of the application:

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

SPRINT is a project launched early 2014. The roadmap of the project has been sliding in time and at the current date (January 2016) the Purchasing solution has been live for 9 months (first deployment made in March 2015 for APAC users, second deployment made in April 2015 for NAM users, third deployment between May and June 2015 for EMEA users and forth deployment in June 2015 for LAM users); the SBS PtP solution is partially deployed since June 2015.

One of the major objectives of the project is to have and maintain a reporting solution that is kept simple, meaning, that unlike what happened with GSV (where more than 80 queries exist due to multiple copies made for each user request), the aim for SPRINT is to keep the number of queries limited.

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

See also previous technical dataflow : SPRINT - Technical Data Flow.pptx

https://drive.google.com/open?id=0BzuKacO6n43ic2tUNjhKelRsWWc

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

Data Mappings

Directory 01. Data Mapping https://drive.google.com/open?id=0B6ePM5y2xkfkLU1WV1JHUjFEdTQ

SPRINT - Data Mapping - Master Data

 https://drive.google.com/open?id=1ECdjg6yFQ_v6bTEWbjuUni8NRNbSvGw0EAApb8XA358

SPRINT - Data Mapping - Purchase Schedule Line V2

https://drive.google.com/open?id=1-TqvFdKifRXQU5vwdBFEXcW9rje9PDNs3EMfCpZf7dc

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

There are some differences between rhodia and solavy data flow.

For exemple, in function module of extractor ZFM_BW_COCKPIT_THDR, in WP1 (Rhodia), the date of rejection (ZWDATE_REJECT) is recovered in table /cockpit/thdr.

It's not the case in PF1 (Sokvay), here ZWDATE_REJECT get the date in /COCKPIT/THDR-CH_TIMESTAMP when STATUS = 13 (this rule will may be applied in Rhodia in the future).

In bw, in transformation between dso DP_RDSF and DB_RDSF, some fields like accounting doc number, posting date, controlling area... come from FIAP.

For Rhodia side, we used DSO DBFIAP01 to take data. For Solvay we used two dso: DPFIAP02 and DB_FIAP2.

Infopackages for datasources, are in delta mode. THe delata is based on change date (the change date is also implemented when it's a creation of cockpit document).

WBS determination reading Settlement Rules 

This rule concerns only RCS & Solvay FIAP data (transformation between DBFIAP01/2 et DB_FIAP1/2). Acetow is not concerned.

The Settlement rules (table COBRB) are loaded every days by another application (RCS : Dso DSRCOBRB / Solvay : Dso DSSCOBRB).

Reuse of rule between ODS_PMEN to DBFICS02. 

Case WBS element is already determined for the FIAP record => keep it, no further determination.

Case WBS element is empty and CO order is filled => read settlement rules

         First check is a previous determination has been done (lookup on Dso)

=> If yes, take the WBS element stored

=> if no, read settlement rules

The check is done to avoid dupplicates as the WBS element is part of the key, and settlment rules can be changed even for the past.

NB: the check can be skip for performance purpose essentielly (case of an initialization for example) => Flag in Global Filter SPRINT/DB_FIAP1 or DB_FIAP2/ put Y in low value and Y. Do not forget to put it back to N afterwards. 

NB : In case of a reload of the DSO, the first WBS Element determination is lost, as the DSO is previously is empted. The WBS Element will be the one correcponding to the current settlement rules

To see Settlement rules on ECC side :

-> use transaction KO03 with Co Order 000010528547 (for WP1)

-> button 'Settlement rule'

How COBRB table is read

=> Read only line Category WBS

=> Use firstly Settlement Type 'PER', then, if not found or out of validity, use 'GES'
=> Use firstly the higher % Settlement percentage rate

Segmentation Domaine/Segment

* The rule for the leading domain and segment is :
* First we use the domain/segment of the vendor
* Else we use the domain/segment of the creditor
* Else we use the domain/segment of the material group of the
* Purchase Order
* Exceptions
* 1- If the domain of the vendor is "LO - Logistic (8)"
* We used this value as leading Domain and take
* the corresponding segment
* 2- If the domain of the creditor is "LO - Logistic"
* We used this value as leading Domain and take
* the corresponding segment

LeadTime

Lead Time https://drive.google.com/open?id=0By6hfdCwPGY_a09sQWJ4NHlWcnc

Material Group (C_MAT_GRP)

The material group can be found at different places:

• masterdata C_MATNR2 : loaded via datasource 0MATERIAL_ATTR.
• masterdata C_PO_ITM : loaded via datasource DTS_BW_PO_ITM. Caution special rule for Item Category 9 "Service" (EKPO-PSTYP) or empty material group (EKPO-MAKTL)
• Schedule line Dsos/Cubes : load via 2LIS_02_SCL, extended. Caution same special rule, but Abap coded slightly differently => DO NOT use it, material group is not always correct.
• FIAP Dsos/Cubes : a lookup is done on Business level of Schedule line => DO NOT use it, material group is not always correct.

Usage of tables :

• Z1M_BW_MAT_GRP for Solvay PF1
• ZWPUT042 for RCS WP1 and Acetow RHO

https://drive.google.com/open?id=1tJe9gPLtq-L6L813vybQq5Lk7nYUJ5PseWDq_a9_RSY

Important : The Material Group in schedule line and FIAP Dsos & Cubes is partly false.

Currently Core & QV queries is using C_MAT_GRP from FIAP or Schedule lines. It has to be changed with C_PO_ITM attribut when Business validates it.

• Solvay cases (the list might be not exhausted)
  • Issue for S1.2009
    Example PO 4511000082/1340 => Document date 31.03.2009 => FI document 6311201583/5835/2015
    Only one part of PO for S1.2009, having a schedule line over 2013 have been loaded into BW. On may 2015 initialization, the PSA was not well loaded, and no action have been done to correct it, so part of S1.2009 is missing. No correction have yet been done as Business DSO for schedule line is using ratio in addition, and a whole re-initialization would take several weeks.
  • PO with schedule line previous to 2013 but in actual FI documents
    Example PO 3100441596 => document date 09.07.2012 => Good Receipt / MM Invoice en 2012 => FI document 6311603854 / 5782 / 2015. These PO have not been loaded into BW. The FI documents do not have PO information.
  • Deleted PO items
    Example PO 3100578083/20 => 2 FI documents created (6311642636/0292/2014 and 6311644101/0292/2015) before the PO item deletion the 22.12.2015.
    The deleted PO items are not kept into BW (0PROCESSKEY non kept between Propa & Business DSOs). The FI documents have been reloaded several times in 2016. As the PO item is not existing anymore in the business DSO, the FIAP document can not be filled with PO information
• Rhodia cases (the list might be not exhausted)
  • Shipment Cost Number archived or other for service PO
    Example PO 4502271249
    PO 4502271249 => entry sheet 1005459308 => Shipment Cost 2164736
    This PO has had a determined material group 0433 when the Shipment Cost was existing on WP1 (table VFKP)
    Today the shipment 2164736 can not be displayed anymore in WP1, so is not existing anymore in table VFKP. Are the shipment costs archived at anytime? et just deleted some how?
    The material group can not be determind any more when the PO schedule line was loaded again when the invoices  were created the 02/05/2016
    
    The material group is also available in masterdata C_PO_ITM.
    For this PO  4502271249, the material group is 0433. No modifications on the PO have been detected, so no additional loading even when the invoices were created. The material group remains 0433. Caution, if the masterdata C_PO_ITM is reloaded today, the material group would be reset to empty!
  • Missing combination in table ZWPUT042
    Example 4502642333. Empty also in masterdata C_PO_ITM as no corresponding value for 9008/12/0003 is existing in table ZWPUT042
    Caution, if the combination is added in table ZWPUT042, previous PO will not be updated, and masterdata C_PO_ITM can not be fully reloaded because Shipment Costs Number are archived or deleted.

   

Web Dynpro

Web dynpro documentation: https://drive.google.com/drive/folders/0B6fsFFWhLf2yZmF2c1VWS21WVXc

Web Dynpro are used to data integration in some master data (list in documentation).

Dependencies with other applications

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

Data loadings

Info providers and objects loaded

See Global Filters (C_GLBFILT) part, it is possible to hold loadings from one or several souce systems.

Main Chains

Slave Chains

Other Chains

Loading frequency

Process Chain PC_SPRINT_DAILY runs daily, Sunday night to thursday night, around 5am.

Process Chain PC_SPRINT_TR_DS1 runs weekly on sundays at 12am

Average performance

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.

SPRINT training & SPRINT presentation 

https://drive.google.com/a/solvay.com/folderview?id=0B5Ivsv4WTtUbVktFZlNVRkNYU1k&usp=sharing

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 year + 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

For information, at the reloading of readsoft there have been issue during activation of data in DSO DB_RDSF1 & DB_RDSF2.

Somes rows had currency = USA, chinese character in field wc user and "!" in the beginning of field Reference document number.

So there is an exclusion in DTPs when currency = USA and routines to clear stranges characters for wc user and reference document number. 

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