2.0 Business Process

---

This application supports the following business processes

XXXXXXXXXXXXX

CO Structure in Solvay:

PF1 Structure

	Code	Description
Operating concern	FO01	Slv ERP Operating concer
Controlling area	CHEF	ERP SOLVAY

WP1 Structure

	Code	Description
Operating concern	Z001	Solvay Engin.Plasti.Polan
	Z006	Rhodia Europe
	Z013	Rhodia Europe
	Z025	Rhodia Latin America
	Z026	Rhodia Asia Pacific
	Z028	Solvay North America
Controlling area	= Operating concern

Overview of the business process in Corporate Function Cost

Structures

The structure is based on: 

• The Cost Centers hierarchy ZCBS

<Insert image>

• The Cost Elements Group ZRCS-FC

<Insert Image>

Corporate Function costs are split in 4 parts:

• Corporate (not re-invoiced)

<insert Description>

• Function services (re-invoiced and under guarantee)

<insert Description>

• R&D and engineering projects

<insert Description>

• Interco flows - It allows the identification of inter-company billing at company level

<insert Description>

Costs included in the report: 

The below costs are included in the Corporate Business 

• Actual costs only: Statistical costs are not taken into account
• IFRS rules only: Costs posted using local gaap accounts are excluded (Brazilian entities)
• Costs posted on CBS (Corporate Business Services) cost centers (directly or through orders or WBS). It corresponds to the cost centers included in the following groups of the cost centers hierarchy ZCBS: 

• • ZCBS-CORPO = Corporate
  • ZCBS-FUNCT = Function services
  • ZCBS-PROJ =Projects
  • ZCBS-ICO = Interco
• Costs are organized with the cost elements group ZRCS-FC
• Inter-company re-invoiced function service costs should be posted on cost centers of the group ZCBS-ICO

3.0 Application Feature Overview

---

Costs are organised with the cost elements group ZRCS-FC. Inter-company re-invoiced function service costs should be posted on cost centers of the group ZCBS-ICO PF1 & WP1 cost centers are included as long as there are included in the hierarchy ZCBS.

Costs included in the report: 

• Actual costs only: Statistical costs are not taken into account
• IFRS rules only: Costs posted using local gaap accounts are excluded (Brazilian entities)
• Costs posted on CBS (Corporate Business Services) cost centers (directly or through orders or WBS). It corresponds to the cost centers included in the following groups of the cost centers hierarchy ZCBS: 

• • ZCBS-CORPO = Corporate
  • ZCBS-FUNCT = Function services
  • ZCBS-PROJ =Projects
  • ZCBS-ICO = Interco
• Costs are organized with the cost elements group ZRCS-FC
• Inter-company re-invoiced function service costs should be posted on cost centers of the group ZCBS-ICO

This Function is split in 4 parts:

• Corporate (not re-invoiced)

<Need more information>

• Function services (re-invoiced and under guarantee)

<Need more information>

• R&D 

<Need more information>

• Engineering projects Interco flows -

<Need more information>

It allows the identification of inter-company billing at company level Costs included in the report: Actual costs only: Statistical costs are not taken into account IFRS rules only: Costs posted using local gaap accounts are excluded (Brazilian entities) Costs posted on CBS (Corporate Business Services) cost centers (directly or through orders or WBS). It corresponds to the cost centers included in the following groups of the cost centers hierarchy ZCBS: ZCBS-CORPO = Corporate ZCBS-FUNCT = Function services ZCBS-PROJ =Projects ZCBS-ICO = Interco

Below we have all the workbooks available:

