Written by Takanashi — Paddy & Water Inc. / Finance & Controlling

Part Two: Cost Center Accounting, Profit Center Accounting, and Profitability Analysis

Design, Transactions, and Configuration of CCA, PCA, and CO-PA

June 2026

Introduction: Management That Cannot See “Where It Is Making Money”

Regardless of whether a company operates in manufacturing, services, or retail, many organizations face the problem of “revenue is growing but profit is not increasing” or “we don’t know which business, product, or customer is generating profit and which is eroding it.” The profit and loss statement in financial accounting shows only the profit or loss of the “company as a whole” and does not visualize the profit structure by business division, product line, or customer segment.

The three pillars of SAP Management Accounting (CO) — Cost Center Accounting (CCA), Profit Center Accounting (PCA), and Profitability Analysis (CO-PA) — solve this problem. The three functions work in a mutually complementary manner, providing a unified, three-layer body of management accounting information: “managing indirect costs by organizational unit (CCA),” “managing the full profit and loss and balance sheet by business segment (PCA),” and “managing contribution margin across cross-dimensions such as product × customer × region (CO-PA).” This article systematically explains these three functions from both the transaction operation and SPRO configuration perspectives.

Part One: Cost Center Accounting (CCA)

1. What Is Cost Center Accounting

The Concept and Role of the Cost Center

A cost center is the “unit for collecting expenses” in SAP Management Accounting. It is set up as a management unit corresponding to the organizational structure of the company (manufacturing department, administrative department, sales department, IT department, etc.), and it collects and manages the expenses incurred at each center (personnel costs, equipment costs, supply costs, outsourcing costs, etc.).

The purpose of cost center management is “to clarify who is responsible for which expenses (the Cost Center Manager) and to run the cycle of budget management, actual performance management, and variance analysis.” By visualizing who is responsible for which costs, how actual results deviate from the plan, and what the causes are, the target and effect of cost-reduction activities can be managed quantitatively.

Cost Center Hierarchy and the Standard Hierarchy

Cost centers are organized into a tree structure called the “Standard Hierarchy.” One standard hierarchy is defined per controlling area, and it has a hierarchical structure such as “Company → Business Division → Manufacturing Division → Plant → Manufacturing Department 1 → Manufacturing Section 1.”

• The standard hierarchy is defined using OKEON (Change Cost Center Standard Hierarchy) or in SPRO. Aggregation and reporting using the hierarchy make it possible to check expenses at various levels of granularity, such as by department, by plant, or by business division.

• Cost center groups (KSH1/KSH2): Separately from the standard hierarchy, cross-cutting “groups for analytical purposes” (for example, a “Direct Manufacturing Department Group” or an “Administrative and Indirect Department Group”) can be defined. Using groups in reports and cycle settings enables flexible aggregation and allocation.

Cost Types and Expense Categories

Cost centers are assigned a “Cost Center Category.” The category is selected from options such as “Production,” “Service,” “Administration,” and “Sales,” and it classifies the nature and function of the cost center. This category determines the assignment of activity types and the direction of allocation.

2. Transaction Operations for Cost Center Accounting

Creating and Managing Master Data

Operation Walkthrough: KS01 Create Cost Center

• Launch KS01 (Create Cost Center). Enter the controlling area, the cost center code (e.g., CC1001), and the validity start date, then press Enter.

• Basic Data screen: enter the “name, description, standard hierarchy node to which it belongs, cost center category (production/service/administration, etc.), person responsible (the responsible manager), and currency.” The “person responsible” is used for authorization management and email notifications.

• Validity Period: a cost center is master data with a validity period. If an organizational change spans fiscal years (a department merger or split), a new version is created with a new validity period. Old data is retained as history.

• KS02 (Change Cost Center) and KS03 (Display Cost Center): changes to and display of existing centers are performed with the same operations as KS01.

Operation Walkthrough: KL01 Create Activity Type

• KL01 (Create Activity Type): defines the type of service (activity) provided by a cost center. Examples: “MAH01: Machine Hours (unit: h),” “LAB01: Direct Labor Hours (unit: h),” “SETUP: Setup Time (unit: h).”

• An “activity type category” (1: manual entry, 2: indirect determination, 3: manual allocation, 4: indirect allocation) is set for each activity type. Activities entered directly in production order confirmation (CO11N) use category 1.

• By linking activity types to allocation settings such as OKTZ, planned cost, actual cost, and variance analysis are performed for each activity type.

Cost Planning and Activity Quantity Planning

Operation Walkthrough: KP06 Enter Cost Planning

• KP06 (Planning Primary Cost Elements): enter planned costs by specifying the version (0), period (1–12), fiscal year, cost center, and cost element (G/L account).

