The ship-pad report is based on "Order Book - To be Issued (SO + PO)".
Tool Leader + IT leader of the application: Name of project or main leader for the application + reporting coodinator
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
In order to meet Aero requirements. several elements were incorporated into existing Order Book.
Same role from Global Sales
| Role Code | Role Description | Explanation |
|---|---|---|
| ZR_RCS_CA_M49 | ||
List of autorisation objects mandatory for the application.
| Authorization object | Explanation |
|---|---|
Reporting documentation drive folder:
https://drive.google.com/drive/folders/0B0qn89R0RGdqYkZZOFZyYXlXVkE
Exemple of dataflow overview :
Template Application name DataFlow
New Composite Provider CPSDAE03 based on HANA Calculation View CV_SD_AE_CPSDAE03
Initially joins DSOs below:
For Sales Order, the "rest to be delivered" (K_NONDEL) is stored, at delivery line level, in DBSDSO9D.
For Purchase Orders, it is calculated dynamically in the view accessing tables below:
DBSDSO66 - to get PO quantity / Confirmed quantity (by schedule line)
DBSDSO69 - to get Delivery quantity
New fields were added to DBSDSO9D and populated in Transformations below
Orders already shipped (DBSDSO56) are not relevant for Ship-pad. They are excluded in the query using filter “Actual GI date = blank”.
New recursive Transformation was created to populate “Passed Specs flag”.
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.
Workbooks:
BW_QRY_CPSDAE03_0001 – Ship pad report
BW_QRY_CPSDAE03_0002 – Open Order – External
BW_QRY_CPSDAE03_0003 – Open Order – Internal
Last 2 queries include only Sales Order (filter on C_ITM_GS-C_SDCATEG = ‘SO’).
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