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
N/A
N/A
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
2 flat files are generated:
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:

Dataflows:

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

| OpenHub 2 name: | OH_COCT13 | Controlling - F2G - Actual data Bridge to Destination EURO |
| Source: | Query BW_QRY_CPCOCT10_0001 | COSTA - F2G Anaplan - Destination Anaplan Bridge |
Specific rules:
Sheduling :
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:
Depencies with COSTA application
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
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_COCT10 | Controlling - F2G Anaplan- Region Country |
| Source: | Query BW_QRY_CPCOCT01_0010 | COSTA - F2G Anaplan - Region Country |
Specific rules:
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_COCT02 | Controlling - F2G Anaplan - SITE |
| Source: | TEXTS C_SITE | Geography / Geographic site (Texts) |
Specific rules:
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_COCT03 | Controlling - F2G Anaplan - FUNCTION |
| Source: | TEXTS C_FUNCT_4 | 4 Sub-function (Texts) |
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_COCT04 | Controlling - F2G Anaplan - BU |
| Source: | TEXTS C_FACUBU | Current Business Unit (Texts) |
Name of the flat file: Currency_list.txt
Heading columns:
Local Currency | Description local currency |
Flat file content example:

Dataflow:

| OpenHub name: | OH_COCT05 | Controlling - F2G - Currency list |
| Source: | Query BW_QRY_DAFICE01_0010 | BW - F2G Anaplan - Currency list |
Specific rules:
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_COCT06 | Controlling - F2G Anaplan - Legal Entity |
| Source: | TEXTS C_COMPPRS | PRS Company code (Texts) |
Specific rules:
Name of the flat file: Bsa.txt
Heading columns:
BSA code | BSA description |
Flat file content example:
![]()
Dataflow:

| OpenHub name: | OH_COCT07 | Controlling - F2G - BSA |
| Source: | BW_QRY_CPCOCT01_0011 | COSTA - F2G Anaplan - BSA |
Specific rules:
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_COCT08 | Controlling - F2G - Exchanges rates |
| Source: | BW_QRY_DAFICE01_0011 | BW - F2G Anaplan - Exchange rates |
Specific rules:
Name of the flat file: GBU_description.txt
Heading columns:
GBU code | GBU Description |
Flat file content example:
![]()
Dataflow:

| OpenHub name: | OH_COCT09 | Controlling - F2G Anaplan - GBU |
| Source: | BW_QRY_CPCOCT01_0012 | COSTA - F2G Anaplan - GBU |
Specific rules:
Depencies with COSTA application, as it is source of several extraction data
Process chain used to extract Master Data to Anaplan : PC_CO_CT_03 COSTA - F2G Anaplan - Extraction

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