SAP CO-PA Profitability-Analysis

Controlling – Profitability Analysis
In SAP ECC 6.0
Step by step guided to learning and understanding
COPA module
Edition 2.0
Sapcollege.co
Copyright © by SAP College
All rights are reserved. No part of this publication may be reproduced, distributed or transmitted in
any form or by any means without prior written permission of the publisher except the non
economical use permitted by copyright law.
SAP is the trademark of SAP SE, and we are not affiliated with them.
The author of this book has made every reasonable attempt to provide the highest accuracy in the
content of this book. However, author assumes no responsibility for errors or omissions. You should
use this book as you deem fit and at your own risk. It is likely that the examples will not be applicable
in your case, and you should adjust your use of information and recommendation accordingly.
Acknowledgement
No task is a single man’s effort. Cooperation and coordination of various peoples at different levels
go into successful implementation of this book.
There is always a sense of gratitude, which everyone expresses others for their helpful and needy
services they render during difficult phases of life and to achieve the goal already set.
At the outset I am thankful to almighty that is constantly and invisible guiding everybody and have
also helped me to work on the right path.
I wish my sincere thanks to colleagues who helped and kept me motivated for writing this text.
We also thank the publisher and the whole staff of the SAP College for bringing this text in nice
presentable form.
Finally I thank everyone who directly or indirectly contributed to complete this authenticate work.
Controlling – Profitability Analysis SAP College
PREFACE
Congratulations on buying this book! This book is designed to provide a one stop reference for your
entire SAP COPA needs. In this book you will find as much SAP COPA configuration as can fit between
the covers. It is the one of the most comprehensive coverage of SAP COPA module available today.
Many topics discussed theoretically as well as practically in different chapters of this book. This book
is a humble attempt made to present the point along with comprehensive examples based on real
life implementation experience.
One thing which has eaten ninety percent of my time is detailed painstakingly captured screenshots
of real life live SAP COPA system. The snapshots are crystal clear and self-explanatory. Even if you
are not able to understand what is written, the screenshot will give you the glimpse of how the
configuration is done. Further the configuration menu paths are described.
This book is ideal for beginners and intermediates, who intend to understand COPA more deeply.
The book philosophy
“Complexity kills. It sucks the life out of developers, it makes product difficult to plan, build and test,
it introduces security challenges, and it causes end-user and administrator frustration.”
Ray Ozzie – Chief software architect at Microsoft Corporation.
Page 4 of 120
Table of Contents
Acknowledgement ................................................................................................................................ 3
PREFACE .............................................................................................................................................. 4
Table of Contents ................................................................................................................................ 5
Introduction ........................................................................................................................................ 7
1 Costing based PA........................................................................................................................... 11
1.1 Define operating concern ..................................................................................................... 11
1.1.1 Maintain characteristics ................................................................................................ 14
1.1.2 Maintain value fields ..................................................................................................... 20
1.1.3 Maintain operating concern ......................................................................................... 24
1.1.4 Assign controlling area to operating concern ............................................................... 29
1.1.5 Define Profitability Segment Characteristics ................................................................ 31
1.2 Master data ........................................................................................................................... 32
1.2.1 Characteristics Values ................................................................................................... 33
1.2.2 Characteristics Hierarchy .............................................................................................. 34
1.2.3 Characteristics Derivation ............................................................................................. 36
1.2.4 Define and assign valuation strategy ............................................................................ 47
1.2.5 Define keys for accessing material cost estimate ......................................................... 52
1.2.6 Assign costing key to any characteristics ...................................................................... 55
1.2.7 Assign value fields ......................................................................................................... 58
1.3 Flow of actual values............................................................................................................. 61
1.3.1 Define number ranges for actual posting ..................................................................... 62
1.3.2 Activate transfer of incoming sales order ..................................................................... 64
1.3.3 Transfer of billing document ......................................................................................... 75
1.3.4 Maintain PA transfer structure for direct posting FI/MM ............................................ 77
1.3.5 Order and Project settlement ....................................................................................... 81
1.3.6 Transfer of Overhead .................................................................................................... 87
1.3.7 Activate profitability analysis ........................................................................................ 92
1.4 End user process – Costing based PA.................................................................................... 94
1.4.1 Direct posting from FI ................................................................................................... 94
1.4.2 Transfer from sales order.............................................................................................. 98
1.5 Information system ............................................................................................................. 109
1.6 Tools .................................................................................................................................... 114
Page 5 of 120
1.6.1 Transport ..................................................................................................................... 114

1.6.2 Subsequent posting of SD Documents ........................................................................ 116
1.7 TABLES................................................................................................................................. 118
Takeaway ............................................................................................................................................ 120
Summary ............................................................................................................................................. 120
Page 6 of 120
Introduction
In order to sustain and thrive in this contemporary and dynamic environment, rapid and timely
decision making is more essential than to make right decision. Organization profitability is one the
core parameter to assess when it comes to designing organization goals, objectives and strategies to
achieve them. In this blog, I am going to discuss the tools incorporated in SAP ERP to analyse
organization profitability
The Intent and Purpose of CO-PA
In addition to mapping contribution margin accounting with actual and planned figures, the purpose
of CO-PA is to answer various business questions, for example:
1. Which customer do I earn the most money from?

2. Which products are the key to my business success?
3. Which specific products are successful with which specific customers?
4. Was my last marketing campaign successful?
5. What effect has my new price strategy had on the purchasing behaviour of my customers?
6. Should I grant a customer further discounts to increase the sales quantity?
7. Are my contribution margins in a business area sufficient to cover the fixed costs assigned
there
These are just some of the questions that CO-PA can answer—provided you have customized it
correctly. As you will recognize from the various questions, CO-PA is designed as a sales controlling
tool. In principle, however, it can map all of the elements of contribution margin accounting down to
earnings before interest and tax (EBIT). Which CO-PA-relevant organizational structure is
advantageous here?
There is one alternative to COPA which is Profit Center Accounting and here are the the usage of
both applications.
Profit Center Accounting (EC-PCA) Profitability Analysis (COPA)
If an organization wants to analyze its internal CO-PA is used to help organization to analyze
Profits and loss department wise or as per its profitability as per market segments by
different areas within your company, then it extracting sales, profit/loss and cost related
is recommended to used Profit center data from other modules like SD , Production
accounting. and MM.
EC-PCA can be used by companies in any CO-PA can be used by companies in any
branch of industry (mechanical engineering, branch of industry (mechanical engineering,
chemical, service industries and so on) and wholesale and retail, chemical, service
with any form of production (repetitive industries and so on) and with any form of
manufacturing, make-to-order production (repetitive manufacturing, make-
manufacturing, process manufacturing). to-order manufacturing, process
Page 7 of 120
The profit-relevant data is displayed by manufacturing).