• Enter “Fixed Plan Costs” and “Variable Plan Costs” on a monthly basis in grid format. Example: personnel costs ¥2,000,000 (fixed) and supply costs ¥200,000 (variable) per month.

• Variable costs can also be entered as “cost per unit of activity quantity” (in conjunction with KP26). This forms the basis for the “Flexible Budget,” in which the variable cost portion is automatically adjusted when the activity quantity changes.

Operation Walkthrough: KP26 Enter Activity Quantity Planning

• KP26 (Plan Activity Quantities): enter the “annual planned activity quantity” for each cost center and activity type. Example: Manufacturing Department 1, machine hours, planned activity quantity = 6,000 hours/year.

• KP27 (Display Planned Activity Price): the “Planned Activity Price = Planned Cost ÷ Planned Activity Quantity” is automatically calculated from the planned cost in KP06 and the planned activity quantity in KP26. This price is used in the cost estimate roll-up in CK11N.

Allocation Cycles: Transferring Indirect Costs Between Organizational Units

Expenses collected in the cost centers of indirect departments (maintenance, IT, quality control, etc.) are transferred to manufacturing department cost centers or CO-PA segments through “Allocation Cycles.” There are two allocation methods: “Assessment” and “Distribution.”

Assessment: KSU1/KSU5

• KSU1 (Maintain Actual Assessment Cycle): defines the allocation cycle. The cycle sets a “Sender: the cost center from which allocation originates” and a “Receiver: the cost center or CO-PA segment to which allocation is made.”

• Tracing Factor: sets the basis for determining the allocation ratio. Choices include “Fixed Percentage (e.g., Department A 20% / Department B 50% / Department C 30%),” “Plan Activity Quantity ratio,” “actual cost ratio,” and “Statistical Key Figures (e.g., headcount, floor area).”

• Assessment aggregates cost elements (G/L accounts) into an “Assessment Cost Element (normally a secondary cost element)” for allocation. Because the receiver receives the amount under a single cost element called “allocated overhead,” the receiving side cannot see a breakdown by original cost element of which costs were transferred.

• KSU5 (Execute Actual Assessment): executes the actual allocation at period end. Specify the plant, period, and allocation cycle name. Always confirm the allocation amounts with a Test Run before executing in production.

Distribution: KSV1/KSV5

• KSV1 (Maintain Actual Distribution Cycle) and KSV5 (Execute Actual Distribution): the operation is similar to Assessment, but it differs in that the posting to the receiver retains the breakdown by cost element (G/L account).

• With Distribution, the receiving cost center can also see the breakdown by original cost element, such as “personnel cost ¥XXX, utilities ¥XXX, communication cost ¥XXX.” Choose Distribution when the management accounting policy calls for “tracking the nature of costs without erasing it.”

Activity Allocation: KB21N

• KB21N (Direct Activity Allocation): directly enters the cost transfer that occurs when one center uses the services of another center (for example, the labor-hour allocation when the maintenance department repairs equipment for the manufacturing department). Enter the sender center, activity type, quantity, and receiver center, and “quantity × activity price” is automatically calculated and posted.

Month-End Processing: Calculating and Revaluing Actual Activity Prices

Operation Walkthrough: KSPI Calculate Planned Activity Price

• KSPI (Calculate Planned Activity Price): executed at the beginning of the fiscal year. It calculates the planned activity price from the planned cost in KP06 and the planned activity quantity in KP26. This price is used in the cost estimate roll-up (CK11N).

Operation Walkthrough: KSII Revaluation at Actual Activity Prices

• KSII (Revaluation at Actual Activity Prices): executed as month-end processing. It corrects, by the difference, the activity costs posted to production orders during the month at the planned activity price, using the actual activity price (actual cost ÷ actual activity quantity). This allows the production order’s processing cost variance (activity price variance) to be calculated accurately.

• KSII is executed before CO88 (Production Order Settlement), because the variance after revaluation is settled in CO88.

Reports and Plan/Actual Variance Analysis

Operation Walkthrough: KSB1 Cost Center Line-Item Report

• KSB1 (Cost Centers: Actual Line Items): displays expense line items by specifying the cost center, period, and fiscal year. Expense details can be drilled down “by cost element, by document, or by posting date.” If an abnormal cost posting is found, it can be traced from the document number back to the original document (invoice, journal entry, etc.).

• KSBL (Cost Center Balance Report): displays “planned cost, actual cost, variance, and variance rate (%)” by cost center. If a Flexible Budget is set up, a comparison against the actual-activity-based “flexible plan cost” is also displayed.

