Roles & Access
Role Code | Role Description | Explanation |
|---|---|---|
| ZR_RCS_CA_M09 | PS - Project Costs | Role menu for all project costs queries |
| ZBI_RCS_PS_A02 | Project Costs and Structures Analysis - End User role | Application Role:
|
Authorization Objects
Authorization object | Explanation |
|---|---|
| C_AUTHMA | Authorization scope : ZR_*_CA_P00 |
Link to the BW Catalog of role
https://drive.google.com/open?id=10GEfKYqrT1eeTO_uHYAheL1GX7L5y_pvH0KQU64qh5I
https://drive.google.com/open?id=1rKhYbUaglLB11ESjep34L9ttFZhrid_jQFc-rDFgpxc
Reporting documentation drive folder:
https://drive.google.com/open?id=0B_p_Afe8sjVlUW1BWFR2ZElITlk
PS - Project Costs (aka PeC & Cash) is a set of BW queries on Rhodia legacy (WP1), Solvay legacy (PF1) and Acetow (RHO) area.
It mainly aims at providing detailed economic survey of projects: Budget, Commitments, Actual costs (PeC), Cash out (CAPEX) and Cash Future (PeC and CAPEX are wording used in BFC to follow-up Investment projects)
The reporting coordinator is Charlotte Rollier.
Usage information
This application has more than 1 000 users Worldwide.
Target users are Controlling teams, but also Project responsibles.
The Critical period is from D-5 to D+5.
History
This application was created in 2013 and it replaces the former RCS Project costs reporting (based on multiprovider MPR_PS004) that should not be used anymore.
https://wiki.solvay.com/x/yro_AQ
https://wiki.solvay.com/x/1r8_AQ
https://wiki.solvay.com/x/1Lo_AQ
COLMAR uses an APD based on a MPR_PS014 query.
Customer Support Wiki (To update):
https://wiki.solvay.com/x/NQI8
RtR presentation:
https://drive.google.com/open?id=1xLR2eV7ZtyYsbGeYOSVL0TCgdp-mcQzdYvbLtZWaL4c
Main queries
BW_QRY_MPR_PS014_0001 - Project costs & Cash out (Core query)
Main Process Chain | Final Provider Loading | Frequency | Time start | Duration |
|---|---|---|---|---|
<Describe the recurring procedures needed to operate the application (eg. start/pause/terminate/restart the app processes, data preparation, data ingestion, ETL, data visualization, data export, other manual activities)>
<Describe the scheduling in place for the application (eg. existing jobs, trigger time/event based, dependencies)>
<Describe the monitoring checks to confirm the application is performing well (eg. check the overall status, check performance metrics like runtime/data volume/memory/disk/CPU, maintain and react to alerts/notifications)>
<Describe how to handle errors (eg. error codes, description and respective resolution, alert users)>
<List the existing bugs, its criticity, workarounds and resolution plan.>
Former Working Capital and Project Costs flow should be decommissioned in a near future.