Reports	Definition	Prompts	BW Workbook Query	Query Technical Name
Synthesis	Costs posted on function cost centers only Categorization of costs following the structure described in the slide ““Synthesis” & “Function – end of month”  report”. Highest level of detail: cost center x cost element The sign of the amount is seen from the function cost center ( +: costs increase / -: costs decrease)		TBC	BW_QRY_MPR_FC001_0005
Functions – End of month	Costs posted on function cost centers only Categorization of costs following the structure described in the slide ““Synthesis” & “Function – end of month”  report”. Highest level of detail: partner CO object The sign of the amount is seen from the function cost center ( +: costs increase / -: costs decrease)		TBC	BW_QRY_MPR_FC001_0001
Functions – During the month	Costs posted on function cost centers only No categorization of costs Highest level of detail: partner CO object The sign of the amount is seen from the function cost center ( +: costs increase / -: costs decrease)		TBC	BW_QRY_MPR_FC001_0003
Functions by Company – End of month	Costs posted on function cost centers only No categorization of costs Highest level of detail: partner CO object The sign of the amount is seen from the function cost center ( +: costs increase / -: costs decrease)		TBC	BW_QRY_MPR_FC001_0002
Functions by companies – During the month	Costs posted on function cost centers and CO objects with function CC as responsible CC No categorization of costs Highest level of detail: partner CO object The sign of the amount is seen from the function cost center ( +: costs increase / -: costs decrease) Same layout as “Functions – During the month”		TBC	BW_QRY_MPR_FC001_0004

Synthesis” & “Function – End of month”  Reports

Additional axis : Structure with 6 categories

	Category	Definition	Example
(1)	Gross	All costs excluding depreciation before any deduction (sales, capitalization, etc…)	all labour costs + travel + services + …
(2)	Depreciation	Postings with depreciation cost elements	depreciation costs
(3)	Sales	postings with sales cost elements (excluding capitalization) + postings with all other cost elements linked to Invoicing WBS element (partners with object class “Profitability Analysis”)	activity (man Hr) posted on invoicing WBS -> time spent on IT project reinvoiced to customer
(4)	Costs going to be capitalized	postings linked to Investment WBS or Orders (partners with object class “Investment”)	activity (man Hr) posted on investment WBS -> time spent on IT project for development phase
(5)	Cost transferred	Credits from overheads CC WBS IO (partners with  class object “Overheads” - excluding sales cost elements)	activity (man Hr) posted on overhead WBS -> time spent on IT project for training phase
	Net Function	Balance of the cost center	(1) + (2) - (3) - (4) - (5)
	postings on function CC from WBS or internal order settlement are classified in Gross

Characteristics available in CBS reports

The below are characteristics 

Characteristic		Synthesis	Functions – End of month	Functions by Companies – End of Month	Reports – During month
0 – Hierarchy	Level 0 of ZCBS hierarchy	X	X	X	X
1 – Organization	Level 1 of ZCBS hierarchy	X	X	X	X
2 – Function	Level 2 of ZCBS hierarchy	X	X	X	X
3 – Sub-Funct Group	Level 3 of ZCBS hierarchy	X	X	X	X
4 – Sub-Function	Level 4 of ZCBS hierarchy	X	X	X	X
Company	Company of the function CC	X	X	X	X
Controlling area	Controlling area of the function CC	X	X	X	X
Cost center	Function cost center	X	X	X	X
Cost Element	Cost element used to post function costs	X	X	X	X
Cost Structure	slide ““Synthesis” & “Function – end of month”  reports	X	X
Country	Country of the company	X	X	X	X
Fixed Cost Group 1	Level 2 of ZRCS-FC hierarchy	X	X	X	X
Fixed Cost Group 2	Level 3 of ZRCS-FC hierarchy	X	X	X	X
Fixed Cost Group 3	Level 4 of ZRCS-FC hierarchy	X	X	X	X
Geographical zone	Zone to which the country is attached	X	X	X	X
Order	Order with a function CC as a responsible CC				X
Partner Activity Type	Type of activity used to transfer costs to the function CC from a partner CC		X	X	X
Partner Cost Center	Cost center with which the function CC exchanges costs (credit or debit)		X	X	X
Partner Order	order with which the function CC exchanges costs (credit or debit/Posting or settlement )		X	X	X
Partner Vendor	Vendor in purchase flows		X	X
Partner WBS element	WBS with which the function CC exchanges costs (credit or debit/Posting or settlement )		X	X	X
Responsible Cost Center	Function CC responsible of an order or a WBS element				X
Sender / Receiver	indicator that identifies the direction of the posting		X	X	X
WBS element	WBS element with a function CC as a responsible CC				X

4.0 Functional Specification

---

4.1 General Data/Calculations 