• S_ALR_87013611 (Cost Centers: Plan/Actual/Variance Report): a standard report that lists the plan/actual variance of cost centers across the entire controlling area. Cost centers with large variances can be sorted to identify targets for improvement.

3. SPRO Configuration for Cost Center Accounting

Setting Up the Standard Hierarchy (OKEON)

The standard hierarchy of cost centers is configured via SPRO under “Controlling → Cost Center Accounting → Master Data → Cost Centers → Define Standard Hierarchy,” or via transaction OKEON.

• OKEON (Define Standard Hierarchy): creates and arranges the nodes (groups) that make up the standard hierarchy of a controlling area. Child nodes branch out from a root node (e.g., “COMP-A”), and cost centers are assigned to the terminal nodes.

• The standard hierarchy determines the “organizational affiliation of the cost center.” The same cost center cannot belong to more than one standard hierarchy node (exclusive affiliation).

Configuring Activity Types (KL04 / SPRO)

Activity type categories and their behavior are defined in SPRO under “Controlling → Cost Center Accounting → Master Data → Activity Types → Define Activity Type Categories.”

• Activity type category 1 (manual entry): entered manually in CO11N and similar transactions. Used for direct processing-cost allocation to production orders.

• Activity type category 2 (indirect determination): indirect activities posted automatically via allocation cycles or automatic entry rules.

• KL04 (Mass Change of Activity Types): a transaction for mass-changing activity type attributes.

Configuring Statistical Key Figures (SK01 / KK01)

“Statistical Key Figures,” used as the basis for allocation ratios, are managed with SK01 (Define Statistical Key Figures) and KK01 (Enter Statistical Key Figures).

• SK01 (Create Statistical Key Figure Master): creates definitions of statistical key figures (for example, “HEADCOUNT: number of employees” or “FLOORAREA: floor space in m²”).

• KK01 (Enter Actual Statistical Key Figures): the actual value of the statistical key figure is entered for each cost center every period. Example: “floor area of Manufacturing Department 1 = 500 m².” This value is used as the allocation basis (tracing factor) in allocation cycles.

Details of Allocation Cycle Configuration (KSU1 / KSV1)

Designing an allocation cycle is the core setting that determines “which cost, from which sender, to which receiver, and on what allocation basis, is allocated.” The following summarizes practical points of attention.

• Cycle execution order: when multiple cycles exist (for example, a multi-stage allocation of “administrative costs → manufacturing departments → product production orders”), each cycle must be executed in the correct order. In SAP’s cycle management, an execution sequence number is set on the “cycle segment.”

• Fixed ratio vs. variable ratio: a Fixed Allocation ratio allocates at the same ratio every period and is therefore stable, but it may drift from actual conditions. A Variable Allocation ratio changes dynamically based on actual activity quantities or statistical key figure results, so it better reflects actual conditions but produces larger month-to-month fluctuations.

• Cost element for Assessment (secondary cost element): the “Secondary Cost Element” used for Assessment is created with KA06 (Create Secondary Cost Element). Cost element category “42 (Assessment)” is specified. This cost element becomes the G/L account used for Assessment postings.

Configuring the Flexible Budget (KPF6 / OKN0)

The Flexible Budget is a function that automatically calculates an “Adjusted Plan” based on actual activity quantity. It calculates the adjusted plan using the logic that “fixed costs remain constant regardless of activity quantity, while variable costs scale in proportion to actual activity quantity,” and it separates pure efficiency variance (Spending Variance) from Activity Variance (capacity/idle-capacity variance).

• Accurately entering the variable/fixed cost split in KP06 is the key to the accuracy of the flexible budget. By accurately setting the variable cost rate (for example, supply cost of ¥50 per machine hour), the adjusted plan scales appropriately as the activity quantity increases or decreases.

• OKN0 (Define Flexible Budget Formulas): defines formulas when a more complex flexible calculation is required, such as a staged fixed/variable cost split.

Part Two: Profit Center Accounting (PCA)

4. What Is Profit Center Accounting

The Concept and Role of the Profit Center

A profit center is the “unit of responsibility for profit and loss” in SAP Management Accounting. Whereas a cost center is a “unit for managing expenses,” a profit center is “a unit that aggregates both revenue and expenses to manage profit and loss (profit-center-level P&L).” A company’s business divisions, product lines, regions, brands, and so on are defined as profit centers, making the P&L responsibility of each business segment explicit.

The greatest feature of Profit Center Accounting (PCA) is that it can manage not only the profit and loss statement but also the balance sheet (assets such as inventory, receivables, and fixed assets) by profit center. This makes it possible to calculate and manage management indicators such as ROI (Return on Investment), ROA (Return on Assets), and capital efficiency, by business, at the profit center level.

Profit Centers and Segments

