Master data management    


The responsibility area is assigned to

Data Management & Reporting  

 

For questions related to Master data management you can contact :

The content of this macro can only be viewed by users who have logged in.

 

 

Responsibility Area & Process


 

Cost center master are displayed with KS03 - Display cost center





The codification of cost centers is different in WP2 & PF2. Depending on the type of request, you must follow the corresponding rules.

An useful reference to the codification of the cost centers is the Assessment cycle rules file for  WP2 or for PF2. This file is particularly helpful in identifying the codification for  technical cost centers. 

Production cost centers



Standard codification

The codification of an organizational cost center used for production is the combination of :

Note: Finance workflow is checking if the "Cost section" code is valid, reading table "ZZK_SECTION" in PF1_050; it should be maintained when required.


Example

Codification of a cost center used for the workshop F2 in the plant OSF Onsan 


Other cost centers



Standard codification

The codification of an organizational cost center not used for production is the combination of :


Example

Codification of a cost center used for Finance & Corporate Development in the plant OSF Onsan 

Production cost centers



Standard codification

The codification of a cost center used for production is the combination of :

  • The plant code (4 digit)
  • "-"
  • 4 digits, the first digit depends on the use of the cost center


Example

Codification of a cost center used for the workshop "Compounding" in the plant 7822 Belle-Etoile

Other cost centers



Standard codification

The codification of a cost center not used for production is the combination of :

  • Company code
  • "-"
  • 4 digits, the first digit (or the first 2 digits) depend on the use of the cost center


Cost centers starting with 8* are technical cost centers. If the codification range for 83* is completed, 85* codification should follow. An helpful resource is the file Assessment cycles rules for WP2.


Example

Codification of a cost center used for Strategic Marketing in the company ZFR3 Rhodia Operations



Valid from

Normally, the “valid from” date of a cost center must follow the following criteria : 

  • be the first of a month
  • be the current month until D-5 [to allow the closing test being performed D-3]
  • be any month in the future
  • for implementation project : date to be determined with the project – and validated by DMR

Reminder : cost centers creation requests for the current month are not processed during the closing period (from D-5 to D+3), except for urgent cases to be specifically validated by PE Leader Costing, via the workflow function “Ask the Process Expert for Validation”.

Action to undertake : during closing period, if date « valid from… » is in the month being closed, inform the requester that the creation will be processed next month.  If the requester insists to get an urgent creation, validation from PE Leader Costing is needed, before proceeding.

Valid to

by default it is valid to “31.12.9999”.

If it is different from 31.12.9999, it must be justified


Usually the name & description of a cost center is free but in some cases there can be special needs listed below


Regarding the name and description is important that, whenever the language of the country where we are creating the cost center is different from English, we add a description in the local language. There are several users that are using SAP in their local languages and not English.

Note: The countries that have a non EN language are properly customized when using the PRS workflow for the cost center creation/update. If there's any specific situation where it has been identified that the PRS workflow can not be used, the non EN languages have to be manually entered by entering in SAP in the required non EN language and update the name and description though KS02 - Update a Cost Center accordingly.

The person responsible of a cost center is accountable for the elements allocated in the cost center

The companies using SRM7 for purchasing should have a SRM7 user ID (=BIP user ID) entered in this field, starting with 5, such as 50000000


When creating a new cost center, you need to select the correct code using the following matrix (star)

=> You can filter by GBU/Function, name or position to find the code to be used. 




(star) if the link is not working you can also use the file (same data source)

The category is a letter, it depends on the type of cost center.
CategoryWP2PF2

F

Direct production cost centers - all cost centers related to workshops - codification : PPPP-1xxxPlant cost sections related to direct production costs
H

Other cost centers started with the plant code but not direct production

Plant cost sections related to indirect production costs, such as:

  • Other fixed costs not included in inventory value (e.g.: warehousing, commercial shipping, engineering,…)
  • Variable costs not included in inventory value (e.g.: tolling on raw materials).
W
All cost centers starting with the company codeAll other cases
E
Exceptional category used in the USA for tax purpose "Vertex" (thus limited to companies in the USA and duly justified by the controller)

Other categories are historically present in SAP. They can no longer be used


Cost center hierarchy in PF2

The code of the standard hierarchy in PF2 is KCHEF_HIER and it is structured in 2 main sub-groups:

  • CC_ORGANIS
  • CC_CHEOPS

The group CC_CHEOPS was used for reporting cost centers. These cost centers are not used anymore.

In other words the group CC_CHEOPS should not be used anymore and all active cost centers should now be included in the group CC_ORGANIS.



The group CC_ORGANIS is only harmonized until the plant level, afterwards it is free for every site.

CC_ORGANIS
  • XX - Country
    • E_CCCC - Company
      • CCCC_PP - Site
        • PPP - Plant 
          • Cost center 1
          • Cost center 2


XX = Country code

CCCC = Company code

PPP = plant code 

PP = First 2 digits of the plant code







Cost center hierarchy in WP2

In WP2, there is one standard hierarchy per Controlling Area

The structure must follow the standard rule:

Zxxx = Controlling Area

PPPP = Plant code

CCCC = Company code 

