You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 18 Next »

  

General presentation

This page provides all the technical and detailed documentation concerning the "FIWC for Solvay Group" (Finance Working Capital) application in BW, including :

  • General overview of the dataflow
  • Query, Workbook, Webtemplate and broadcasts documentation
  • Maintenance operations : necessary manual updates of master data.

This application replaces the former FIWC application which was created for Rhodia legacy (WP1).

Systems involved

  • Rhodia ERP WP1

  • Solvay ERP PF1 (020)

  • CICC ERP PI1

  • Acetow ERP RHO

  • PRS ERP PF1 (050)

  • BFC (flat files)

General definitions

Working Capital definition

  • Global definition:*
    The working capital is a financial indicator used to measure the Free Cash Flow of the enterprise.

It is equal to the sum of:

  • Value of the stocks
  • Value of the customer receivables
  • Value of the vendor payables

It excludes:

  • Intercompany
  • Componies not in consolidation area (consolidation view) - for GBU usage only

In BFC:
Every month, persons in each company will get the values from RCS/BW for each account and enter it manually in BFC.

  • Values are entered in local currency. BFC then converts to EUR.
  • If amounts are not affected to a business unit then they will manually affect the amounts using rules.

G/L Accounts

We can split the Working Capital in 3 main component (GL Type), which separates in sub-components (GL Sub types). 

+G/L Accounts restitution:

Account types and sub types are managed in WP1 and PF1 systems (PF1 and PI1 share GL accounts so no need to load from PI1 system).
For Acetow system, it's managed manually

Consolidation or Accouting view

Working Capital for GBU queries are working in consolidation view, meaning we exclude Intercompany and other filters in restricted key figures also the intergration rate.
Working Capital for Accounting offers with a variable to working in accounting view, without any filters.

Intercompany exclusion

In the queries, we keep only the company with Intercompany flag as X. This flag is determined in PRS source system.
The flag is stated as X for the consolidation methods 10 (IG - Fully consolidated), 30 (IP - Proportionately consolidated) and 55 (ME - Equity method futur IP). The table used is ZZF_T001_MGT.

Business Assignments

For data coming from FIAR, the base is the Sub-Activity 0G_CWWE01. It's a mix of IECRA (WP1 and RHO systems) and Business area (PF1 and PI1). Functionnally speaking IECRA and Business area are similar so we decided to mix it an existing object, 0G_CWWE01.

For data coming from FIGL and FIAP, the base of the business assignment is the Sub-activity 2 C_SUBACT2. It's a mix of Profit center (WP1) and Business area (PF1, PI1 and RHO systems). As Profit center has a compounded key with the controlling area we were not able to use the same info object as for FIAR.

The notion of Profit center exists in PF1/PI1 but for a different usage that accounting. So to avoid data pollution in existing object 0PROFIT_CTR, we decided to create a new info object, C_SUBACT2.

Both info objects give the Business structure with same attributes used for reporting purpose.

Illustration for WP1 system:

Example of the profit center hierarchy that is used to define the Industrial Axis in Sub-activity 2 info object:

PRS Source system

We load some master data from PRS system (PF1_050).
With this some source system, we can be sure to have an unique code for companies, customers and vendors.

In RCS and Acetow, the link between ERP and PRS is managed in tables ZZR_T001_MAP (company), KNA1 (customer) and LFA1 (vendor).

For Solvay and CICC, the PRS code is the same than ERP code.

PRS master data are stored in dedicated info objects: C_COMPPRS, C_CUSTPRS and C_VENDPRS.

We also have dedicated info objects from the ERP with the ERP system and code and the PRS attributes: C_COMPCDE, C_CUSTID and C_VENDID.
At the beginning  we used C_COMPPRS, C_CUSTPRS and C_VENDPRS in the info providers in order to use their attributes but due to poor data quality we had too oftenly the case of missing link in the ERP between ERP and PRS codes. That's why we decided to replicate PRS attributes in C_COMPCDE, C_CUSTID and C_VENDID info objects.

Currency conversion

The BW working capital reports are all based on amounts in Local Currency Those amounts come directly from the source systems.

If user selects a currency in the prompt the query will convert, otherwise it will return the values in local currency.

This conversion is based on the ZRHO rate (coming from WP1).

The current available rate s applied to ALL data (even past data) independently of the date.

For base amount we use the Debit/Credit Amount 0DEB_CRE_LC or FIGL/FIAR/FIAP data and the Stock Value for IM data.