period.
The data can be analyzed by period, or by
Profit Center Accounting uses Period order or project.
accounting and Cost-of-sales accounting.
Profitability Analysis uses Cost-of-sales
accounting method.
In EC-PCA we structure the units which we The market segments are structured like
want to evaluate as Profit centers. You can product, customers, orders,
create profit center according to region other characteristic and Organization units
(branch offices, plants) function (production, such as company codes or business area
sales), or product (product ranges, divisions). wise. It support management in decision
making by provided in-depth reports from
market oriented viewpoint
Customer+ Product= Market Segment (niche

marketing)
CO-PA Organization Structure
In order to use functionality of CO-PA (Profitability Analysis), the operating concern must be create
which is highest hierarchical unit in combined FICO module. The structure and assignment of
operating concern, controlling area and company code is shown in the figure below,
The Operating Concern
In an SAP system, the operating concern is the organizational unit responsible for Profitability
Analysis (COPA). What are organizational units in the SAP system? You usually use organizational
units to map your company structure: you set up company codes for your independent accounting
units; you create sales areas in SD; you define plants etc. for MM and PP. The entire remaining
customizing of your SAP system is based on this organizational representation of your company
structure. The organizational structure is the backbone of your system.
In an operating concern, you define all operating concern-relevant master data that you need for
your subsequent work with CO-PA. You then assign the operating concern to one or more controlling
areas. Here I would recommend a 1:1 relationship—i.e., assign the operating concern to only one
controlling area. You may wonder whether it makes sense to define a 1:1 relationship here when
Page 8 of 120
you will want to evaluate data across the group or company later on. Your thinking is correct, but the
clue is in the assignment of controlling areas to company codes: a controlling area is the
organizational unit of the CO module—you can assign one or more company codes to one
controlling area. To enable you to perform evaluations across the group or company (and not only in
Excel or a business warehouse, which would lead to further costs), you have to assign all of your
“live” company codes to one controlling area. You then assign this controlling area to the operating
concern. This ensures that you can see not only your costs across the group, but also your revenues,
contribution margins, and of course, your profit.
Common error in practice

If you do not think through the mapping of the organizational structure in the SAP
system thoroughly from the very beginning, meaning that you have to make
changes later, you will have to check the customizing that is based on this
structure whenever you make changes. SAP projects often take longer and
become unnecessarily expensive because the management thinks about
changes to organizational structures during the SAP implementation phase.
The SAP implementation is later deemed to have taken very long and been too expensive, but in
reality, it is the management decisions that have caused the extended time frame. Consultants, on
the other hand, are very happy.

A fellow consultant once told me that he was called to a customer who had already
gone live with SAP but was having problems with his Report Writer reports. The
customer wanted to evaluate his costs across the group, but the reports did not
allow him to do this. Unfortunately my colleague could not help him: the
customer had set up one controlling area for each company code, meaning
that he could only see the costs of this company code in the Report Writer
reports for this controlling area. This example shows how important it is to think about your
organizational structure in the SAP system thoroughly in advance.
However, to work with only one operating concern, all controlling areas and company codes must
work with the same fiscal year variant, generally K4 (here, the fiscal year corresponds to a calendar
year with four special periods). All company codes must also use the same chart of accounts.
Page 9 of 120
PA module is the most important module, when it comes to analysing the results of organisation.
In profitability analysis you basically collect the revenues from the sales order, the cost from the
production order, cost center or internal order and analyse their results.
The interesting part about PA is that when it collects the cost and revenues it also collects the
characteristics associated with costs and revenues and this is what makes it stand out.
For e.g. using PA you can find out the following:
 Profit of a certain product

 Profit of a certain product in a certain region
 Profit of a certain product in a certain region by a certain customer
 Profit of a certain product in a certain region by a certain sales person
 And the list can go on in depth
The aim of the system is to provide your sales, marketing, product management and corporate
planning departments with information to support internal accounting and decision-making.
Two forms of Profitability Analysis are supported: costing-based and account-based:
Costing-based Profitability Analysis: It is the form of profitability analysis that groups costs and
revenues according to value fields and costing-based valuation approaches, both of which you can
define yourself. It guarantees you access at all times to a complete, short-term profitability report.
Account-based Profitability Analysis: It is a form of profitability analysis organized in accounts and

using an account-based valuation approach. The distinguishing characteristic of this form is its use of
cost and revenue elements. It provides you with a profitability report that is permanently reconciled
with financial accounting.
You can also use both of these types of CO-PA simultaneously.
Page 10 of 120
1 Costing based PA
We will configure operating concern 7000 (Organisational structure of CO-PA). Controlling area FS00
is assigned to operating concern. Company code FS00 is attached to controlling area.
1.1 Define operating concern
An operating concern represents an organizational unit in your company. It is the valuation level for
Profitability Analysis (CO-PA).
Structure
You structure an operating concern by selecting characteristics and value fields

 Characteristics - You should ask yourself at what level your analyses should be performed,
such as the sales organization, region, product, or customer level.
 Value fields - You should ask yourself which values and key figures should be analysed, such
as revenues, sales deductions, costs, or quantities.
We can use user-defined and sap delivered structures and value fields.
Access the activity using the following navigation options:
SAP Easy Access Controlling -> Profitability Analysis -> Structures -> Define
Operating Concern -> Maintain Operating Concern
Transaction code KEA0
Page 11 of 120
The operating concern 7000 is created and activated, but before activating operating concern we
need to define or select characteristics and value fields for operating concern. So in below step we
will see how to configure characteristics and value fields.
Master Data in CO PA
 Currency of operating concern
 Master data in Profitability analysis
Page 12 of 120
 Profitability segment: Profitability Segment- object within Profitability Analysis to which

costs and revenues are assigned. A profitability segment corresponds to a market segment.
You can calculate the profitability of a profitability segment by setting off its sales revenues
against its costs. A profitability segment in an operating concern is defined by a combination
of characteristic values. Characteristics can be concepts that already exist in the R/3 System
(customer, product, sales organization, and so on).
Page 13 of 120
1.1.1 Maintain characteristics
What are the characteristics?

Characteristics are nothing but those aspects on which we want to break down the profit logically
such as a customer, region product, sales person etc.
Several essential and obvious characteristics are pre-defined automatically for every operating
concern; these are known as fixed characteristics.
In addition to fixed characteristics, up to 50 non-fixed characteristics can be added to an operating
concern.
Characteristics can be categorised in four types:
 Fixed characteristics: Some characteristics are automatically pre-defined in every operating

concern.
 Pre-defined characteristics: In addition to fixed characteristics, a number of other pre-
defined characteristics are available in the field catalogue and can be added to operating
concern.
 Copying characteristics from reference table: You can create characteristics by coping from
table.
 Characteristics created from scratch: You can create characteristics, by defining own logic to
derive values.
To derive values of these characteristics, it is necessary to create derivation rules or table lookup
rules unless they are readily available in the sender application (For e.g. in SD data flow to CO-PA,
fields on the billing document).
Characteristics derivation makes it possible for the system to automatically derive unknown
characteristics value (especially for user defined characteristics) if these are dependent on
characteristics whose values are known.
Page 14 of 120
Operating Concern -> Maintain characteristics
Click on display.
Following screen shows available and created CO-PA Characteristics in the TSQ system.
The characteristic region is not readily available, so we need to create it.
Page 15 of 120
Click on
Then click on
We are copying region characteristic from table KNA1
Page 16 of 120
Here you can see the field region is added.
Now we will create a user define characteristics.
Note: A user defined characteristics should begin with WW.
Page 17 of 120
Inputs:
Description: District (we are creating district characteristic)