GB = GBU code 

  • CB - Corporate Business Services
  • CM - Composite Materials
  • CS - Novecare
  • OG - Oil & Gas
  • PA - Aroma Performance
  • SP - Specialty Polymers
  • TS - Technology Solutions


The group PPPP-FUNCT is only used by the GBU Novecare


It's not possible to change the business area field during a fiscal year once there are already postings or planned postings in that fiscal year.

The Business area is used in PF2 only and is used to identify the business involved in each transaction.

The codification of the Business area is:



Profit center to be used in PF2

The profit center to be used in the master data of a cost center is the organizational profit center of the plant.

Standard codification

The codification of an organizational profit center 

  • Letter C
  • Plant code



Profit center to be used in WP2

The profit center to be used in the master data of a cost center in WP2 must be chosen carefully as it is used for several purposes :

  • Fixed costs dashboard
  • Industrial dashboard
  • Working Capital

Two controls must be performed when assigning a profit center to a cost center :

1. The GBU & the value stream

The profit center that is assigned to a cost center is used to identify to which GBU & value stream the cost center belongs. The profit center used must be included in the right value stream & GBU.


All profit centers must be attached to a node in the standard hierarchy
In WP2, there is one standard hierarchy per Controlling Area. Its structure must follow the standard rule 

The profit center hierarchy can be displayed in SAP with: 

Value stream

The value stream (VS) is the lower level of the profit center hierarch in WP1 system, where the profit centers are assigned through the "Profit Ctr Group".

Historically, the value stream nodes in the profit center hierarchy were used for some Industrial reporting on specific production lines but currently this reporting level is no longer used, unless there's a justified request for it. Nevertheless, we need to maintain the value stream node at a standard level.

Most of the value stream codes are already defined for a certain GBU and geographical zone and just need to be extended to a particular company code. It has to be always checked before creating a new code.

 

VALUE STREAM CODIFICATION in the profit center hierarchy: 


XXXX-VZYMN


XXXX - Stands for the company code

V - Standard for all the VS codes