For these reports, it is important to understand some general concepts which are transversal to all the reports which allows the users to work with the reports in the same way as the SAP system and BFC tool.

Functional and Technical rules on Workbench + Reporting

Rules & Explanations

We needed a solution for Solvay or other companies not working on ERP SAP. We have created a specific transaction : ZBW_CBS

The transaction is based on program : ZBW_CYTEC_CBS

With this transaction, user can load excel file for

• Customer master data

• Cost Element master data

• Non-ERP Function costs data

The transaction is available in SOLIA portal. For information, it's better to use IE and not Chrome

We have created a new authorization object (C_SRSYST) to be sure that users can only load data for companies they have access to.

The program checks user’s authorizations with DPAUTH01 DSO

For master data, we can display content of master data in the screen and also save it in an excel file

For master data and transactional data, user is available to load excel files using lay-out already defined.

We control the content of the file to be sure that there is no error (missing field or incorrect values).

Once data is loaded:

• The file is saved as csv in /exploit/BW/Cytec

• The info packages are executed to load flat file in PSAs.

• The process chains are executed

  • By schedule (hourly with abap condition looking time in global filter).

  • Manage “delta queue” is several loadings at the same time

• Another process chains to load from PSA to BW Info provider

  • 2 for Master data

  • 1 for DSO and cubes

  • Process chain runs twice a day (managed in Global filter master data)

The abap program was developed to help user loading flat file in master data cost center & cost element and transactional data CBS function costs.

Below there is a list of entries in global filter used to support the program to do several activities, like: check authorizations, upload flat file, check company code, run process chain, etc.

Lay-out of files

Cost Center

InfoObject	Description	Type	Size	Key	Business rules and Comment
CO_AREA	Controlling area	CHAR	4	Y	always ZCYT ; authorization object in the specific transaction in WBP
C_COSTCTR	Cost Center	CHAR	10	Y	cytec cost center codes
LOGSYS	Source System	CHAR	10	Y	NERP003 or NERPCYT
C_FUNCT_0	0 Hierarchy	CHAR	32	N	check : always ZCBS
C_FUNCT_1	1 Organisation	CHAR	32	N	check with existing values for C_COSTCTR-C_FUNCT_1
C_FUNCT_2	2 Function	CHAR	32	N	check with existing values for C_COSTCTR-C_FUNCT_2
C_FUNCT_3	3 Sub-function Grouping	CHAR	32	N	no check
C_FUNCT_4	4 Sub-function	CHAR	32	N	no check
C_COMPCDE	Company code	CHAR	4	N	check with C_COMPCDE
CREATEDON	Creation date	DATS	8	N	sy datum (not in the file but populated by the specific program)
USERNAME	User Name	CHAR	12	N	sy uname (not in the file but populated by the specific program)
DATETO	Valid to	DATS	8	Y	YYYYMMDD
DATEFROM	Valid from	DATS	8	N	YYYYMMDD
PROFIT_CTR	Profit Center	CHAR	10	N	It is not filled in Cytec case
LANGU	Language Key	LANG	1	Y	always 'E' for English
TXTSH	Short description	CHAR	20	N	free text
TXTMD	Medium description	CHAR	40	N	free text
CPFCTR1_2	BFC Global Business Unit	CHAR	2	N	BFC GBU for example CS (NOVECARE) or SI (SILICA) etc..
CPFCTR2_2	BFC Group of activities	CHAR	5	N	For example code = CTTEX (FIBRAS TEXTILE)
C_PLANT	Plant	CHAR	4	N	For the filling of the fields C_RPLANT (Responsible Plant) and 0PLANT (PLANT)

Template of flat file for Cost center (the fields in red are mandatory = need to be filled with values)

CO_AREA Controlling area

C_COSTCTR Cost Center

LOGSYS Source System (linked to company code)

C_FUNCT_0 0 Hierarchy

C_FUNCT_1 1 Organisation

C_FUNCT_2 2 Function

C_FUNCT_3 3 Sub-function Grouping

C_FUNCT_4 4 Sub-function

COMP_CODE Company code

DATETO Valid to

DATEFROM Valid from

PROFIT_CTR Profit Center

LANGU Language Key

