General presentation

Objective of the application

The objective is to load via a flat file the data to adjust the Budjet and the Reel. You can find examples of adjustments in the file bellow :

Tool Leader + IT leader of the application: 

Ludovic Depoix & Selim Ulhasan

Usage information

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

History

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

Roles & Access

Roles and access

List of application role + menu role  and explanation if we have several applications role with specials rules.

Role CodeRole DescriptionExplanation
ZR_RCS_CA_M731







Authorization objects

List of autorisation objects mandatory for the application.

Authorization objectExplanation






Dataflow overview (Source => composite)

Functional and Technical rules on Workbench + Reporting

Rules & Explanations

You can find the functional and technical documentation with the link bellow :

Upload a file in BW 

Open the SAP Logon  and double click "BW - Production - WBP"

Enter the transaction code ZBW_COSTA_CORRECTIV in the search bar and click 


If you can not access the transaction, you must create a ticket and ask for the role ZR_RCS_CA_M731 - CT - COSTA Transactions. (It is not a standard role, it is not in the list proposed in the form so you should request it in the field: SAP WBP - BW Business Warehouse : Comment)

Before starting, it is recommended to close and save your excel files to avoid interferences with excel

  1. Select the file to be uploaded. 






Dependencies with other applications

Dependencies with other application (BW, QV, Externals tools like PVelocity or Dynasis etc...

Data loadings

Info providers and objects loaded

Process Chain :  PC_CT_CORRECTIVE_2_01 

Loading frequency

The process chain is loaded at each new flat file integration by the user via the transaction and the program.

Average performance

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 FigureEstimation
~ Average Process Chain Runtime
~ Average nb of rows loaded per load
~ Total nb of rows loaded (if full)
~ Average Runtime for 10k lines

Record Keeping

Give details if any historisation is done, example: keep only data greater than beginning of Y-3

Reporting

Queries End User Documentation

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.


Main queries

List the most important and complex queries only with a link to the documentation

Main functionalities

Give detail on all complex functionalities: list most important and/or complex KPI, query jump, alerts

Broadcast

Indicate if there are broadcasts and give some details on the broadcast settings.

Maintenance

Known bugs

Give the list and explanation on the known, not-solved, bugs.

Recurring procedure

The only the storage is on acquisition layer APCOCT20. The KPIs are on Overwrite mode and all the fields are in key. In case data want to be delete, you have to execute a selective suppression and reload the new corrective file with transaction. In case you wish only replace the KPI value you have just reload the same Key (all field) with new amount and the raw will be update.

Planned Evolution

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