ZY - Is used to define a specific GBU code as follows (the currently active GBU's are the ones highlighted):

•ZA for a VS under GBU ACETOW

•ZB for a VS under GBU PEROXIDES

•ZC for a VS under GBU COATIS

•ZD for a VS under GBU SODA ASH

•ZE for a VS under GBU ECO SERVICES

•ZF for a VS under GBU FIBRAS

•ZG for a VS under GBU ENG PLASTICS

•ZH for a VS under GBU SPECIAL CHEM

•ZI for a VS under GBU EMERGING BIOCHEMICALS

•ZJ for a VS under GBU TECHNOLOGY SOLUTIONS

•ZK for a VS under GBU COMPOSITES MATERIALS

•ZL for a VS under GBU SOLD ACTIVITIES (2003-2010)

•ZM for a VS under GBU SPECIALTY POLYMERS

•ZN for a VS under GBU NOVECARE

•ZO for a VS under GBU AROMA PERFORMANCE

•ZP for a VS under GBU POLYAMIDE & INTERMEDIATES

•ZQ for a VS under GBU Oil & Gas

•ZR for a VS under GBU CBS (former NON REPARTI RHODIA)

•ZS for a VS under GBU SILICA

•ZT for a VS under GBU RARE EARTH SYSTEMS

•ZY for a VS under GBU ENERGY


M - stands for the geographical zones, as follows:

EU: 0, 1, 2
NA: 3, 4
LA: 5, 6
AP: 7, 8
WW: 9


N - it's a serial number


Note: The value stream codes have to be included in table ZWFAT187 to be able to define the related descriptions in several standard languages.

For this, the codification has to be converted to an 8 digit code as follows (some of the digits are already defined when establishing the VS node in the profit center hierarchy):


CGUZY0MN


CGU - Standard for all the standard VS codes

ZY - Is used to define a specific GBU code, as per list above

0 - Always zero 

M - stands for the geographical zones, as per list above

N - it's a serial number


Link to the old WP2 Codification Value Streams Master (OBSOLETE).

Usually a specific value stream is used for production cost centers (PPPP-1xxx & PPPP-2xxx) and a non allocated value stream is used for other cost centers.

2. The department of the profit center

  • A profit center with a department = plant code is assigned to production cost centers (PPPP-1xxx & PPPP-2xxx)
  • A profit center with a department = GBU plant is assigned to other cost centers especially for SG&A, R&I...

The field "Department" of the profit center is a critical field that is used in BW to assign a cost center to a plant and then to a site

ex:

  • The cost center 7512-1022 is assigned to the profit center 7512-I0449
  • The department of the profit center 7512-I0449 is 7512

=> The cost center is assigned to the plant 7512

Depending on the type of profit center the department code can be: 

  • a plant code = a code maintained in table T001W in WP1 or PF1 (1) 

  • a generic plant code (only in WP1) created by GBU (2). This code doesn't exist in the table T001W. 



Rule by ERP + type of profit center

ERPType of profit centerDepartmentExample
PF1Reporting profit center= "blank"

= plant code 

By default the department code = profit center code without the letter C

However the rule is to have one department code by site even if for historical reasons there can be several profit centers in the same site. 

ex: in Tavaux, all profit centers are assigned to the department TAU: 

Profit centerDepartment
CTAH Slvfr-Fr /Tavaux (Spc)

TAU Tavaux

CTAU Slvfr-Fr /Tavaux (Pvdc)

There is one exception when there are several management units / GBU in the site (only in GBU Soda Ash).

In the GBU Soda Ash, there should be one dedicated department for Soda Ash another one for Bicar. 

ex: in Torrelavega

Profit centerDepartment
CTOS Slvq-Es /Torrelavega (Su)

TOSA (management unit Soda Ash)

CTOSA Slvq-Es /Torrelavega (Sod)
CTOSB Slvq-Es /Torrelavega (Bir) TOSB (management unit Bicar)



WP1Profit center used in the master data of production cost centers (the codification of the cost center starts with the plant code (star))

= plant code 

= first digits of the profit center code (star)

ex: department of profit center 7512 -I0449 = 7512 

Profit center used in the master data of SG&A / CBS / Financial cost centers (the codification of the cost center starts with the company code (star))

These profit centers are used in cost center that could be shared between several plants/sites. 

Ex: in Rhodia Operation, there can be people working in the same team located in Paris or Lyon. Then the cost center is allocated neither to the Paris site nor to the Lyon site but to a generic site.

By default this rule applies to all cost centers that are not used on production plants.

The only exception is the facilities cost centers in CBS.

= generic GBU code 

= BFC GBU code + 00

ex:  Novecare = CS00 


Last update:  

Generic code
CB00CB Corporate Business Services
CH00CH Special Chem
CM00CM Composite Materials
CS00CS Novecare
CT00CT Coatis
GY00GY Energy Services
NB00NB New Business Development
OG00OG Oil & Gas
PA00PA Aroma
PE00PE Peroxides
SD00SD Soda Ash
SI00SI Silica
SP00SP Specialty Polymers
TS00TS Technology Solution

Exception: Facilities cost centers included in the group ZCBS-FFAC of the ZCBS hierarchy

= plant code 

= first digits of the profit center code (star)

ex: department of profit center 7925 -I0569  = 7925

(star) For historical reasons, there may be exceptions to the codification


ZCBS is the code of the alternative cost centers hierarchy that is mainly used for reporting purposes (ex:  Co$ta - Reports Fixed costs ).

You can display the ZCBS hierarchy:

You can also use the report FC - Cost centers master data to display all cost centers with their assignment in the hierarchy ZCBS. 


All active must be assigned to the lowest level in the hierarchy so that the full ZCBS levels are properly shown for the related cost center.

A cost center in included in ZCBS according to the following principles: 



1. There is a direct link between the first level of the ZCBS hierarchy and the Activity 1


CBS cost centers

  • All cost centers included in the groups  SCBS-CORPO Corporate Function &  SCBS-FUNCT  FUNCTION SERVICES are assigned to the  Activity 1  CBSS in WP2 (=IECRA00569) and PF2 (=DIV 50 or =BA 8500).
  • Cost centers included in the group SCBS-ICO INTERCOMPANIES are assigned to the Activity 1 CBSS in WP2 (=IECRA01148) and PF2.




Non allocated cost centers

  • All cost centers  included in the group SCBS-OTH CBS NON FUNCTION COSTS are assigned to the Activity 1 CBNR in WP2 (=IECRA00450)  and PF2 (=DIV 59 or =BA 8590).




GBU cost centers

  • All cost centers included in the group ENTRP  ENTERPRISE are assigned to a GBU.

There can not be cost centers allocated to CBS included in the group ENTRP. 







Other groups

  • The group RHXXX TECHNICAL COST CENTERS is used for technical cost centers (not reported in fixed costs report) 
  • The group DISC DISCONTINUED is used for cost centers that are blocked 
  • The group ZNS-FUNCT NON SOLVAY - FUNCTION SERVICES can be used for entities sold when they want to keep working with a fixed costs report with their own groups


Group ZNS-FUNCT

Currently, the group ZNS-FUNCT does not exist in WP2 or PF2 because it doesn't need to be maintained.




2. There is a direct link between the first (or second) level of the ZCBS hierarchy and the P&L



CBS cost centers




Non allocated cost centers

  • Cost centers included in the group SCBS-OTH CBS NON FUNCTION COSTS :  they will be allocated to corresponding BFC headings depending on its destination (ie:  Administrative or Commercial expenses, Other recurring operating income/expenses, etc)




GBU cost centers

  • The allocation of cost centers included in the group ENTRP  ENTERPRISE depends on the type of costs:
ZCBS groupDefinition
EPRD

All production cost centers should be included in the group EPRD: 

  • Indirect production cost centers (PPPP-2 in WP2) should be included in a group EPRD1=>EPRD6. 
    • Utilities cost centers should be included in the group EPRD4Y in PF2 only. In WP2 they are included in the group ECP)
  • Direct production cost centers (PPPP-1 in WP2, EE32xxxxxx in PF2) should be included in the EPRD0: 
    • EPRD0X when the production cost center is not mixed (all cost centers in WP2 and some cost centers in PF2)
    • EPRD0Y when the production cost center is mixed (only in PF2) 
    • EPRD0Z can be used to manage underactivity (only in very specific cases)

=> Definition of Period non-proportional costs of production (R25460)

EADM

This group is used for cost centers allocated to the BFC account Administrative expenses (R33310)

  • A GBU can request the creation of sub-groups to detail its own organization. 