Data type: Character
Length: 18
Check table: T25** (here system will create table which starts from T25 and the values of this
characteristics there)
We have created this characteristic from scratch (without any reference), so we need to update it
manually at the time of posting.
Page 18 of 120
Click on
After activating characteristics you can see the status of characteristic and generated table.
Characteristic district is created.
Page 19 of 120
1.1.2 Maintain value fields
Value fields are nothing but values associated with the above characteristics. Once you have defined
the characteristics then you need to determine, what are the values you would like to analyse for
e.g. sales, raw material cost, labour cost etc.
Value fields are only required in costing-based Profitability Analysis. These are the fields that contain
the currency amounts and quantities that you want to analyse in CO-PA.
Meaning of value fields → In costing-based Profitability Analysis, value fields store the base
quantities and amounts for reporting. Value fields can either be highly summarized (representing a
summary of cost element balances, for example) or highly detailed (representing just one part of a
single cost element balance).Unlike characteristics, there are no fixed value fields for a new
operating concern.
 Categories of value fields
Operating Concern -> Maintain value fields
Page 20 of 120
Click on display and you will be prompted with below screen.
Page 21 of 120
Like characteristics, we can also create value fields if required.
Click on to create user defined value fields.
Note: Value field should begin with VV and should 4 to 5 characters total.
Page 22 of 120
Click on activate.
You can see the value field is added
Page 23 of 120
1.1.3 Maintain operating concern
The operating concern is the main organizational unit in CO-PA, just as the plant is for MM, the
company code for FI, and the controlling area for CO.
The operating concern has a higher organization level than the controlling area; you can have an
operating concern that combines multiple controlling areas or just one controlling area.
Before you can execute some of the functions for Profitability Analysis (CO-PA), you first need to
specify the operating concern for which the function is to be performed and the type of Profitability
Analysis (costing-based or account-based) you wish to use.
Now that you’ve created the field catalog for characteristics and value fields, you must define the
operating concern and assign the characteristics and value fields to the operating concern.
In costing based we define operating concern by selecting the characteristics and the value fields to
be used in data structure.
Operating Concern -> Maintain operating concern
In this screen, define the operating concern as a four-character alphanumeric field, give it a
description, and indicate whether it is costing-based or account-based operating concern. You must
first define its attributes before creating the data structure for the operating concern.
Page 24 of 120
Page 25 of 120
Click on attribute tab
You can maintain operating concern currency.

By selecting company code currency, you can analyse reports of PA in company code’s currency
You can run any CO-PA report in the controlling area currency and also in the company code cur-
rency. You can also select to store profit center valuation currency; this currency will then be
available in the CO-PA reports.

By selecting additional currencies to be available in your operating concern,
you are considerably increasing the database size. Before selecting all
currencies for your operating concern, be sure that analysis in
different currencies is truly necessary for your organization.
Page 26 of 120
After defining the Attributes tab, return to the Data Structure tab, save the operating concern, and
click on the Create Data Structure button
Here we need to select characteristics available, into our operating concern.
Select the characteristics from left side and add it to right side.
Page 27 of 120
Now click on value field tab to add value fields in operating concern.
Once done with adding value fields and characteristics to operating concern, click to activate
the data structure.
The below message will generate
It is important to note here that no customising request get generated here. You have to transport
the setting through a separate transaction code called as KE3I.
Page 28 of 120
1.1.4 Assign controlling area to operating concern
When you transfer data to Profitability Analysis, the system derives the appropriate operating
concern from the controlling area, and derives the controlling area, in turn, from the company code.
In Customizing, therefore, you have to assign each operating concern at least one controlling area.
Generally, you assign several controlling areas.
We assign the controlling area FS00 to operating concern 7000
SAP Easy Access IMG -> Enterprise structure -> Assignment -> Controlling ->
Assign controlling area to operating concern
Transaction code
Page 29 of 120
Click on save
Page 30 of 120
1.1.5 Define Profitability Segment Characteristics
In this step, you specify whether a characteristic in CO-PA is used to create profitability segments.
Characteristics that are used to create profitability segments are available for the information
system and in planning, for example.
Characteristics that are not involved in the creation of profitability segments remain in their line
item in CO-PA.
Frequently occurring characteristics that rarely bear the same value (such as the sales order number
for a repetitive manufacturer) can thus be excluded from the creation of your profitability segment.
In this way, you can improve the performance of your profitability analysis considerably.
Page 31 of 120
1.2 Master data
When a value flows from SD, MM, CO, and FI to CO-PA, it will create a line item in the CO-PA tables.
The way you customize the master data will directly impact how the characteristics and value fields
are populated in the line items. Below is one example of a CO-PA line item.
You can see that the characteristics were populated automatically by the system in above snapshot.
You can change the behaviour of the assignments and also complete the missing ones. It’s very
important to have all characteristics filled for each posting so that the CO-PA reports you run for any
characteristic are complete.
In master data you’ll customize three important definitions:
Page 32 of 120
 Characteristic values
 Characteristic derivation
 Valuation
We’ll explore these in the following tabs.
1.2.1 Characteristics Values
When you created the field catalog for characteristics, if you defined any fields as custom
characteristics with own value maintenance, you now need to create the values for these
characteristics to be used in CO-PA. This means that the values for the characteristics will be
selected from values in a table you define.
SAP Easy Access Controlling -> Profitability analysis -> Master data ->
Characteristics values -> Maintain characteristics values
Transaction code KES1
For operating concern 7000, there is only one user defined characteristics available
Add values in region table by clicking on it.
Here simply mention the region names and then it is added into the region table which is created
when we activated this characteristics.
Now when you post any document you will have options of regions to select or you can simply enter
the name of region in profitability segment tab and system will validate that region with the
available region in table.
And with this you can have region wise data to explore the stats.
Page 33 of 120
1.2.2 Characteristics Hierarchy
In a characteristics hierarchy, you place the characteristic values for a single characteristic into a
hierarchical relationship.
In the information system, you can run analyses on a characteristics hierarchy.
A characteristics hierarchy is made up of nodes that can be posted to. These nodes are the
characteristic values. Furthermore, you can add to the hierarchical structure by creating nodes that
cannot be posted to.
Profitability segment characteristics
Transaction code KES3
Page 34 of 120
Select characteristics and enter the variant name, then click on create
In reporting section we will see the use of this derivation.
Page 35 of 120
1.2.3 Characteristics Derivation
When the system can’t determine a value for the characteristic, or if in certain cases, you want to
override what has been defined by the system, you can create a derivation step to determine the
characteristic values during posting of the CO-PA documents.
Note: Derivations are used only for characteristics. You can’t modify value fields using derivations.
Page 36 of 120
The CO-PA derivations are defined by five different types of derivation steps:
 Derivation rule - This rule is based on an “if-then” where you define a condition and a
derivation to use if the condition is met.
 Table lookup - The system will read a specified table that contains a key that must exist as a
characteristic, and then it will derive the field content from this table to the characteristic if
the characteristic has the same definition as the table field. It can be used, for example, to
derive a value from the material master table that is not present in the posting document.
 Move - This step will move a characteristic value or a constant to a target field.
 Clear - This step will delete the characteristic value.
Page 37 of 120
 Enhancement - If you want to create a custom program to define the characteristic

