SAP CO-PA Profitability Analysis: Operating Concern, Characteristics, SD Billing, PA Assessment and KE24 Line Items

The final part of the SAP CO overview covers CO-PA (Profitability Analysis). Where the financial statements show the profit of the company as a whole, CO-PA answers a narrower question: which product, sold to which customer, through which channel, produced the profit.

Note: data structures, screens, T-codes and reports vary by SAP version and by how each company operates CO-PA.

1. CO-PA splits profit by characteristic

The top-level organizational unit of CO-PA is the Operating Concern. It defines the characteristics and value structure used for analysis. The combination of characteristic values forms the analysis unit, the Profitability Segment, on which P&L items such as revenue, discounts, cost of goods sold and selling expenses are collected.

Typical characteristic Example
Product Product, product hierarchy
Customer Customer, customer group
Sales organization Sales organization
Distribution channel Distribution channel
Plant Plant
Company-specific Region, country, brand and other items the company manages

2. SD billing is the main data source for CO-PA

The standard sales flow runs Sales Order → Delivery → Goods Issue → Billing → Payment. FI posts accounting documents for inventory, cost of goods sold, revenue and receivables at goods issue and billing. In CO-PA, the billing data is the center: revenue, cost of goods sold and the characteristic values (customer, product, distribution channel) are linked to the profitability segment.

Sales step FI effect CO-PA effect
Sales Order – Characteristic values originate here
Delivery / Goods Issue Inventory and cost of goods sold –
Billing Revenue and receivable Revenue, cost of goods sold and characteristic values posted to the profitability segment
Payment Receivable cleared –

When a CO-PA value differs from what was expected, the PA configuration is only one place to look. The characteristic values on the sales order and billing document, the material and customer master, the account assignment and the derivation rules have to be checked together.

Slide reference: main SD billing fields mapped to CO-PA characteristic values.

3. Cost that is not directly attributable is allocated by PA Assessment

Not every cost is linked to a product or customer at the point of sale. Cost collected on cost centers, such as marketing, head-office support and shared selling and administrative expenses, can be allocated to CO-PA on an appropriate basis.

PA Assessment element Definition
Sender Cost center and cost element where the cost is collected
Receiver Combination of CO-PA characteristics: product, customer, region
Allocation basis Revenue, quantity, number of transactions, fixed percentage
Result item Cost element or P&L item shown on the receiver side

The allocation basis determines what the result means. Whether the basis can be explained in business terms matters more than whether the system can calculate it.

4. Start from the line item and work up to the profitability report

When a profitability figure looks wrong, do not stop at the summary report; trace the source transaction from the line items. The training material uses KE24 as the example of the PA actual line item report.

Step Analysis activity
1 Locate the unusual product, customer or period in the final profitability report
2 Display the line items for that characteristic combination (KE24)
3 Separate the records by origin: billing, FI document, assessment
4 Verify characteristic derivation and value mapping
5 Correct master or transaction data in the source module where needed

Slide reference: profitability report comparing plan and actual by product, customer and distribution channel.

5. Points to check when operating CO-PA

Area Check point
Characteristics Too many characteristics increase data volume and operating complexity
Master data Product and customer master quality directly determines analysis quality
Recognition Timing of revenue and cost of goods sold recognition, and the valuation basis, have to be defined clearly
PA Assessment The person in charge has to be able to explain and reproduce the allocation basis
Closing policy Decide how the difference between standard and actual cost is reflected in CO-PA
Traceability Design the final report and the line-item trace path together

6. Series summary

This series covered the big picture of SAP CO in four steps.

Part Topic
1 FI and CO, organizational structure, data flow
2 Overhead management with cost centers and internal orders
3 Product cost linking standard cost and actual cost
4 CO-PA profitability by product, customer and distribution channel

SAP CO is a framework that links costs and revenues to their responsibility units and analysis views. Allocation, closing and profitability analysis are only reliable when the master data and source transactions are accurate.

This is part 4 of a 4-part SAP CO overview.

Comments

Post a Comment

Popular posts from this blog

SAP S/4HANA Table Reference — Tables I Actually Query, by Topic

SAP tables I actually queried while building custom reports and running end-to-end tests on an S/4HANA sandbox, grouped by topic. Updated continuously as development goes on. Each table: Table / Description / Key fields / T-codes / Used in our custom reports. Last updated: 2026-08-13 1. CO — Allocation Cycles (Assessment / Distribution) Table Description Key fields T-codes Used in our reports T811C Allocation cycle header ※ Distribution = ALART 'V', assessment = ALART 'U'. Classic CO-OM uses TAB='CCSS' TAB / CYCLE / SDATE KSU3, KSV3 ZCO0040 (allocation cycle report), ZCO0041 (distribution cycle detail) T811S Cycle segments ※ SRULE (sender rule) / RRULE (receiver rule) / SPERCENT / RCDATA (variable portion type) / NEGTEST (negative tracing factors — stored value differs from the screen code) TAB / CYCLE / SDATE / SEQNR KSU3, KSV3 ZCO0040, ZCO0041 T811K Selection criteria per segment ※ SETKIND: 0=cycle, 1=sender control, 2=sender, 3=rece...
Read more

Production Order Variance Calculation KKS1 — Fixing KV031 and KV011, and What Lands in COSB

In the last post on cost center variance calculation (KSS1) I noted that the similarly-named KKS1 is a different animal. This is that post: production order variance calculation. I hit two errors on the way in, so we start with their causes and fixes, then verify — by comparing the database before and after — exactly what gets stored where. Environment: controlling area JNC2, plant JNC2, period 2026/008, KRW, three production orders. ※ Screens, menus, and settings may differ depending on your SAP release and system configuration. Two errors before it would even run KV031 ("no target cost version") — version 0 itself existed. What was empty was the variance variant for orders (AWVAO) in OKV6: only the cost-center one (AWVAS) was maintained, which is why KSS1 worked fine while KKS1 refused. Same OKV6 screen, different column. KV011 is an order status problem. Order 1004916 got its goods receipt and final delivery on August 2 — run KKS1 for period 007 and, as of that pe...
Read more

Modern ABAP Syntax Notes — Patterns and Pitfalls from Real Development

ABAP syntax actually used while developing our custom Z reports, organized by topic. Examples come from working sources, together with the pitfalls we actually hit. Structure: syntax item → explanation → example code. Last updated: 2026-08-13 1. Data Declarations and Types ▷ Inline declarations DATA(...) / @DATA(...) — Declare and assign in one statement. SELECT result tables land directly in @DATA(lt_...) — the structure is derived from the SELECT list SELECT matnr, maktx FROM makt INTO TABLE @DATA(lt_makt) WHERE spras = @sy-langu. DATA(lv_qty) = ls_stpo-menge * iv_losgr / lv_bmeng. LOOP AT lt_mat INTO DATA(ls_mat). " loop variable inline too ENDLOOP. ▷ FIELD-SYMBOLS / ASSIGNING — Modify internal table rows in place without copying. ASSIGN COMPONENT lets you pick the column name at runtime (used for dynamic logic such as auto-hiding empty columns) LOOP AT gt_list ASSIGNING FIELD-SYMBOL(<ls_list>) WHERE typps = 'M'. <ls_list...
Read more