EMSV

This group is used for cost centers allocated to the BFC account Commercial expenses (R33320)

  • A GBU can request the creation of sub-groups to detail its own organization. 
RDD

This group is used for cost centers allocated to the BFC account Research and Development (R360)

  • A GBU can request the creation of sub-groups to detail its own organization. 

For other groups you can look at the file by ERP in Assessment cycles Rules




Technical cost centers  are not allocated to BFC




3. There is a direct link between the lowest level of the ZCBS hierarchy and a BSA



The ZCBS hierarchy is used for the allocation of cost centers to a BSA using. 

The assignment of cost centers to a BSA is done with the cost center hierarchy = ZCBS_BSA which is built using the last level of the ZCBS hierarchy



a) All the production cost centers (cost center category F) must have the "Record Quantity" field flagged:


b) Cost centers Cost of goods sold - Statistics (codification CCCC-9200 in WP1) must have the "Actual revenues" and "Plan revenues" fields not flagged and

the "Record Quantity" field flagged:


 

 


 

There are 2 types of cost elements: 

  1. Primary Cost Elements for cost flows from Financial Accounting to Controlling. They are the replica of GL Accounts
  2. Secondary Cost Elements for cost flows within Controlling. They are created within the CO module. 


Master Data to be maintained in PF2 & WP2

Display cost elements master data with KA03 - Display Cost Element



1. Codification

The codification of a cost element depends on the ERP & the usage of the cost element: 

 

A primary cost elements is for CO the equivalent as accounts in FI with the same codification that is detailed in the page GL Accounts codification tables.

In PF2


The codification of a primary cost element is:

  • 6 when it is a cost & 7 a revenue 
  • 9 digits : it can depend on the use of the cost element





In WP2


The codification of a primary cost element is:

  • 98 : primary cost element
  • 6 digits that can depend on the use of the cost element

 

There are 2 types of secondary cost elements: 

  • Cost elements to transfer costs between cost centers, orders & WBS
  • Cost elements to transfer costs from the cost centers to COPA (in PF2 we speak about "Reporting cost elements")

In PF2


The codification of a cost element to transfer costs between cost objects is: 

  • 9 : secondary cost element
  • 4 digits : cost section
  • 3 digits : local need
  • 1 digit
    • 0 - ad cost
    • 1 - unit price
    • 2 - fixed price
  • 1 digit
    • 0 - settlement
    • 1 - assessment
    • 2 - activities

cost element_codification 2ndary Pf1 org.png

Example

Codification of a non reporting secondary cost element used to  settle Maintenance with assessment cycles  

  • 9 : secondary cost element

  • 4 digits : cost section :  105  Maintenance

  • 3 digits : by default  000

  • 1 digit : 0  - ad cost

  • 1 digit : 1  - assessment

cost element_codification 2ndary Pf1 org ex.png

The codification of a Reporting cost element (to transfer costs from a cost center to COPA):

  • 98 : reporting cost element
  • 3 digits : cost section
  • 3 digits : local need
  • 1 digit
    • 0 - ad cost
    • 1 - unit price
    • 2 - fixed price
  • 1 digit
    • 0 - settlement
    • 1 - assessment
    • 2 - activities

cost element_codification 2ndary Pf1 report.png



In WP2


The codification of a secondary cost element is:

  • 99 : secondary cost element
  • 6 digits : the first digits depend on the use of the cost element


2. Categories

Depending on the type & usage of the cost element, the category differs: 

Primary cost element

Category 01 : the account can use a cost element or a profitability segment

  • The sign used in the account in FI is the same used in CO-PA

Category 11 : the account must use a profitability segment

  • The sign used in the account in FI is inversed in CO-PA (KE24)
  • The report re-inverse the sign in the line (KE30)
  • We cannot mix the 2 categories in the same CO-PA value field
  • Be careful in the assessment cycles from cc to CO-PA (rules need to be followed)

Category 22 : external settlement > used in the primary cost elements defined as a counter part of a cost object settlement to a balance account (ex: wbs UAC in Europe )

Secondary cost element

  • Category 21 : internal settlement > used in the cost elements of PM orders settlement
  • Category 42 : assessment > used in the assessment cycles of cost centers 
  • Category 43 : internal activity allocation > assigned to the activity types. Every one could represents a fix cost or a variable cost , never mixed cost. 



3. Groups


A cost element is included in 2 core groups :


  • In PF2, the group XCS-ALL is the base for allocation structures of Utilities and for new Splitting Structures
  • In WP2, the group XCS-ALL is used in the PA transfer structures for settling WBS elements, process orders and internal orders to CO/PA




The group ZSOLV is created in PF2 & WP2. 

It replaces the cost element group ZRCS-FC from  

It is used:


How to display the group ZSOLV ?








 

There are 2 types of profit centers in PF2: 

1. Reporting profit centers

In PF2, the determination of the business structure is done in the P&L using a reporting profit center  that is in the  COPA posting.  To make this everything works (through interfaces):

  • All material codes should be assigned to a reporting profit center (in the view "costing 1")
  • All objects in CO should be assessed to a profit center in COPA 

2. Organizational profit centers

All CO objects (cost centers, orders, WBS) are assigned to a non reporting profit center