In SAP S/4HANA, to comply with IFRS 8 (Operating Segment disclosure) and US GAAP ASC 280, a “Segment” attribute can be set on a profit center. By aggregating profit centers belonging to the same segment, segment-level disclosure information for consolidated financial statements is automatically generated.

• Setting up segments: a segment code (for example, “SEG01: Electronics Business” or “SEG02: Industrial Equipment Business”) is assigned to the “Segment” field of the profit center master (KE52).

• Segment-level balance sheets: because the S/4HANA Universal Journal (ACDOCA) has a segment column, segment-level balance sheets and profit-and-loss statements can be generated in real time.

5. Transaction Operations for Profit Center Accounting

Managing Master Data

Operation Walkthrough: KE51 Create Profit Center

• KE51 (Create Profit Center): enter the controlling area, profit center code (e.g., PC1001), and validity period, then press Enter.

• Basic data: enter the name, profit center group (affiliation in the hierarchy), person responsible, segment, and profit center currency. The “profit center group” determines affiliation to the standard hierarchy (managed via KECM/KCH1).

• KE52 (Change Profit Center) and KE53 (Display Profit Center): the basic operations are the same as for CCA.

Operation Walkthrough: KCH1 Manage Profit Center Groups

• KCH1 (Create Profit Center Group) and KCH5 (Change Profit Center Standard Hierarchy): organize profit centers into hierarchies “by business division, by product line, or by region.” Reports using the hierarchy make it possible to aggregate, for example, “total profit and loss by business division” or “total profit and loss by region.”

Assigning Costs and Revenue to Profit Centers

The assignment of costs and revenue to profit centers is performed automatically via the “profit center attribute” of the material master, cost center, production order, and so on.

• Assigning a profit center to the material master (MM02): a profit center is set in the “Profit Center” field of the material master. Inventory changes and cost of goods sold arising from manufacturing or selling this material are automatically posted to that profit center.

• Assigning a profit center to the cost center (KS02): a “profit center” is set in the cost center master. Costs posted to this cost center are simultaneously posted to the linked profit center as well.

• Assigning a profit center to production orders: a production order inherits the profit center from the material master. Material cost and processing cost postings to the production order are automatically posted to the profit center.

• Assigning a profit center to sales orders: the profit center is automatically determined from the settings of the material or customer group on the sales order item. When revenue for the sales order is recognized (VF01), the revenue is posted to that profit center.

Internal Transfers Between Profit Centers (Transfer Pricing)

When a product or service is transferred between profit centers (for example, a transfer from the profit center that manufactures an intermediate product to the profit center that assembles the finished product), inter-profit-center transactions using a “Transfer Price” can be configured.

• 8ME (Transfer Price Configuration): sets the transfer rate between profit centers. The transfer price is set as either “Cost-based,” “Market-based,” or “Negotiated.”

• KE1G (Cross-Profit-Center Posting): a manual internal transfer posting. Service provided from profit center A to profit center B is recorded with KE1G.

• Elimination of internal transactions: in consolidated reporting, internal transactions between profit centers (internal sales, internal purchases) must be eliminated by offsetting. This is processed using SAP’s profit center elimination function (or a consolidated financial statement system such as SEM-BCS / SAP Group Reporting).

Reports and Analysis

Operation Walkthrough: KE5X/KE5T Profit Center P&L Reports

• KE5X (Profit Center: Actual Line Items): displays the line items of profit and loss (revenue, cost, overhead allocation, and other line items) by specifying the profit center, period, and fiscal year. This is a real-time report based on the Universal Journal (ACDOCA).

• KE5T (Profit Center Plan/Actual/Variance Report): aggregates and displays “planned revenue, actual revenue, planned cost, actual cost, planned profit, actual profit, and variance” by profit center. A business-division-level P&L summary aggregated by hierarchy (profit center group) can also be checked.

• F.5D (Profit Center Balance Sheet Report): displays balances of balance sheet accounts such as “inventory, accounts receivable, accounts payable, and fixed assets” by profit center. The asset allocation information required for calculating ROI by business can be checked here.

• GR55 (Profit Center Report Tree): enables drill-down analysis of the P&L summary using a tree of the profit center hierarchy.

6. SPRO Configuration for Profit Center Accounting

Activating Profit Center Accounting (OKKS / 0KEB)

• OKKS (Basic Settings for Profit Center Accounting): activates Profit Center Accounting for the controlling area. Once activated, profit center assignment becomes mandatory for cost centers, production orders, and sales orders.

• 0KEB (Set Profit Center Entities): defines the Dummy Profit Center. The dummy profit center functions as a “catch-all” for postings that occur without a profit center assigned, due to error. If postings to the dummy occur frequently, check for missing profit center settings in master data.