We then apply conversion type ZRH2 for Working Capital - CTK_ZRHWC :

  • Based on * ate ZRHO* :

  • Uses the rate available for date = * revious Day Exit (Working Cap) -* DATEWC00

  • We use the target currency from variable * urrency (Single Value, Optional)*- CURVAR01

Dataflow in BW

Overview dataflow

FIAR data flow

This part of the Working Capital has been done via ITC project. Please check ITC page for more details.

FIAP fata flow

FIAP data re also be used for SPRINT (Purchasing) and CAPEX (Project costs) applications.

+Net due date management:

The net due date is managed at the document item level and is calculated in the ERP. A new net due date managed manually has been set in each system.
It's available in ZZF_BSEG table.

For each system we created a new data source based on this table and a dedicated DSO (DPFIWC01 to 04).
In BW, there is a direct loading between Net due date DSO and Business layer DSO and also a look-up between Propagation and Business layers to read DPFIWC DSO.

+Reclassification of Sub-Activity C_SUBACT2:

In the ERP, when a profit center or a business area is set, it's not possible to modify it later.
In order to resolve that issue, mecanisms have been created in the ERP.

In WP1

Documents can be modified in ZWFAT205 table (transaction ZWFAT205).
In the example below, document has been modified with a different profit center:

This table is loaded in DSO_FI11 in BW and data are updated in Business layer DSO.

In PF1 and PI1

In PI1 system, the mecanism is different and is not managed document by document, like in WP1.
It's done in PI1 (for PI1 and PF1) through data source ZZFCM_BU_EXCEPTIONS_NEW.

This table is loaded in DBFIWC01 DSO in BW.

Between Propagation and Business layers, we read this DSO to determine the new business area.

For example, document for company code 0005 and business area 3240, the new business area will be 8500.

+Rhodia legacy rules:

Initial loading was done from existing DSO ODSFIAP1 and not from WP1 system due to archived document not loadable anymore.

A split of data is done between propagation and business DSO (DPFIAP01 and DBFIAP01), in the start routine inside program z_start__dpfiap01__dbfiap01.

The split is also done in WP1 system, in ZWFAT123 table. This table is filled in WP1 when the data source 0FI_AP_4 is launched. The data are retrieved in ODS_FIWC.

+Solvay legacy rules:

A split of data is done between propagation and business DSO (DPFIAP02 and DBFIAP02) but the mecanism and the logic is much more simple.

We split data using DPFIGL02 DSO (FIGL data) for document with reference procedure RMRP (Invoice receipt) with detail by material, plant, purchase order number and item.

We calculate the item's quote part in FIGL and apply this quote part on amount from FIAP document. For the last splitted item, amount is the total amount minus the sum of other splitted lines.

For CICC, there isn't specific rule.

+Acetow legacy rules:

The same split that Solvay legacy is done.

FIGL fata flow

FIAP data re also be used for SPRINT (Purchasing) and CAPEX (Project costs) applications.

FIGL-AR fata flow

FIAP data re also be used for SPRINT (Purchasing) and CAPEX (Project costs) applications.

FIGL-AP fata flow

FIAP data re also be used for SPRINT (Purchasing) and CAPEX (Project costs) applications.

FIGL-IM fata flow

FIAP data re also be used for SPRINT (Purchasing) and CAPEX (Project costs) applications.

Reporting

Workbooks

All the reporting is available throught workbooks in the role "WCAP - Working Capital Solvay Group" ZR_RCS_CA_M41

There are 2 sub-folders, 1 for GBU usage and 1 for Accounting and BFC usage.
All workbooks are based on the same info providers. 

Broadcasts

A broadcast is sent to users. The schedule is determined in the BW process chains. Actually, the broadcasts are sent the 6th, 10th, 15th and 20th working day of the month.

For those days, at the end of the process chain, a file is put in the BO server. When the BO server idenfity this file (an empty txt) file, it triggers the broadcasts.
All the design and settings are managed in BO. 

Authorization objects

    • PRS Company code (C_COMPCDE__C_COMPPRS)

    • Management Area (C_COMPCDE__C_MNGAREA)

    • WC Account type (0GL_ACCOUNT__C_GL_TYPE)

    • BFC GBU (C_SUBACT2__CPFCTR1_2)

Data loading

+During closing period (last day of the month and 4 fist working days):

  • WP1 data are loaded 7 times a day: 6am, 10am, 12am, 2pm, 4pm, 6pm and 10pm (french time)
  • PF1, PI1 and RHO systems are loaded 3 times a day: 6am, 12am and 6pm (french time)

+Outside closing period:

  • All systems are loaded 3 times a day: 6am, 12am and 6pm (french time)
  • No labels