In WP2 the profit center is used to:

Assign the following variances to the P&L (COPA)

  • Variances on purchase
  • Inventory differences
  • Variances on transfer
  • Variances on process order
  • Revaluation variances

Split the Working Capital by enterprise

  • Split the accounts payable and the stocks by CGU (Cash Generating Unit)

Calculate some indicators of the industrial dashboard and identify by Value Stream

  • Inventories
  • Variable costs (the actual ones posted through process order)
  • Fixed costs (from the direct production costs center)
  • Freight on sales costs (from the P&L and freight on sales cost centers)
  • Accounts payable


Note

In WP2, since we can not restrict the usage of the profit center to a certain controlling area, it is recommended that whenever creating a new profit center in a certain controlling area, it's also extended to the VPART nodes in the other active controlling areas.



Profit center master data are displayed with KE53 - Display Profit Center

PF2

WP2


PIF level


Standard codification

The codification of a reporting profit center used at PIF level:

  • Letter F
  • Activity 1 code - 2 characters of the Reporting Division from SM30 table V_134G, Division code (check in Material Master Data (MM03), tab Basic Data 1, the field Division) + Plant code, to get the correct Business Area.
  • PIF code - Use the first 5 characters of the PIF code (complete with “X” to reach 5 characters). To identify the correct code, go to T-code MM03Basic Data 1 tab, check the Prod. Hierarchy field. In SM30 table ZZRT179V, confirm that the Prod. Hierarchy code is marked with an “X” in the Flag PIF column. 
  • Country of origin - 1 character for the country code of the industrial origin, i.e. where the goods are manufactured - see appendix for the codes.
  • A - Austria

    B - Belgium

    C - Switzerland

    D - Germany

    E - Spain

    F - France

    G - Great Britain - UK

    H - China

    I - Italy

    J - Japan

    K - Korea

    L - India

    M - Mexico

    N - Netherlands

    O - Russia (possible extension to other countries)

    P - Portugal

    Q - Not used

    R - Brazil

    S - Finland (possible extension to other countries)

    T - Thailand

    U - USA

    V - Argentina

    W - Not used

    X - Improperly used for some “3rd parties” and some other strange ones

    Y - Egypt, Saudi Arabia, Chile and other miscellaneous countries

    Z - Inovyn Martorell - other / future use to determine

    1 - Rhodia EMEA region (only for “green” GBU - when production center is not specifically known)  - corresponding to industrial origin 9991

    2 - Rhodia NAM region (only for “green” GBU - idem) - corresponding to industrial origin 9992

    3 - Rhodia LATAM region (only for “green” GBU - idem) - corresponding to industrial origin 9993

    4 - Rhodia APAC region (only for “green” GBU - idem) - corresponding to industrial origin 9994

    9 - Third parties - corresponding to industrial origin 9997

  • Code packaging - 1 character (normally a digit) to differentiate - normally odd for packed and even for bulk.

These profit centers are used for postings at the lower level of detail : PIF + industrial origin.



Activity 1 level


Standard codification

The codification of a reporting profit center used at Activity 1 level

    • D + Business Area
      • Letter D
        Business Area
      • Sector code
      • Activity 1 code
      • Free

These profit centers are used for posting at “company code” + “BFC Activity 1” level. Should wait until the Business Area has been created by APDM and is available in PF2_020 before creating the D* profit center.



Profit centers at company & company/object levels should not be used anymore 

Before the project SPS (COPA in PF2) there were 2 other types of reporting profit centers:

At company level

They were used for posting at “company code” level for which there was no subdivision between GBU or BFC Activities.  

The codification of a reporting profit center used at Company code level was:

  • Letter E
  • Company code

At company & object level

These profit centers represent the shares of the company hold by other Solvay companies. Can be created for any Solvay companies, operating in the ERP Solvay or not.

The codification of a reporting profit center used at Company code and object level was:

  • Letters SCHEF
  • Company code

Reporting profit centers at company & company/object levels should not be used anymore 


Standard codification

The codification of an organizational profit center 

  • Letter C
  • Plant code


Codification - Standard codification

The codification of a profit center is 

  • Company code or plant code
  • Letter 
  • Last 4 digits of the IECRA



The recommended practice is to put a Profit Center with "plant" codification in the Master Data of a "plant" Cost Center


Example

Codification of a profit center for Novecare in the plant 8091 Zhuhai

Usually it is created from the 1st day of the current year to 31.12.9999

In PF2, the name of a profit center is critical for the reporting, the rules must be strictly followed.

PIF level


The name of a reporting profit center used at PIF level (F)

  • position 1-3        = first 3 characters of the Business Area (Sector code + Activity 1 code)

  • positions 4-5     = Spaces
  • positions 6-10   = PIF code (always in  Caps Lock ) + spaces to make it 5 chars
  • positions 11-14 = industrial origin code - see transaction ZPRI - in case of tolling in an external plant, use the one of the Syensqo plant responsible for the tolling
    • 9997 for product bought outside the group from third parties
    • 9991 - 9994 for Rhodia GBU for which we do not know the specific industrial origin 
  • position 15       = E (packed) or V (bulk) if a differentiation is made at that level.

  • positions 16-20 = free (not relevant for BFC)