Automatic Assignment Rules (3KEH)

• 3KEH (Default Profit Center Assignment by Company Code): sets the “default profit center to use when a profit center cannot be automatically determined” by G/L account and transaction type. This automatically assigns a profit center for postings not linked to a material master or cost center, such as administrative accounts (prepaid expenses, accrued expenses, various provisions, etc.).

Configuring Profit Center Planning (KEKF)

• KEKF (Configure Profit Center Planning): configures the entry layout and reference periods for profit center planning (revenue, expense, and inventory planning). Profit center planning itself is performed with KE1P (Enter Profit Center Planning).

Allocating Balance Sheet Items to Profit Centers (3KA1)

• 3KA1 (Balance Sheet Account Assignment to Profit Centers): configures cycles that allocate balance sheet accounts such as inventory, accounts receivable, and accounts payable to profit centers proportionally. For example, a rule such as “allocate the company-wide accounts receivable balance to profit centers by sales ratio” is defined here.

Part Three: Profitability Analysis (CO-PA)

7. What Is Profitability Analysis (CO-PA)

The Concept of CO-PA and Its Two Valuation Approaches

Profitability Analysis (CO-PA) is a management accounting function that “analyzes profit and loss at the level of profitability segments, which are defined by combinations of multiple dimensions (characteristics) such as product × customer × region × sales channel.” Whereas the profit center manages profit and loss along an “organizational axis” (business division, regional site), CO-PA analyzes profit and loss multi-dimensionally along a “market axis” (product, customer, sales channel).

CO-PA has two valuation approaches: “Account-based CO-PA” and “Costing-based CO-PA.” In SAP S/4HANA, the account-based approach is fully integrated with the Universal Journal and is the recommended architecture.

• Account-based CO-PA: aggregates profit and loss for profitability segments based on the same G/L accounts (P&L accounts) used in financial accounting. Because it reconciles with the financial statements, consistency is high, and in S/4HANA it is integrated into ACDOCA and updated in real time. The flexibility of costing methods is somewhat lower.

• Costing-based CO-PA: aggregates revenue and cost using “Value Fields” independently defined by SAP. It is stored in a database separate from financial accounting (CEXXXX: tables specific to the operating concern). It offers high computational flexibility (enabling multi-stage contribution margin calculations that progressively subtract cost, discounts, and allocated overhead from revenue), and it was the method widely used in the earlier ECC era. In S/4HANA, both approaches can also be used in parallel.

Profitability Segments: Axes of Multi-Dimensional Analysis

A Profitability Segment is the unit of analysis in CO-PA. It is defined by a combination of characteristics such as “product (material) × customer × customer group × sales region × sales organization × delivery route.” For example, “Product A × Customer Group X × EMEA region” constitutes one segment.

• The design of characteristics is defined in the Operating Concern. Which characteristics are used as axes of profitability analysis is designed based on the business requirement of “from what angle do we want to analyze profit and loss.” Too many characteristics increase management complexity, while too few result in insufficient analytical granularity.

8. Data Flow Into CO-PA

Posting Revenue and Costs From SD to CO-PA

The primary data flow into CO-PA is “billing document posting from the Sales and Distribution (SD) module (VF01: Create Billing Document).” At the time of billing document posting, SAP “automatically determines the profitability segment from the characteristic values of the billing item (material, customer, sales organization, etc.) and posts revenue, sales deductions, cost of goods sold, and so on to CO-PA.”

Operation Walkthrough: VF01 Billing Document Posting and Confirming the CO-PA Posting

• VF01 (Create Billing Document): in the flow of sales order (VA01) → delivery (VL01N) → billing document (VF01), the CO-PA posting is executed automatically when the billing document is finalized.

• KE24 (CO-PA Line Item Report): after VF01, launch KE24 and search for line items by billing document number. Confirm that “profitability segment, revenue, sales deduction, standard cost (COGS), variable manufacturing cost variance, etc.” have been posted by segment.

• KE57 (Individual Confirmation of CO-PA Postings): a debugging-oriented transaction for confirming the details of a CO-PA posting (which value field received which amount) for a specific billing document or production order.

Settling Variances From CO-PC to CO-PA

Production order variances (variances against the standard cost that arise in cost accounting) are posted to CO-PA via CO88 settlement.

Operation Walkthrough: CO88 Settlement and CO-PA Posting

• When CO88 (Collective Settlement of Production Orders) is executed, production order variances (quantity variance, price variance, labor variance, etc.) are posted to the corresponding value field in CO-PA (Production Variance).

• The CO-PA characteristics of the settlement destination are determined by “value field mapping via KE4I” and “characteristics mapping via KEPC.” The destination profitability segment is determined from information such as “the sales order item linked to the production order → material → customer → sales organization, etc.”