TXTSH Short description

TXTMD Medium description

CPFCTR1_2 BFC Global Business Unit

CPFCTR2_2 BFC Group of activities

C_PLANT Plant

ZCYT

160-7600

NERPCYT

ZCBS

ZCBS-PROJ

ZCBS-PIND

ZPINDEC

ZPINDEC2

7180

99991231

20190101

E

GEC Project - US

GEC Project US

Cost Element

InfoObject	Description	Type	Size	Key	Business rules and Comment
CO_AREA	Controlling area	CHAR	4	Y	always ZCYT ; authorization object in the specific transaction in WBP
COSTELMNT	Cost Element	CHAR	10	Y	cytec specific cost elements
CSTELMNTYP	Cost element category	CHAR	2	N	always '01'
LOGSYS	Source System	CHAR	10	N	NERP003 or NERPCYT, check against global filter
C_CELTHF1	Fixed cost Group 1	CHAR	32	N
C_CELTHF2	Fixed cost Group 2	CHAR	32	N
C_CELTHF3	Fixed cost Group 3	CHAR	32	N
C_CELTHF4	Fixed cost Group 4	CHAR	32	N
DATETO	Valid to	DATS	8	Y	YYYYMMDD
DATEFROM	Valid from	DATS	8	N	YYYYMMDD
LANGU	Language Key	LANG	1	Y	always 'E' for English
TXTSH	Short description	CHAR	20	N	free text
TXTMD	Medium description	CHAR	40	N	free text

Template of flat file for Cost element 

CO_AREA Controlling area

COSTELMNT Cost Element

CSTELMNTYP Cost element category

LOGSYS Source System

C_CELTHF1 Fixed cost Group 1

C_CELTHF2 Fixed cost Group 2

C_CELTHF3 Fixed cost Group 3

C_CELTHF4 Fixed cost Group 4

DATETO Valid to

DATEFROM Valid from

LANGU Language Key

TXTSH Short description

TXTMD Medium description

ZCYT

2602

1

NERPCYT

ZRCS-AC

ZRCS-30

ZRCS-3020

99991231

20170101

E

AMORTIZATION

AMORTIZATION

CBS Function Costs

InfoObject	Description	Type	Size	Key	Business rules and Comment
0CO_AREA	Controlling area	CHAR	4	Y	always ZCYT
0FISCVARNT	Fiscal year variant	CHAR	2	Y	Always K4
0FISCPER	Fiscal year / period	NUMC	7	Y	yyyymmm
0CURTYPE	Currency Type	CHAR	2	Y	always 10 meaning company code currency
0CO_DOC_NO	CO Document Number	CHAR	10	Y	counter defined by cytec not fill by the interface => still empty
0CO_ITEM_NO	Line Item of CO Document	NUMC	3	Y	always 1 not fill by the interface => still empty
C_COSTCTR	Cost Center	CHAR	10	Y	check with master data C_COSTCTR with controlling area ZCYT and company code
0COSTELMNT	Cost Element	CHAR	10	Y	check with master data C_COSTELMNT with controlling ares ZCYT
0LOGSYS	Source System	CHAR	10	N	NERP003 or NERPCYT
0FISCYEAR	Fiscal year	NUMC	4	N	YYYY
C_COMPCDE	Company code	CHAR	4	N	check with master data C_COMPCDE (PRS code)
0DB_CR_IND	Sender/Receiver indicator	CHAR	1	N	S = debit, H = credit
0VTYPE	Value type	NUMC	3	N	always 10
0CURRENCY	Currency key	CUKY	5	N	USD
0AMOUNT	Amount	CURR	9	N	decimal is '.', sign is xxx
0PSTNG_DATE	Posting date	DATS	8	N	format YYYYMMDD with no separator
0DOC_DATE	Document date	DATS	8	N	format YYYYMMDD with no separator

Template CBS Function Costs flat file

<Insert template>

Dependencies with other applications

There is no dependencies with other applications, all data is loaded using flat files by users.

Data loadings

Info providers and objects loaded
Main Process Chain: PC_FC_CYTEC