Example

The name of the profit center F49JLAXXU1 is  349  JLA  3272E

  • Sector code = PLASTICS

  • Reporting Activity 1 code = 49 FLUOR MATERIALS
  • “empty”
  • PIF code   = JLA Tecnoflon
  • Industrial origin code = 3272 SOLVAY SPOL US

  • Packaging code = E Packed

  • “empty”





The long text of a reporting profit center used at PIF level (F)

  • Description of the PIF from table view ZZRT179V
  • Space - hyphen - space
  • City name of the establishment (EMEA… for 9991 - 9994 - and “3RD PARTIES” for industrial origin 9997)
  • Space - hyphen - space
  • “PACK” or “PACKED” // “BULK"

Note: If over the SAP 40-chars limit, abbreviate the names according to SLV traditions.




Activity 1 level


Example

The name of the profit center D3490 is  349

  • Sector code =  PLASTICS

  • Reporting Activity 1 code = 49 FLUOR MATERIALS
  • “empty”
  • not applicable
  • “empty”

The name of a reporting profit center used at PIF level (D)

  • position 1-3      = first 3 characters of the Business Area (Sector code + Activity 1 code) - essential as used by COPA / BW for automatic determination
  • positions 4-10    = Spaces
  • positions 11-14  = Industrial origin code (only for specifics cheops value item like “ARRET”)
  • position 15         = Spaces
  • positions 16-20  = Free (not relevant for BFC)

The long text of a reporting profit center used at PIF level (D)

  • Description from table ZZR_REPO_DIV taking the middle 2 characters from the Business Area (ex. profit center D9TN0 - search for “TN”).



Company level


The name of a reporting profit center used at company level (E)

  • positions 1-4     = Reporting company code

  • positions 5        = Space
  • positions 6 -20  = Company “Enterprise abbreviation” from transaction ZPRI

  • last 3 positions = "hyphen"+"Country code" (from transaction ZPRI)


Example

The name of the profit center E6288 is 6288 SFLX-DE

  • Reporting company code = 6288

  • “empty”
  • Enterprise abbreviation = SFLX
  • "Hyphen"
  • County = DE


The long text of a reporting profit center used at company level (E)

  • positions 1-4     = Reporting company code

  • positions 5        = Space
  • positions 6-20  = Company “Enterprise medium name” from transaction ZPRI



Company and object level


The name of a reporting profit center used at Company and object level (S)

  • positions 1-4     = Object company code
  • positions 5 = Space
    positions 6-20 = Company “Enterprise abbreviation” from transaction ZPRI in PRS

  • last 3 positions = "hyphen"+"Country code" (from transaction ZPRI)


Example

The name of the profit center SCHEF6329 is  6579 FIOP-BR

  • Object company code = 6579

  • “empty”
  • Enterprise abbreviation = FIOP
  • "Hyphen"
  • County = BR



The long text of a reporting profit center used at Company and object level (S)

  • positions 1-13     = PARTICIPATION

  • position 14          = Space

  • position 15 -18    = Object company code
  • positions 19         = Space
  • last positions      = Company “Enterprise medium name” from transaction ZPRI

Unlike reporting profit centers, the description of organizational profit center doesn't matter.

  • Short name - company code + space + plant “establishment abbreviation” from PF2 - ZPRI Display table ETAB (using the first 3 chars of the plant)
  • Long text - plant NAME1 from view V_T001W (if needed using standard SLV abbreviation for the site) + abbreviated NAME2 from V_T001W if making it clearer.

In WP2, the name of a profit center does not matter as it is not used in reporting. 

Plant level


The name of profit center created at plant level: 

  • PPPP = plant code
  • name of the profit center
  • VVVVV = value stream code

Example: 7666 divers Diphénols MEL - VZS05



Company code level


The name of profit center created at company level: 

  • PPPP = Generic plant code (=BFC GBU code + 00)
  • name of the profit center (by default the GBU name)
  • VVVVV = value stream code

Example: SI00 Silica - VSL01


PIF level


The Person responsible of a reporting profit center used at PIF level (F) is

  • position 1-4         = "X   "

  • positions 5-20     = free (not relevant for BFC)

Example

The person responsible of the profit center F49JLAXXU1 is X

  • position 1-4         = X

  • positions 5-20     = “empty”

=> In case of inter-company sales, the person responsible is 

  • position 1-4         = partner company code

  • positions 5          = partner sector
  • positions 6-7       = division partner
  • positions 8-20     = free (not relevant for BFC)

Example

The person responsible of the profit center F27UYXXXFB is 3490727

  • žpartner company code = 3490 SOLVAY SPECIALIT FR

  • partner sector         =CHEMICALS
  • activity 1 partner      = 27 PCC
  • “empty”


Activity 1 level


The Person responsible of a reporting profit center used at Activity 1 level (D) is

  • position 1-4         = "X   "

  • positions 5-20     = free (not relevant for BFC)

Example

The person responsible of the profit center D3490 is X

  • žposition 1-4         = X

  • positions 5-20     = “empty”



Company level


The Person responsible of a reporting profit center used at company level (E) is

  • position 1-4         = Company code

  • positions 5-20     = free (not relevant for BFC)

Example

