This report / application is to track the Purchase Info Record price change information by change date
Before this report, the business was retrieving information on Purchasing Info Record (PIR) price changes from the following back end reports (the reports have a different name per back end report in PF1 and WP1 but are basically the same):
TRANSACTION | PROGRAM | DESCRIPTION |
ZWPU83 | ZWPUR05800 | Report for PIR Price Modifications – WP1 |
Z1M_PIR_PRICE_MODIFS | Z1M_PIR_PRICE_MODIFS | Report for PIR Price Modifications – PF1 |
The above reports provide differences in Price only when the calculations based on the Condition records assigned to the PB** conditions set at PIR (Changes to the PIR’s price condition, which are saved in table CDHDR with OBJECTCLAS = COND_A.). But, there are several other factors that impacts the PIR price information changes. This application is to handle all the relevant factors that affect the PIR price changes.
Tool Leader + IT leader of the application:
Reporting Coordinator : Duarte Costa (Lisbon)
Purchasing Data and P-t-P Interface Manager : Sylvie Severini (Brussels)
D&A and buyers are the key users of this report
Business requested a BW report that can provide a structure similar to the above mentioned reports in PF1 and WP1 and that is able to provide the price changes per material Base Unit of Measure and also per last condition record unit of measure considering changes done not only to the condition records but the Price Unit information and its quantity conversions.
Requestor: Luis Dias
List of application role + menu role and explanation if we have several applications role with specials rules.
| Role Code | Role Description | Explanation |
|---|---|---|
| ZR_RCS_CA_M04 | SPRINT - Purchasing | Role menu ZR_RCS_CA_M04 uses application role ZR_RCS_SPRINT2_A01 linked to IA_PUR_SPRINT* Authorization Object ZBI_SPRINT2 / Authorization on zone, GBU, Plant. |
List of authorization objects mandatory for the application.
| Authorization object | Explanation |
|---|---|
| Plant (C_PLANT) | ZR_*_CA_P02 ZR_7866_CA_P02 => Plant 7866 - Chalampé (ex 7027) - (Cie ZFR9) ZR_TOUT_CA_P02 => All Plants "Solvay" |
Reporting documentation drive folder:
https://drive.google.com/drive/folders/0B0qn89R0RGdqYkZZOFZyYXlXVkE
Exemple of dataflow overview :
Template Application name DataFlow
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