derivation, use COPA0001.
In below sections we will see the configuration for each characteristics derivation type.
1. Derivation Rule
SAP Easy Access Controlling -> Profitability analysis -> Master data -> Define
characteristics derivation
Transaction code KEDR
Click on the create button
Page 38 of 120
Select the derivation rule and hit enter
Page 39 of 120
You will be prompted with the above screen
In this screen, you’ll enter the step description and then build the derivation rule. In the Source
Fields area, you select the “If” condition for the derivation, and in the Target Fields area, you select
the “Then” field.
After defining the “If and Then” for the derivation rule, click on Maintain Rule Values button
to update the values for the Source Fields and Target Fields.
Page 40 of 120
Here you can see the rule, as per the rule, whenever the characteristic customer containing value
105 then the sales district characteristics will be updated as NORTH
Returning to the first customizing screen, two more tabs are left to discuss: Condition and Attributes.
In the condition tab, you can further restrict the derivation rule by defining user filters for the
derivation selection. The last tab, Attributes, shows additional options for the derivation rule.
With this condition, now the above derivation rule only be valid for IN country key
In the Attributes tab, you can define whether the system will issue an error when the derivation
doesn’t find a value to derive, define if the validation will have a starting date, and restrict the
validation by removing the from-to option.
Page 41 of 120

If you indicate that an error will be issued when no value is
found for the derivation, it will block the creation of the
CO-PA document, and consequently the FI document.
Make sure this is the desired outcome before
choosing this option.
2. Table lookup
Click on the create button
Select the table lookup and hit enter
Page 42 of 120
Enter the table name, from which table you want the value in COPA field.
Source Fields
In the below image we can see that following information has to be maintained:
 Origin (Table Name) and Origin Field (Field Name) from standard table
 Origin (CO-PA) and Origin Field (Field Name)
This information works as the basic condition, in the below example we can see the KNA1-
KUNNR as source in standard tables and COPA-KNDNR in CO-PA Tables. This means the value
in COPA-ARTNR is to be passed on to table KNA1 under field KUNNR to identify the
information under target field.
Target Fields
In the below image we can see that following information has to be maintained:
 Origin (Table Name) and Origin Field (Field Name) from standard table
 Origin (CO-PA) and Origin Field (Field Name)