The person responsible of the profit center E0001 is 0001

  • žposition 1-4         = 0001

  • positions 5-20     = “empty”



Company and object level


The person responsible of a reporting profit center used at Company and object level (S)

  • positions 1-4     =  "X   "
  • positions 5-20   = free (not relevant for BFC)

Example

The person responsible of the profit center SCHEF0001 is X

  • position 1-4         = X

  • positions 5-20     = “empty”



The only reporting profit centers impacted by the change of the Person Responsible field are the ones started by D* and F*



 The field is not used but since it's a mandatory field put a X.

 The field is not used

The field "Department" of the profit center is a critical field that is used in BW to assign a cost center to a plant and then to a site

ex:

  • The cost center 7512-1022 is assigned to the profit center 7512-I0449
  • The department of the profit center 7512-I0449 is 7512

=> The cost center is assigned to the plant 7512

Depending on the type of profit center the department code can be: 

  • a plant code = a code maintained in table T001W in WP1 or PF1 (1) 

  • a generic plant code (only in WP1) created by GBU (2). This code doesn't exist in the table T001W. 



Rule by ERP + type of profit center

ERPType of profit centerDepartmentExample
PF1Reporting profit center= "blank"

= plant code 

By default the department code = profit center code without the letter C

However the rule is to have one department code by site even if for historical reasons there can be several profit centers in the same site. 

ex: in Tavaux, all profit centers are assigned to the department TAU: 

Profit centerDepartment
CTAH Slvfr-Fr /Tavaux (Spc)

TAU Tavaux

CTAU Slvfr-Fr /Tavaux (Pvdc)

There is one exception when there are several management units / GBU in the site (only in GBU Soda Ash).

In the GBU Soda Ash, there should be one dedicated department for Soda Ash another one for Bicar. 

ex: in Torrelavega

Profit centerDepartment
CTOS Slvq-Es /Torrelavega (Su)

TOSA (management unit Soda Ash)

CTOSA Slvq-Es /Torrelavega (Sod)
CTOSB Slvq-Es /Torrelavega (Bir) TOSB (management unit Bicar)



WP1Profit center used in the master data of production cost centers (the codification of the cost center starts with the plant code (star))

= plant code 

= first digits of the profit center code (star)

ex: department of profit center 7512 -I0449 = 7512 

Profit center used in the master data of SG&A / CBS / Financial cost centers (the codification of the cost center starts with the company code (star))

These profit centers are used in cost center that could be shared between several plants/sites. 

Ex: in Rhodia Operation, there can be people working in the same team located in Paris or Lyon. Then the cost center is allocated neither to the Paris site nor to the Lyon site but to a generic site.

By default this rule applies to all cost centers that are not used on production plants.

The only exception is the facilities cost centers in CBS.

= generic GBU code 

= BFC GBU code + 00

ex:  Novecare = CS00 


Last update:  

Generic code
CB00CB Corporate Business Services
CH00CH Special Chem
CM00CM Composite Materials
CS00CS Novecare
CT00CT Coatis
GY00GY Energy Services
NB00NB New Business Development
OG00OG Oil & Gas
PA00PA Aroma
PE00PE Peroxides
SD00SD Soda Ash
SI00SI Silica
SP00SP Specialty Polymers
TS00TS Technology Solution

Exception: Facilities cost centers included in the group ZCBS-FFAC of the ZCBS hierarchy

= plant code 

= first digits of the profit center code (star)

ex: department of profit center 7925 -I0569  = 7925

(star) For historical reasons, there may be exceptions to the codification

 

The code of the standard hierarchy in PF2 is KCHEF_HIER and it is structured in 2 main sub-groups:

  • CHEFCHEOPS for reporting profit centers
  • CHEF_CNTRL for non reporting Profit Center
GB = GBU code
GAA = Group Activity 1 code 
S = Sector code
AA = Activity code
PPP = Plant code 


 

All profit centers must be attached to a node in the standard hierarchy
In WP2, there is one standard hierarchy per Controlling Area. Its structure must follow the standard rule 

The profit center hierarchy can be displayed in SAP with: 

Value stream

The value stream (VS) is the lower level of the profit center hierarch in WP1 system, where the profit centers are assigned through the "Profit Ctr Group".

Historically, the value stream nodes in the profit center hierarchy were used for some Industrial reporting on specific production lines but currently this reporting level is no longer used, unless there's a justified request for it. Nevertheless, we need to maintain the value stream node at a standard level.

Most of the value stream codes are already defined for a certain GBU and geographical zone and just need to be extended to a particular company code. It has to be always checked before creating a new code.

 

VALUE STREAM CODIFICATION in the profit center hierarchy: 


XXXX-VZYMN


XXXX - Stands for the company code

V - Standard for all the VS codes

