1.PURPOSE AND USAGE OF BUSINESS STRUCTURES IN BFC

Solvay IFRS reporting is organized per legal companies (one reporting package per legal company) reporting their Financial Statements (P&L, Balance Sheet and Cash Flow Statement). To allow Businesses to get their Financial results, each legal company will in addition split its results on Business dimensions. 

The following items of financial results require an allocation per Business:

  • P&L until EBIT
  • Internal sales and external sales
  • Working Capital (stocks, acc. receivables and payables), CAPEX (capital expenditures), Fixed assets and Investments
  • Free Cash flow

It means that Consolidated results can be obtained as sum of legal companies and as sum of Businesses.

This IFRS reporting per Businesses used by both Businesses and Corporate Controlling teams to prepare the analysis of Solvay Businesses performance included in both Financial press releases every quarter and Annual report.

To be noted that Business structures are also used in Controlling categories (RSB and PREV).


2.BUSINESS STRUCTURES HIERARCHIES IN BFC

Business structures are organized around 5 levels aggregating each others in a global hierarchy (following a Russian dolls principle - 1 level can belong to only one upper level and never two):

  • CLUSTER = Operating segment
    • This is the upper level of the hierarchy
    • Codification rule : 4 letters 
    • Corresponds to level of communication on Solvay Businesses performance to external markets
    • Example: CHEM "Chemicals", MATE "Materials", SOLU "Solutions"...
  • SEGMOP = Group of GBU's = Operational Segment
    • This is the 2nd level of the hierarchy
    • Codification rule : 3 letters 
    • Used internally to group GBU's - not a level subject to external communication
    • Examples in Cluster CHEM "Chemicals": GCT "Coatis", GEB "Vinythai"...
  • ENTREP = GBU = Global Gusiness Unit
    • This is the 3rd level of the hierarchy
    • Codification rule : 2 letters 
    • Used internally  - corresponds to real Business organization with Global Director, Finance teams...
    • Exception/constraint: do not choose codes starting with "D", "Dx" codes dedicated to Discop GBU's (examples: DO "Discop Acetow" / DM "Discop Performance Polyamides"...)
    • Examples in Segmop GCT "Coatis"": CT "Coatis", FI "Fibras"
  • BU = Business Unit
    • This is the 4th level of the hierarchy
    • Codification rule :  always 5 letters - the 2 first letters are the ones of the belonging GBU code
    • Used internally  - allows each GBU to split its activities (criterias can be external market, external application, product lines...)
    • Exception/constraint: do not choose codes starting with "D", "Dx" codes dedicated to Discop GBU's (examples: DO "Discop Acetow" / DM "Discop Performance Polyamides"...)
    • Examples in GBU FI "Fibras"": FITEX " Fibras Textile"

5th level combines 2 different dimensions : MARK "Activity1" and CGU "Activity2"

  • MARK "Activity1"
    • Level for data entry in the IFRS reporting packages to enter P&L components and Acc Receivables
    • Level also directly used in BFC customizing (category scenario, reports, business users accesses...)
    • Codification rule :
      • Different practices coming from the past Solvay (letters & digits - digits coresponding to Division codes from former Cheops conso tool from Solvay) and Rhodia legacies (letters)
        • example on the right side on GBU CH "Special Chem": BU CHRAR coming from Rhdoia legacies and included Activity 1 codes made of letters only (ex CHAT) while BU CHFLO "Fluorine" coming from the Solvay legacy includes Activity1 codes made of letters & digits (ex CH3A)
      • Best practice: it is recommended to cross check that any new Activity1 code proposed for BFC (for both Solvay and Rhodia legacies) does not exist already 1) in Solvay ERP (PF1, WP1) with FSL SU MAC Master Data team  and 2) in BFC dimension builder
  • CGU "Activity2"
    • Level for data entry in the IFRS reporting packages to enter Working capital, Fixed assets and Investments
    • Level also directly used in BFC customizing (category scenario, reports, business users accesses...)
    • Codification rule :
      • As for MARK dimension, different practices coming from the past Solvay and Rhodia legacies
        • example on the right side on GBU CH "Special Chem": BU CHRAR coming from Rhodia legacies and included Activity 2 codes made of letters &digits (ex CHCGU113) while BU CHFLO "Fluorine" coming from the Solvay legacy includes Activity2 codes made of letters & digits but not following the same sequence (ex CHCGU3AP)
      • Best practice: it is recommended to cross check that any new Activity2 code proposed for BFC (for both Solvay and Rhodia legacies) does not exist already 1) in Solvay ERP (PF1, WP1) with FSL SU MAC Master Data team  and 2) in BFC dimension builder












3. OVERALL PROCESS FOR BUSINESS STRUCTURES UPDATES 


4. CREATION / UPDATES OF BUSINESS STRUCTURES IN BFC

4.1. CREATION OF NEW OBJECTS


4.2. UPDATE OF OBJECTS: OLD & EMPTY VALUES


4.3. CHANGE OF LINKS INSIDE HIERARCHIES



5. PILOTING TO BFC_PRODUCTION


6. DOCUMENTATION UPDATES IN GAR AODOC


7. RELATED IMPACTS ON BFC USERS ACCESSES


END OF THE PROCEDURE