This information under KNA1-KTOKD i.e. Customer account group is identified in the table
for KTOKD value available from source field and is passed on to KDGRP field under CO-PA.
Page 43 of 120
The functioning of other two tabs condition and attributes is same here also; in condition tab we can
assign more condition to apply this rule, e.g. making this rule valid only for specific sales org.
3. Move
Hit enter
Page 44 of 120
Here we are moving the product number to material number field
And as required condition tab is also available as this kind of rule cannot be applicable for everyone
you can make it specific to any smallest object. E.g. you can validate this rule to one customer also.
4. Clear
Select clear
Page 45 of 120
As the name suggest, it will remove the values from field region in COPA.
Page 46 of 120
1.2.4 Define and assign valuation strategy
Valuation is optional functionality in costing based CO-PA which is used to extract or calculate
additional information in CO-PA which is not available at the time of data transfer to CO-PA.
In costing based CO-PA, you can define valuation methods to add more information to your
reporting analysis. From billing documents, the system will automatically add the values that have an
accounting posting in FI, such as revenues, discounts and quantities, to CO-PA. In valuation you
determine which cost estimate the system will use for value fields that can’t be directly obtained
from SD. If it is not available in cost estimate, you can also determine the value using a costing sheet.
Here we define valuation strategies and assign them to a point of valuation. Since we want to use
material cost estimate for valuation, we will check the material costing field and specify the quantity
field.
In this activity we simply manipulate the data before it goes to COPA. As you can see in the above
screenshot, system is getting input from sales order like quantity of product, revenue and discount
Page 47 of 120
then as per the valuation strategy system will find out the cost estimate of the product then multiply
it with quantity and find out the COGS of the product.
If we have assigned any cost sheet to it then cost of various objects will also get calculated as per the
formulas in cost sheet. (In above screenshot we can observe that the sales commission is calculated
on the amount of revenue.
So to conclude this activity, system gets an input of quantity, revenue, product customer and so on…
On that input system calculates the COGS as per the components maintained in cost component
structure. Various cost as per the cost sheet get calculated as well.
SAP Easy Access Controlling -> Profitability analysis -> Master data -> valuation -
> Valuation strategies -> Define and assign valuation strategy
Transaction code KE4U
Create valuation strategy and give a name to it.
Page 48 of 120
If you want to valuate using a material cost estimate, select the field material costing. You also need
to specify the CO-PA quantity field you want to use for the valuation.
Whatever COPA value field you will assign here system will consider the quantity from that field only
to multiply the cost of product/material.
Here in above snapshot you can also see that you have an option of assigning costing sheet to
calculate the overhead/sales related fixed expenses.
If you noticed SAP has not close the window here, they gave us one more option and with this open
a door of unlimited options. You can probably guess, the option is we can also assign a user exit to
our valuation strategy to get desired result by using all ifs and buts.
This is also one of the functionality of COPA which makes it stand out among other alternatives.
Now assign this valuation strategy to point of valuation
Page 49 of 120
You might get an idea now that for each point of valuation and each record type you could have
different valuation strategy.
Page 50 of 120
If we put this in different words it would be like:
1. For Real time valuation of Sales order you can have specific valuation strategy with its own
functions.
2. For Real time valuation of Billing documents you can use different user exit than sales
order’s.
3. For periodic revaluation of project settlement you can use unique costing sheet.
4. And this list goes on and on……
Page 51 of 120
1.2.5 Define keys for accessing material cost estimate
Product cost planning is used to determine the planned cost of goods manufactured for a finished
product. We access these material cost estimate to valuate data in CO-PA.
In product cost planning, you know that you can create costing variants for different purposes, such
as standard costs, simulated new costs, new production lines, new BOMs, and so on. In CO-PA, you
can bring these costs to your profitability reports. To determine COGS, for example, the system will
use Sales Quantity × Cost Estimate; if you’ve defined the cost component split, you can also add that
to the CO-PA.
You can also select the released cost estimate effective for the goods issue posting date, the valid
cost estimate for the posting date, or the cost estimate valid for a specific period or date.
Alternatively, you can set in the costing key to read the cost estimate from a different plant than the
plant in the posting.
> Set up valuation using material cost estimate -> Define access
to standard cost estimates
Transaction code
Page 52 of 120
Here in this costing key we assigned costing variant, from where system will convey cost component
structure.
The idea here is to make you familiar with all the possibilities of the COPA. Probably you have come
to know now that we cannot cover all the aspects in one book but it is like formula of mathematics if
you know the formula then simply using it you can solve thousands of problem.
Now if you notice in above configuration screen of costing key, various options is in front of us, from
all of that we tried to choose or go ahead with the one which is used by most of the organisations.
After all it is a decision which is taken by coordinating with management. For e.g. here we have
selected that standard cost estimate should be transferred to COPA, but many organisation might go
with sales order cost estimate.
Going forward in same configuration you have to select the appropriate costing variant with costing
version.
You can have multiple costing keys for various organisational objects as per their need. We will see it
in upcoming pages.
Page 53 of 120
In costing variant, cost component structure is assigned where manufacturing cost of material is
tailored.
As COPA required the knowledge of product costing as a prerequisite and if you have that then this
is not hard science to understand the above snapshot and how material will be costed in product
costing. The costed value of material then flows to the COPA provided the check of the material
costing in valuation strategy should be applied.
Page 54 of 120
1.2.6 Assign costing key to any characteristics
Now that you’ve created the costing key to access the cost estimate and also for the Material
Ledger, you must now define how the material cost estimate will be accessed by the system. You
have three options to define the assignment
The steps
 Assign Costing Keys to Products
 Assign Costing Keys to Material Types
 Assign costing keys to any characteristics
In the first option, assign costing keys to products, you’ll make the assignment material by material.
This is mostly used when you need to define a different costing key for a specific material. We
recommend that you avoid using this option for all materials because you need to maintain the
customizing every time a new material is created. Use Transaction KE4H to assign the costing key to
individual materials.
Page 55 of 120
The second option, assign costing keys to material types, is most commonly used. We’ll describe
how to make the assignment using this option.
In cases where the product-dependent or material-dependent call-up of material cost estimates in

Product Cost Accounting is not flexible enough to meet your requirements, you can determine the
costing keys using ‘assign costing key to characteristics’.
These user-defined assignment tables let you assign costing keys separately for each point of
valuation, record type and plan version. In addition to these source fields, which are automatically
contained in each assignment table, you can specify up to three characteristics in your operating
concern as source fields for determining the costing key. Thus you can assign costing keys not only to
certain "products" or "materials types", but to any combination of values of any characteristics. For
example, you could define an assignment table to assign costing keys to specific combinations of
"company code", "plant" and "product group".
> Set up valuation using material cost estimate -> Assign costing
keys to any characteristics
Transaction code KEPC
Click on create
Page 56 of 120
Here we can see three default fields are there and we added two more characteristics there which
are company code and plant.
Click on to maintain values.
You can see here the costing key is assigned to the combination of point of sale, record type,
company code and plant.
Page 57 of 120
1.2.7 Assign value fields
To use the cost component split, you must have created a value field for each cost component. To
assign the cost component to the value fields, either use Transaction KE4R, or go to…
SAP Easy Access Controlling -> Profitability analysis -> Master data -> Valuation -
> Set up valuation using material cost estimate -> Assign value
fields
Transaction code KEDR
Here we assign cost component structure from product cost planning to the value fields of our
operating concern.
Press enter
Page 58 of 120
In the first column, you define the point of value; in the second column, you define the cost
component. You can split the fixed and variable costs from the cost components in different value
fields if you want, by selecting 1 – Fixed amounts, 2 – Variable amounts, or 3 – Sum of fixed and
variable amounts, and then maintaining the value field.
Page 59 of 120
Below graphic will summed up the above all
When a sales order or a billing document is posted, the system first checks whether valuation using
material cost estimates is active.
The type of costing that is to be used to calculate the cost of sales is specified in a costing key.
Costing keys can be assigned to different characteristic values. The cost components for cost of
goods manufactured from Product Cost Planning are assigned to value fields in CO-PA.
Page 60 of 120
1.3 Flow of actual values
In the preceding section, we discussed how to customize CO-PA to obtain values from cost estimates
and also how to use costing sheet to create additional values. Now you will see how to customize
CO-PA to directly import values from other SAP ERP components like SD, FI and CO.
CO-PA lets you assign all primary, profit-related postings and activities from the FI (G/L account
postings), MM (invoice receipts, purchase orders) and SD (sales orders) application components to
profitability segments.
Here we need to customize the following areas to transfer actual values from other components or
other CO subcomponents.
 Transfer of incoming sales order

 Transfer of billing document
 Order and project settlement
 Direct posting from FI/MM
 Settlement of production variances
 Transfer of Overhead
Page 61 of 120
1.3.1 Define number ranges for actual posting
Here you define a number range to be used for actual line item
SAP Easy Access Controlling -> Profitability analysis -> Flow of actual values ->
Initial step -> Define number ranges for actual posting
Transaction code KEN1
Click on intervals
Enter the intervals
Click on
Then click on maintain groups.
Page 62 of 120
You will be prompted with by default assignment.
Note:
For actual data as well as for planning data, Profitability Analysis (CO-PA) generally stores all values
as positive in the individual fields.
Revenues, sales deductions, and costs should therefore be entered into separate value fields.
The cost element categories should correspond to those recommended by SAP. This is the
prerequisite for producing a true representation of the +/- signs in the transfer of actual data to CO-
PA. SAP recommends the following cost element categories:
_ Revenues: Cost element category 11

_ Sales deductions: Cost element category 12
_ Costs: Cost element category 01
Page 63 of 120
1.3.2 Activate transfer of incoming sales order
You can valuate incoming sales orders (as expected revenues) and transfer them from SD to
CO-PA in order to obtain an early estimate of anticipated profits. By analysing these data
characteristic values, you can obtain early profitability results of your business. Consequently, you
can create reports that not only reflect the course of actual profits and contribution margins on the
basis of billing documents, but also allow you to analyse these developments on the basis of
incoming orders. (To analyse incoming orders, specify record type A in the report. To analyse billing
data, specify record type F.)
This function is especially useful when there is a long span of time between when you open the sales
order and when you actually bill the customer. It allows you to react early and appropriately if you
notice any unexpected developments.
Features:
When you create or change a sales order, the system automatically transfers line items to
Profitability Analysis in real-time. You can determine in which period the sales order should appear
in CO-PA.
 Period of the date of entry
This option means that the orders are updated under the same period in which they were created in
the system.
 Period of the planned delivery or the scheduled billing dates
This option means that the order appears in Profitability Analysis in the period of the planned
delivery or the scheduled billing date. It thus comes closer to reflecting the expected billing
information.
Orders are updated according as follows, depending on how they were activated.
Sales order:
Date entered: 01.09.2019
Material Quantity - 40 Delivery date Delivery Qty.

10.10.2019 15
10.11.2019 25
 Activate for date of entry
This creates one line item with the quantity “40 PCS” in Profitability Analysis in September.
 Transfer with date of delivery/scheduled billing date
This causes two line items to be posted in Profitability Analysis. One contains the quantity “15 PCS”
in period 010, while the other contains “25 PCS” in period 011.
If the sales order is changed (either its values or characteristics), the line items already posted to
Page 64 of 120
CO-PA is completely cancelled, and new line items containing the new characteristics and values are
transferred from the order.
Access the transaction by:
SAP Easy Access Controlling -> Profitability analysis -> Flow of actual values ->
Transfer of incoming sales order -> Activate transfer of
incoming sales order.
Transaction code KEKF
Here we activating incoming sales order with entry date, so the data will be transferred to COPA on
entry date of sales order.
Page 65 of 120
1.3.2.1 Assign value fields
In this section you make the basic settings required for posting data from the SD, FI, and CO
application components to Profitability Analysis. Which functions you need to carry out will depend
on your information requirements and on the applications you are using in your company.
Access this transaction by following menu path:
SAP Easy Access Controlling -> Profitability Analysis -> Flows of Actual Values ->
Transfer of Incoming Sales Orders -> Assign Value Fields
Transaction code KE4I
Click on choose button.
Page 66 of 120
You will be prompted with below screen.
Assign the condition types to value fields.
Generally CO-PA stores values in the table with a positive sign, leaving the negative sign to be
declared in the report form. Sometimes, it’s necessary to transfer the sign from SD. If it’s necessary
to transfer the sign, use the indicator in the last column shown in the assignment screen. This would
typically be used for reversals, credit memos, or returns.
Sign handling in CO-PA
For actual data as well as for planning data, Profitability Analysis (CO-PA) generally stores all values
as positive in the individual fields.
Negative values generally only occur for business transactions (such as reversals, credit memos or
returns) that revise the business transaction results when claims are processed or errors are
corrected.
Page 67 of 120
This is an important principle, particularly for the purposes of comparing actual values and planning
values, because the logic in the information system for calculating the contribution margin lines for
planning and actual values must be consistent.
How all this is related is depicted in the following graphic:
Page 68 of 120
1.3.2.2 Assign quantity fields
Here you assign all the quantity fields you want to transfer from the billing system to costing-based
CO-PA.
From SD, you can choose from the following options for quantity:
 ABSMG: Sales quantity
 BRGEW: Gross weight
 FKIMG: Billed quantity
 FKLMG: Billing qty in SKU
 KBMENG: Cumulative confirmed quantity in sales unit
 KLMENG: Cumulative confirmed quantity in base
 KWMENG: Order Quantity
 LSMENG: Required deliv. qty
 NTGEW: Net weight
 VOLUM: Volume
After defining which field you want to transfer as the sales quantity, you can then assign the CO-PA
field for the sales quantity.
Access transaction through below path:
Transfer of Incoming Sales Orders -> Assign Value Fields
Page 69 of 120
Assign the SD quantity fields to value fields.
Note:
It is possible to subsequently post existing sales orders to Profitability Analysis. This is particularly
useful if you implement CO-PA after SD and you wish to transfer sales orders, for example, for the
current or previous periods to CO-PA.
You execute the function for posting sales orders subsequently in Customizing under Tools _
Production Start-up _ Subsequent Posting of SD Documents.
Page 70 of 120
1.3.2.3 Reset value fields
Sometimes we have to raise credit memo only for the material price and not for the quantities so in
order to avoid the quantities getting reversed in CO-PA, you need to reset those value fields as well
as quantity fields in configuration.
Transfer of Incoming Sales Orders -> Reset value/quantity field
Transaction code KE4W
Now the credit memo raised with billing type G2 will not shows the quantities in CO-PA.
Page 71 of 120
1.3.2.4 Sales order Settlement profile
Here we will configure sales order settlement profile and assign PA transfer structure to it.
Settlement of production variance settlement -> Assign PA
transfer structure to settlement profile
Transaction code SPRO
Page 72 of 120
Assigned PA transfer structure to sales order profile.
Page 73 of 120
Now we will assign this sale order profile to requirement class.
Access transaction through below path
SAP Easy Access Controlling -> Product Cost Controlling -> Cost Object
Controlling -> Product Cost by Sales Order-> Control of Sales-
Order -> Check Requirements Classes
Transaction code SPRO
The requirement class is further assigned to requirement type, which is assigned to item category in
our case.
Page 74 of 120
1.3.3 Transfer of billing document
When billing document data is posted, the online transfer function transfers the values directly into
Profitability Analysis. In the process, it uses the record type F to generate a line item automatically in
Profitability Analysis for each item on the billing document.
The system transfers all the characteristics defined in Profitability Analysis and contained in the
billing document, along with the customer and product numbers, from the document to the CO-PA
line item.
If the system recognizes an error (such as in characteristic derivation) while posting billing data to
Financial Accounting or Profitability Analysis, it posts the billing document in SD anyway, but updates
neither Financial Accounting nor Profitability Analysis.
1.3.3.1 Assign value fields
All revenues, sales deductions are defined as condition type in SD. In this step you assign this step
you assign these conditions type to the corresponding CO-PA value fields.
Transfer of billing document-> Assign Value Fields
Page 75 of 120
1.3.3.2 Assign quantity fields
This activity has been already performed in 1.3.2.2 node.
Page 76 of 120
1.3.4 Maintain PA transfer structure for direct posting FI/MM
You can also work with a direct account assignment to Profitability Analysis. Costs are then directly
assigned to a value field, not first posted on an account assignment object (e.g., an internal order or
a cost center). This makes sense for cost elements such as inventory differences; perhaps you want
to analyse them by material in Profitability Analysis, but the material information gets lost when
costs first get posted on a cost center or an internal order and then are transferred to Profitability
Analysis.
Here you define the PA transfer structure which is used to post costs and revenues directly to
profitability segments. You specify how the cost elements are to be defined to the CO-PA value
fields.
Access the transaction by:
Direct posting from FI/MM -> Maintain PA transfer structure for
direct posting
Transaction code KEI2
Page 77 of 120
In below step, we will assign source cost elements to each line.
Define which value fields should be updated.
Page 78 of 120
Do the same for sales deduction and other secondary costs.
1.3.4.1 Automatic account assignment (OKB9)
Automatic postings created in MM and FI can be passed to CO-PA by means of automatic

assignment to profitability segment.
In profitability analysis documents are updated to the profitability segment generated according to
the characteristics values found in the corresponding financial accounting document.
Direct posting from FI/MM -> Automatic account assignment
Transaction code OKB9
Page 79 of 120
Page 80 of 120
1.3.5 Order and Project settlement
In the SAP System, you can settle internal orders (component CO), sales orders (component SD) and
projects (component PS) as well as production orders and run schedules with production cost
collectors (component PP) to profitability segments. These objects are used for various purposes
relevant to Profitability Analysis.
The steps we’ll now cover apply to order and project settlement, direct posting to FI/MM, and
settlement of production variances.
When variances are calculated in cost object controlling, on production order, you transfer these
variances – differentiated by cost element and variance category – to value fields in CO-PA.
Order and project settlement -> Define PA trf struc. For
settlement
Transaction code KEI2
After creating the PA transfer structure, mark the recently created one here A1, and double- click on
Assignment lines in the left side of the screen to create the lines of assignment.
Page 81 of 120
If you want to split the source costs to different value fields in CO-PA, you can create assignments for
each cost element or use groups of cost elements.
If you mark the field Qty billed/delivered, you can transfer production quantities to a quantity value
field in CO-PA.
Select one line in the right side of the screen, and double-click on source in the left side of the
screen, which will then bring you to the screen to define the source cost elements.
Page 82 of 120
In this screen, you define the range of cost elements or a cost element group to be the source of the
amounts to be transferred. You may also define if it will transfer all costs/revenues or variances on
production orders. If you mark to transfer variances on production orders, you must also define the
variance category you want to transfer by choosing from the following options:
 PRIV: Input Price Variance

 QTYV: Input Quantity Variance
 RSUV: Resource-Usage Variance
 INPV: Remaining Input Variance
 MXPV: Mixed-Price Variance
 OPPV: Output Price Variance
 LSFV: Lot Size Variance/Fixed-Cost Variance
 REMV: Remaining Variance
 SCRP: Scrap
After defining the source cost elements, double-click on Value fields on the left side of the screen to
define the receiver value fields in CO-PA
Click on New Entries, and in the right side of the screen, add the new value field. You can add up to
three value fields for each assignment: one for fixed amounts (1), one for variable amounts (2), and
one for the sum of fixed and variable amounts (3). If you use (3), only one value field is needed.
You must repeat this process until you’ve filled all assignment lines with a source and a value field.
Page 83 of 120
Page 84 of 120
1.3.5.1 Assign PA transfer structure to settlement profile
Now that you’ve created the PA allocation structure, you’ll need to assign it to a settlement profile
when you want to settle from orders, projects, or production orders.
Settlement of production variances -> Assign PA transfer
structure to settlement profile
Transaction code OKO7
Page 85 of 120
Understand the logic of settlement with below graphical image.
Page 86 of 120
1.3.6 Transfer of Overhead
When we previously discussed costing sheets, you saw that you can create a costing sheet to
allocate overhead values, so that for every CO-PA document, the system will accrue a value for
overhead. As an alternative to this approach, you can also transfer using an allocation from CO-CCA
to CO-PA.
The most commonly used allocation is the assessment from CO-CCA to CO-PA.
Cost center costs are always transferred to one profitability segment:

 Production cost centers :
These cost centers are first credited during production as the activities they perform (such as
machine hours and assembly hours) are required. The amount of the credit is based on the
quantities confirmed by production and on the activity prices (such as machine hour rates)
usually calculated in cost center planning. The balances that are thus achieved - or the over
absorption/under absorption remaining for the production cost centers due to the difference
between credits and actual costs - are transferred en bloc in periodic profit analysis to those
profitability segments in CO-PA that caused those costs.
 Sales and administration cost centers :
Many companies transfer the costs from administrative cost centers to CO-PA en bloc instead of
allocating them to cost objects. This reduces the period results of the individual divisions,
product groups, or business areas.
Here we define actual assessment cycles for allocation actual costs from cost center to profitability
analysis.
Transfer of Overheads -> Access cost center cost -> Define
structure of cost center Assessment
Transaction code KEU1
Press enter
Page 87 of 120
In this screen, you need to define in the Indicators section if you want to split the costs into fixed and
variable or not (overall costs) by selecting either 1 – Unsplit Costs (Overall Costs) or 2 – Split costs
(separated in fixed and variable costs) for the sender select type. In the Preset Selection Criteria
section, you must also select the CO Area to identify whether the assessment is for costing based or
account-based CO-PA.
You can choose to either use a secondary cost element for assessment (category 42) or use an
allocation structure, where you can define assessment cost elements for a group of sender cost
elements.
Page 88 of 120
Define the sender and receiver values on the second tab
Page 89 of 120
Click on the receiver tracing factor to decide the percentage for assessment
Page 90 of 120
Here 100 percent of the cost recorded in cost center will be transferred to mentioned value fields as
per this assessment rule.
Page 91 of 120
1.3.7 Activate profitability analysis
Here you activate the interface to the profitability analysis for the controlling area FS00.
Check the controlling area settings before activating the indicator.
Page 92 of 120
Activate the profitability analysis through following navigation path:
Activate Profitability analysis
Transaction code KEKE
Page 93 of 120
1.4 End user process – Costing based PA

1.4.1 Direct posting from FI
In this activity we will post customer invoice through FB70
SAP Easy Access SAP easy access -> Accounting -> Financial accounting ->
Account Receivable -> Invoice
Transaction code FB70
In above transaction, we are posting invoice with profitability segment.
Page 94 of 120
In Profitability segment we have only entered the value of country let’s see what characteristics
flows to CO-PA
Page 95 of 120
To see the CO-PA document execute transaction KE24.
SAP Easy Access SAP easy access -> Accounting -> Controlling -> Profitability
analysis -> Actual posting -> Display line item
Transaction code KE24
Enter the required values in selection parameter and execute.
Double click on the line item.
Page 96 of 120
We can notice here that no other characteristics than country derived automatically.
As per analysis, we cannot derive characteristics like customer, automatically through any kind of
derivation rule at the time of posting from FI. The argument behind that is profitability segment is
assigned to revenue line item and it is not possible to find out the customer for that particular line
item.
Hence we have to update all required characteristics manually at the time of FI posting.
Page 97 of 120
1.4.2 Transfer from sales order
Create a MTO sales order
SAP Easy Access SAP easy access → Logistics → Sales & Distribution → Sales →
Order → Create
Transaction code VA01
Go to the condition tab
Page 98 of 120
Here the requirement type is KEKT and to this requirement type the requirement class 042 is
assigned.
And in requirement class we have assigned settlement profile, which will called at the time of sales
order settlement.
Page 99 of 120
And if we further drill down to the settlement profile, we can see the PA settlement structure
assigned to the settlement profile.
Here we can see that the PA transfer structure XU is assigned to the settlement profile SOSET, but
we can also change it from sales order.
Page 100 of 120

Click on the settlement rule
Now if you want to see through which structure the cost is going to settle down in COPA →
Click on Goto → Settlement parameter
Page 101 of 120

We can change this parameter manually for this sales order
Save the sales order.
Page 102 of 120

To see the generated COPA document relevant to sales order execute transaction KE24
Click on execute button.
Here we can see two documents are generated, one is in operating concern currency and one is in
company code currency.
Page 103 of 120

Click on value fields tab to see the flowed values.
Page 104 of 120

Here we can see the values are updated in value fields which are assigned to the condition types.
But this report does not provide clear picture of the profitability, so we need to develop a report
that will suit to our requirement.
How derivation rule works →
If you recall the chapter 1.2.4 Derivation rule, where we have maintained several derivation rules.
We will test one rule here, in order to know how the functionality works.
Derivation rule set:
Page 105 of 120

As per this derivation rule, for customer 104, sales district NORTH will automatically populate in SAP
Sales order:
Page 106 of 120

Sales order saved.
Now if we open the CO-PA document of sales order, we can notice the sales district NORTH is arrived
as a characteristic via derivation rule. (Refer below Figure)
Page 107 of 120

Page 108 of 120

1.5 Information system
The CO-PA information system is mainly created by the user. SAP ERP provides one standard line
item report each for actual and plan, Report KE24 and Report KE25, respectively. For all other
reporting needs, you’ll need to build your own CO-PA reports using the Report Painter functionality,
in which you define a form and use it to create a report.
The advantage of creating your own reports is that you can create the result analysis lines as you
wish, depending on your needs. These custom reports provide multidimensional analysis of both
actual and planning data, using the characteristics you’ve defined in your CO-PA.
When defining your profitability report, you specify the different analysis criteria mainly by selecting
characteristics and value fields.
Execute the transaction code KE31
Page 109 of 120

Enter the report name and click on create
Press enter or click on highlighted area.
Page 110 of 120

Select the characteristics based on which you want to see report.
You find all the characteristics of the operating concern in the Characteristics tab page. In this tab
page, you can select the ones that you want to analyze. The characteristics that you select then form
the different dimensions of the "data cube" that you wish to analyze. If characteristic groups have
been defined for the operating concern, you can select one of those available in the Characteristic
group field. If you enter a characteristic group, the system only displays the characteristics in that
group, instead of all the characteristics of the operating concern.
Note: The amount of data that is called up for processing by the report is determined by the number
of characteristics selected and by which characteristics you select.
Then click on key figures tab and select the key figures.
You find all the value fields of the operating concern in the Key figures tab page. In this tap page, you
can select the ones that you want to analyze. If key figure schemes have been defined for the
operating concern, you can select one of those available in the Key figure scheme field. In this way,
the calculated key figures for the selected key figure scheme are added to the list of value fields.
Note: It is not always necessary to choose key figures for your report. If you are defining a form
report that uses a form for which key figures have already been specified, the Key figures tab page is
not displayed and you cannot select any key figures here.
Page 111 of 120

And then save the reports
Now execute the report from transaction code KE30
Click on execute button.
Page 112 of 120

Let’s try this in your system
How system fetch data from CO-PA tables? → explain in below graphic.
Page 113 of 120

1.6 Tools
When customizing the different areas for CO-PA you’ll notice that for some, the system creates a
transport request and for others not. For example, in the operating concern definition, the system
won’t ask for a transport request, but for the section valuation, it will. Next, you’ll see how to
transport the operating concern settings.
1.6.1 Transport
The transport process in CO-PA differs from other CO subcomponents because it requires a user
action to be transported. To transport the operating concern definition and other areas for which
you need to create a transport request
SAP Easy Access Controlling -> Profitability analysis -> Tools -> Production
startup -> Transport
Page 114 of 120

In this screen, you can select which object from the operating concern you want to transport. If you
mark Operating concern, you can select all operating concern customizing to be transported at one
time. The system will ask for two transport requests—one for customizing and the other for the
workbench.
Select the operating concern you want to transport, and then click on Execute. The system will
prompt a screen to define which operating concern customizing option you want to be included in
the transport request.
Page 115 of 120

Select the customizing areas you want to transport, and then save.

Be careful when sending the transport request to a production environment. It will overwrite
any existing customizing in the receiving environment. Because the transport also
creates database tables and creates relationships between other SAP ERP
components, we strongly recommend that you transport to a production
environment at a time when there are no other users in the system. After transporting the operating
concern customizing, you must then activate it in the receiving environment by using Transaction
KEA0.
If you’ve activated CO-PA in a production environment with data already in it, it’s possible to import
the old data to the newly activated CO-PA component.
1.6.2 Subsequent posting of SD Documents
SAP ERP provides a tool that you can use to bring existing SD documents to the CO-PA tables even if
they were created before the CO-PA activation. The system will import SD data according to the
current CO-PA customizing using the valuation strategy defined in the CO-PA customizing.
Page 116 of 120

SAP Easy Access Controlling -> Profitability analysis -> Tools -> Production
startup -> Subsequent Posting of SD Documents
Transaction code KE4S
Enter the selection options for the documents you want to import and run.
If you defined a range where the system had already posted documents to CO-PA, it will post only
the documents that are not already posted in the component.
Page 117 of 120

1.7 TABLES
The concepts line item and profitability segment are essential for understanding how data is stored
in CO-PA. A line item can be compared, for example, to an item in a billing document from the SD
component. The combination of characteristic values stored in a line item is what defines the
particular profitability segment to which the line item must be posted.
There is the table CE1xxxx for actual line items (where xxxx = operating concern), which contains all
the data at the most detailed level. Planned line items are stored in the table CE2xxxx.
There is also the segment table CE4xxxx, which is located at a higher level. It is used to assign
segment numbers to each combination of characteristic values. For the first summarization to be
performed, at least the document number and the billing item are hidden. The characteristics that
were deactivated from use in the profitability segment in Customizing are also hidden. Segment
table CE4xxxx should therefore be optimized for processing data within Profitability Analysis, such as
for the information system. Table CE4xxxx_ACCT contains external account assignment information
as well as the characteristics for CE4xxxx and serves as the "interface" to other applications.
Example
You have invoiced three documents for customer 0815. The first posting occurs in March (posting
period 003), and revenues of 100 DEM and 200 DEM are posted respectively for the products ART1
and ART2. The second posting occurs in April. Revenues of 400 DEM and 800 DEM are posted
respectively for the products ART1 and ART3. The third posting also occurs in April. Revenues of
1600 DEM and 3200 DEM are posted respectively for the products ART1 and ART3. When the line
Page 118 of 120

items are posted, the segment table and segment level are updated, producing the following table
contents:
Segment table CE4***

Segment number Customer Product Number Additional Char
0047 0185 ART1 ….
0048 0185 ART2 ….
0049 0185 ART3 ….
Segment Level CE3***

Segment number Period Revenue Additional value
0047 03.2020 100.00 ….
0048 03.2020 2000.00 ….
0049 03.2020 200.00 ….
Line Item table CE1***

Segment Additional Additional
number Period Document item customer Product chars Revenue value fields
0047 03.2020 150015 010 815 ART1 …. 200 ….
0048 03.2020 150016 010 816 ART2 …. 300 ….
0049 03.2020 150017 010 816 ART3 …. 2000 ….
This brings us to an end.
Page 119 of 120

Takeaway
Reporting is a most important function of an ERP system. As it provides information for decision
making and operational analysis. It is also important to gather the relevant information on markets
and products to develop strategic goals. SAP COPA module offers the all necessary tools to meet all
business needs of reporting and analysing data for critical business decisions.
Summary
Then end result of most ERP functions is extracting and evaluating data. These chapters discussed in
this book has been learned and identified in the lifetime career. I hope this book has provided you all
the necessary knowledge and skills that you are looking for. Do submit your honest feedback on the
platform from where you have brought this book.
Page 120 of 120

SAP CO-PA Profitability-Analysis

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

SAP CO-PA Profitability-Analysis

Uploaded by

Copyright:

Available Formats

Controlling – Profitability Analysis

In SAP ECC 6.0

Step by step guided to learning and understanding

Copyright © by SAP College

The book philosophy

Ray Ozzie – Chief software architect at Microsoft Corporation.

1.6.1 Transport ..................................................................................................................... 114

The Intent and Purpose of CO-PA

1. Which customer do I earn the most money from?

Profit Center Accounting (EC-PCA) Profitability Analysis (COPA)

The profit-relevant data is displayed by manufacturing).