ZY - Is used to define a specific GBU code as follows (the currently active GBU's are the ones highlighted):

•ZA for a VS under GBU ACETOW

•ZB for a VS under GBU PEROXIDES

•ZC for a VS under GBU COATIS

•ZD for a VS under GBU SODA ASH

•ZE for a VS under GBU ECO SERVICES

•ZF for a VS under GBU FIBRAS

•ZG for a VS under GBU ENG PLASTICS

•ZH for a VS under GBU SPECIAL CHEM

•ZI for a VS under GBU EMERGING BIOCHEMICALS

•ZJ for a VS under GBU TECHNOLOGY SOLUTIONS

•ZK for a VS under GBU COMPOSITES MATERIALS

•ZL for a VS under GBU SOLD ACTIVITIES (2003-2010)

•ZM for a VS under GBU SPECIALTY POLYMERS

•ZN for a VS under GBU NOVECARE

•ZO for a VS under GBU AROMA PERFORMANCE

•ZP for a VS under GBU POLYAMIDE & INTERMEDIATES

•ZQ for a VS under GBU Oil & Gas

•ZR for a VS under GBU CBS (former NON REPARTI RHODIA)

•ZS for a VS under GBU SILICA

•ZT for a VS under GBU RARE EARTH SYSTEMS

•ZY for a VS under GBU ENERGY


M - stands for the geographical zones, as follows:

EU: 0, 1, 2
NA: 3, 4
LA: 5, 6
AP: 7, 8
WW: 9


N - it's a serial number


Note: The value stream codes have to be included in table ZWFAT187 to be able to define the related descriptions in several standard languages.

For this, the codification has to be converted to an 8 digit code as follows (some of the digits are already defined when establishing the VS node in the profit center hierarchy):


CGUZY0MN


CGU - Standard for all the standard VS codes

ZY - Is used to define a specific GBU code, as per list above

0 - Always zero 

M - stands for the geographical zones, as per list above

N - it's a serial number


Link to the old WP2 Codification Value Streams Master (OBSOLETE).



Consistency checks to be made before validating a “PIF level” profit center : if one of these conditions is not met, we need to challenge / reject the request


STEP 1

Check the consistency between the data present in the code, in the short name and in the long description

 


STEP 2

Check that the Reporting Division is within the validity dates in table ZZR_REPO_DIV

 


STEP 3

In the table view ZZRT179V control that:

  • The “ Flag PIF ” is ticked,

  • The PIF is not deleted - The description of Product hierarchy can't contain *D*,

  • The validity period  - We cannot have profit centers at higher / lower levels of the hierarchy than the PIF
 
 


STEP 4

Check the Business area assignment in the production plant is consistent with the Reporting division present in the profit center, in table view V_134G :

  • Plant = plant code where the material is going to be extended. If it's a production plant you can check its validity via transaction ZPRI,


  • Product division = the one corresponding to the PIF, in table view ZZRT179V,


  • The Business area indicated in view V_134G must be consistent with the Reporting division of the profit center.



STEP 5

Check that the other profit centers for the same PIF are linked to the same or other Reporting divisions.

Taking into account that they are exceptions, such as for  PIF U* for utilities which can be assigned to several reporting divisions, as well as some product lines for which there are several Reporting divisions (e.g. chlorovinyls Russia <> Thailand <> Mercosur)

 





 

When a profit center becomes obsolete, we need to lock it :
  • Set the “lock indicator” in “indicators” tab.

  • Insert ZZ at the end of the short description.

  • Insert ZZZZ at the beginning of the long description.

 

As the BFC Act1 or the plant is part of the code, we cannot change their meaning, retaining the code.

 

The only case where we can update profit center short description is when a production facility changes of “ETAB” code, still representing the same reality. This can occur usually in a Legal Entity Reduction or Carve Out project.

 

 

Internal order master are displayed with KO03 - Display Internal Order


List of fields to be filled when creating an internal order: 

  1. Description
  2. Order type

  3. Business area (only in PF1)
  4. Profit center
  5. Responsible CCtr
  6. External order no.
  7. Settlement Rule


 TBC
 TBC
 TBC

Process of cost centers maintenance


Operating procedures


  • Page:
    OP.007 I update R&D WBS
  • Page:
    OP.012

    Error rendering macro 'excerpt-include'

    User 'null' does not have permission to view the page.

  • Page:
    OP.030

    Error rendering macro 'excerpt-include'

    User 'null' does not have permission to view the page.

  • Page:
    OP.031

    Error rendering macro 'excerpt-include'

    User 'null' does not have permission to view the page.

  • Page:
    OP.032

    Error rendering macro 'excerpt-include'

    User 'null' does not have permission to view the page.

  • Page:
    OP.033

    Error rendering macro 'excerpt-include'

    User 'null' does not have permission to view the page.

  • Page:
    OP.034

    Error rendering macro 'excerpt-include'

    User 'null' does not have permission to view the page.

  • Page:
    OP.055 I create or update a statistical key figures
  • Page:
    OP.075 SBS-OP-DRTR-02-075 - I create R&D WBS
  • Page:
    OP.076

    Error rendering macro 'excerpt-include'

    User 'null' does not have permission to view the page.

  • Page:
    OP.077

    Error rendering macro 'excerpt-include'

    User 'null' does not have permission to view the page.

  • Page:
    OP.079

    Error rendering macro 'excerpt-include'

    User 'null' does not have permission to view the page.

  • Page:
    OP.080

    Error rendering macro 'excerpt-include'

    User 'null' does not have permission to view the page.

  • Page:
    OP.082

    Error rendering macro 'excerpt-include'

    User 'null' does not have permission to view the page.

  • Page:
    OP.102

    Error rendering macro 'excerpt-include'

    User 'null' does not have permission to view the page.

Local procedures