There is an abap condition ZBW_UPDATE_GLB_FILTER used to define the hours that the process should be executed based on global filter rule CYNE_STIME, nowdays twice a day.
In WBP : 5 times 11:00am + 01:00pm + 03:00pm + 04:00pm + 05:00pm (CET TIME)


In WBQ : from 8:00am to 09:00 pm each hour so 14 times

Cube CUB_FC007 - Fixed costs Analysis (External data)

DSO ODSBCCA9 - Cost Centers: Actual Costs (External data)

4.2 Process Detail 

4.2.1.  Report/Process Definition 

Domain	Finance
Application	BW reports under Function Costs folder
Provider	Multi provider MPR_FC001.
Existing Documentation	BW RTR - CBS Function Costs#History BW RTR - CBS Function Costs

Main flows

This section represents the process with detail information for the application. Can include specific or special cases, complex logics , calculations, flows, among others.

5.0 Non-functional Descriptions 

---

Non functional Descriptions are quality attributes that describe how the system should be. They judge the system as a whole based on fitness standards

5.1 Usability

Usability is about the ease with which a User can learn to start using the solution and the ease with which they can use the system.  In addition to ease of learning and ease of use, usability also includes areas such as ease of recall, error avoidance and handling, accessibility among others e.g., 99% of metadata entry Users who have use the Maintenance Dashboard should be able to change filters, extract etc., when required.  Maintenance data will be centrally stored in the Google Cloud platform, which will be available to other applications e.g., and Dashboards if needed.

5.2 Regulatory Compliance

Software systems must comply with legal and regulatory e.g., GDPR requirements, this can change depending on country, organisation industry and / or region.  The software systems must be secure from unauthorized access.  The Maintenance Dashboard will comply with Solvay’s regulations and compliance e.g., access only granted to authorized Users.

5.3 Security

• All data will be encrypted in the dashboard
• Only authorised Users / Administrative Users will be able to access data.
• Maintenance data will be split between either SCO or ECO, and Users will only have authority to one Entity data.

5.4 Performance

Average performance

Depending on number of records loaded there is a variance between 30 seconds and 5 minutes.

Key Figure	Estimation
~ Average Process Chain Runtime	2 minutes
~ Average nb of rows loaded per load	2K records
~ Total nb of rows loaded (if full)	20K
~ Average Runtime for 10k lines	2 minutes

5.5 Reliability

Reliability is the ability of a solution or its component to perform its required functions without failure under predefined conditions for a specified time / period.  Reliability can possibly be specified in terms of average time system runs before failure occurs, percentage of operations completed successfully within a time / period, maximum acceptable failure probability, or number of failures within a period.  Reliability aspects are in reference to (but not limited to) evaluation of the system to be considered as reliable, classification of reliability defining failures vs. regular failures, and the impact of failure on business operations.  The Maintenance Dashboard will display data from the previous refresh of data.   

5.6 Scalability

Scalability refers to the degree to which a solution can evolve to handle increased amounts of work.  The increased amount of work could be in terms of the user base, transactions, data, network traffic, or other factors e.g., the system should be able to handle an additional load of a maximum of 5,000 Users every month for the next 6 months without any noticeable performance impacts.  

5.7 Compatibility

Interoperability is the degree to which the solution is compatible with other components.  It is a measure of how effectively the system interoperates with other software systems and how easily it integrates with external hardware devices.

Interoperability aspects to be discussed during elicitation are in reference to (but not limited to) software systems to be interfaced with along with data / messages to be exchanged and any standard data formats, hardware components to be integrated with, and any standard communication protocols to be followed e.g., Order Management system will push the order file into a secured file transfer protocol server from where it will be loaded into the system through a daily job.  To guarantee between Google Cloud platform and SAP BW Queries e.g., BW_QRY_MVPMOR01_0002, Solvay has introduced a new tool called Xtract (Xtract).

5.8 Availability

Availability is the degree to which the solution is operable and accessible when required. It is a measure of time during which the system is fully operational e.g., available for use and sometimes included as a Service Level Agreement (SLA) considering its criticality to the business, e.g., the system shall be at least 99% available on weekdays between 09:00 to 18:30 Central European Time (CET).

5.9 Refresh of the Data

Loading frequency

Daily, twice a day.