General presentation

Objective of the application

The goal of the application is to extract data from BW WBP to Anaplan.

This solution is based on flat files automated generation.

Anaplan documentation is available on the following wiki page : https://wiki.solvay.com/x/cwBvKg

Tool Leader + IT leader of the application: Guillaume.THEVENET@solvay.com 

Usage information

N/A

History

N/A

Master Data extraction

Dataflow overview

Use the google presentation below as a template. This google presentation must be saved in the Reporting GDrive folder under the corresponding application. Then post the link to the document here.

Reporting documentation drive folder:

https://drive.google.com/drive/folders/0B0qn89R0RGdqYkZZOFZyYXlXVkE

Exemple of dataflow overview :

Template Application name DataFlow

Functional and Technical rules on Workbench + Reporting

Rules & Explanations

Original User requirements are available in the following document: BW requirements - Basic master data and Exchange rates for Anaplan F2G models

Flat files are generated using '.txt' extension and comma separator ','.

All extracted description is done using english language EN.

All generated files are stored in AL11 folder  /exploit/BW/Anaplan_outbound:

These are generated by OpenHubs located in InfoArea IA_FMCO_CO_CT_VIRTUAL:

Generated file's names and location are set up using logical file (Transaction FILE):

In order to generate header lines in flat files, an ABAP specific solution has been implemented in all extraction data flow.

Concerning this solution, the dedicated documentation is available : OpenHub for APD CSV File interface.docx

1) Region (Com); Country (Com)

Name of the flat file: Region_country.txt

Heading columns:

Country code 

Country description

Zone code

Zone description

Flat file content example:

Dataflow:

OpenHub name: OH_COCT10Controlling - F2G Anaplan- Region Country
Source: Query BW_QRY_CPCOCT01_0010COSTA  - F2G Anaplan - Region Country

Specific rules:

2) Site

Name of the flat file:  Site.txt

Heading columns:

Geography / Geographic site CODE from C_SITE

Geography / Geographic site Description

Flat file content example:

Dataflow:

OpenHub name: OH_COCT02Controlling - F2G Anaplan - SITE
Source: TEXTS C_SITEGeography / Geographic site (Texts)

Specific rules:

3) Function

Name of the flat file: Function.txt

Heading columns:

4 Sub-function code

4 Sub-function description

Flat file content example:

Dataflow:

OpenHub name: OH_COCT03Controlling - F2G Anaplan - FUNCTION
Source: TEXTS C_FUNCT_44 Sub-function (Texts)





4) BU

Name of the flat file: BU_BFC_Group_of_activities.txt

Heading columns:

/BIC/C_FACUBU code

/BIC/C_FACUBU description

Flat file content example:

Dataflow:

OpenHub name: OH_COCT04Controlling - F2G Anaplan - BU
Source: TEXTS C_FACUBUCurrent Business Unit (Texts)



5) Currency List

Name of the flat file: Currency_list.txt

Heading columns:

Local Currency

Description local currency

Flat file content example:

Dataflow:

OpenHub name: OH_COCT05Controlling - F2G - Currency list
Source: Query BW_QRY_DAFICE01_0010BW - F2G Anaplan - Currency list



6) Legal Entity

Name of the flat file: Legal_entity.txt

Heading columns:

Company Code - PRS Company code

Description of company code

Flat file content example:

Dataflow:

OpenHub name: OH_COCT06Controlling - F2G Anaplan - Legal Entity
Source: TEXTS C_COMPPRSPRS Company code (Texts)



7) BSA

Name of the flat file: Bsa.txt

Heading columns:

BSA code

BSA description

Flat file content example:

Dataflow:

OpenHub name: OH_COCT07Controlling - F2G - BSA
Source: BW_QRY_CPCOCT01_0011COSTA - F2G Anaplan - BSA



8) Exchange rates

Name of the flat file: CAR5_exchange_rates.txt

Heading columns:

Unique ID

Currency Type

Currency

Year

Month 

Conversion Rate

Flat file content example:

Dataflow:

OpenHub name: OH_COCT08Controlling - F2G - Exchanges rates
Source: BW_QRY_DAFICE01_0011BW - F2G Anaplan - Exchange rates




9) GBU code and description

Name of the flat file: GBU_description.txt

Heading columns:

GBU code 

GBU Description

Flat file content example:

Dataflow:

OpenHub name: OH_COCT09Controlling - F2G Anaplan - GBU
Source: BW_QRY_CPCOCT01_0012COSTA - F2G Anaplan - GBU




Dependencies with other applications

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

Data loadings

Info providers and objects loaded

Detail of process chain, list + link between or special event done for the loading

Loading frequency

Detail of frequency : monthly; weekly or else

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

List recurring procedures

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