You are on page 1of 74

Project SPIRIT RCF_CD_CO_A1.

0
SAP_ CUSTOMIZATION DOCUMENT
Project
Name:
SPIRIT Rashtr!a Chemca"s # Fert"$ers
Doc%me&t
Name:
C%stom$ato& Doc%me&t 'or Co&tro""&( Mo)%"e
Doc%me&t
ID:
RCF_CD_CO_A1.0
*erso&:
1.0
Pre+are)
,!:
S-ara" Thte .CO Co&s%"ta&t/
Date:
101No2103
Re"ease)
,!:
S-ara" Thte .CO Co&s%"ta&t/
Date:
101No2103
Revision History
SR.
NO.
*ER
SION
NO.
DATE
OF
RE*ISI
ON
SECTION
NUM4ER
DESCRIPTION
OF C5AN6E
REASON FOR
C5AN6E
C5AN6E
MADE 47
RE*IE8ED
47
*ERSION MANA6EMENT
This document is subject to the version management. Each Configuration Matrix must be allocated an
unique version. Each released change to this document should be recorded as a new version of the
respective Configuration Matrix.
Siemens Information Systems Ltd Author: Swarali Thite
16-NO-!" #a$e 1 of %& 'ontrollin$

Project SPIRIT RCF_CD_CO_A1.0
INDE9:
CO001: Enterprise Structure Create/ Define Controlling Area......................................................4
CO002: Enterprise Structure Assign Company Coe to Controlling Area....................................!
CO00": #eneral Controlling $aintain Controlling Area...............................................................%
CO004: #eneral Controlling $aintain &um'er (anges for Controlling Documents...................)
CO00*: #eneral Controlling $aintain +ersions............................................................................12
CO00!: Cost Element Accounting Create Cost Element #roups.................................................14
CO00%: Cost Center Accounting Define Cost Center Stanar ,ierarc-y.................................1!
CO00.: Cost Center Accounting Define Cost Center Categories.................................................1.
CO00): Cost Center Accounting Create Cost Center #roups......................................................20
CO010: Cost Center Accounting Eit Automatic Account Assignment.......................................2"
CO011: /rouct Costing Define Cost Component Structure........................................................2!
CO012: /rouct Costing Define Costing +ariants.........................................................................2.
CO01": /rouct Costing Define (esults Analysis 0eys................................................................2)
CO014: /rouct Costing Define (esults Analysis +ersions..........................................................."1
CO01*: /rouct Costing Define +aluation $et-o 1Actual Costs2..............................................""
CO01!: /rouct Costing Define 3ine 4Ds 5 Assignment.............................................................."*
CO01%: /rouct Costing Define 6pate 5 /osting (ules for Settling 74/................................"%
CO01.: /rouct Costing Define +ariance 0eys.............................................................................")
CO01): Actual Costing/$aterial 3eger 8 Acti9ate +aluation Areas for $aterial 3eger...........42
CO020: Actual Costing/$aterial3eger 8 Assign Currency :ypes to $aterial 3eger type.........4"
CO021: Actual Costing/$aterial 3e.8 Assign $3 :ypes to +aluation area..................................44
CO022: Actual Costing/$3 8 $aintain &um'er (anges for $aterial 3eger Documents...........4*
CO02": Actual Costing/$aterial 3eger 8 Configure Dynamic /rice C-anges.............................4%
CO024: Actual Costing/$aterial 3eger 8 (easons for /rice C-anges...........................................4.
CO02*: Actual Costing/$3 8 $aterial 6pate 8 Define $aterial 6pate Structure.....................4)
CO02!: Act. Costing/$3 8 $at 6pate 8 Assign $at 6pate Stru to a +aluation Area................*1
CO02%: Actual Costing/$aterial 3eger 8 Actual Costing 8Acti9ate Actual Costing.....................*2
CO02.: Actual Costing/$3 8 Actual Costing 8 Acti9ate Actual Cost Component Split.................*4
CO02): /rofita'ility Analysis Structures 8 Define Operating Concern.......................................**
CO0"0: /rofita'ility Analysis 8 :ransfer of ;illing Documents.......................................................*.
Siemens Information Systems Ltd Author: Swarali Thite
16-NO-!" #a$e ( of %& 'ontrollin$

Project SPIRIT RCF_CD_CO_A1.0
CO0"1: /rofita'ility Analysis 1 Orer an /ro<ect Settlement........................................................!0
CO0"4: /rofita'ility Analysis 1 Orer an /ro<ect Settlement.......................................................!2
CO0"*: /rofit Center Accounting $aintain Controlling Area Settings.......................................!4
CO0"!: /rofit Center Accounting $aintain /rofit Center Stanar ,ierarc-y........................!!
CO0"%: /rofit Center Accounting Create Dummy /rofit Center.................................................!.
CO0".: /rofit Center Accounting $aintain Default /rofit Center..............................................%0
Siemens Information Systems Ltd Author: Swarali Thite
16-NO-!" #a$e ) of %& 'ontrollin$

Project SPIRIT RCF_CD_CO_A1.0
CO001: Enterprise Structure Create/ Define Controlling Area
Co&'(%rato& Matr:
*erso& 1.0 *a") From 01!ct"00# *a") U&t" $ext %elease
A%thor.s/ &warali Thite
CO001.1 Access Path
Enterprise &tructure 'efinition Controlling Maintain Controlling (rea
CO001.; P%r+ose
Controlling (rea is created as the highest level in the C! hierarch) to address the financial
controlling related requirements in an organi*ation. The controlling area is an organi*ational unit in
(ccounting used to subdivide the business organi*ation from a cost accounting standpoint.
CO001.< Prere=%stes
The existence of Chart of (ccounts + ,iscal -ear .ariant is a prerequisite to setting up a
Controlling area. !nl) Compan) Codes with the same Chart of (ccounts + ,iscal -ear .ariant can
be assigned to a controlling (rea.
CO001.0 De+e&)e&ces
(ll postings in the C! module are made referencing the Controlling (rea. The controlling area is
embedded in the organi*ational structure through assignment to one or more compan) codes. /n
case the controlling area is shared amongst compan) codes0 crosscompan) code cost
accounting is available for allocations + evaluations.
CO001.3 Re'ere&ces
!rgani*ation &tructure 1 C!
CO001.> Co&'(%rato&
Siemens Information Systems Ltd Author: Swarali Thite
16-NO-!" #a$e & of %& 'ontrollin$

Project SPIRIT RCF_CD_CO_A1.0
CO001.? *a")t! Crtera
&(2 %34 Enterprise
CO001.@ Reaso& 'or Dsco&t&%ato&
$ot (pplicable
Siemens Information Systems Ltd Author: Swarali Thite
16-NO-!" #a$e " of %& 'ontrollin$

Project SPIRIT RCF_CD_CO_A1.0
CO002: Enterprise Structure Assign Company Code to Controlling Area
Co&'(%rato& Matr:
*erso& 1.0 *a") From 01!ct"00# *a") U&t" $ext %elease
A%thor.s/ &warali Thite
CO00;.1 Access Path
Enterprise &tructure (ssignment Controlling (ssign compan) code to controlling area
CO00;.; P%r+ose
Compan) codes for which common cost controlling is to be carried out are assigned to the
specified controlling area.
CO00;.< Prere=%stes
5efore the assignments are made0 basic data in the controlling area i.e.0 the assignment control
indicator0 the chart of accounts0 the fiscal )ear variant0 and the currenc) settings must be
maintained.
CO00;.0 De+e&)e&ces
(ll postings made in compan) codes assigned to particular Controlling (rea result in Controlling
documents getting created in the same thus setting the platform for crosscompan) code cost
accounting.
CO00;.3 Re'ere&ces
!rgani*ation &tructure 1 C!
CO00;.> Co&'(%rato&
CO00;.? *a")t! Crtera
&(2 %34 Enterprise
CO00;.@ Reaso& 'or Dsco&t&%ato&
Siemens Information Systems Ltd Author: Swarali Thite
16-NO-!" #a$e 6 of %& 'ontrollin$

Project SPIRIT RCF_CD_CO_A1.0
$ot (pplicable
Siemens Information Systems Ltd Author: Swarali Thite
16-NO-!" #a$e % of %& 'ontrollin$

Project SPIRIT RCF_CD_CO_A1.0
CO003: eneral Controlling !aintain Controlling Area
Co&'(%rato& Matr:
*erso& 1.0 *a") From 01!ct"00# *a") U&t" $ext %elease
A%thor.s/ &warali Thite
CO00<.1 Access Path
Controlling 6eneral Controlling !rgani*ation Maintain Controlling (rea
CO00<.; P%r+ose
7aving set up the basic contours of Controlling (rea settings with Currenc)0 Chart of (ccounts and
,iscal -ear .ariant0 the components that ma8e the controlling area are activated in here. ,or
instance in the case of %C,0 Cost Center0 /nternal !rder0 2rofitabilit) (nal)sis + 2rofit Center
components are made active.
CO00<.< Prere=%stes
The deciding factor for basic data characteristics is the organi*ation of cost accounting0 meaning
the assignment of compan) code9s: to a controlling area. /f the master data is alread) created0 the
alread) assigned Compan) Codes cannot be removed. 7owever0 more Compan) Codes can be
assigned to the Controlling (rea.
CO00<.0 De+e&)e&ces
This step in goes a step further in deciding the details involved in maintaining the Controlling (rea.
!ne will get to use the functionalit) of the man) sub modules that form a part of the Controlling
(rea will be decided b) the fact that the components mentioned are made active in here.
CO00<.3 Re'ere&ces
!rgani*ation &tructure 1 C!
CO00<.> Co&'(%rato&
Siemens Information Systems Ltd Author: Swarali Thite
16-NO-!" #a$e * of %& 'ontrollin$