Customer+ Product= Market Segment (niche

CO-PA Organization Structure

The Operating Concern

Common error in practice

Common error in practice

For e.g. using PA you can find out the following:

 Profit of a certain product

Two forms of Profitability Analysis are supported: costing-based and account-based:

Account-based Profitability Analysis: It is a form of profitability analysis organized in accounts and

You can also use both of these types of CO-PA simultaneously.

1.1 Define operating concern

You structure an operating concern by selecting characteristics and value fields

Access the activity using the following navigation options:

Transaction code KEA0

 Currency of operating concern

 Master data in Profitability analysis

 Profitability segment: Profitability Segment- object within Profitability Analysis to which

1.1.1 Maintain characteristics

What are the characteristics?

Characteristics can be categorised in four types:

 Fixed characteristics: Some characteristics are automatically pre-defined in every operating

Access the activity using the following navigation options:

Transaction code KEA5

The characteristic region is not readily available, so we need to create it.

We are copying region characteristic from table KNA1

Here you can see the field region is added.

Now we will create a user define characteristics.

Note: A user defined characteristics should begin with WW.

Description: District (we are creating district characteristic)

Characteristic district is created.

1.1.2 Maintain value fields

 Categories of value fields

Access the activity using the following navigation options:

Transaction code KEA6

Click on display and you will be prompted with below screen.

Like characteristics, we can also create value fields if required.

Click on to create user defined value fields.

You can see the value field is added

1.1.3 Maintain operating concern

Access the activity using the following navigation options:

Transaction code KEA0

Click on attribute tab

You can maintain operating concern currency.

Common error in practice

click on the Create Data Structure button

Here we need to select characteristics available, into our operating concern.

1.1.4 Assign controlling area to operating concern

We assign the controlling area FS00 to operating concern 7000

Access the activity using the following navigation options:

1.1.5 Define Profitability Segment Characteristics

1.2 Master data

In master data you’ll customize three important definitions: