The new wiki link for this data flow is here:

BW RTR - Anaplan data export from BW

Please update the doc there and no longer here.

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

Actual Data Origin extraction

Functional and Technical rules on Workbench + Reporting

Original User requirements are available in the following document:

Flat file generated using '.txt' extension and comma separator ','.

Generated file is stored in AL11 folder /exploit/BW/Anaplan_outbound

1) Actual Origin

Name of the flat file: Actual_data_from_Origin.txt

Heading columns:

unique ID

Responsible Cost Center

Cost Package

Month

Year

Local Currency

Reporting Currency (EUR)

Flat file content example:

$TECHNO - BI TEAM > BW RTR - Anaplan data export from BW /!\ Obsolete /!\ > image2022-4-27_8-58-7.png$

Dataflow:

$TECHNO - BI TEAM > BW RTR - Anaplan data export from BW /!\ Obsolete /!\ > image2022-4-27_9-15-5.png$

OpenHub name:	OH_COCT11	Controlling - F2G - Actual data from Origin
Source:	BW_QRY_CPCOCT01_0004	COSTA - Cost Transparency Actual Origin for OpenHub

Specific rules:

Ignore entries where amounts are 0 or null, or where Controlling Area and Responsible Cost Center are both empty or null or GBU and Responsible CC are both empty or null.
Set P11115 as default Cost Package if null
Set Responsible Cost Center = GBU if null
Amount TGT_CURR is converted to Euro from Legal View amount, using Exchange Rate CAR5 on first day of the month of the entry.

Scheduling :

Extraction is scheduled in process chain PC_CO_CT_04 COSTA: TD - M - Anaplan Origin Costs Extraction. It runs monthly at 01:00 on the 8th workday of the BE Calendar.

Dependencies with other applications

Dependencies with COSTA application, which is the source for this dataflow.

Actual Data Bridge Destination extraction

Functional and Technical rules on Workbench + Reporting

Original User requirements are available in the following document: F2G requirements - Destination Bridge view extractions

Flat file generated using '.txt' extension and comma separator ','.

Generated file is stored in AL11 folder /exploit/BW/Anaplan_outbound

1) Actual Destination Bridge (Local Curr)

Name of the flat file: Actual_data_bridge_to_destination_local.txt

Heading columns:

Actuals Unique Id

Responsible Cost Center Code

Month

Year

IFRS16

Good Consumed from Inventory

Charge-In

Charge-Out

Capitalisation

Flat file content example:

$TECHNO - BI TEAM > BW RTR - Anaplan data export from BW /!\ Obsolete /!\ > image2022-4-27_8-57-4.png$

Dataflow:

$TECHNO - BI TEAM > BW RTR - Anaplan data export from BW /!\ Obsolete /!\ > image2022-4-27_9-13-48.png$

OpenHub name:	OH_COCT12	Controlling - F2G - Actual data Bridge to Destination
Source:	BW_QRY_CPCOCT10_0001	COSTA - F2G Anaplan - Destination Anaplan Bridge

Specific rules:

Contains sum of all amounts for key Actuals Unique Id as decimals, ignoring currencies.
Ignore all entries where all amounts are 0 or null and where CO_AREA or C_RESP_CC are empty or null.
KPi decimal separator is 'point' (.)
KPi sign is displayed before value, i.e.: -78340.87
All necessary filters are set in source query, copy of query QV_BW_QRY_CPCOCT10_0001
- Fiscal period Y-1 to M-1, except in January (Y-2 to M-1) (Variables V_0FISCPER_0021/22)
- Fixed Cost Group 2 not 'ZCRS-6'0 or 'ZCRS-X60'

2) Actual Destination Bridge (EUR)

Name of the flat file: Actual_data_bridge_to_destination_euro.txt

Heading columns:

Actuals Unique Id

Responsible Cost Center Code

Month

Year

IFRS16

Good Consumed from Inventory

Charge-In

Charge-Out

Capitalisation

Flat file content example:

$TECHNO - BI TEAM > BW RTR - Anaplan data export from BW /!\ Obsolete /!\ > image2022-4-27_8-57-33.png$

Dataflow:

$TECHNO - BI TEAM > BW RTR - Anaplan data export from BW /!\ Obsolete /!\ > image2022-4-27_9-14-29.png$

OpenHub name:	OH_COCT13	Controlling - F2G - Actual data Bridge to Destination EURO
Source:	BW_QRY_CPCOCT10_0001	COSTA - F2G Anaplan - Destination Anaplan Bridge

Specific rules:

Amounts are converted to Euro in the first transformation, using corresponding amount in Legal View and Local Currency from source query and Exchange Rate CAR5 on first day of the month of the entry.
For everything else, same as Actual Destination Bridge (EUR)

Scheduling :

Extraction is scheduled in process chain PC_CO_CT_03 COSTA - F2G Anaplan - Extraction, along with Master Data extractions.

Actual data extraction is conditioned to working days set up in Global filter:

Stream = COSTA2FILE
Rule = CALENDAR (DEFAULT = BE)
Rule = RANGE_DAY (DEFAULT = EQ 4)

Dependencies with other applications

Dependencies with COSTA application, which is the source for this dataflow.

Master Data extractions

Functional and Technical rules on Workbench + Reporting

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:

$TECHNO - BI TEAM > BW RTR - Anaplan data export from BW /!\ Obsolete /!\ > image2021-12-16_17-14-23.png$

These are generated by OpenHubs located in InfoArea IA_FMCO_CO_CT_VIRTUAL:

$TECHNO - BI TEAM > BW RTR - Anaplan data export from BW /!\ Obsolete /!\ > image2021-12-16_17-16-16.png$

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

$TECHNO - BI TEAM > BW RTR - Anaplan data export from BW /!\ Obsolete /!\ > image2021-12-16_17-18-43.png$

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:

$TECHNO - BI TEAM > BW RTR - Anaplan data export from BW /!\ Obsolete /!\ > image2021-12-16_18-6-11.png$

Dataflow:

$TECHNO - BI TEAM > BW RTR - Anaplan data export from BW /!\ Obsolete /!\ > image2021-12-17_10-44-50.png$

OpenHub name:	OH_COCT10	Controlling - F2G Anaplan- Region Country
Source:	Query BW_QRY_CPCOCT01_0010	COSTA - F2G Anaplan - Region Country

Specific rules:

Source query has the same filters as the query BW_QRY_CPCOCT01_0002 COSTA - Cost Transparency - Origin view
Period: from January year N-1 (last year) to December year N (current year)
Exclusion of Country key = Unassigned # and Geographie/Zone = Unassigned #

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:

$TECHNO - BI TEAM > BW RTR - Anaplan data export from BW /!\ Obsolete /!\ > image2021-12-16_18-6-38.png$

Dataflow:

$TECHNO - BI TEAM > BW RTR - Anaplan data export from BW /!\ Obsolete /!\ > image2021-12-17_10-45-13.png$

OpenHub name:	OH_COCT02	Controlling - F2G Anaplan - SITE
Source:	TEXTS C_SITE	Geography / Geographic site (Texts)

Specific rules:

Exclusion of the record if Site Description contains the character '#'

3) Function

Name of the flat file: Function.txt

Heading columns:

4 Sub-function code

4 Sub-function description

Flat file content example:

$TECHNO - BI TEAM > BW RTR - Anaplan data export from BW /!\ Obsolete /!\ > image2021-12-16_18-7-34.png$

Dataflow:

$TECHNO - BI TEAM > BW RTR - Anaplan data export from BW /!\ Obsolete /!\ > image2021-12-17_10-45-37.png$

OpenHub name:	OH_COCT03	Controlling - F2G Anaplan - FUNCTION
Source:	TEXTS C_FUNCT_4	4 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:

$TECHNO - BI TEAM > BW RTR - Anaplan data export from BW /!\ Obsolete /!\ > image2021-12-16_18-9-44.png$

Dataflow:

$TECHNO - BI TEAM > BW RTR - Anaplan data export from BW /!\ Obsolete /!\ > image2021-12-17_10-46-4.png$

OpenHub name:	OH_COCT04	Controlling - F2G Anaplan - BU
Source:	TEXTS C_FACUBU	Current 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:

$TECHNO - BI TEAM > BW RTR - Anaplan data export from BW /!\ Obsolete /!\ > image2021-12-16_18-10-11.png$

Dataflow:

$TECHNO - BI TEAM > BW RTR - Anaplan data export from BW /!\ Obsolete /!\ > image2021-12-17_10-46-18.png$

OpenHub name:	OH_COCT05	Controlling - F2G - Currency list
Source:	Query BW_QRY_DAFICE01_0010	BW - F2G Anaplan - Currency list

Specific rules:

Exchange rate type = CAR5
Period: from January year N-1 (last year) to December year N (current year)

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:

$TECHNO - BI TEAM > BW RTR - Anaplan data export from BW /!\ Obsolete /!\ > image2021-12-16_18-10-19.png$

Dataflow:

$TECHNO - BI TEAM > BW RTR - Anaplan data export from BW /!\ Obsolete /!\ > image2021-12-17_10-46-30.png$

OpenHub name:	OH_COCT06	Controlling - F2G Anaplan - Legal Entity
Source:	TEXTS C_COMPPRS	PRS Company code (Texts)

Specific rules:

Exclusion of the record if Company code description contains the string '*D*'

7) BSA

Name of the flat file: Bsa.txt

Heading columns:

BSA code

BSA description

Flat file content example:

$TECHNO - BI TEAM > BW RTR - Anaplan data export from BW /!\ Obsolete /!\ > image2021-12-16_18-11-44.png$

Dataflow:

$TECHNO - BI TEAM > BW RTR - Anaplan data export from BW /!\ Obsolete /!\ > image2021-12-17_10-46-51.png$

OpenHub name:	OH_COCT07	Controlling - F2G - BSA
Source:	BW_QRY_CPCOCT01_0011	COSTA - F2G Anaplan - BSA

Specific rules:

Source query has the same filters as the query BW_QRY_CPCOCT01_0002 COSTA - Cost Transparency - Origin view
Period: from January year N-1 (last year) to December year N (current year)
Exchange rate type = CAR5
Zero suppression activated on Actual origin Key Figure

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:

$TECHNO - BI TEAM > BW RTR - Anaplan data export from BW /!\ Obsolete /!\ > image2021-12-16_18-12-5.png$

Dataflow:

$TECHNO - BI TEAM > BW RTR - Anaplan data export from BW /!\ Obsolete /!\ > image2021-12-17_10-47-13.png$

OpenHub name:	OH_COCT08	Controlling - F2G - Exchanges rates
Source:	BW_QRY_DAFICE01_0011	BW - F2G Anaplan - Exchange rates

Specific rules:

Period: from January year N-1 (last year) to December year N+1 (next year)
Exchange rate type = CAR5
Conversion rate = -1 X Currency Exchange rate X Ratio for the From Currency / Ratio for the To Currency
Decimal separator for conversion rate is point '.'
An Unique ID is generated for each record by concatenation of : Convertion Type + To Currency + Year + Month (i.e.: CAR5EUR202112)
Conversion rate EUR to EUR (equals to 1) is added in routine for years N-1 to N+1

9) GBU code and description

Name of the flat file: GBU_description.txt

Heading columns:

GBU code

GBU Description

Flat file content example:

$TECHNO - BI TEAM > BW RTR - Anaplan data export from BW /!\ Obsolete /!\ > image2021-12-16_18-12-17.png$

Dataflow:

$TECHNO - BI TEAM > BW RTR - Anaplan data export from BW /!\ Obsolete /!\ > image2021-12-17_10-48-24.png$

OpenHub name:	OH_COCT09	Controlling - F2G Anaplan - GBU
Source:	BW_QRY_CPCOCT01_0012	COSTA - F2G Anaplan - GBU

Specific rules:

Source query has the same filters as the query BW_QRY_CPCOCT01_0002 COSTA - Cost Transparency - Origin view
Period: from January year N-1 (last year) to December year N+1 (next year)
Filter on: Flag - Anaplan Perimeter = #

Dependencies with other applications

Dependencies with COSTA application, as it is source of several extraction data

Data loadings

Info providers and objects loaded

Process chain used to extract Master Data to Anaplan : PC_CO_CT_03 COSTA - F2G Anaplan - Extraction

$TECHNO - BI TEAM > BW RTR - Anaplan data export from BW /!\ Obsolete /!\ > image2022-1-7_14-46-41.png$

Loading frequency

Process chain PC_CO_CT_03 is scheduled every working day (Factory calendar : BE) at 05:00am CET

Actual Bridge Destination data extraction is conditioned to working days set up in Global filter:

Stream = COSTA2FILE
Rule = CALENDAR (DEFAULT = BE)
Rule = RANGE_DAY (DEFAULT = EQ 4)

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 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

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