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:

Flat file content example:

Dataflow:

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:

Flat file content example:

Dataflow:

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:

Flat file content example:

Dataflow:

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:

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:

Flat file content example:

Dataflow:

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:

Flat file content example:

Dataflow:

Specific rules:

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

3) Function

Name of the flat file: Function.txt

Heading columns:

Flat file content example:

Dataflow:

4) BU

Name of the flat file: BU_BFC_Group_of_activities.txt

Heading columns:

Flat file content example:

Dataflow:

5) Currency List

Name of the flat file: Currency_list.txt

Heading columns:

Flat file content example:

Dataflow:

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:

Flat file content example:

Dataflow:

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:

Flat file content example:

Dataflow:

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:

Flat file content example:

Dataflow:

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:

Flat file content example:

Dataflow:

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

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

Record Keeping

Reporting

Queries End User Documentation

Main queries

Main functionalities

Broadcast

Maintenance

Known bugs

Recurring procedure

Planned Evolution