This application is not really a BW application, but a collection of DSO to provide data to an external tool nammed pVelocity.
pVelocity is a tool which help the Novecare GBU to optimize their Assets.
In BW, we extract the data from RCS and then generate flat files on a WBP folder and it is the pVelocity tool which is transfering the file from BW to pVelo.
IT Learder is now Nathalie Manirakiza in the IS-RtR team
The Tool Leader is in the Novecare GBU.
The reporting coordinator is Sandrine Micollet
There is around 50 users on pVelocity tool WW, all working in the Novecare GBU.
They are Asset Manager, Industrial manager and also financial controlers.
This project was launch using BW as Hub because the pVelocity team was not allowed to extract data directly from RCS (WP1).
It was a kind of shadow project.
There is no direct usage of the BW infoproviders, so no roles nor authorizations.
The data flow is very simple because in the main cases, it re-use existaing DSO which are already loaded for other applications.
Then an abap program generates the files in a text format.
The namming rule for the files is a prefix represented the content of the file, then "–" and then a timestamp, which is the dateTime (YYYMMDDHHMMSS)
| File name | File description | BW Source | Type of data |
|---|---|---|---|
| CD | Distribution Channel | 0DISTR_CHAN | Text |
| CDSA | CD x SA | C_CDSA | Master Data |
| COAREA | Controlling Area | 0CO_AREA | Text |
| COMP | Companies | 0COMP_CODE | Text |
| CURR | Exchange rate | TCURR table | Transactionnal |
| IECRA | IECRA | 0G_CWWE01 | Master Data |
| MARM | Material Alternative unit of measure | ODS_MARM | Master Data |
| MATNR | Material | C_MATNR C_MATPLNT | Master data & text |
PBOM | Standard production cost | ODS_PCP1 | Transactionnal |
| PLANT | Plant | 0PLANT | Master Data & Text |
| PROD | Produced quantity | ODS_PP01 | Transactionnal |
| PROFITCTR | Profit Center | 0PROFIT_CTR | Master Data & Text |
| RAWP | Raw material costs | ODS_PCP3 | Transactionnal |
| RESOURCE | Resources Unit price | ODS_PCP8 | Transactionnal |
| RSAL | Resales of the month | ODS_PA06 | Transactionnal |
| SA | Division | 0DIVISION | Text |
| SHIP | Sales of the month | ODS_PA06 | Transactionnal |
| STDCOST | Standard cost by cost Elements | ODS_PCP7 | Transactionnal |
| TRANSFER | Transfer movement between plants | ODS_IC01 | Transactionnal |
| TVAPT | Sales documents item category | 0ITEM_CATEG | Text |
| TVFKT | Sales billing type | 0BILL_TYPE | Text |
| UOM | Unit of Mesure | T006 table | Master Data |
| VALSTR | Value Stream | C_VALSTR | Master Data & Text |
| VC | Standard Variable costs | ODS_PCP3 | Transactionnal |
| ZSECT | Global Business Unit | C_ZSECT | Master Data & text |
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 application (BW, QV, Externals tools like PVelocity or Dynasis etc...
Detail of process chain, list + link between or special event done for the loading
Detail of frequency : monthly; weekly or else
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 |
Give details if any historisation is done, example: keep only data greater than beginning of Y-3
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.
List the most important and complex queries only with a link to the documentation
Give detail on all complex functionalities: list most important and/or complex KPI, query jump, alerts
Indicate if there are broadcasts and give some details on the broadcast settings.
Give the list and explanation on the known, not-solved, bugs.
List recurring procedures
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