Allocating Cost Center Expenses to CO-PA

Indirect costs (manufacturing overhead, selling expenses, general and administrative expenses) are posted to CO-PA segments via a “period-end allocation cycle (KEU5)” or “overhead calculation (via CO43)” to CO-PA.

Operation Walkthrough: KEU5 Execute the CO-PA Actual Allocation Cycle

• KEU1 (Maintain CO-PA Allocation Cycle): defines the allocation source (cost center), allocation destination (CO-PA segment), and allocation key (sales ratio, product sales volume ratio, etc.). Example: “allocate the expenses of the sales expense cost center to CO-PA segments by the sales ratio of the products sold.”

• KEU5 (Execute CO-PA Actual Allocation): executed at period end. Execute in production after confirming with a test run. After allocation, confirm in KE30 that the allocated overhead has been posted by segment.

Manual CO-PA Posting (KE21N)

• KE21N (Enter CO-PA Actual Line Items): used when a manual posting to CO-PA is required (costs or revenue that cannot be processed via SD or CO-PC). The profitability segment, value field, and amount are entered directly.

Reports and Contribution Margin Analysis

Operation Walkthrough: KE30 Execute Profitability Report

• KE30 (Execute Profitability Report): select and execute a predefined report (report group). Reports include “contribution margin by product,” “contribution margin by customer,” and “profit and loss by region.”

• The report screen is displayed in a matrix format: “rows: product groups; columns: monthly P&L items (revenue / sales deductions / gross profit / allocated overhead / contribution margin).” Double-clicking a specific cell allows drill-down into the CO-PA line items (KE24).

• KE24 (Display CO-PA Line Items): retrieves line items by specifying the profitability segment, period, and characteristics. Traces “from which billing document, production order, or allocation cycle this amount originated” at the document level.

• KE5Z (CO-PA Plan/Actual/Variance Report): variance analysis between planned and actual profit and loss. This is useful when the plan has been entered via KEPM (CO-PA Planning).

9. CO-PA Planning: Multi-Dimensional Budgeted Profit and Loss

How CO-PA Planning Works

CO-PA Planning (Profitability Planning) is a function that sets planned values for “revenue, sales deductions, cost of goods sold, allocated overhead, and contribution margin” by profitability segment, such as product × customer × region. Comparison against actuals (KE5Z) enables real-time visibility into “which segments are over- or under-achieving against budget.”

Operation Walkthrough: KEPM CO-PA Plan Entry

• KEPM (Enter CO-PA Planning): launches the plan entry screen by specifying the plan version, fiscal year, and planning period. Expand the segments (product group × region × customer group, etc.) and enter planned revenue, planned sales volume, planned unit price, and so on into each cell.

• Top-down Distribution: a “top-down planning” function is available that distributes a company-wide planned sales figure by product group and by region. An upper-level planned value is entered, and it is automatically apportioned to lower-level segments using a distribution key (such as the prior-year actual ratio).

• Transferring the plan (plan-to-actual comparison): after entering values in KEPM, check the plan/actual comparison report in KE5Z. Because planned and actual values are stored in the same operating concern, variances are calculated in real time.

10. SPRO Configuration for CO-PA

Configuring the Operating Concern (KEA0)

The Operating Concern is the “highest-level configuration object” of CO-PA. It is the “design document for the data structure” that defines the characteristics and value fields used in CO-PA. It is managed with KEA0 (Set Operating Concern) or via SPRO under “Controlling → Profitability Analysis → Basic Settings → Set Operating Concern.”

Defining Characteristics

• KEA5 or “Maintain Characteristics” in KEA0: defines the axes (dimensions) that define a CO-PA segment as characteristics. Examples: PRDHA (product hierarchy), KDGRP (customer group), VKORG (sales organization), BZIRK (sales district), WERKS (plant), and so on.

• Characteristics are derived from “SD fields (sales orders, billing documents), CO-PC fields (production orders), and master data fields (material and customer attributes).” KE4W (characteristic value derivation rules) sets “from which field of the billing document the CO-PA characteristic value is derived.”

• Designing the number and granularity of characteristics: more characteristics increase analytical flexibility but greatly increase the size of CE1XXXX (the Costing-based CO-PA data table). For Account-based CO-PA, since data is stored in ACDOCA, the impact is limited, but excessive characteristics still affect query performance. In practice, it is important to limit characteristics to “the analysis axes that management actually uses.”

Defining Value Fields (Costing-based CO-PA)

• KEA6 or “Maintain Value Fields” in KEA0: defines P&L items (revenue, discounts, cost of goods sold, quantity variance, allocated selling and administrative expenses, etc.) of CO-PA as “Value Fields.” Value fields can be freely designed independent of G/L accounts.

• Assignment of G/L accounts to value fields (KE4I): maps financial accounting G/L accounts (P&L accounts) to CO-PA value fields. Example: “revenue account group (800000–899999) → value field VV010 (Revenue).” This mapping is the basis for CO-PA postings.

Transferring Characteristic Values From SD to CO-PA (KE4W / KE4U)

• KE4W (Characteristic Value Derivation Rules): defines mapping rules from “SD fields → CO-PA characteristics” for billing documents and sales order items. Examples: “customer group (KDGRP) in the SD customer master → CO-PA characteristic KDGRP” and “product hierarchy (PRDHA) in the SD material master → CO-PA characteristic PRDHA.”

• KE4U (Cost Estimation: Condition Types → Value Fields): maps SD price condition types to CO-PA value fields. Examples: “PR00 (base price) → VV010 (Revenue)” and “K007 (special discount) → VV020 (Special Discount).” With this configuration, each SD pricing condition is automatically posted to the corresponding CO-PA value field at the time of VF01 billing document posting.

CO-PA Characteristics Mapping for Settlement Rules (KEPC)

• KEPC (Characteristics Transfer Rules for Profitability Segments): defines the mapping from “characteristics of the settlement source (production order) → CO-PA profitability segment characteristics” when settling production orders or internal orders. Example: “material code of the production order → CO-PA characteristic ARTNR (Product)” and “sales order item of the production order → CO-PA characteristic KDPOS (Sales Order Item).”

• If KEPC is not configured correctly, the profitability segment will not be determined correctly when production order variances are posted to CO-PA, and the variance will end up being recorded to an “unknown segment.” It is recommended to check the destination segment of the variance in KE24 after settlement.

Configuring CO-PA Reports (GRR1 / KE34)

• GRR1 (Configure Report Group) and KE34 (Define Profitability Report): configures the display format of the CO-PA KE30 report (row/column definitions, aggregation level, sorting, and conditions). A report is designed as a combination of a “row layout (aggregation axes such as by product, by customer, or by region)” and a “column layout (a column structure of plan/actual/variance for each period).”

• KE31 (CO-PA Report Rows): defines each row of the report. For example, it defines report rows for a multi-stage contribution margin calculation such as “Row 1: Revenue (VV010); Row 2: Sales Deduction (VV020); Row 3: Contribution Margin I (=VV010+VV020); Row 4: Direct Material Cost (VV030); Row 5: Direct Processing Cost (VV040); Row 6: Contribution Margin II.”

11. Integrated Management Accounting Design of CCA, PCA, and CO-PA

The Division of Roles and Flow of Information Across the Three Layers of Management Accounting

CCA, PCA, and CO-PA are not independent functions; they work together to provide “complete management accounting information.” The flow of information is a chain: “CCA (collection of expenses and overhead allocation) → CO-PC (conversion into product cost) → CO-PA (aggregation of profit and loss along the product × customer axis) and PCA (aggregation of profit and loss along the organizational axis).”

• The role of CCA: collects and manages the expenses of the manufacturing, administrative, and sales departments in cost centers, and transfers costs to CO-PC production orders and to CO-PA through activity allocation and assessment. It manages “who spent how much” along the organizational axis.

• The role of PCA: aggregates CO-PC’s product inventory, sales, and cost of goods sold by segment (business division, product line), and manages “profit and loss by business division and asset efficiency,” including balance sheets by business. It supports segment disclosure under IFRS 8.

• The role of CO-PA: aggregates SD’s sales and discount data together with CO-PC’s variance and allocation data along business axes such as “product × customer × region,” providing contribution margin analysis along the market axis of “which product, sold to which customer, through which channel, is profitable.”

Practical Points of Attention for Integrated Design

• Consistency between characteristics and segments: if CO-PA’s profitability segment characteristics and PCA’s segment attributes are not consistent, discrepancies will arise between CO-PA and PCA profit and loss. During the design phase, clearly map “which CO-PA segment corresponds to which PCA profit center/segment.”

• Order of execution for actual allocation: month-end actual processing must follow the order “CCA allocation (KSU5/KSV5) → KSII revaluation → KKS1 variance calculation → CO88 settlement (→ CO-PA posting) → KEU5 CO-PA allocation.”

• Consistency of plans: by designing an “end-to-end management accounting plan” in which CO-PA planning (KEPM), profit center planning (KE1P), cost center planning (KP06), and CO-PC standard cost (CK11N) are all consistent, the accuracy of comparative analysis against actuals is maximized.

12. Case Studies From Other Companies

Case Study 1: Multi-Business Conglomerate Company A — ROI Management by Profit Center

Background and Challenges

At Company A, a conglomerate with multiple business divisions (electronics, industrial equipment, and solutions), even though the company appeared profitable on a consolidated basis, it was unclear which businesses were earning money and which were dragging down performance. Although revenue and expenses could be tracked by business, the “assets” used by each business — inventory, equipment, accounts receivable, and so on — could not be tracked by business, making it impossible to calculate a business-level ROI that accounted for the cost of capital (WACC).

Introduction of PCA Segments and Results

Company A set up Segments in the PCA of SAP S/4HANA and visualized business-level balance sheets (inventory, fixed assets, accounts receivable) within management accounting. Segment-level profit and loss and asset balances became visible in real time on a monthly basis, and the calculation of business-level ROA and ROI was automated. Management meetings could now discuss the allocation of management resources based on figures such as “the electronics business has an ROI of 15% and the industrial equipment business has an ROI of 7%,” and it is reported that the speed and accuracy of investment decisions improved significantly.

Case Study 2: Global Consumer Goods Manufacturer Company B — Customer Profitability Management With CO-PA

Background and Challenges

At Company B, the actual state of special discounts and logistics costs for major customers (mass retailers, e-commerce marketplaces) could not be captured as “profit and loss by customer.” Because customers “with high revenue but a high discount rate” and customers “with lower revenue but high profitability” were treated the same in sales activities, concentration on low-profitability major customers was dragging down the company’s overall profit margin.

Customer Profitability Management With CO-PA and Results

Company B set up “customer (KUNNR), customer group, sales channel, and product line” as characteristics in CO-PA, and automatically aggregated “revenue, special discounts, allocated logistics costs, cost of goods sold, and manufacturing variance” into CO-PA’s multi-stage contribution margin report at the time of billing document posting. “Contribution Margin II (net profit)” by customer and by channel became visible on a monthly basis, and it is reported that overall profit margin improved through discount-rate reviews for low-profitability customers and logistics efficiency improvements. In addition, setting sales targets by salesperson (sales, discount rate, and contribution margin targets) using CO-PA Planning (KEPM), along with actual performance management, became established as a monthly cycle.

Case Study 3: Integrated Manufacturing-and-Sales Company C — Integrated Design of CCA, PCA, and CO-PA

Background and Challenges

At Company C, which handles everything from manufacturing to direct sales in an integrated manner, “the cost of manufacturing a product (CO-PC),” “the cost of selling a product (CO-PA),” and “factory overhead (CCA)” were managed separately, and the product-level “Full Absorption Cost” — direct manufacturing cost plus allocated manufacturing overhead plus allocated selling expenses — could not be viewed in one place.

Integration of CCA, CO-PC, and CO-PA and Results

Company C carried out an integrated design of CCA, CO-PC, and CO-PA, establishing a monthly flow of “CCA overhead → aggregated to production orders via CO43 overhead calculation → posted to CO-PA’s manufacturing variance field via CO88 settlement → selling expenses allocated to CO-PA segments via the KEU5 allocation cycle.” This achieved a state in which “net gross profit (sales − standard cost − manufacturing variance − allocated selling and administrative expenses)” can be calculated across the three dimensions of product × customer × region, and the company uses this for decision-making on pricing strategy, product discontinuation decisions, and sales channel strategy.

13. SAC Integration and Visualization

Live Connection Between SAC and CO-PA/PCA

By referencing S/4HANA’s CO-PA and PCA data from SAP Analytics Cloud (SAC) via Live Connection (a BW connection or an S/4HANA Live Connection), it is possible to provide more advanced visualization (charts, interactive filters, drill-down) than the KE30/KE5T reports, as a management dashboard.

• Recommended architecture: an architecture is recommended in which SAP Datasphere is placed as an intermediate layer, CO-PA, PCA, FI, and SD data are integrated and given semantic meaning in Datasphere’s business layer, and SAC connects to Datasphere via Live Connection.

• Integration with Smart Insights: by applying SAC’s Smart Insights (AI-driven factor analysis) to CO-PA data, it is possible to automatically analyze factors such as “why did this month’s contribution margin by product decline by X yen.” However, since SAC’s AI features cannot be used with Live Connection, an import-based approach is required.

Standard Fiori Analytical Apps

• Contribution Margin Analysis (SAP Fiori): a standard CO-PA analytical app provided as a Fiori app in S/4HANA. It allows interactive review of multi-stage contribution margin by product line and by customer group.

• Actual vs Plan Analysis (SAP Fiori): a standard app that visualizes CO-PA and CCA plan/actual variance in Fiori. It supports drill-down and root-cause analysis.

End of document.