Project SPIRIT RCF_CD_CO_A1.0
CO00<.? *a")t! Crtera
&(2 %34 Enterprise
CO00<.@ Reaso& 'or Dsco&t&%ato&
$ot (pplicable
Siemens Information Systems Ltd Author: Swarali Thite
16-NO-!" #a$e + of %& 'ontrollin$

Project SPIRIT RCF_CD_CO_A1.0
CO00": eneral Controlling !aintain #um$er %anges for Controlling Documents
Co&'(%rato& Matr:
*erso& 1.0 *a") From 01!ct"00# *a") U&t" $ext %elease
A%thor.s/ &warali Thite
CO000.1 Access Path
Controlling 6eneral Controlling !rgani*ation Maintain $umber %anges for Controlling
'ocuments
CO000.; P%r+ose
Ever) posting in C! generates a numbered document thus giving it a unique identit). Each
transaction t)pe present in the various components of Controlling (rea is assigned to number
ranges. /n C!0 there are no legal requirements for a continuous assignment of document
numbers.
CO000.< Prere=%stes
/dentification of different transaction t)pes and their assignment to number ranges will be a
prerequisite for this activit). !ne can ensure a clear differentiation between different t)pes of
transactions. ,or instance planning + actual transactions can be separated b) their assignment to
separate number ranges.
CO000.0 De+e&)e&ces
Each posting made through various components of the Controlling (rea generates a unique
document number. The document number thus generated can be identified with the different
transaction t)pes aligned to the Controlling (rea components.
CO000.3 Re'ere&ces
!rgani*ation &tructure 1 C!
CO000.> Co&'(%rato&

Prmar! Post&(s
C!/$ C! Throughpostings from ,/
;(<! 'own pa)ment
1000000000 1========= 1000000>==
P"a&&&( Tra&sacto&s
,/2( 2a)ment scheduling
;(<2 2lan cost center accrual
;!(2 2lan settlement
;2/. (ctual cost distrib. cost object
;225 &tandard cost estimate
;&// (ctual price calculation
;&20 2lan split costs
;&25 2lan assessment to C!2(
;<22 2lan overhead 9periodic:
;<%2 /nterest Calculation 92lan:
2(2? 2rofit 2lanning
%;21 2lanning primar) costs
%;2" 2lanning activities
%;24 2lanning secondar) costs
Siemens Information Systems Ltd Author: Swarali Thite
16-NO-!" #a$e 1! of %& 'ontrollin$

Project SPIRIT RCF_CD_CO_A1.0
%;2> 2lanning stat. 8e) figures
%;2# 2lan %evenue T)pes
%;2@ 2lanning activit)dep. costs
%;2A 2lanning act.dep. sec. costs
%;2B 2lanning order costs
%;2= 2lan. actdep. settlement costs
%;25 2eriodic %eposting1 2lan 'ata
%;2? 2lan indirect activit) alloc.
%;2C Manual cost planning
%;2& &ec. planning with template
%;2D 2lan overhead cost assessment
%;2. 2lan overhead cost distrib.
%;2E &econdar) order cost planning
%;2F (t)dep. sec. order cost plan.
%;2< 2lanning overhead credits
%;D1 %epost costs
%;D" %epost revenue
%;D4 %epost C! line items
"000000000 "========= "0000000==
Assessme&tA Dstr,%to&A Or)er Sett"eme&t I&ter&a"
;(M. Manual cost allocation
;(</ (ctual cost center accrual
;62' 'istribution acc. to peg
;;;2 Control Costs 92rimar):
;;;& Control Costs 9&econdar):
;!(! (ctual settlement
;&/0 (ctual cost center split
;&!2 2rim. Target Cost Calculation
;<2/ (ctual overhead 9periodic:
;<%/ /nterest calculation 9actual:
%;/5 (ctual 2eriodic %epostings
%;/? (ctual inverse activit) alloc.
%;/D (ctual !verhead (ssessment
%;/. (ctual !verhead 'istribution
%;? (ctual activit) allocation
%;?T (ctual template allocation
%;$ (ctual nonalloc. activities
%%/5 &eg. adjust.1 (ct.per.repost.
%%/D &egment adjust.1 (ct. (ssess.
%%/. &egment adjust.1 (ct. distrib.
4000000000 4========= 0000000000
Prmar! Post&(s
;(56 (utomat. E/23results anal)sis
;(5M Manual E/23results anal)sis
;(,M 2a)ment data
;(D& Calculate &crap
;E;5 Dnit costing
;E;< Dnit costing 9overhead:
;,2/ Transfer price allocation
;,22 Transfer price agreement
;22< &tandard costing 9overhead:
Siemens Information Systems Ltd Author: Swarali Thite
16-NO-!" #a$e 11 of %& 'ontrollin$

Project SPIRIT RCF_CD_CO_A1.0
;&!& &ec. Target Cost Calculation
;&2( (ssessment to C!2(
;&E2 2rim. Target Cost Calc. 9E/2:
;&E& &ec. Target Cost Calc. 9E/2:
;.(% .ariance calculation
%;?F 2redistribution of fixed costs
%;& Enter statistical 8e) figures
>000000000 >========= 0000000000
CO000.? *a")t! Crtera
&(2 %34 Enterprise
CO000.@ Reaso& 'or Dsco&t&%ato&
$ot (pplicable
Siemens Information Systems Ltd Author: Swarali Thite
16-NO-!" #a$e 1( of %& 'ontrollin$

Project SPIRIT RCF_CD_CO_A1.0
CO00&: eneral Controlling !aintain 'ersions
Co&'(%rato& Matr:
*erso& 1.0 *a") From 01!ct"00# *a") U&t" $ext %elease
A%thor.s/ &warali Thite
CO003.1 Access Path
Controlling 6eneral Controlling !rgani*ation Maintain .ersions
CO003.; P%r+ose
/n planning0 versions displa) alternative plan scenarios based on different planning assumptions.
,or example0 one can illustrate var)ing emplo)ment mar8ets0 price and wage increases0 or sales
programs in different versions with differing parameters. /n the &(2 s)stem one can have 2lan3
(ctual versions depicting (ctual0 !ptimistic or 2essimistic scenarios.
CO003.< Prere=%stes
Controlling area settings in the customi*ing for the Cost Center (ccounting0 !verhead !rders0 and
other components need to be carries out in order to go ahead with creating versions.
CO003.0 De+e&)e&ces
(ll Controlling transactions get posted to the relevant components referencing the version. !ne
can have a separate set of transactional data for each version defined for reporting3 M/&
purposes.
CO003.3 Re'ere&ces
CO_0;_01:1 Cost Center 0 Cost Element 2lanning and Dpdation
CO003.> Co&'(%rato&
Siemens Information Systems Ltd Author: Swarali Thite
16-NO-!" #a$e 1) of %& 'ontrollin$

Project SPIRIT RCF_CD_CO_A1.0
CO003.? *a")t! Crtera
&(2 %34 Enterprise
CO003.@ Reaso& 'or Dsco&t&%ato&
$ot (pplicable
Siemens Information Systems Ltd Author: Swarali Thite
16-NO-!" #a$e 1& of %& 'ontrollin$

Project SPIRIT RCF_CD_CO_A1.0
CO00(: Cost Element Accounting Create Cost Element roups
Co&'(%rato& Matr:
*erso& 1.0 *a") From 01!ct"00# *a") U&t" $ext %elease
A%thor.s/ &warali Thite
CO00>.1 Access Path
Controlling Cost Element (ccounting Master 'ata Cost Elements Create Cost
Elements 6roups
CO00>.; P%r+ose
&imilar cost elements can be combined into cost element groups. &imilar cost element groups can
be combined to form other cost element groups so as to build a cost element hierarch). The cost
element groups can be used1
/n the informational reports as grouping cost elements together in the report can create
totals for each node. The row structure of the cost element report is determined b) the
cost element structure.
Ehen processing of several cost elements in one transaction0 li8e Cost center planning0
(ssessment or 'istribution.
%eport totaling ta8es place via cost element group nodes. To achieve a clear illustration0
each node on a level must have the same number of subordinate levels.
CO00>.< Prere=%stes
To be able to create a cost element grouping0 the chart of accounts must be maintained for the
compan) code in question. (lso0 the 2rofit + ?oss 63? (ccounts need to be well identified and be
created as cost elements wherever required.
(lso0 /n the 6eneral Controlling section of the /M6 under the Enterprise &tructure the Controlling
(rea is maintained.

CO00>.0 De+e&)e&ces
Cost Element 6roups can be used in a variet) of transactions and eliminate the need to select the
required cost elements at all places. Cost Elements can be grouped together functionall) and
otherwise. (lternate Cost Elements groups can be created with cost elements present alread) in
other groups.
CO00>.3 Re'ere&ces
CO_01_01:1 Cost Element
CO00>.> Co&'(%rato&
CE 6ro%+ Descr+to&
('M/$EF2 (dministrative !verheads
(?? (ll Cost Elements G%C,
(&&E,(CEF2 ,actor) Expenses
C!$2!EE% C!MM!$ 2!EE%,(CT!%-
C!$&ET2 C!$&DM2T/!$ !, /TEM& ,!% ET2
C!$&DMT/!$ C!$&DM2T/!$ (CC!D$T&
C!2?($ C!&T E?EME$T& ,!% C! 2?($
'E2%E5?'6 'E2%EC/(T/!$ C!MM!$ 5D/?'/$6&
'E2%EH2 'epreciation for Hoint 2roduct
'E2%E2?M7 'E2%EC/(T/!$ ,!% C!MM!$ 2?($T + M(C7
'E2%E$ 'epreciation
Siemens Information Systems Ltd Author: Swarali Thite
16-NO-!" #a$e 1" of %& 'ontrollin$

Project SPIRIT RCF_CD_CO_A1.0
'/%!2E%?(5 'irect operating ?abour
EF2E$&E& (ll Expenses Cost Elements
,(CT!7H2 ,actor) !verheads for Hoint 2roduct C&T
,(CT!%-EF2 ,actor) Expenses
/$&D%($CE /$&D%($CE
/$TE%E&T /nterest
M(/$&E%. &ervices for Maintenance
M(/$TEF2 Maintenance Expenses
M;T6&(? M(%;ET/$6 &(?(%/E&
M;T6T!T&(? M(%;ET/$6 2%/M(%- + &EC!$'(%- &(?(%-
2?($T'E2 2?($T 9'/%ECT I M(/$T: 'E2
2%ECC7EMC(2recious Metal Chemicals + Catal)st
%E2M(/$ %epaires and MaintenanceMaterial
%E.E$DE(C %E.E$DE (CC!D$T& C(T 11
&(?E(6E& &(?(%/E& ($' E(6E&
T?'E2%E 'epreciation for Hoint 2roduct
T?,(CTEF2& T7(? ,actor) Expenses
EE?,(%EEF2 Eelfare Expenses
EE?,!7H2 Eelfare Expenses Hoint 2roducts
CO00>.? *a")t! Crtera
&(2 %34 Enterprise
CO00>.@ Reaso& 'or Dsco&t&%ato&
$ot (pplicable
Siemens Information Systems Ltd Author: Swarali Thite
16-NO-!" #a$e 16 of %& 'ontrollin$

Project SPIRIT RCF_CD_CO_A1.0
CO00): Cost Center Accounting Define Cost Center Standard *ierarc+y
Co&'(%rato& Matr:
*erso& 1.0 *a") From 01!ct"00# *a") U&t" $ext %elease
A%thor.s/ &warali Thite
CO00?.1 Access Path
Controlling Cost Center (ccounting Master 'ata Cost Centers 'efine &tandard
7ierarch)
CO00?.; P%r+ose
To create cost center0 a structure in master data maintenance is required to which cost centers
can assigned. This C! structure0 the standard hierarch)0 is created when maintaining a controlling
area. /f this hierarch) is not present during controlling area maintenance0 the %34 &)stem
automaticall) creates the highest node there.
CO00?.< Prere=%stes
The Controlling (rea is to be created as the highest level in the C! hierarch). This organi*ation
structure is created with minimal basic data that includes controlling area currenc)0 a fiscal )ear
variant and chart of accounts.
CO00?.0 De+e&)e&ces
To create cost centers0 a structure in master data maintenance is required to which cost centers
can be assigned. The standard hierarch) is an indicated hierarch) of cost center groups in which
all cost centers in a controlling area are gathered together. (ll cost centers created in the
controlling area will fall under the standard hierarch)0 which is the highest node.
CO00?.3 Re'ere&ces
CO_01_0;:1 Cost Center
CO00?.> Co&'(%rato&
Siemens Information Systems Ltd Author: Swarali Thite
16-NO-!" #a$e 1% of %& 'ontrollin$

Project SPIRIT RCF_CD_CO_A1.0
CO00?.? *a")t! Crtera
&(2 %34 Enterprise
CO00?.@ Reaso& 'or Dsco&t&%ato&
$ot (pplicable
Siemens Information Systems Ltd Author: Swarali Thite
16-NO-!" #a$e 1* of %& 'ontrollin$

Project SPIRIT RCF_CD_CO_A1.0
CO00,: Cost Center Accounting Define Cost Center Categories
Co&'(%rato& Matr:
*erso& 1.0 *a") From 01!ct"00# *a") U&t" $ext %elease
A%thor.s/ &warali Thite
CO00@.1 Access Path
Controlling Cost Center (ccounting Master 'ata Cost Centers 'efine Cost Center
Categories
CO00@.; P%r+ose
Cost Center Categories are created to add functional characteristics to a cost center master. The
master data of an activit) t)pe includes one or more cost center categories. The activit) t)pe ma)
be used onl) b) cost centers of the appropriate categories. ,or each categor)0 default values for
the J?oc8J and J%ecord quantit)J indicators can be defined0 for transfer to the cost center master
data.
CO00@.< Prere=%stes
The Controlling (rea is to be created as the highest level in the C! hierarch). This structure would
include a full) setup controlling area including a cost center standard hierarch) and required
components dul) activated.
CO00@.0 De+e&)e&ces
The following indicators are activated3 deactivated for each cost center categor) as mentioned
below1
?oc8 primar) postings
?oc8 secondar) postings
?oc8 revenue postings and revenue planning
?oc8 primar) cost planning
?oc8 secondar) cost planning
?oc8 consumption quantities
The s)stem defaults this indicator when the cost center master data is created. The Cost center
categor) field is also used in activit) t)pe planning. (3so0 in the activit) t)pe master record the cost
center categor) is entered for which the activit) t)pe can be planned. (n JKJ can be entered if the
activit) t)pe is allowed for all cost center categories.
CO00@.3 Re'ere&ces
C!G01G0" 1 Cost Center
CO00@.> Co&'(%rato&
Siemens Information Systems Ltd Author: Swarali Thite
16-NO-!" #a$e 1+ of %& 'ontrollin$

Project SPIRIT RCF_CD_CO_A1.0
CO00@.? *a")t! Crtera
&(2 %34 Enterprise
CO00@.@ Reaso& 'or Dsco&t&%ato&
$ot (pplicable
Siemens Information Systems Ltd Author: Swarali Thite
16-NO-!" #a$e (! of %& 'ontrollin$

Project SPIRIT RCF_CD_CO_A1.0
CO00-: Cost Center Accounting Create Cost Center roups
Co&'(%rato& Matr:
*erso& 1.0 *a") From 01!ct"00# *a") U&t" $ext %elease
A%thor.s/ &warali Thite
CO00B.1 Access Path
Controlling Cost Center (ccounting Master 'ata Cost Centers 'efine Cost Center
6roups
CO00B.; P%r+ose
Cost center hierarchies summari*e the decisionma8ing0 responsibilit)0 and control areas
according to the userLs requirements. /ndividual cost centers are the lowest hierarchical level. This
ensures that at least onegroup holds all cost centers0 and thereb) represents the entire
organi*ation. Moreover0 alternative groups can be created which can be divided according to
structural and3or functional standpoints.
CO00B.< Prere=%stes
The Controlling (rea is to be created as the highest level in the C! hierarch). This structure would
include a full) setup controlling area including a cost center standard hierarch) and required
components dul) activated.
CO00B.0 De+e&)e&ces
6rouped cost centers can be utili*ed in carr)ing out transactions and other informational data with
ease. These groups can be created functionall) or otherwise and eliminate the need to select
individual cost centers required for transactional input.
CO00B.3 Re'ere&ces
CO_01_0> :1 !verhead group code
CO00B.> Co&'(%rato&
('M$/$&D ('M/$/&T%(T/!$ /$&D%($CE
(7M$(%E(CC(7ME'$(6(% (%E( C!&T CE$TE% 6%!D2
(;!(%E(CC (;!?( (%E( C!&T CE$TE% 6%!D2
(MM!$/(/3. (MM!$/( / ($' (MM!$/( .
(2(%E(CC (2 (%E( C!&T CE$TE%
(%E(6%!D2 (%E( 6%!D2 ,!% &(?(%/E&
(D%(%E(CC (D%($6(5(' (%E( C!&T CE$TE% 6%!D2
57%(%E(CC 5/7(% (%E( C!&T CE$TE% 6%!D2
C6(%E(CC C7(TT/&6(%7 (%E( C!&T CE$TE% 6%!D2
C!M(&&ET 'E2%EC/(T/!$ C!MM!$ 2+M
C!MM2!EE% C!MM!$ 2!EE% ,(CT!%-
C!MME(TE%C!MM!$ E(TE% ,(CT!%-
C!MM!$CC Common Cost Center
C!MM%E2,( C!MM!$ ,(CT!%- %E2(/%&
C!M%E2,(T7 Common repaires factor) Thal
C!%26%!D2 C!%2!%(TE ,E%T M%;T C!&T CE$TE%
C!%2!%(TE Corporate
'(2M(27$'? %EC/.E% ,!% /$T?. 7($'?/$6 !, %!C;27!&
'M(CC!M&(?'(MC C!MM!$ &(?(%-
'M,C!M&(? 'M, C!MM!$ &(?(%-
Siemens Information Systems Ltd Author: Swarali Thite
16-NO-!" #a$e (1 of %& 'ontrollin$

Project SPIRIT RCF_CD_CO_A1.0
,(C!M&(? ,!%M/C (C/' C!MM!$ &(?(%-
,(CT/$&D ,(CT!%- C!MM!$ /$&D%($CE
,(CT2!EE% C!MM!$ ,(CT!%- 2!EE%
,(CTE(TE% ,(CT!%- C!MM!$ E(TE%
,E%T/?/<E% Mar8eting ,ertili*er
6!%;(%E(CC6!%(;72D% (%E( C!&T CE$TE% 6%!D2
6DH(%E(CC 6DH(%(T (%E( C!&T CE$TE% 6%!D2
72(%E(CC 7/M(C7(? 2%('E&7 (%E( C!&T CE$TE% 6%!D2
7%(%E(CC 7(%-($( (%E( C!&T CE$TE% 6%!D2
/2' Mar8eting /ndustrial 2roduct
H(?(%E(CC H(?6(!$ (%E( C!&T CE$TE% 6%!D2
H7((%E(CC H7(%;7($' (%E( C!&T CE$TE% 6%!D2
;$(%E(CC ;(%$(T(;( (%E( C!&T CE$TE% 6%!D2
;!?7(%E(CC ;!?7(2D% (%E( C!&T CE$TE% 6%!D2
;!$(%E(CC ;!$;($ (%E( C!&T CE$TE% 6%!D2
?DC;(%E(CC ?DC;$!E (%E( C!&T CE$TE% 6%!D2
MEE%(%E(CCMEE%DT (%E( C!&T CE$TE% 6%!D2
MET7-?(M/$ Meth)lamines Cost Center
M2(%E(CC M('7-( 2%('E&7 (%E( C!&T CE$TE% 6%!D2
$(6(%E(CC $(62D% (%E( C!&T CE$TE% 6%!D2
$(&;(%E(CC $(&/; (%E( C!&T CE$TE% 6%!D2
2$(%E(CC 2D$H(5 (%E( C!&T CE$TE% 6%!D2
2%!'CC 2roduction cost center
2D$E(%E(CC 2D$E (%E( C!&T CE$TE% 6%!D2
2D$E%E6CC 2D$E %E6/!$(? !,,/CE C!&T CE$TE% 6%!D2
%C,
%!C;7$'? %EC/.E% ,!% /$T?. 7($'?/$6 !, %!C;27!&
&$$2H2 H!/$T 2%!'DCT& ,!%&!'/DM $/T%(TE3$/T%/TE
&D27(?(($2 &D27(?( ($' ($2 C!&T CE$TE%
T7(? Thal 9Manufacturing Dnit:
T7(?(MMEFT Thal (mmonia Extension
T7(?C!MMCCT7(? C!MM!$ C!&T CE$TE%
T7(?2%!'CC T7(? 2%!'DCT/!$ C!&T CE$TE%
T72?(CTCC T7(? C!&T CE$TE% ,!% 2?($$/$6
T?,(CT'E2 T7(? C!MM!$ ,(CT!%- 'E2%EC/(T/!$
T?M(2$EE T7(? M(2 $EE
T?M(2!?' T7(? M(2 !?'
T?T!E$'E2 T7(? T!E$&7/2 'E2%EC/(T/!$
T?T!E$%E2 T7(? T!E$&7/2 %E2(/%E&
T?D%E(H2 T7(? D%E( H!/$T 2%!'DCT&
T$(%E(CC T(M/?$('D (%E( C!&T CE$TE% 6%!D2
T!E$/$&D T!E$&7/2 C!MM!$ /$&D%($CE
T!E$%E2 %E2(/%& T! T!E$&7/2 (&&ET&
T!E$E(TE% T!E$&7/2 C!MM!$ E(TE%
T%(CT2%/CE Tromba) cost centerfor (ctivit) 2lanning
T%($&'E2 'E%2EC/(T/!$ !$ T%($&2!%T?!C!M!T/.E&
T%!M5(- Tromba) 9Manufacturing Dnit:
D2(%E(CC D2 (%E( C!&T CE$TE%
D%E(H2 D%E( H!/$T 2%!'DCT
DT%(%E(CC DTT(%($C7(? (%E( C!&T CE$TE% 6%!D2
.(%(%E(CC .(%($(&/ (%E( C!&T CE$TE% 6%!D2
E5(%E(CC EE&T 5E$6(? (%E( C!&T CE$TE% 6%!D2
EE&T<!$ECCEE&T <!$E C!&T CE$TE% 6%!D2
Siemens Information Systems Ltd Author: Swarali Thite
16-NO-!" #a$e (( of %& 'ontrollin$

Project SPIRIT RCF_CD_CO_A1.0
CO00B.? *a")t! Crtera
&(2 %34 %elease
CO00B.@ Reaso& 'or Dsco&t&%ato&
$ot (pplicable
Siemens Information Systems Ltd Author: Swarali Thite
16-NO-!" #a$e () of %& 'ontrollin$

Project SPIRIT RCF_CD_CO_A1.0
CO010: Cost Center Accounting Edit Automatic Account Assignment
Co&'(%rato& Matr:
*erso& 1.0 *a") From 01!ct"00# *a") U&t" $ext %elease
A%thor.s/ &warali Thite
CO010.1 Access Path
Controlling Cost Center (ccounting (ctual 2ostings Manual (ctual 2ostings Edit
(utomatic (ccount (ssignment
CO010.; P%r+ose
(utomatic assignment occurs during postings in external accounting 9within the ,/0 MM0 or &'
components: if a C! account assignment object is not entered 9cost center0 order0 or project: for a
cost accounting relevant posting. Examples of (utomaticall) Created /tems1
'iscounts0 exchange rate differences0 and ban8ing fees in ,/
2rice differences and minor differences in MM
2ossible automatic additional account assignments include1
Cost center
!rder
2rofit center 9for revenue postings:
CO010.< Prere=%stes
The following activities must be completed to set up automatic assignment of cost centers1
(ctivate Cost Center (ccounting in Controlling (rea
Maintain Cost Elements 9for automatic assignments:
Create Cost Centers
/n addition to cost centers0 additional objects 9such as orders0 profit centers0 valuation areas or
business area: must be created for use in automatic account assignment.
CO010.0 De+e&)e&ces
The s)stem finds a default cost object based on account assignment rules enlisted below1
1 .aluation area is mandator)
" 5usiness area is mandator)
4 2rofit center is mandator)
(ccount assignment follows these rules1
/f the customi*ing step is used for definition per compan) code0 account0 and business
area or valuation area0 the s)stem does not find an assignment since neither business nor
valuation area are 8nown.
/f the customi*ing step is used to save an automatic assignment per compan) code and
account0 this becomes the default.
/f the automatic assignment is not saved in the customi*ing0 the default is ta8en from the
cost element master data record.
7owever0 the cost object value input during document entr) ta8es priorit) over all settings.
CO010.3 Re'ere&ces
C!G01G011 Cost Element
CO010.> Co&'(%rato&
Siemens Information Systems Ltd Author: Swarali Thite
16-NO-!" #a$e (& of %& 'ontrollin$

Project SPIRIT RCF_CD_CO_A1.0
CO010.? *a")t! Crtera
&(2 %34 %elease
CO010.@ Reaso& 'or Dsco&t&%ato&
$ot (pplicable
Siemens Information Systems Ltd Author: Swarali Thite
16-NO-!" #a$e (" of %& 'ontrollin$

Project SPIRIT RCF_CD_CO_A1.0
Siemens Information Systems Ltd Author: Swarali Thite
16-NO-!" #a$e (6 of %& 'ontrollin$

Project SPIRIT RCF_CD_CO_A1.0
CO011: .roduct Costing Define Cost Component Structure
Co&'(%rato& Matr:
*erso& 1.0 *a") From 01!ct"00# *a") U&t" $ext %elease
A%thor.s/ &warali Thite
CO011.1 Access Path
Controlling 2roduct Cost Controlling 2roduct Cost 2lanning 5asic &ettings ,or Material
Costing 'efine Cost Component &tructure
CO011.; P%r+ose
( control of how the results of activit) price calculation or material costing are stored. The cost component
structure groups cost elements into cost components to show the following information1
(ctivit) prices for an activit) t)pe
Cost of a process
2lanned cost of a product
/n 2roduct Cost Controlling 9C!2C:0 the cost component structure determines the attributes for passing on
the following costs1
Material costs passed on to material valuation as the standard price or inventor) price
Cost of goods manufactured passed on to 2rofitabilit) (nal)sis
CO011.< Prere=%stes
(ll the organi*ational structures must be maintained before creating cost component structure as
the same cannot exist in isolation.
CO011.0 De+e&)e&ces
Ehen defining the cost components0 it must be specified whether the cost component pla)s a role in the
creation of the different prices that are transferred into the material master record. The following options
could be considered1
&tandard price
Costs that are flagged as relevant for stoc8 valuation form part of the standard price if the results of
the standard cost estimate are mar8ed and released. These costs also serve as a basis for the
following1
1. The calculation of target costs in variance calculation
". The valuation of scrap in variance calculation
4. The valuation of wor8 in process for the confirmed )ield for the operation 9orderrelated
production0 process manufacturing: or at the reporting point 9repetitive manufacturing:
Commercial price
Costs that are flagged as relevant for inventor) valuation for the purposes of commercial law form
part of the commercial price. This price is calculated in an inventor) cost estimate and can be
written to the material master record.
Tax price
Costs that are flagged as relevant for inventor) valuation for the purposes of tax law form part of the
tax price. This price is calculated in an inventor) cost estimate and written to the material master
record.
Transfer price surcharge 9optional:
This categor) allows )ou to group together several cost components of a cost component structure.
'ifferences between the transfer prices 9delta profit:
/f )ou use the functions of multiple valuations ingroup costing0 )ou can specif) that costs that arise
from suppl) relationships with other compan) codes and profit centers are updated under the cost
component. -ou can specif) this for one cost component for each cost component structure.
Siemens Information Systems Ltd Author: Swarali Thite
16-NO-!" #a$e (% of %& 'ontrollin$

Project SPIRIT RCF_CD_CO_A1.0
CO011.3 Re'ere&ces
C!G04G0":1 &tandard Cost Estimate
CO011.> Co&'(%rato&
(ttached is a file containing details of the cost component structure designed for %C,.
Cost component
structure.xls
CO011.? *a")t! Crtera
&(2 %34 %elease
CO011.@ Reaso& 'or Dsco&t&%ato&
$ot (pplicable
Siemens Information Systems Ltd Author: Swarali Thite
16-NO-!" #a$e (* of %& 'ontrollin$

Project SPIRIT RCF_CD_CO_A1.0
CO012: .roduct Costing Define Costing 'ariants
Co&'(%rato& Matr:
*erso& 1.0 *a") From 01!ct"00# *a") U&t" $ext %elease
A%thor.s/ &warali Thite
CO01;.1 Access Path
Controlling 2roduct Cost Controlling 2roduct Cost 2lanning Material Cost Estimate Eith
Cuantit) &tructure 'efine Costing .ariants
CO01;.; P%r+ose
Costing variants form the lin8 between the application and Customi*ing0 since all cost estimates
are carried out and saved with reference to a costing variant.
CO01;.< Prere=%stes
Creating a costing variant depends on the control parameters li8e Costing T)pe0 .aluation .ariant0
'ate Control. Cuantit) &tructure Control and Transfer Control among others which need to be
defined before hand.
CO01;.0 De+e&)e&ces
The costing variant contains all the control parameters for costing. The costing variant for a
material cost estimate contains the following control parameters1
Costing t)pe
.aluation variant
'ate control
Cuantit) structure control 9!nl) relevant for cost estimates with quantit) structure:
Transfer control 9optional:
%eference variant 9optional:
CO01;.3 Re'ere&ces
C!G04G0":1 &tandard Cost Estimate
CO01;.> Co&'(%rato&
(ttached is file containing detailed specifications on valuation variants available.
"Costing
Variants.xls"

CO01;.? *a")t! Crtera
&(2 %34 %elease
CO01;.@ Reaso& 'or Dsco&t&%ato&
$ot (pplicable
Siemens Information Systems Ltd Author: Swarali Thite
16-NO-!" #a$e (+ of %& 'ontrollin$

Project SPIRIT RCF_CD_CO_A1.0
CO013: .roduct Costing Define %esults Analysis /eys
Co&'(%rato& Matr:
*erso& 1.0 *a") From 01!ct"00# *a") U&t" $ext %elease
A%thor.s/ &warali Thite
CO01<.1 Access Path
Controlling 2roduct Cost Controlling Cost !bject Controlling 2roduct Cost 5) 2eriod
2eriod End Closing Eor8 /n 2rocess 'etermine %esults (nal)sis ;e)s
CO01<.; P%r+ose
( 8e) specif)ing that the object is to be selected during results anal)sis or when wor8 in process is
calculated. ( number of valuation control parameters are lin8ed to this 8e).
Ehether results anal)sis is revenuebased0 quantit)based or manual
!n which basis 9planned or actual data: results anal)sis is carried out
7ow profits are reali*ed
Ehether the inventor)0 reserves and cost of sales are to be split
CO01<.< Prere=%stes
Each order for which wor8 in process is to be ascertained 9E/2: must receive a results anal)sis
8e). The presence of a results anal)sis 8e) in the order means that the order is included in E/2
calculation during periodend closing.
CO01<.0 De+e&)e&ces
E/2 calculation determines the value of the unfinished products in the 2roduct Cost b) 2eriod
component and in the 2roduct Cost b) !rder component. E/2 calculation in 2roduct Cost b)
!rder or 2eriod is used chiefl) in ma8etostoc8 production0 salesorderrelated production with a
valuated sales order stoc80 and engineertoorder environments with a valuated project stoc8.
CO01<.3 Re'ere&ces
C!G04G0":1 &tandard Cost Estimate
CO01<.> Co&'(%rato&
Siemens Information Systems Ltd Author: Swarali Thite
16-NO-!" #a$e )! of %& 'ontrollin$

Project SPIRIT RCF_CD_CO_A1.0
CO01<.? *a")t! Crtera
&(2 %34 %elease
CO01<.@ Reaso& 'or Dsco&t&%ato&
$ot (pplicable
Siemens Information Systems Ltd Author: Swarali Thite
16-NO-!" #a$e )1 of %& 'ontrollin$

Project SPIRIT RCF_CD_CO_A1.0
CO01": .roduct Costing Define %esults Analysis 'ersions
Co&'(%rato& Matr:
*erso& 1.0 *a") From 01!ct"00# *a") U&t" $ext %elease
A%thor.s/ &warali Thite
CO010.1 Access Path
Controlling 2roduct Cost Controlling Cost !bject Controlling 2roduct Cost 5) 2eriod
2eriod End Closing Eor8 /n 2rocess 'etermine %esults (nal)sis .ersions
CO010.; P%r+ose
( version that enables multiple valuations of the same object 9such as a sales order item: in
results anal)sis and in the calculation of wor8 in process.
Example
,or balance sheet purposes0 the object is valuated using a method that determines the
value of the unfinished products on the basis of the actual cost incurred to date.
,or internal anal)sis purposes0 the value of the unfinished products is determined using a
method that includes unreali*ed profits.
CO010.< Prere=%stes
The following process must be completed1
/mplementation of Controlling 6eneral
/mplementation of Cost Center (ccounting
/mplementation of Cost and %evenue Element (ccounting
/mplementation of 2roduct Cost Controlling 9'efine %esults (nal)sis ;e)s:
CO010.0 De+e&)e&ces
(ll results anal)sis data 9wor8 in process in the 2roduct Cost b) 2eriod component0 and wor8 in
process or reserves for unreali*ed costs in the 2roduct Cost b) !rder component: calculated in
results anal)sis is updated on the order with reference to the results anal)sis version. This
enables the calculation of wor8 in process on the basis of multiple results anal)sis versions
simultaneousl).
CO010.3 Re'ere&ces
C!G04G0":1 &tandard Cost Estimate
CO010.> Co&'(%rato&
Siemens Information Systems Ltd Author: Swarali Thite
16-NO-!" #a$e )( of %& 'ontrollin$

Project SPIRIT RCF_CD_CO_A1.0
CO010.? *a")t! Crtera
&(2 %34 %elease
CO010.@ Reaso& 'or Dsco&t&%ato&
$ot (pplicable
Siemens Information Systems Ltd Author: Swarali Thite
16-NO-!" #a$e )) of %& 'ontrollin$

Project SPIRIT RCF_CD_CO_A1.0
CO01&: .roduct Costing Define 'aluation !et+od 0Actual Costs1
Co&'(%rato& Matr:
*erso& 1.0 *a") From 01!ct"00# *a") U&t" $ext %elease
A%thor.s/ &warali Thite
CO013.1 Access Path
Controlling 2roduct Cost Controlling Cost !bject Controlling 2roduct Cost 5) 2eriod
2eriod End Closing Eor8 /n 2rocess 'efine .aluation Methods 9(ctual Costs:
CO013.; P%r+ose
The following status codes are relevant for E/2 calculation in this component1
2%E? 9The order is partiall) released.:
%E? 9The order is released.:
'?. 9The order has been completel) delivered.:
TEC! 9The order is technicall) completed.:
/f the status is 2%E? or %E?0 the s)stem creates wor8 in process in the amount of the actual costs
with which the order is debited. /f the status is '?. or TEC!0 the s)stem cancels the wor8 in
process. The difference between the debit through actual costs postings and the actual credit of
the order from goods receipts is interpreted as a variance with this status.
CO013.< Prere=%stes
The following steps must have alread) been processed before configuring this node1
'efine results anal)sis 8e)s
'efine results anal)sis versions
Chec8 control data for repetitive manufacturing profiles
CO013.0 De+e&)e&ces
/f wor8 in process is to be calculated at actual costs calculate0 create a valuation method for each
combination of controlling area0 results anal)sis version0 and results anal)sis 8e) for the statuses that are
relevant to E/2 calculation. /f the wor8 in process is valuated at actual costs0 it must be made sure that the
wor8 in process that is created and settled in a period can be cancelled at a later time. 'efining valuation
methods for the cancellation does this.
,or the status 2%E?0 enter status number J1J. The s)stem generates a valuation method of results
anal)sis t)pe , 9calculate wor8 in process:.
,or the status %E?0 enter status number J"J. The s)stem generates a valuation method of results
anal)sis t)pe , 9calculate wor8 in process:.
,or the status '?.0 enter status number J4J. The s)stem generates a valuation method of results
anal)sis t)pe < 9cancel data of E/2 calculation and results anal)sis:.
,or the status TEC!0 enter the status number J>J. The s)stem generates a valuation method of
results anal)sis t)pe < 9cancel data of E/2 calculation and results anal)sis:.
CO013.3 Re'ere&ces
C!G04G0":1 &tandard Cost Estimate
CO013.> Co&'(%rato&
Siemens Information Systems Ltd Author: Swarali Thite
16-NO-!" #a$e )& of %& 'ontrollin$

Project SPIRIT RCF_CD_CO_A1.0
CO013.? *a")t! Crtera
&(2 %34 %elease
CO013.@ Reaso& 'or Dsco&t&%ato&
$ot (pplicable
Siemens Information Systems Ltd Author: Swarali Thite
16-NO-!" #a$e )" of %& 'ontrollin$

Project SPIRIT RCF_CD_CO_A1.0
CO01(: .roduct Costing Define 2ine 3Ds 4 Assignment
Co&'(%rato& Matr:
*erso& 1.0 *a") From 01!ct"00# *a") U&t" $ext %elease
A%thor.s/ &warali Thite
CO01>.1 Access Path
Controlling 2roduct Cost Controlling Cost !bject Controlling 2roduct Cost 5) 2eriod
2eriod End Closing Eor8 /n 2rocess 'efine ?ine /'Ms3 (ssignment
CO01>.; P%r+ose
?ine /' is a concept used to structure the costs and revenue of a results anal)sis object. To pass the data on
to ,inancial (ccounting0 posting rules must be defined that lin8 this data to 63? accounts.
?ine /'s allow1
&eparate the costs that must be capitali*ed from the costs that cannot be capitali*ed for the balance
sheet
The following data is updated with reference to a line /'1
Eor8 in process
%eserves for unreali*ed costs
%eserves for costs of complaints
Cost of sales
CO01>.< Prere=%stes
The following must alread) have been defined1
'efine results anal)sis version
Create results anal)sis 8e)s
'efine line /'s
The following also has to be noted1
To calculate the wor8 in process using actual costs0 an additional line /' must be created for the
cost elements under which the goods receipts are posted.
,or each line /'0 a cost element 9t)pe 41: has to be created. /f the values are separated according
to creation and usage0 then two cost elements have to be created for each line /'.
/n Customi*ing for 2roduct Cost 2lanning0 specif) in the step 'efine cost components which values
are relevant to inventor) valuation0 ph)sical inventor) valuation0 and taxbased inventor) valuation.
Cost components classif) the costs calculated in the cost estimate into groups. The line /'s for E/2
calculation is normall) structured according to the same logic as the cost components in 2roduct
Cost 2lanning. ,or example0 a line /' Jraw materialsJ normall) has the same cost element interval
assigned to it that is assigned to the cost element Jraw materialsJ.
CO01>.0 De+e&)e&ces
The wor8 in process or reserves for unreali*ed costs are calculated as a total for each order and apportioned
to the line /'s. /t can be separatel) defined for each line /' whether the wor8 in process for that line /' must
be capitali*ed. E/2 calculation updates the wor8 in process and reserves for unreali*ed costs on the process
order0 grouped b) line /'. The line /'s put the costs incurred for the order into specific groups such as1
'irect material costs
2roduction costs
/ndirect costs
These groups should be based on the structure of the cost of goods manufactured in the cost component
structure
CO01>.3 Re'ere&ces
C!G04G0":1 &tandard Cost Estimate
Siemens Information Systems Ltd Author: Swarali Thite
16-NO-!" #a$e )6 of %& 'ontrollin$

Project SPIRIT RCF_CD_CO_A1.0
CO01>.> Co&'(%rato&
(ttached is a file containing details of the account assignment for Eor8 in 2rocess.
Assignment of Cost
Elements for WIP
CO01>.? *a")t! Crtera
&(2 %34 %elease
CO01>.@ Reaso& 'or Dsco&t&%ato&
$ot (pplicable
Siemens Information Systems Ltd Author: Swarali Thite
16-NO-!" #a$e )% of %& 'ontrollin$

Project SPIRIT RCF_CD_CO_A1.0
CO01): .roduct Costing Define 5pdate 4 .osting %ules for Settling 63.
Co&'(%rato& Matr:
*erso& 1.0 *a") From 01!ct"00# *a") U&t" $ext %elease
A%thor.s/ &warali Thite
CO01?.1 Access Path
Controlling 2roduct Cost Controlling Cost !bject Controlling 2roduct Cost 5) 2eriod
2eriod End Closing Eor8 /n 2rocess 'efine Dpdate3 'efine 2osting %ules for &ettling Eor8
in 2rocess
CO01?.; P%r+ose
,or each line /'0 the results anal)sis cost element under which the wor8 in process and 9under some
circumstances: the reserves for unreali*ed costs are updated is specified and each line /' assigned to a
categor). The line /'s put the costs incurred for an order into groups such as the following1
'irect material costs
2roduction costs
/ndirect costs
These groups should be based on the structure of the cost of goods manufactured in the cost component
structure. The categor) indicates whether the cost elements under which the different postings are made are
debits or credits for E/2 calculation.
CO01?.< Prere=%stes
The following steps must have alread) been carried out1
Create controlling area
Create compan) code
'efine results anal)sis versions
'efine assignment 9for results anal)sis categories: or
'efine update 9for results anal)sis cost elements:
CO01?.0 De+e&)e&ces
63? accounts are specified in ,inancial (ccounting to which the wor8 in process is settled. ( results anal)sis
cost element or a group of results anal)sis cost elements are specified to two 63? accounts. ( posting
document is generated in ,inancial (ccounting on the basis of the settlement of wor8 in process.
'ata is written to the balance sheet.
'ata is written to the profit and loss statement.
The results anal)sis data can be assigned to 63? accounts at the following levels1
%esults anal)sis categories
The results anal)sis categories are created on the basis of the assignment of the costs to line /'s1
1. E/2% Eor8 in process with requirement to capitali*e costs
". E/2! Eor8 in process with option to capitali*e costs
4. E/22 Eor8 in process with prohibition to capitali*e costs
$ormall) a posting rule is defined that assigns the wor8 in process with requirement to capitali*e costs to the
63? accounts for unfinished products 9balance sheet: and stoc8 changes 923?:.
CO01?.3 Re'ere&ces
C!G04G0":1 &tandard Cost Estimate
CO01?.> Co&'(%rato&
Siemens Information Systems Ltd Author: Swarali Thite
16-NO-!" #a$e )* of %& 'ontrollin$

Project SPIRIT RCF_CD_CO_A1.0
CO01?.? *a")t! Crtera
&(2 %34 %elease
CO01?.@ Reaso& 'or Dsco&t&%ato&
$ot (pplicable
Siemens Information Systems Ltd Author: Swarali Thite
16-NO-!" #a$e )+ of %& 'ontrollin$

Project SPIRIT RCF_CD_CO_A1.0
CO01,: .roduct Costing Define 'ariance /eys
Co&'(%rato& Matr:
*erso& 1.0 *a") From 01!ct"00# *a") U&t" $ext %elease
A%thor.s/ &warali Thite
CO01@.1 Access Path
Controlling 2roduct Cost Controlling Cost !bject Controlling 2roduct Cost 5) 2eriod
2eriod End Closing .ariance Calculation 'efine .ariance ;e)s
CO01@.; P%r+ose
2arameters that control the calculation of variances and scrap on production orders and process
orders are defined in here. This is controlled b) variance 8e) that ensures the relevant object is
selected during variance calculation. The variance 8e) also controls whether scrap costs are
reported in a separate categor).
CO01@.< Prere=%stes
'efining .ariance ;e)s involves setting up the controlling area along with all necessar) settings
for the product cost b) order component.
(lso0 the following requirements must be met before calculating scrap1
The material must have a standard cost estimate with quantit) structure0 or another cost
estimate in accordance with the valuation variant for wor8 in process and scrap.
CO01@.0 De+e&)e&ces
/n 2roduct Cost b) !rder variances are usuall) calculated cumulativel). /n cumulative variance
calculation0 the target costs are calculated on the basis of the quantit) that is transferred to stoc8
for the order. The actual costs are for the entire life of the order. .ariance calculation requires that
the order have the status '?. 9delivered: or TEC! 9technicall) completed:.
The variance 8e) specifies the following1
Ehether the scrap variances are calculated
Ehether a document is written containing the date0 user name0 and change made 9line
item:
(s a rule0 the line item document is not necessar) for variance calculation. /f0 however0
)ou decide to turn on this indicator0 )ou should be prepared for extended run times during
variance calculation.
Transfer of the .ariance ;e) into an !rder
The variance 8e) is transferred into the master data of the order in the following wa)1
( variance 8e) is defined as a default value for each plant.
Ehen a material master record is created0 the s)stem proposes a variance 8e) using the
default value for that plant.
Ehen a production order or process order is created to manufacture the material0 the
s)stem proposes a variance 8e) through the entr) in the material master record.
CO01@.3 Re'ere&ces
C!G04G0":1 &tandard Cost Estimate
CO01@.> Co&'(%rato&
Siemens Information Systems Ltd Author: Swarali Thite
16-NO-!" #a$e &! of %& 'ontrollin$

Project SPIRIT RCF_CD_CO_A1.0
Siemens Information Systems Ltd Author: Swarali Thite
16-NO-!" #a$e &1 of %& 'ontrollin$

Project SPIRIT RCF_CD_CO_A1.0
CO01@.? *a")t! Crtera
&(2 %34 %elease
CO01@.@ Reaso& 'or Dsco&t&%ato&
$ot (pplicable
Siemens Information Systems Ltd Author: Swarali Thite
16-NO-!" #a$e &( of %& 'ontrollin$

Project SPIRIT RCF_CD_CO_A1.0
CO01-: Actual Costing/!aterial 2edger 7 Acti8ate 'aluation Areas for !aterial 2edger
Co&'(%rato& Matr:
*erso& 1.0 *a") From 01!ct"00# *a") U&t" $ext %elease
A%thor.s/ &warali Thite
CO01B.1 Access Path
Controlling 2roduct Cost Controlling (ctual Costing3Material ?edger (ctivate .aluation
(reas for Material ?edger
CO01B.; P%r+ose
Material ?edger is a tool that collects transaction data for materials whose master data is stored in
material master. The material ledger uses this data to calculate prices to valuate these materials.
The material ledger is the basis of actual costing. /t enables material inventories to be valuated in
multiple currencies and allows the use of different valuation approaches.
Material ?edger can be activated for one or more .aluation area. /f the material ledger is active for a
particular valuation area0 all materials in the valuation area are valuated using the material ledger.
CO01B.< Prere=%stes
The following steps must have alread) been carried out1
Create controlling area
Create compan) code
Creation of plant
Creation of valuation area
CO01B.0 De+e&)e&ces
Material ?edger can be activated for one or more .aluation area. /f the material ledger is active for a
particular valuation area0 all materials in the valuation area are valuated using the material ledger.
CO01B.3 Re'ere&ces
C!G04G01 1 (bsorption costing
CO01B.> Co&'(%rato&
Siemens Information Systems Ltd Author: Swarali Thite
16-NO-!" #a$e &) of %& 'ontrollin$

Project SPIRIT RCF_CD_CO_A1.0
CO01B.? *a")t! Crtera
&(2 %34 %elease
CO01B.@ Reaso& 'or Dsco&t&%ato&
$ot (pplicable
CO020: Actual Costing/!aterial2edger 7 Assign Currency 9ypes to !aterial 2edger type
Co&'(%rato& Matr:
*erso& 1.0 *a") From 01!ct"00# *a") U&t" $ext %elease
A%thor.s/ &warali Thite
CO0;0.1 Access Path
Controlling 2roduct Cost Controlling (ctual Costing3Material ?edger (ssign Currenc)
T)pes to Material ?edger T)pe
CO0;0.; P%r+ose
Material ?edger t)pe is a combination of multiple currencies or valuations that are 8ept in the
material ledger for a particular valuation area.
Currenc) t)pe is a 8e) identif)ing the role of a currenc) in the &(2 s)stem. /n addition to the local
currenc) as house currenc)0 )ou can manage parallel currencies with the following currenc) t)pes1
6roup currenc)
7ard currenc)
/ndex currenc)
6lobal compan) currenc)
Material ledger t)pe and allocate up to three currenc) t)pes to each of these material ledger t)pes.
CO0;0.< Prere=%stes
Material ?edger should be activated for .aluation (rea.
CO0;0.0 De+e&)e&ces
5efore converting data for production startup0 ma8e sure that the currenc) settings in ,inancial
(ccounting and in the Material ?edger are correct. -ou cannot change the currencies0 currenc)
t)pes and material ledger t)pes after production startup.
Siemens Information Systems Ltd Author: Swarali Thite
16-NO-!" #a$e && of %& 'ontrollin$

Project SPIRIT RCF_CD_CO_A1.0
CO0;0.3 Re'ere&ces
C!G04G01 1 (bsorption costing
CO0;0.> Co&'(%rato&
&pecif) which currenc) t)pes which is to be used for the respective material ledger t)pe
Enter a fourdigit identification code in the field ML type. The first character of this identification
code must be a letter. &pecif) which currenc) t)pes which is to be used for the respective material
ledger t)pe.
CO0;0.? *a")t! Crtera
&(2 %34 %elease
CO0;0.@ Reaso& 'or Dsco&t&%ato&
$ot (pplicable
CO021: Actual Costing/!aterial 2ed:7 Assign !2 9ypes to 'aluation area
Co&'(%rato& Matr:
*erso& 1.0 *a") From 01!ct"00# *a") U&t" $ext %elease
A%thor.s/ &warali Thite
CO0;1.1 Access Path
Controlling 2roduct Cost Controlling (ctual Costing3Material ?edger (ssign Material
?edger T)pes to .aluation (rea
CO0;1.; P%r+ose
Material ?edger t)pe is to be allocated to the valuation areas. !nl) one material ledger t)pe can
be allocated to each valuation area. This must contain the currenc) t)pe 10.
CO0;1.< Prere=%stes
&ame material ledger t)pe can be allocated to several valuation areas. /f )ou have several
valuation areas within a single compan) code 9that is0 when the valuation area corresponds to a
plant:0 )ou must assign all valuation areas in this compan) code to the same material ledger t)pe.
The following steps must have alread) been carried out1
The relevant valuation areas
The relevant material ledger t)pes
CO0;1.0 De+e&)e&ces
5efore )ou convert data for production startup0 ma8e sure that the currenc) settings in ,inancial
(ccounting and in the Material ?edger are correct. !nce production has been started0 )ou cannot
change currencies0 currenc) t)pes and material ledger t)pes.
CO0;1.3 Re'ere&ces
C!G04G01 1 (bsorption costing
Siemens Information Systems Ltd Author: Swarali Thite
16-NO-!" #a$e &" of %& 'ontrollin$

Project SPIRIT RCF_CD_CO_A1.0
CO0;1.> Co&'(%rato&
To assign material ledger t)pes to a valuation area0 proceed as follows1
1. Choose the function $ew entries.
". Enter a valuation area.
4. Enter a material ledger t)pe.
>. &ave )our entries.
CO0;1.? *a")t! Crtera
&(2 %34 %elease
CO0;1.@ Reaso& 'or Dsco&t&%ato&
$ot (pplicable
CO022: Actual Costing/!2 7 !aintain #um$er %anges for !aterial 2edger Documents
Co&'(%rato& Matr:
*erso& 1.0 *a") From 01!ct"00# *a") U&t" $ext %elease
A%thor.s/ &warali Thite
CO0;;.1 Access Path
Controlling 2roduct Cost Controlling (ctual Costing3Material ?edger Maintain $umber
%anges for Material ?edger 'ocuments
CO0;;.; P%r+ose
( material ledger document must be clearl) identified in the s)stem. This is achieved b) saving
each transaction in the material ledger under a unique number.
CO0;;.< Prere=%stes
,ollowing configuration must be maintained in the s)stem.
(ctivate .aluation (reas for Material ?edger
(ssign Currenc) T)pes to Material ?edger T)pe
(ssign Material ?edger T)pes to .aluation (rea
CO0;;.0 De+e&)e&ces
$umber ranges have to define for price changes as well as debits and credits to materials. /n
addition to the accounting document that is created during such a transaction0 the s)stem also
creates a material ledger document.
CO0;;.3 Re'ere&ces
C!G04G01 1 (bsorption costing
CO0;;.> Co&'(%rato&
6roups exist for material ledger documents per transaction t)pe in the standard setup
Material ledger update 96roup 01:
Material ledger closing 96roup 0":
Siemens Information Systems Ltd Author: Swarali Thite
16-NO-!" #a$e &6 of %& 'ontrollin$

Project SPIRIT RCF_CD_CO_A1.0
Material ledger price changes 96roup 04:
&inglelevel material ledger settlement 96roup 0>:
Multilevel material ledger settlement 96roup 0#:
Material ledger repair 96roup 0@:
Each group is assigned a number from a range of 100 000 000 numbers.
CO0;;.? *a")t! Crtera
&(2 %34 %elease
Siemens Information Systems Ltd Author: Swarali Thite
16-NO-!" #a$e &% of %& 'ontrollin$

Project SPIRIT RCF_CD_CO_A1.0
CO0;;.@ Reaso& 'or Dsco&t&%ato&
$ot (pplicable
CO023: Actual Costing/!aterial 2edger 7 Configure Dynamic .rice C+anges
Co&'(%rato& Matr:
*erso& 1.0 *a") From 01!ct"00# *a") U&t" $ext %elease
A%thor.s/ &warali Thite
CO0;<.1 Access Path
Controlling 2roduct Cost Controlling (ctual Costing3Material ?edger Configure ')namic
2rice Changes
CO0;<.; P%r+ose
/n this activit)0 )ou can specif) in each valuation area that a planned price is activated as the
valuation price upon the first goods movement in a new posting period as long as the validit) date
of the planned price has been reached.
CO0;<.< Prere=%stes
The planned prices are handled b) the s)stem with the following priorit)1
1. mar8ed standard cost estimates
". future valuation prices
CO0;<.0 De+e&)e&ces
&tandard cost estimate should be mar8ed.
CO0;<.3 Re'ere&ces
C!G04G01 1 (bsorption costing
CO0;<.> Co&'(%rato&
(ctivate d)namic price release for the relevant valuation areas and save the changes.
CO0;<.? *a")t! Crtera
&(2 %34 %elease
CO0;<.@ Reaso& 'or Dsco&t&%ato&
Siemens Information Systems Ltd Author: Swarali Thite
16-NO-!" #a$e &* of %& 'ontrollin$

Project SPIRIT RCF_CD_CO_A1.0
$ot (pplicable
CO02": Actual Costing/!aterial 2edger 7 %easons for .rice C+anges
Co&'(%rato& Matr:
*erso& 1.0 *a") From 01!ct"00# *a") U&t" $ext %elease
A%thor.s/ &warali Thite
CO0;0.1 Access Path
Controlling 2roduct Cost Controlling (ctual Costing3Material ?edger %easons for 2rice
Changes 'ispla) (ccounts ,or (ccount ;e) DM5
CO0;0.; P%r+ose
!ne posting reason and one account code grouping can be assigned to the transactions M%"1
2rice Changes and M%"" Credit3'ebit Material.
CO0;0.< Prere=%stes
Chec8 the (ccount determination for transaction DM5
Enter the account grouping and assign it to the account )ou want the postings to be made to.
CO0;0.0 De+e&)e&ces
%espective 6? accounts should be created.
CO0;0.3 Re'ere&ces
C!G04G01 1 (bsorption costing
CO0;0.> Co&'(%rato&
Siemens Information Systems Ltd Author: Swarali Thite
16-NO-!" #a$e &+ of %& 'ontrollin$

Project SPIRIT RCF_CD_CO_A1.0
CO0;0.? *a")t! Crtera
&(2 %34 %elease
CO0;0.@ Reaso& 'or Dsco&t&%ato&
$ot (pplicable
CO02&: Actual Costing/!2 7 !aterial 5pdate 7 Define !aterial 5pdate Structure
Co&'(%rato& Matr:
*erso& 1.0 *a") From 01!ct"00# *a") U&t" $ext %elease
A%thor.s/ &warali Thite
CO0;3.1 Access Path
Controlling 2roduct Cost Controlling (ctual Costing3Material ?edger Material Dpdate N
'efine Material Dpdate &tructure
CO0;3.; P%r+ose
( determinant of how the values from transactions relevant to valuation are collected in the
material ledger0 influencing the determination of new valuation prices and the closing postings with
singlelevel and multilevel material price determination.'uring the material ledger update0 the
s)stem collects data from valuationrelevant transactions such as goods receipts0 invoice receipts0
and settlement of production orders. This data is collected in different categories in the material
ledger in accordance with the material update structure.
CO0;3.< Prere=%stes
The influence that these transactions have on the valuation price upon material price
Siemens Information Systems Ltd Author: Swarali Thite
16-NO-!" #a$e "! of %& 'ontrollin$

Project SPIRIT RCF_CD_CO_A1.0
determination depends on the categor) to which the) were assigned. The following categories are
available1
%eceipts
Consumption
!ther %eceipts3Consumption
( receipt alwa)s effects the valuation price. Eith consumption0 )ou can determine whether or not
it has an effect on the valuation price of a material1 the categor) !ther receipts3consumption has
an effect0 the categor) Consumption does not.
CO0;3.0 De+e&)e&ces
Material ?edger should be activated
CO0;3.3 Re'ere&ces
C!G04G01 1 (bsorption costing
CO0;3.> Co&'(%rato&
/n the standard setup0 the categories are defined in material update structure 00"# such that the
valuation price from material settlement corresponds to the weighted average price. This standard
setting is used for customi*ing M?.

CO0;3.? *a")t! Crtera
&(2 %34 %elease
CO0;3.@ Reaso& 'or Dsco&t&%ato&
$ot (pplicable
Siemens Information Systems Ltd Author: Swarali Thite
16-NO-!" #a$e "1 of %& 'ontrollin$

Project SPIRIT RCF_CD_CO_A1.0
CO02(: Act: Costing/!2 7 !at 5pdate 7 Assign !at 5pdate Stru to a 'aluation Area
Co&'(%rato& Matr:
*erso& 1.0 *a") From 01!ct"00# *a") U&t" $ext %elease
A%thor.s/ &warali Thite
CO0;>.1 Access Path
Controlling 2roduct Cost Controlling (ctual Costing3Material ?edger Material Dpdate N
(ssign Material Dpdate &tructure to a .aluation (rea
CO0;>.; P%r+ose
/n this section0 )ou can assign a material update structure to one or more valuation areas.
CO0;>.< Prere=%stes
Material update structure should be defined.
Corresponding valuation area should be activated for the Material ?edger.
CO0;>.0 De+e&)e&ces
Material ?edger should be activated
CO0;>.3 Re'ere&ces
C!G04G01 1 (bsorption costing
Siemens Information Systems Ltd Author: Swarali Thite
16-NO-!" #a$e "( of %& 'ontrollin$

Project SPIRIT RCF_CD_CO_A1.0
CO0;>.> Co&'(%rato&
Enter a valuation area and a material update structure.
CO0;>.? *a")t! Crtera
&(2 %34 %elease
CO0;>.@ Reaso& 'or Dsco&t&%ato&
$ot (pplicable
CO02): Actual Costing/!aterial 2edger 7 Actual Costing 7Acti8ate Actual Costing
Co&'(%rato& Matr:
*erso& 1.0 *a") From 01!ct"00# *a") U&t" $ext %elease
A%thor.s/ &warali Thite
CO0;?.1 Access Path
Controlling 2roduct Cost Controlling (ctual Costing3Material ?edger O (ctual Costing O
(ctivate (ctual Costing
CO0;?.; P%r+ose
(ctual Costing can be activated for per plant0 for materials and activit) consumption update in the
quantit) structure.
CO0;?.< Prere=%stes
Material ?edger should be activated
CO0;?.0 De+e&)e&ces
Siemens Information Systems Ltd Author: Swarali Thite
16-NO-!" #a$e ") of %& 'ontrollin$

Project SPIRIT RCF_CD_CO_A1.0
/f )ou use (ctual Costing0 )ou can decide whether activit) consumption and3or processes which
are used to produce a material should be updated in the quantit) structure in (ctual
Costing3Material ?edger.
'epending on the activation t)pe chosen1
(ctual consumption is updated in the quantit) structure but not considered during price
determination.
-ou can use this setting if )ou just want to receive information on the complete actual
quantit) structure. .ariances between the plan price for the cost center3activit) t)pe 9or
process: and the actual price calculated at the end of the period can be debited to the cost
object at period closing using the function L%evaluation at (ctual 2ricesL.
(ctual consumption is updated in the quantit) structure and is considered during price
determination.
/f )ou choose this setting0 the variances between the plan price and the cost
center3activit) t)pe 9or process: and the actual price calculated at the end of the period
are adjusted subsequentl). The cost center or the process is then credited and the
material associated with the consumption is debited. /n the context of multilevel price
determination0 these variances can be rolled up through the production structure up to the
finished product in the same wa) that material price variances are rolled up.
/f )ou choose this setting0 )ou cannot use the function L%evaluation at (ctual 2ricesL at
period closing in Cost !bject Controlling0 as the variances from the cost center 3 process
are debited directl) to the material. /f )ou use the function L%evaluation at (ctual 2ricesL at
period closing0 the cost center 3 process will be credited twice and the materials will be
debited twice.
CO0;?.3 Re'ere&ces
C!G04G01 1 (bsorption costing
CO0;?.> Co&'(%rato&
/n case of P%C,?Q the first option is used i.e. P(ctual consumption is updated in the quantit)
structure but not considered during price determination.Q
Siemens Information Systems Ltd Author: Swarali Thite
16-NO-!" #a$e "& of %& 'ontrollin$

Project SPIRIT RCF_CD_CO_A1.0
CO0;?.? *a")t! Crtera
&(2 %34 %elease
CO0;?.@ Reaso& 'or Dsco&t&%ato&
$ot (pplicable
Siemens Information Systems Ltd Author: Swarali Thite
16-NO-!" #a$e "" of %& 'ontrollin$

Project SPIRIT RCF_CD_CO_A1.0
CO02,: Actual Costing/!2 7 Actual Costing 7 Acti8ate Actual Cost Component Split
Co&'(%rato& Matr:
*erso& 1.0 *a") From 01!ct"00# *a") U&t" $ext %elease
A%thor.s/ &warali Thite
CO0;@.1 Access Path
Controlling 2roduct Cost Controlling (ctual Costing3Material ?edger O (ctual Costing O
(ctivate (ctual Cost Component &plit
CO0;@.; P%r+ose
/n this step0 )ou can activate the actual cost component split for each valuation area
CO0;@.< Prere=%stes
The cost component structure in Customi*ing for 2roduct Cost 2lanning should be
defined.
/f0 in the cost estimate0 )ou have defined multiple costing variants with which )ou update
standard prices0 )ou must have allowed mar8ing for the standard cost estimate. The
s)stem uses the costing variants selected there to determine the cost component
structure for the actual cost component split.
CO0;@.0 De+e&)e&ces
Material ?edger should be activated
CO0;@.3 Re'ere&ces
C!G04G01 1 (bsorption costing
CO0;@.> Co&'(%rato&
CO0;@.? *a")t! Crtera
&(2 %34 %elease
CO0;@.@ Reaso& 'or Dsco&t&%ato&
$ot (pplicable
Siemens Information Systems Ltd Author: Swarali Thite
16-NO-!" #a$e "6 of %& 'ontrollin$

Project SPIRIT RCF_CD_CO_A1.0
CO02-: .rofita$ility Analysis Structures 7 Define Operating Concern
Co&'(%rato& Matr:
*erso& 1.0 *a") From 01!ct"00# *a") U&t" $ext %elease
A%thor.s/ &warali Thite
CO0;B.1 Access Path
Controlling 2rofitabilit) (nal)sis O &tructures O 'efine !perating Concern
CO0;B.; P%r+ose
/n order to use 2rofitabilit) (nal)sis 9C!2(:0 )ou have to define operating concerns. (n operating
concern is an organi*ational unit in ,inancials. The structure of an operating concern is
determined b) anal)sis criteria 9characteristics: and the values to be evaluated 9value fields:.
/n a first step0 )ou have to define the characterstcs for )our operating concerns. -ou define
characteristics in the Customi*ing activit) Ma&ta& characterstcs. ,or costingbased
2rofitabilit) (nal)sis0 )ou also need to define 2a"%e 'e")s. -ou do this using the activit) Ma&ta&
2a"%e 'e")s. These characteristics and value fields can be used in several operating concerns.
Their definition applies to all clients.
CO0;B.< Prere=%stes
Compan) Code and Controlling area should be created.
CO0;B.0 De+e&)e&ces
Controlling area should be assigned to Compan) code.
CO0;B.3 Re'ere&ces
C!G0>G0" 1 2roduct wise profitabilit) at (rea 3 district office level
CO0;B.> Co&'(%rato&
(fter this0 )ou have to define the structure of )our operating concern in the activit) Maintain
operating concern. -ou do this b) selecting the desired characteristics and adding them to the
data structures of )our operating concern. /f costingbased 2rofitabilit) (nal)sis is active0 )ou also
Siemens Information Systems Ltd Author: Swarali Thite
16-NO-!" #a$e "% of %& 'ontrollin$

Project SPIRIT RCF_CD_CO_A1.0
need to select and add the required value fields. The structure of an operating concern is valid in
all clients./n the step JMa&ta& o+erat&( co&cer&J0 )ou also specif) the attributes of )our
operating concern 9fiscal )ear variant0 currencies:. 5) maintaining the attributes0 )ou ma8e an
operating concern J8nownJ in the current client. The attributes are clientspecific.
Maintain .alue fields1 TC!'E1;E(@
(fter this0Maintain !perating Concern1 TC!'E1;E(0
Data structure
The data structure determines the structure of the profitabilit) segments that )ou can anal)*e and
how costs and revenues are organi*ed. (ll information in the data structure definition is valid for
a"" c"e&ts. /f )ou use the operating concern in more than one client0 )ou still onl) need to define
the data structure once. -ou then need to set the attributes in each client individuall).
Siemens Information Systems Ltd Author: Swarali Thite
16-NO-!" #a$e "* of %& 'ontrollin$

Project SPIRIT RCF_CD_CO_A1.0
CO0;B.? *a")t! Crtera
&(2 %34 %elease
CO0;B.@ Reaso& 'or Dsco&t&%ato&
$ot (pplicable
Siemens Information Systems Ltd Author: Swarali Thite
16-NO-!" #a$e "+ of %& 'ontrollin$

Project SPIRIT RCF_CD_CO_A1.0
CO030: .rofita$ility Analysis 7 9ransfer of ;illing Documents
*erso& 1.0 *a") From 01!ct"00# *a") U&t" $ext %elease
A%thor.s/ &warali Thite
CO0<0.1 Access Path
Controlling O 2rofitabilit) (nal)sis O ,lows of (ctual .alues O Transfer of 5illing 'ocuments
CO0<0.; P%r+ose
/n this section )ou ma8e the basic settings required for posting data from the &' application
component to 2rofitabilit) (nal)sis.
/n costingbased C!2(0 )ou need to assign condition t)pes and quantit) fields from &ales and
'istribution 9&': to the value and quantit) fields C!2(.
CO0<0.< Prere=%stes
2rofitabilit) (nal)sis should be activated.
CO0<0.0 De+e&)e&ces
(ll the Characteristics and .alue fields should be maintained for !perating concern.
CO0<0.3 Re'ere&ces
C!G0>G0" 1 2roduct wise profitabilit) at (rea 3 district office level
CO0<0.> Co&'(%rato&
Activities:
Siemens Information Systems Ltd Author: Swarali Thite
16-NO-!" #a$e 6! of %& 'ontrollin$

Project SPIRIT RCF_CD_CO_A1.0
(ssign condition t)pes to the desired value fields. These assignments let )ou transfer
JrealJ conditions 9those that are posted to ,/: and JstatisticalJ 9fictitious: conditions to C!
2(. (ssign value fields.
,or real conditions0 the corresponding revenue0 sales deduction0 and costofsales
accounts must be defined as C!relevant accounts 9cost or revenue elements:.
(ssign the quantit) fields in &' to the desired quantit) fields in C!2(. (ssign quantit)
fields.
(ssignment of &' conditions to value ,ields1 Tcode1;E>1
Assi$n &' Ct) fields to C!2( Ct) ,ields1 Tcode1 ;E>M
CO0<0.? *a")t! Crtera
&(2 %34 %elease
Siemens Information Systems Ltd Author: Swarali Thite
16-NO-!" #a$e 61 of %& 'ontrollin$

Project SPIRIT RCF_CD_CO_A1.0
CO0<0.@ Reaso& 'or Dsco&t&%ato&
$ot (pplicable
Siemens Information Systems Ltd Author: Swarali Thite
16-NO-!" #a$e 6( of %& 'ontrollin$

Project SPIRIT RCF_CD_CO_A1.0
CO031: .rofita$ility Analysis 1 Order and .ro<ect Settlement
Co&'(%rato& Matr:
*erso& 1.0 *a") From 01!ct"00# *a") U&t" $ext %elease
A%thor.s/ &warali Thite
CO0<1.1 Access Path
Controlling 2rofitabilit) (nal)sis O ,lows of (ctual .alues O !rder and 2roject &ettlement
CO0<1.; P%r+ose
/n this section )ou set up settlement of actual and plan data for orders and projects to 2rofitabilit)
(nal)sis.
CO0<1.< Prere=%stes
2rofitabilit) (nal)sis should be activated.
CO0<1.0 De+e&)e&ces
(ll the Characteristics and .alue fields should be maintained for !perating concern.
CO0<1.3 Re'ere&ces
C!G0>G0" 1 2roduct wise profitabilit) at (rea 3 district office level
CO0<1.> Co&'(%rato&
-ou can settle actual data from orders0 internal orders0 sales orders0 and projects and plan data
from planintegrated internal orders and projects.
To settle data to C!2(0 )ou need to define a socalled Jsettlement profileJ and assign this to the
master data of the objects )ou want to settle.
This settlement profile contains an allocation structure0 which defines how the corresponding order
or project is credit. /t also contains a 2( transfer structure0 which determines how the values are
settled to value fields in 2rofitabilit) (nal)sis.
/n the 2( transfer structure0 )ou first assign the original cost elements on the order or the project
to lines 9assignments:0 which )ou then assign to value fields in 2rofitabilit) (nal)sis.
'efine 2( transfer &tructure for &ettlement1 Tcode1 ;E/1
Siemens Information Systems Ltd Author: Swarali Thite
16-NO-!" #a$e 6) of %& 'ontrollin$

Project SPIRIT RCF_CD_CO_A1.0
CO0<1.? *a")t! Crtera
&(2 %34 %elease
CO0<1.@ Reaso& 'or Dsco&t&%ato&
$ot (pplicable
Siemens Information Systems Ltd Author: Swarali Thite
16-NO-!" #a$e 6& of %& 'ontrollin$

Project SPIRIT RCF_CD_CO_A1.0
CO03": .rofita$ility Analysis 1 Order and .ro<ect Settlement
Co&'(%rato& Matr:
*erso& 1.0 *a") From 01!ct"00# *a") U&t" $ext %elease
A%thor.s/ &warali Thite
CO0<0.1 Access Path
Controlling 2rofitabilit) (nal)sis O ,lows of (ctual .alues O 'irect 2osting from ,/3MM
CO0<0.; P%r+ose
-ou can transfer direct primar) postings from ,inancial (ccounting 9,/: and Materials
Management 9MM: to profitabilit) segments.
CO0<0.< Prere=%stes
2rofitabilit) (nal)sis should be activated.
CO0<0.0 De+e&)e&ces
(ll the Characteristics and .alue fields should be maintained for !perating concern.
CO0<0.3 Re'ere&ces
C!G0>G0" 1 2roduct wise profitabilit) at (rea 3 district office level
CO0<0.> Co&'(%rato&
The following are some typical cases of when you would want to do this:
-ou post special direct costs from sales0 such as transport insurance for a certain deliver)0
and would li8e to assign these primar) costs directl) to a profitabilit) segment.
-ou post an invoice for promotional events and )ou want this invoice to appear statisticall)
in the responsible mar8eting cost center0 and at the same time assign it to a profitabilit)
segment in 2rofitabilit) (nal)sis. /n this case0 )ou would assign the invoice to both a cost
center and a profitabilit) segment.
-ou create automatic postings in Materials Management and )ou want these revenues
and expenses from the revaluation of material stoc8s to be posted automaticall) to
2rofitabilit) (nal)sis. This instance also requires that )ou define J(utomatic assignment to
a profitabilit) segmentJ.
Maintain 2( Transfer &tructure for 'irect 2ostings1 Tcode1;E/"
/n this activit)0 )ou define the 2( transfer structure ,/0 which )ou use to post costs and revenues
directl) to profitabilit) segments. /n the 2( transfer structure J,/J0 )ou specif) how the cost
elements are to be defined to the C!2( value fields.
&ince this maintenance dialog is also used in the definition of 2( transfer structures for other
allocations0 there are several selection options that do not appl) to the 2( transfer structure J,/J.
Siemens Information Systems Ltd Author: Swarali Thite
16-NO-!" #a$e 6" of %& 'ontrollin$

Project SPIRIT RCF_CD_CO_A1.0
CO0<0.? *a")t! Crtera
&(2 %34 %elease
CO0<0.@ Reaso& 'or Dsco&t&%ato&
$ot (pplicable
Siemens Information Systems Ltd Author: Swarali Thite
16-NO-!" #a$e 66 of %& 'ontrollin$

Project SPIRIT RCF_CD_CO_A1.0
CO03&: .rofit Center Accounting !aintain Controlling Area Settings
Co&'(%rato& Matr:
*erso& 1.0 *a") From 01!ct"00# *a") U&t" $ext %elease
A%thor.s/ &warali Thite
CO0<3.1 Access Path
Controlling 2rofit Center (ccounting 5asic &ettings Controlling (rea &ettings Maintain
Controlling (rea &ettings
CO0<3.; P%r+ose
5asic settings required to run 2rofit Center (ccounting are customi*ed in here. Dnder Maintain
Controlling (rea &ettings the following elements are configured.
(ssign certain master data to the controlling area
Ma8e the settings for elimination of internal business volume. The Eliminate /nternal
5usiness lets )ou eliminate internal business volume in the specified controlling area. /f
this field is not chec8ed0 the s)stem will not update transaction data between objects
which are assigned to the same profit center in the profit center accounting.
'etermine which currencies and0 where required0 which valuation views are to be used.
2rovide a dumm) profit center to ta8e care of all the unassigned transactions.
2ropose a profit center standard hierarch).
CO0<3.< Prere=%stes
The controlling area needs to be set up along with activating components li8e Cost Center
(ccounting + !rder Management as the 2rofit Center (ccounting module primaril) ta8es
all its data from the above said modules.
( dumm) profit center has to be in place before setting up the profit center accounting
component. The dumm) profit center receives all the postings in the s)stem to objects
which are not assigned to a profit center. This ensures that all data will be complete in
2rofit Center (ccounting.
( profit center standard hierarch) is proposed during activating profit center accounting in
the controlling area which must be created for the same.
CO0<3.0 De+e&)e&ces
7aving made the configuration to have the profit center accounting component in place0 it is to be
noted that ever) posting ta8ing place in the financial accounting module will have a corresponding
entr) in the relevant profit center. /t is hence imperative to note that required profit center is
populated in account assignment objects li8e Cost Center0 C!322 !rder0 Material Master and
other cost objects. 7aving done this0 another important point to be noted is the fact that all balance
sheet accounts be made a part of transaction code 4;E7 that defaults a profit center against a
specified 63? (ccount.
CO0<3.3 Re'ere&ces
C!G01G0412rofit Center
CO0<3.> Co&'(%rato&
Siemens Information Systems Ltd Author: Swarali Thite
16-NO-!" #a$e 6% of %& 'ontrollin$

Project SPIRIT RCF_CD_CO_A1.0
CO0<3.? *a")t! Crtera
&(2 %34 %elease
CO0<3.@ Reaso& 'or Dsco&t&%ato&
$ot (pplicable
Siemens Information Systems Ltd Author: Swarali Thite
16-NO-!" #a$e 6* of %& 'ontrollin$

Project SPIRIT RCF_CD_CO_A1.0
CO03(: .rofit Center Accounting !aintain .rofit Center Standard *ierarc+y
Co&'(%rato& Matr:
*erso& 1.0 *a") From 01!ct"00# *a") U&t" $ext %elease
A%thor.s/ &warali Thite
CO0<>.1 Access Path
Controlling 2rofit Center (ccounting Master 'ata 2rofit Center Maintain &tandard
7ierarch)
CO0<>.; P%r+ose
To create profit center0 a structure in master data maintenance is required to which profit centers
can assigned. This C! structure0 the standard hierarch)0 is created when maintaining a controlling
area for the profit center component.
The standard hierarch) consists of two structural elements. The end nodes are the nodes of the
structure to which profit centers can be assigned. &ummari*ation nodes cannot contain profit
centers themselves0 but rather summari*e the profit centers of the nodes which are attached to
them.
This distinction between t)pes of nodes is made automaticall) b) the s)stem. !nce profit centers
have been assigned to a node0 it can no longer be assigned to another node. ?i8ewise0 once other
nodes have been attached0 a profit center can no longer be assign to it.
CO0<>.< Prere=%stes
The Controlling (rea is to be created as the highest level in the C! hierarch). This organi*ation
structure is created with minimal basic data that includes controlling area currenc)0 a fiscal )ear
variant and chart of accounts.
CO0<>.0 De+e&)e&ces
To create profit centers0 a structure in master data maintenance is required to which profit centers
can be assigned. The standard hierarch) is an indicated hierarch) of profit center groups in which
all profit centers in a controlling area are gathered together. (ll profit centers created in the
controlling area will fall under the standard hierarch)0 which is the highest node.
CO0<>.3 Re'ere&ces
C!G01G0412rofit Center
CO0<>.> Co&'(%rato&
Siemens Information Systems Ltd Author: Swarali Thite
16-NO-!" #a$e 6+ of %& 'ontrollin$

Project SPIRIT RCF_CD_CO_A1.0
CO0<>.? *a")t! Crtera
&(2 %34 %elease
CO0<>.@ Reaso& 'or Dsco&t&%ato&
$ot (pplicable
Siemens Information Systems Ltd Author: Swarali Thite
16-NO-!" #a$e %! of %& 'ontrollin$

Project SPIRIT RCF_CD_CO_A1.0
CO03): .rofit Center Accounting Create Dummy .rofit Center
Co&'(%rato& Matr:
*erso& 1.0 *a") From 01!ct"00# *a") U&t" $ext %elease
A%thor.s/ &warali Thite
CO0<?.1 Access Path
Controlling 2rofit Center (ccounting Master 'ata 2rofit Center Create 'umm) 2rofit
Center
CO0<?.; P%r+ose
'ata is posted to the dumm) profit center when the original account assignment object 9e.g. cost
object0 order...: is not assigned to a profit center. This guarantees that the data in 2rofit Center
(ccounting is complete. The data in the dumm) profit center can be transferred to the correct
profit center later b) means of assessment3 distribution or through the means of a manual
reposting. The dumm) profit center can be created using a special transaction and can be created
onl) once. There cannot be more than one dumm) profit center.
The dumm) profit center receives all the postings in the s)stem to objects which are not assigned
to a profit center. This ensures that the data will be complete in 2rofit Center (ccounting.
CO0<?.< Prere=%stes
5efore venturing into creating a dumm) profit center the standard hierarch) must exist for the
current controlling area.
CO0<?.0 De+e&)e&ces
/t is important to note that ever) posting ta8ing place in the financial accounting module will have a
corresponding entr) in the relevant profit center. /t therefore becomes necessar) to note that the
required profit center is populated in account assignment objects li8e Cost Center0 C!322 !rder0
Material Master and other cost objects. /n this event an) unassigned object will flow to the default
profit center and will have to be reposted.
(lso0 activating the profit center accounting component requires that a dumm) profit be in place
beforehand.
CO0<?.3 Re'ere&ces
C!G01G0412rofit Center
CO0<?.> Co&'(%rato&
Siemens Information Systems Ltd Author: Swarali Thite
16-NO-!" #a$e %1 of %& 'ontrollin$

Project SPIRIT RCF_CD_CO_A1.0
CO0<?.? *a")t! Crtera
&(2 %34 %elease
CO0<?.@ Reaso& 'or Dsco&t&%ato&
$ot (pplicable
Siemens Information Systems Ltd Author: Swarali Thite
16-NO-!" #a$e %( of %& 'ontrollin$

Project SPIRIT RCF_CD_CO_A1.0
CO03,: .rofit Center Accounting !aintain Default .rofit Center
Co&'(%rato& Matr:
*erso& 1.0 *a") From 01!ct"00# *a") U&t" $ext %elease
A%thor.s/ &warali Thite
CO0<@.1 Access Path
Controlling 2rofit Center (ccounting (ctual 2ostings Choose (dditional 5alance &heet
and 2+? (ccounts 'erivation %ules for ,inding the 2rofit Center
CO0<@.; P%r+ose
/n the standard s)stem0 all postings made to cost and revenue elements are transferred to 2rofit
Center (ccounting. 2rofit and loss accounts are also transferred if the) affect operations in
?ogistics or where a profit center is entered for the underl)ing operation. This function RChoose
(ccounts and 'erivation %ules for ,inding the 2rofit CenterM helps transfer additional accounts to
2rofit Center (ccounting.
/f no profit center is set for a specific transaction in one of these additional accounts0 the s)stem
posts to the default profit center for that account interval.
CO0<@.< Prere=%stes
The controlling area along with the profit center accounting component need to be activated to go
ahead with this transaction.
CO0<@.0 De+e&)e&ces
5alance &heet (ccounts that can directl) be identified with a profit center can be assigned a
default profit center. Transactions arising out of the logistics 9materials management0 sales +
distribution and other related postings need a changeable profit center field. This feature is
provided b) maintaining the profit center field changeable at the time of document entr). (lso0
accounts li8e these will be assigned to the default profit center =====.
CO0<@.3 Re'ere&ces
C!G01G0412rofit Center
CO0<@.> Co&'(%rato&
CO0<@.? *a")t! Crtera
&(2 %34 %elease
CO0<@.@ Reaso& 'or Dsco&t&%ato&
$ot (pplicable
Siemens Information Systems Ltd Author: Swarali Thite
16-NO-!" #a$e %) of %& 'ontrollin$

Project SPIRIT RCF_CD_CO_A1.0
Siemens Information Systems Ltd Author: Swarali Thite
16-NO-!" #a$e %& of %& 'ontrollin$

You might also like