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
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
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
List of application role + menu role and explanation if we have several applications role with specials rules.
| Role Code | Role Description | Explanation |
|---|---|---|
List of autorisation objects mandatory for the application.
| Authorization object | Explanation |
|---|---|
Reporting documentation drive folder:
https://drive.google.com/drive/folders/0B0qn89R0RGdqYkZZOFZyYXlXVkE
https://drive.google.com/drive/search?q=MPR_CHG5
pre query used
Exemple of dataflow overview :
BW OTC - Order Changes DataFlow
The DSO DSO_DLV1 + DSO_DLV2 + DSO_DLV3 are used for EHS application only
See EHS SVT documentation in the wiki or in the link below :
https://drive.google.com/file/d/1UuzZGuQKAlhClQm9meh4_ZDD92PK5WQWFYu6zYHKPg8/view
Dataobject : DSO_CHG6
Only one query
Query : BW_QRY_DSO_CHG6_0001 BW - Follow-up currency change on customer sales(Core Query)
Focus on the DSO_SD02 Sales Document Schedule Line => used for APO system in the past and now for Dynasys
More general doc : http://help.sap.com/saphelp_di471/helpdata/en/dd/55fb20545a11d1a7020000e829fd11/content.htm
Source 1 : 2LIS_02_SCL Purchasing Data (Schedule Line Level) this one is used on Purchase dataflow (SPRINT project)
Source 2 : 2LIS_11_VASCL Sales Document Schedule Line
Sales Order is a contract between a customer and sales organization for supplying goods or service to customer within a agreed time period. Data on the sales order screen is derived from Customer Master Table and Material Master Table for a particular sales area.The sales area that accepts the inquiry is responsible for completing the contract. T-code for sales order is -
To create sales order we need data at four levels-
1.Organization data : Organization data is first screen of sales document which contains fields like Sales organization,distribution channel,division,Sales Office ,Sales Group etc.
2.Header data : Sales order header contain many tab(sales,shipping,billing etc.). Header essentially contains information mostly from the Customer Master in the Transaction. We can click on header 
button for sales header screen display.
Sales Header screen is displayed as below -
3. Item data : This contains line item .Line item contain all information related to customer / material / quantity .
4 . Schedule line data : For each line item their are schedule line items.This data describes quantity and date. Select item lines for item data and click on schedule line 
buttons.
Click on schedule line 
button AGAIN -
Their are three views for schedule line -
Purchase application, Dynasys + Qlickview Dashboard with all naming convention without beginning QV but with RBS in the technical name.
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