Professional Documents
Culture Documents
Description
HELP.CACOMPCO
Release 4.6B
™
CO Component Short Description SAP AG
Controlling
Copyright
©
Copyright 2000 SAP AG. All rights reserved.
No part of this brochure may be reproduced or transmitted in any form or for any purpose without
the express permission of SAP AG. The information contained herein may be changed without
prior notice.
Some software products marketed by SAP AG and its distributors contain proprietary software
components of other software vendors.
® ® ® ® ® ®
Microsoft , WINDOWS , NT , EXCEL , Word and SQL Server are registered trademarks of
Microsoft Corporation.
® ® ® ® ® ® ® ® ®
IBM , DB2 , OS/2 , DB2/6000 , Parallel Sysplex , MVS/ESA , RS/6000 , AIX , S/390 ,
® ® ®
AS/400 , OS/390 , and OS/400 are registered trademarks of IBM Corporation.
®
ORACLE is a registered trademark of ORACLE Corporation, California, USA.
® ® TM
INFORMIX -OnLine for SAP and Informix Dynamic Server are registered trademarks of
Informix Software Incorporated.
® ® ® ®
UNIX , X/Open , OSF/1 , and Motif are registered trademarks of The Open Group.
®
HTML, DHTML, XML, XHTML are trademarks or registered trademarks of W3C , World Wide
Web Consortium, Laboratory for Computer Science NE43-358, Massachusetts Institute of
Technology, 545 Technology Square, Cambridge, MA 02139.
®
JAVA is a registered trademark of Sun Microsystems, Inc. , 901 San Antonio Road, Palo Alto,
CA 94303 USA.
®
JAVASCRIPT is a registered trademark of Sun Microsystems, Inc., used under license for
technology invented and implemented by Netscape.
2 December 1999
SAP AG CO Component Short Description
Controlling
Icons
Icon Meaning
Caution
Example
Note
Recommendation
Syntax
Tip
December 1999 3
CO Component Short Description SAP AG
Controlling
Contents
4 December 1999
SAP AG CO Component Short Description
Controlling
December 1999 5
CO Component Short Description SAP AG
Controlling
6 December 1999
SAP AG CO Component Short Description
Controlling
Controlling
Purpose
Controlling provides you with information for management decision-making. It facilitates
coordination, monitoring and optimization of all processes in an organization. This involves
recording both the consumption of production factors and the services provided by an
organization.
As well as documenting actual events, the main task of controlling is planning. You can
determine variances [Ext.] by comparing actual data with plan data. These variance calculations
enable you to control business flows.
Income statements such as, contribution margin accounting, are used to control the cost
efficiency of individual areas of an organization, as well as the entire organization.
Integration
Controlling (CO) and Financial Accounting (FI) are independent components in the SAP system.
The data flow between the two components takes place on a regular basis.
Therefore, all data relevant to cost flows automatically to Controlling from Financial Accounting.
At the same time, the system assigns the costs and revenues to different CO account
assignment objects, such as cost centers, business processes, projects or orders. The relevant
accounts in Financial Accounting are managed in Controlling as cost elements [Ext.] or revenue
elements [Ext.]. This enables you to compare and reconcile the values from Controlling and
Financial Accounting.
Features
Cost and Revenue Element Accounting (CO-CEL)
Cost and Revenue Element Accounting provides you with an overview of the costs and revenues
that occur in an organization. Most of the values are moved automatically from Financial
Accounting to Controlling. Cost and Revenue Element Accounting only calculates costs which
either do not have another expense or only one expense in Financial Accounting.
If needed, reconciliation [Ext.] of the values in Financial Accounting and Controlling takes place in
Cost and Revenue Element Accounting.
For more information, see Cost and Revenue Element Accounting [Page 11].
Activity-Based-Accounting (CO-OM-ABC)
Activity-Based Costing analyzes cross-departmental business processes. The goals of the whole
organization and the optimization of business flows are prioritized.
For more information, see Activity-Based Costing [Page 86].
December 1999 7
CO Component Short Description SAP AG
Controlling
8 December 1999
SAP AG CO Component Short Description
Overhead Cost Controlling
Features
Overhead Cost Controlling is divided into the following areas.
Internal orders
Overhead Orders are internal orders used either to monitor overhead costs for a limited period,
or overhead incurred by executing a job, or for the long-term monitoring of specific parts of the
overhead. Independently of the cost center structure, internal orders collect the plan and actual
costs incurred, enabling you to control the costs continuously. You can also use internal orders to
control a cost center in more detail. You can assign budgets to jobs. These budgets are then
monitored automatically by the SAP system to ensure that they are kept to.
December 1999 9
CO Component Short Description SAP AG
Overhead Cost Controlling
Activity-Based Costing
In contrast to the responsibility and function-oriented basis of Cost Center Accounting, Activity-
Based Costing provides a transaction-based and cross-functional approach for activity output in
which several cost centers are involved. The emphasis is not on cost optimization in individual
departments, but the entire organization.
By allocating process quantities based on cost drivers, rather than using overhead calculation,
cost allocation along the value chain is more source-based. Activity-Based Costing enables you
to cost products more accurately in the overhead areas.
10 December 1999
SAP AG CO Component Short Description
Cost Element Accounting
Integration
In an integrated accounting system such as the SAP System, you do not need to carry out
complicated entry of cost data. This is because each business transaction relevant to cost
accounting provides the (CO) component with detailed information concerning both the cost
element [Ext.] and the account assignment object itself. Each consumption transaction in Material
Management (MM), each billing in Sales and Distribution (SD) (= revenue), and each external
transaction for invoice verification flows directly through the G/L account [Ext.] (= cost element) to
the corresponding account assignment object.
Features
You can restrict the entry of cost data to a part of the Outlay Costs [Ext.] and Additional Costs
[Ext.]. While, for example, you can transfer depreciation costs from Asset Accounting for the
depreciation of fixed assets, you must use accrual calculation in cost accounting for management
income.
The Controlling (CO) component also has the task of identifying which costs occurred in what
subareas of an organization, and which the cost flows took place. The system provides a
complete display of the costs for all types of account assignment objects (such as cost centers,
orders, projects, and so on).
For cross-company-code or cross-business-area cost accounting, the cost flow within Controlling
may require reconciliation between internal and external accounting. The necessary
reconciliation is also one of the tasks of Cost Element Accounting.
December 1999 11
CO Component Short Description SAP AG
Cost Elements
Cost Elements
Definition
Cost elements classify an organization’s valuated consumption of production factors within a
controlling area [Ext.]. A cost element corresponds to a cost-relevant item in the chart of
accounts [Ext.].
Structure
We distinguish between primary cost [Ext.] and revenue elements [Ext.] and secondary cost
elements [Ext.].
Integration
Cost elements in Controlling (CO) are closely related to the general ledger accounts used in
Financial Accounting (FI). This is because the SAP System is structured as an Integrated
Accounting System [Ext.]:
12 December 1999
SAP AG CO Component Short Description
Cost Elements
Cost elements document which costs (differentiated by category) are incurred within a settlement
period, and in which amount. They provide information concerning the value flow and the value
consumption within the organization. Cost Element Accounting and Cost Center
Accounting/Internal Orders are closely linked in the SAP System. Each posting to an account that
is also a cost element, is assigned either to a cost center or order. This ensures that at period-
end the data is subdivided by cost elements and cost centers/internal orders for analysis
purposes. The following section describes how you can subdivide and characterize cost
elements in the SAP System.
Cost element characteristics depend on the controlling area and the allocation
methods used in your organization.
December 1999 13
CO Component Short Description SAP AG
The Reconciliation Ledger
Use
The reconciliation ledger has the following tasks:
• It reconciles Controlling with Financial Accounting.
− It provides reports with which you can control the CO/FI reconciliation for each
account.
− It can determine and display value flows that were posted in Controlling across
company code, functional area or business area borders.
− You can this value flow in Financial Accounting as the basis for summarized clearing
entries. Clearing entries represent value flows within Controlling that have an effect
on the legal closing of an organization (balance sheet, profit and loss account). You
can either enter the clearing entries using the values determined or let the system
execute them automatically.
• It provides an overview of all the costs incurred.
− The reconciliation ledger reports provide a suitable starting point for the analysis of
the costs incurred. For example, in the reconciliation ledger reports you can
investigate an item of the Profit and Loss Account, which is displayed in the Financial
Information System (FIS), with regard to the costs assigned. For a more detailed
analysis, you can use the reconciliation ledger reports to call up reports from other
CO components.
14 December 1999
SAP AG CO Component Short Description
Activity Types
Activity Types
Definition
Activity types classify the activities produced in the cost centers within a controlling area [Ext.].
Use
To plan and allocate the activities, the system records quantities, which are measured in activity
units. Activity quantities are valuated using a price (allocation price).
In Overhead Cost Controlling, costs based on the activity quantity of an activity type are posted
separately in fixed and variable portions. When you divide the activities of a cost center into
activity types, you should consider whether the costs can be allocated effectively to the activity
types.
The prices of the activity types of a cost center can be either entered manually, or calculated by
the system based on the costs allocated to the activities. Prices can be calculated either on the
basis of plan costs or actual costs.
You can plan, allocate, and control costs either at the activity type level of a cost center, or at the
cost center level. You can only enter actual costs at the cost center level. Costs entered at the
cost center level are assigned using actual cost splitting [Ext.].
When the activities produced by a cost center are used by other cost centers, orders, processes,
and so on, this means that the resources of the sending cost center are being used by the other
objects.
Integration
You can assign one activity type, multiple activity types, or no activity types to a cost center.
Typical examples of activity types for cost centers are machine hours, administrator
hours, CPU minutes or units produced.
December 1999 15
CO Component Short Description SAP AG
Statistical Key Figures
You assess the costs for the cafeteria to the individual cost centers, based on the
number of employees in each cost center. To do this, you need to enter the number
of employees in each cost center as a statistical key figure.
Structure
You can define statistical key figures as either:
• Fixed values
• Totals values
Key figures defined as fixed values are valid as of the posting period, and in all subsequent
posting periods of the fiscal year.
The statistical key figure Employees is defined as a fixed value. In period 1 of the
fiscal year, you post 10 Employees on cost center 4100. The system then
automatically posts 10 employees in periods 2 through 12.
In period 6, the number of employees is increased to 15. This means that in period 6,
you post 15 Employees on the cost center. The system automatically posts 15
employees in periods 6 through 12.
Key figures defined as Totals values are valid only in the posting period in which they are
entered.
You define the statistical key figure Telephone units as a totals value. In period 1 of
the fiscal year, you post 1000 Telephone units on cost center 4100. The system
posts 1000 telephone units in period 01 only.
16 December 1999
SAP AG CO Component Short Description
Statistical Key Figures
Integration
As well as entering statistical key figures manually, you can also transfer them automatically from
the information systems of other SAP System application components. To do this, statistical key
figure maintenance includes an interface that enables you to link the statistical key figures in
Controlling with those in the Logistics Information System (LIS). You transfer plan and actual key
figures from the LIS separately.
December 1999 17
CO Component Short Description SAP AG
Cost Center Accounting
• Assigning costs to cost centers lets you determine where costs are incurred within the
organization.
• If you plan costs at cost center level, you can check cost efficiency at the point where costs
are incurred.
• If you want to assign overhead costs accurately to individual products, services, or market
segments, you need to further allocate the costs to those cost centers directly involved in the
creation of the products or services. From these cost centers you can then use different
methods to assign the activities and costs to the relevant products, services, and market
segments.
This enables you to valuate semi-finished and finished products in Product Cost
Controlling (CO-PC), and to calculate contribution margins in Profitability Analysis (CO-
PA).
The “activities” of cost centers represent “internal resources” for business processes in
Activity-Based Costing.
Implementation
Cost Center Accounting (CO-OM-CCA) is often used in the first phase of an R/3 implementation,
together with the main areas of Financial Accounting (General Ledger (FI-GL), Assets Payable
(FI-AP), Assets Receivable (FI-AR)) and Overhead Orders (CO-OM-OPA).
You can also implement Cost Center Accounting without Financial Accounting. Some settings,
however, such as chart of accounts, company code, must be made in Financial Accounting.
18 December 1999
SAP AG CO Component Short Description
Cost Center Accounting
Integration
The costs of each cost-accounting-relevant business transaction portrayed in the R/3 System
through can be assigned through Cost and Revenue Element Accounting (CO-OM-CEL) to an
account assignment object in the Controlling component (CO). For overhead costs this can be
cost centers, internal orders, business processes, or overhead projects.
Recording and assigning overhead costs allows you to control costs and prepare information for
the subsequent areas of Cost Accounting.
You can use the methods of activity allocation, assessment or distribution to further allocate
costs, for example, to internal orders (CO-OM-OPA), projects (PS), cost objects (CO-PC) or
market segments (CO-PA).
Features
Entering actual costs
Primary costs can be transferred to Cost Accounting from other components, for example,
Materials Management (MM), Asset Accounting (AA), Payroll Accounting (PY).
Additional costs and outlay costs are recorded using the accrual method.
Activity Accounting
Activity Accounting uses the activity produced by a cost center as the tracing factor for the costs.
You can use activities to measure the operating rate or the rate of capacity utilization for a cost
center. The target costs of the cost center refer to the activity output.
Depending on the source of the costs, the activities of a cost center are divided into various
activity types (for example, for the Work center cost center: Repair hours or Assembly hours.
December 1999 19
CO Component Short Description SAP AG
Cost Center Accounting
Information system
The information system provides tools with which you can analyze the cost flows that have
occurred in your organization. You can carry out standard recurring evaluations; and create
special reports for unique tasks or situations.
Constraints
Note that you can only post revenues statistically on cost centers. The true posting must
occur on a revenue-carrying object. This could be, for example, a revenue-carrying order (see:
Account Assignment for Controlling Objects [Ext.]).
20 December 1999
SAP AG CO Component Short Description
Master Data in Cost Center Accounting
The cost center structure can reflect the structure of your organization. It generally
remains constant over long periods. You can execute cost center planning to reflect
your cost center structure and generate periodic cost center and area reports, which
can be passed on to the person responsible for analysis. These reports help identify
economic weaknesses and planning errors in individual cost centers. In order to
compare results effectively, you should not make changes to this data.
You generally maintain master data once, before the start-up of Cost Center Accounting. You
can do this manually or by transferring data from non-SAP systems using the appropriate user-
defined interface programs.
Master data for Cost Center Accounting is stored in master data tables.
Integration
In the SAP System we distinguish between:
• Master data
• Transaction data
Transaction data can be subdivided into:
• Totals data
• Line items
Transaction data is business transaction-oriented data that you can continuously create or
change in a live system.
You store transaction data for Cost Center Accounting in line item tables and totals tables.
The R/3 System saves the results of individual postings and business transactions in line item
tables. These include postings from external accounting systems, which are found both in
Financial Accounting (FI) and in the line item table for primary costs. The following postings are
recorded in this way:
• Postings of primary costs in the Financial Accounting (FI)
• Material withdrawals from Materials Management (MM)
• Postings generated during distribution
In these cases, the data is held redundantly in the system. This is necessary, however, as
external and internal accounting evaluate the data from different perspectives. External
accounting (Financial Accounting) requires the complete document for evaluations, whereas
internal accounting (Controlling) differentiates between primary and secondary costs.
Transaction data also includes postings within Controlling (CO). These postings are made either:
December 1999 21
CO Component Short Description SAP AG
Master Data in Cost Center Accounting
22 December 1999
SAP AG CO Component Short Description
Cost Center Planning
December 1999 23
CO Component Short Description SAP AG
Planning Closing
Planning Closing
Definition
After the end of the period halts plan postings for the corresponding period, “planning closing”
encompasses the execution of period-based business transactions, such as
• Distribution
• Assessment
• Imputed cost calculation
• Indirect activity allocation
• Activity price calculation
24 December 1999
SAP AG CO Component Short Description
Cost Center Budgeting
Selection criteria
Cost center budgeting is a further planning instrument along with primary and secondary cost
planning, allowing the option of comparing the sum of actual postings with the budgets as
planned. Budget overruns can be identified and availability controls undertaken via the
information system. Budget planning is made for an individual cost center or for a larger cost
center group. A budget report illustrates the comparison of plan, commitment, and actual data
(taken from actual postings) in addition to the requisitioned and available amounts.
December 1999 25
CO Component Short Description SAP AG
Funds Commitments (Cost Centers, Internal Orders, Projects)
Integration
Funds commitments assigned to WBS elements, networks, or internal orders are subject to
active budget availability control. The funds commitment checks whether the available budget is
still sufficient. Account is taken of tolerance limits defined above and below the budget.
For more information, read Availability Control [Ext.] .
The funds commitment appears as a commitment in the information system for the account
assignment object. For more information, see CO Commitment Management [Page 45].
You can archive the funds commitment documents. See CA - Archiving Application Data [Ext.].for
details.
Prerequisites
To process funds commitments, you need the appropriate authorization from authorization object
K_KMOB_DCT for each document type.
Features
Funds commitments involve the following individual activities:
• Create funds commitment [Ext.]
You enter the funds commitment as a reservation document. The reservation document
contains the following:
− The reservation document header contains data that applies to the whole document.
− At least one funds commitment item which contains the actual funds commitment
information.
• Change funds commitment [Ext.]
You can change the existing reservation amount and add more items to the funds
commitment.
• Reduce funds commitment [Ext.]
When you reduce the funds commitment manually, you enter the reduction amount for a
funds commitment item. You determine the reduction amount based on the amount still
open. This is calculated by determining the difference between the reservation amount
and the total of the partial amounts already reduced. You may not reduce the reservation
by more than the amount still open.
26 December 1999
SAP AG CO Component Short Description
Funds Commitments (Cost Centers, Internal Orders, Projects)
December 1999 27
CO Component Short Description SAP AG
Period-End Closing
Period-End Closing
Purpose
Period-end closing in Overhead Cost Controlling is part of the work carried out at period-end
throughout the entire organization.
The tasks required at period-end, and the sequence in which they must be carried out, depend on
what system functions you use and which cost accounting method. This topic describes the basic
elements of period-end closing. The explanations assume that you are using all the features
available.
Implementation Considerations
Before you can close a period in Overhead Cost Controlling, the data transferred to this
component from other application SAP System components must be complete. In particular, all
postings in Financial Accounting (FI) that are relevant to Cost Accounting must have been carried
out.
This means, for example, that:
• Payroll accounting must have taken place in Personnel Management (PA).
• In Sales and Distribution (SD), all the invoices have been created and passed on to Financial
Accounting.
• The vendor and customer accounts have been locked against postings in the period to be
closed.
You are not allowed to lock all accounts, as period-end closing in Overhead Cost
Controlling sometimes requires postings to be made Financial Accounting.
Features
Transferring of Statistical Key Figures from the LIS
To ensure that all primary costs and revenues from other components have been posted to
Overhead Cost Controlling, it is advisable to start by updating the statistical key figures.
Statistical key figures are used as the basis for allocations. This update can occur, for example,
through a transfer of the key figures from the Logistics Information System (LIS).
28 December 1999
SAP AG CO Component Short Description
Period-End Closing
Periodic Allocations
Secondary allocations then occur. Using the appropriate allocation or settlement method, the costs
are allocated between the business objects of Overhead Cost Accounting and to the cost objects of
Product Cost Controlling (CO-PC).
Splitting
When all the costs have finally been assigned to the cost centers, you use splitting [Ext.] to
assign the activity types to the cost centers. This is the basis for calculating the prices of the
activity types based on actual costs. Using the actual prices, you can perform an actual price
valuation of the activity produced by the cost centers.
Variances
After splitting you can analyze the variances [Ext.] of the actual costs from the target costs.
These variances lead to cost center under- or over-absorption. The variances of the production
cost centers and the costs of the sales and distribution and the administration cost centers are
transferred to Profitability Analysis (CO-PA). In CO-PA, the overhead costs can be assigned to
any level of the contribution margin scheme. This is the final step in actual cost accounting. You
should now lock the period against all postings.
December 1999 29
CO Component Short Description SAP AG
Period-End Closing
Follow-up costs can be dealt with by repeating the processing for the given period.
30 December 1999
SAP AG CO Component Short Description
Cost Center Summarizations
Implementation Considerations
You should consider carefully whether to generate an extract [Ext.] of the report data or execute
a summarization. Summarizations generate a far more data than extract generation does (see:
Executing Report-Painter Report [Ext.]).
• If you only need a few reports, we recommend you periodically save the reports in the
background for the entire cost center hierarchy and access the extracts afterwards online
(see: Variation [Ext.]). This spares you the repeated definition of new summarization
reports.
• You use summarization if you wish to access a large number of reports (including those
defined spontaneously) within the entire the cost center hierarchy.
Features
You create summarizations during Customizing in the Implementation Guide (IMG) for the
highest group node of a cost center group. This can be the highest group node of:
• The standard hierarchy
• An alternative hierarchy
Summarization carried out within the application framework can also be used:
• For as many subareas of the hierarchy as desired
• For individual periods
In both cases, note during the evaluations afterward that data with differing degrees of relevance
is included within a summarization.
Several forms of summarization are possible:
December 1999 31
CO Component Short Description SAP AG
Cost Center Summarizations
• Normal summarization applies to the object information, meaning the R/3 System
replaces the cost center in the totals records with the representative cost center given for
the cost center group. The degree of summarization depends on the data constellation,
in particular that of the secondary allocations.
• You can achieve a much higher degree of summarization by ignoring selected data. If,
for example, you wish to generate the cost structure for the entire corporation in strategic
reporting, you can leave out information on partner updating. This results in far faster
runtimes for the evaluations.
32 December 1999
SAP AG CO Component Short Description
Internal Orders
Internal Orders
Purpose
Internal orders are normally used to plan, collect, and settle the costs of internal jobs and tasks.
The SAP system enables you to monitor your internal orders throughout their entire life-cycle;
from initial creation, through the planning and posting of all the actual costs, to the final
settlement and archiving:
Implementation Considerations
Order management within a company usually differentiates between sales-oriented orders, and
internal orders. Sales-oriented orders (production or sales orders) are intended mainly for the
logistical control of input factors and sales activities. Internal orders are categorized as either:
• Orders used only for monitoring objects in Cost Accounting (such as, advertising or trade fair
orders)
• Productive orders that are value-added, that is, orders that can be capitalized (such as in-
house construction of an assembly line).
Internal order management is the most detailed operational level of cost and activity accounting.
It can be used for:
• Cost monitoring, for example, where costs need to be looked at from object-related
aspects, unlike in Cost Element Accounting or Cost Center Accounting
• Assisting decision-making, when you need to decide between in-house production and
external procurement
An enterprise’s internal orders can be used for different controlling purposes. For more
information, see Classified by Controlling Objectives [Ext.].
Features
• You can use master data [Page 35] to assign certain characteristics to your internal orders,
which enables you to control which business transactions can be used with the internal order.
• Internal order planning [Page 36] enables you to roughly estimate the costs of a job before
the order starts and to make an exact calculation at a later date. You can choose between
various planning approaches to compare the effectiveness of different methods.
• You can assign and manage budgets [Ext.] for internal orders.
• You apply the actual costs incurred by a job to your internal orders using actual postings
[Ext.]. In Financial Accounting, you can assign primary cost postings (such as the
procurement of external activities and external deliveries) directly to internal orders.
• In period-end closing [Page 47] you can use various different allocation methods (for
example, overhead costing) to allocate costs between different areas of Cost Accounting.
Order settlement [Page 51] enables you to transfer the costs incurred by an order to the
appropriate receivers.
• The information system for internal orders [Page 82] enables you to track planned and
assigned costs on your orders in each stage of the order life-cycle.
December 1999 33
CO Component Short Description SAP AG
Internal Orders
• You can archive internal orders that you no longer require. See Archiving [Ext.].
34 December 1999
SAP AG CO Component Short Description
Master data in internal orders
Features
For more information on the classification of order master data, see Structuring the Order Layout
[Ext.].
You can print master data for internal orders, using forms adaptable to your needs. For more
information, see the implementation guide (IMG), under Controlling →=Internal Orders →==Order
Master Data=→=Prepare for Order Printing [Ext.].
See also:
Creating an Internal Order [Ext.]
December 1999 35
CO Component Short Description SAP AG
Planning in Internal Orders
Unlike cost center planning, you can plan overhead rates on internal orders (except
for statistical orders) as well as overheads.
Implementation Considerations
Cost planning is performed mostly on internal orders with long durations. You do not usually plan
internal orders that only exist for a very short period (such as, internal orders for unexpected
small repairs). You can plan order costs in more than one version and using various planning
forms, depending on when you are planning and the information available.
Integration
You can manage the approved cost framework for an internal order or an order group using
Budget Management [Ext.].
Features
The SAP system provides you with a range of planning functions for the processing of internal
orders covering the different levels of planning detail required at different stages of order
execution:
Integrated Planning
Integrated Planning for Internal Orders [Ext.] allows you to settle internal order plan data to cost
centers or business processes. You can then transfer them to Profit Center Accounting and the
General Ledger. To do this, you should note the difference between:
• Plan-Integrated Internal Orders
Plan-integrated internal orders enable you to plan cost elements and activity inputs
integrated with cost centers and business processes in a plan version. The system
updates plan allocations directly to the cost center or the business process. You can
settle plan integrated internal orders to cost centers and business processes in the plan.
You then transfer the plan data to Profit Center Accounting and the Extended General
Ledger.
• Non-Plan-Integrated Internal Orders
You can only plan costs and activities locally on non-plan-integrated internal orders.
There is no scheduling on the performing cost centers or business processes. You
cannot execute a plan settlement of these orders to cost centers and business
36 December 1999
SAP AG CO Component Short Description
Planning in Internal Orders
processes. Neither can you transfer the data to Profit Center Accounting or the General
Ledger.
Types of Planning
• Manual Internal Order Planning [Page 39]
Activity-dependent or activity independent planning of both primary and secondary costs,
which occur as a result of activity input.
• Overall Planning for Internal Orders [Ext.]
• Unit Costing [Ext.]
• Primary Cost and Revenue Planning [Ext.]
• Planning Activity Input [Ext.]
• Planning Statistical Key Figures [Ext.]
• Planning Allocations [Ext.]
Automatic internal order planning of the allocations made at period-end closing.
• Periodic Reposting in Planning [Page 40]
• Planning Overhead Rates [Ext.]
• Planned Settlement for Internal Orders [Ext.]
• Allocations from Cost Centers [Ext.]
Planning of allocations that occur during period-end closing from cost centers to orders.
Period-End Closing
In period-end closing, you can debit an order in version 0 using overhead, assessments or
distribution. You can also execute a periodic reposting of plan-integrated internal orders. You do
this by debiting or settling indirect activity allocation.
Planning Documentation
You can record changes to internal order planning in planning documents. You normally do so for
changes in a plan that has already been approved. You use the Write plan line items activity,
December 1999 37
CO Component Short Description SAP AG
Planning in Internal Orders
which you allow by setting an appropriate user status (see also: Status Management for Internal
Orders [Ext.]) to define whether and from which status planning documents are written.
38 December 1999
SAP AG CO Component Short Description
Manual Internal Order Planning
Integration
The various types of planning are only possible if the relevant business transactions are
permitted.
Features
These planning types are not mutually exclusive, but you can also use them in a combination.
Depending on the information status, you use one or more of the planning types listed below.
This means that for certain parts of an internal order, you can use unit costing or cost element
planning, while roughly estimating the costs of the other parts of the order using overall planning.
Function Use See also:
Overall planning Overall planning is the simplest way of planning Overall Planning
costs on internal orders. This type of planning does [Ext.]
not depend on cost elements. You can use it to
plan overall and annual values for an internal order.
Unit costing If you have access to more information on sources Unit Costing [Ext.]
planning of supply, quantities and prices, you can perform
unit costing taken from the overall planning.
Cost/revenue You use these types of planning when you have Primary Cost and
element and detailed information on costs. Each planning type is Revenue Planning
activity input carried out for one year and covers cost-element- [Ext.]
planning related planning of primary costs, revenues and
Planning Activity
activity inputs.
Input [Ext.]
If more than one currency is permitted within your
controlling area, the system will propose a value
date each time you use cost element planning. You
can overwrite this date if required.
Planning You can plan statistical key figures in order to Planning Statistical
statistical key calculate the business-related key figures in orders. Key Figures [Ext.]
figures
December 1999 39
CO Component Short Description SAP AG
Periodic Reposting in Planning
Features
At the period end, the costs (first collected on a costs collector, such as an order, or cost center)
are reposted to the corresponding receivers, using keys (internal order, cost center). The
following data remains unchanged:
• The original cost element (primary cost element or revenue cost element)
• The accounting proof of origin
For more information on this subject, see Periodic Reposting [Page 48] in cost center planning.
You can execute periodic repostings of costs on internal orders, regardless of the version
in the plan, if you activated integrated planning of internal orders with Cost Center
Accounting (see also Indicator for Integrated Planning in the Version [Ext.]).
40 December 1999
SAP AG CO Component Short Description
Overheads
Overheads
Purpose
You use overhead costing to allocate overhead through percentage-based or quantity-based
overhead rates. The basis for the allocation are the primary cost elements that you post as
overhead costs. In the manufacturing industry, for example, these are usually the labor and
material costs.
Integration
To make an overhead costing, you need to define control data in customizing for the
corresponding application, and include this in a Costing sheet [Ext.].
Features
You can apply overhead to both plan and actual costs, or on the basis of commitment data.
Constraints
You start Overhead Calculation [Ext.] using its own transaction. This means that you cannot carry
out transaction-based overhead calculation.
December 1999 41
CO Component Short Description SAP AG
Settlement
Settlement
Purpose
The SAP components all handle settlement of business objects using the same settlement logic.
During settlement, some or all of the plan or actual costs incurred on an object are allocated to
one or more receivers. The system automatically generates offsetting entries to credit the sender
object. The debit postings assigned once to a sender object remain in place, even after
settlement to a receiver (and can therefore be displayed). The costs settled are updated on the
corresponding receiver object and displayed in reporting.
IM Settlement AA
to fixed asset
Investment order
Valuation areas
L 50.- Curr. type Area
K (40.-) 50.- 01 01
P (60.-) 50.- 11 31
50.- 21 32
A line item settlement to a fixed asset is only possible, if the legal valuation is the
operational valuation.
For more information on settlement of investment measures, see IM - Investment Management
[Ext.] in the Investment Measures (Orders/Projects), Settlement functions, Settlement sections.
42 December 1999
SAP AG CO Component Short Description
Budget Management
Budget Management
The budget is the approved cost structure for a project.
It differs from project cost planning in that it is binding. While you must estimate costs as
accurately as possible during the planning phase, it is in the approval phase that you prescribe
your project funds, in the form of a budget. The budget is the device by which the management
approves the expected development of project costs over a given timeframe.
Budget Allocation
Submitted Approved
budget budget
Budget
Total planned costs
Top-down
Bottom-up distribution
summation
• Original budget
The original budget is the budget originally allocated - that is, the budget before any updates
were carried out. From a point in time which you stipulate, it can only be amended by means
of budget updates.
• Budget updates
Unforeseen events, additional requirements, prices rises, and so on, may mean that you
need to correct the original budget - that is, budget updates are necessary. These take the
form of:
– Supplements
– Returns
– Transfers
• Current budget
The current budget is calculated as follows:
Original budget
+ Supplements
- Returns
December 1999 43
CO Component Short Description SAP AG
Budget Management
+/- Transfers
= Current budget
• Releases
In many businesses, budget distribution is not the same as releasing the funds. For this
reason, the Project System includes a separate funds release facility, which you can use to
make successive budget releases. The release is based on the current budget - that is, the
original budget as amended by budget updates.
This section describes:
• How you can carry out budget updates [Page 67] in the form of supplements, returns,
and transfers
44 December 1999
SAP AG CO Component Short Description
Commitments Management
Commitments Management
Purpose
CO Commitments Management enables you to enter and analyze commitments [Ext.] at an early
stage, and thus to account for them in controlling.
Implementation Considerations
Purchase orders or purchase requisitions lead to financial commitments with varying degrees of
obligation (See also: Commitments Management Flow [Ext.]). Commitments reserve funds for
costs that will be incurred at a future date. Therefore, commitments must be included in funds
monitoring.
For more information on funds commitment, see Funds Commitment [Page 26].
Integration
In Commitments Management, data from the following SAP components is processed integrally:
• Controlling (CO)
In Controlling you can perform tasks such as planning, checking and controlling costs.
Commitments management is a part of the cost monitoring process. Commitments are
displayed either on internal orders, cost centers, or projects.
• Materials Management (MM)
This covers tasks such as material requirements planning, purchasing, goods receipt,
inventory management, and invoice verification. Commitments are created through purchase
requisitions and purchase orders. Commitments are reduced by various business
transactions such goods receipt. The commitments data is transferred to Controlling.
Features
• Creation of Commitments
For example, specific goods are ordered for an internal order, a cost center, or a project.
A purchase order commitment is created that is equivalent to the purchase order value.
• Commitments Display
Commitments are always displayed with a value and, if required, a quantity for the cost
element, the fiscal year, and the period when the costs are expected to be incurred (See
also: Commitments Information System [Ext.]).
• Commitments Currency
The system executes all commitments in the currency used, in the original business
transaction (for example in the ordering transaction). It then translates the amount into
the controlling area currency, company code currency and the object currency. The PO
currency exchange rate is used for currency translation.
• Reducing the Commitment:
The commitment is reduced by business transactions (such as goods receipts) and
actual costs are incurred by the corresponding account assignment object. This
continues until, for example, the business transaction "Purchase order" is closed and the
purchase order commitment is reduced to zero.
December 1999 45
CO Component Short Description SAP AG
Commitments Management
46 December 1999
SAP AG CO Component Short Description
Period-End Closing in Internal Orders
Features
The following belong to periodic actual postings:
• Revaluation at Actual Prices [Ext.]
• Calculating Overhead [Page 62]
• Periodic Reposting [Page 48]
• Actual Template Allocation [Ext.]
For more information, see Template [Ext.].
• Internal Order Settlement [Page 51]
• Assessment and Distribution Methods
December 1999 47
CO Component Short Description SAP AG
Periodic Repostings
Periodic Repostings
Use
Periodic Repostings [Ext.] enable you to adjust postings made to your cost centers, business
processes, internal orders, or WBS elements. They lead to the same result as transaction-based
repostings. The results of transaction-based repostings have a direct effect on the actual costs of
the sender and the receiver, whereas periodic repostings have a one-time effect on actual costs
at period-end closing.
Postings relevant to Controlling (CO) such as telephone costs, postal charges, insurance, and so
on are entered in Financial Accounting (FI) and posted to an allocation cost center or a business
process. These are used exclusively for cost collection. This minimizes the number of different
account assignments you have to make when entering data in FI. At the end of the period, the
collected costs are reposted to the cost centers or business processes which incurred the costs
by of means user-defined keys (fixed values or dynamic tracing factors). The following
information is passed on to the receivers:
• The original cost element (that is, the primary cost element [Ext.]) is retained.
During periodic repostings, you can allocate activity-dependent plan costs to receiver
objects of the category “Cost center” (sender activity type is retained) or "business
process".
You can allocate activity-independent costs to all receiver object categories, for
example, cost centers, business processes, or orders.
• The allocation cost center is not important for the receiver cost centers (neither is the sender
business process for the receiver processes). The SAP System therefore stores data records
for periodic reposting in a way that uses less memory than for, say, distribution [Ext.]. For this
reason, the sender cost center or sender process is not updated with this method. You can
only analyze from which cost center or from which business process the costs originate from
the line items, and not from the totals records.
48 December 1999
SAP AG CO Component Short Description
Periodic Repostings
Telephone 06/1998
Allocation
Allocation rule
rule
such
such as,
as, meter
meter readings
readings
. . .Administration Administration
...
Telephone Primary
Primary cost
cost element
element Telephone
06/1998 06/1998
- Posting aid
- without sender-receiver information
If you are working with Transfer Prices [Ext.] (parallel value flows) the periodic
reposting is executed in parallel in all valuations. The costs to be allocated are taken
from the corresponding valuation. The tracing factor is always taken from the
operational valuation. The values allocated may differ in the different valuation
methods.
Senders and receivers are displayed in the results list, differentiated according to the
parallel actual versions of the various valuations.
For more information about transfer prices, see the SAP Library under AC
Accounting → Enterprise Controlling → Profit Center Accounting → Transfer Prices
(see: Transfer Prices [Ext.]) and under Parallel Valuations [Ext.].
See also:
Defining Periodic Repostings or Periodic Allocations [Ext.]
Creating or Changing Cycles [Ext.]
Executing Periodic Repostings or Periodic Allocations Online [Ext.]
Displaying the Cycle Overview [Ext.]
December 1999 49
CO Component Short Description SAP AG
Overheads
Overheads
Purpose
You use overhead costing to allocate overhead through percentage-based or quantity-based
overhead rates. The basis for the allocation are the primary cost elements that you post as
overhead costs. In the manufacturing industry, for example, these are usually the labor and
material costs.
Integration
To make an overhead costing, you need to define control data in customizing for the
corresponding application, and include this in a Costing sheet [Ext.].
Features
You can apply overhead to both plan and actual costs, or on the basis of commitment data.
Constraints
You start Overhead Calculation [Ext.] using its own transaction. This means that you cannot carry
out transaction-based overhead calculation.
50 December 1999
SAP AG CO Component Short Description
Internal Order Settlement
Features
To be able to settle an order, you must have saved a settlement rule in each of the senders. This
settlement rule determines where the costs are to be settled to. You can achieve this in two
ways:
• Settlement to One Receiver
You use this basic form of order settlement to completely settle the costs collected on the
internal order. This is either to a cost center, or a G/L account under a settlement cost
element. The system generates the appropriate settlement rule from the information
contained in the internal order master data.
For more information on order settlement to one receiver, see Order Settlement To One
Receiver [Ext.].
• Comprehensive Settlement
Definition of a comprehensive settlement rule gives you more settlement possibilities, for
example, you can:
• Settle costs to a wide range of receivers (project, sales order, profitability segment, and so
on).
• Specify how the costs are to be distributed between receivers.
• Define the cost elements under which the sender is to be credited and the receivers debited.
For more information on comprehensive settlement, see Settlement [Page 42].
Constraints
You can only use one of these settlement methods at a time: For example, if you defined
settlement to one cost center in the master data for an internal order, then you can only define a
more comprehensive settlement rule once you have deleted the first rule.
December 1999 51
CO Component Short Description SAP AG
Summarization
Summarization
Use
You need more than a cost structure analysis of individual internal orders (Internal Orders [Ext.],
Production Orders [Ext.], Projects) to ensure efficient controlling. You need to be able to group
together account assignment objects with common attributes and analyze them collectively. This
provides a much greater degree of cost transparency within your organization.
You can, for example, summarize and analyze the costs of all your orders according
to the following criteria:
• Order type [Ext.]
• Responsible cost center
• Plant [Ext.]
Integration
You can summarize internal orders, production orders and projects collectively.
For more information on project summarization, see Project Summarization [Ext.].
Features
For reporting purposes, summarization collects account assignment objects with common
attributes.
You can use summarization initially to obtain an overview of a large number of orders. It is also
useful for processing order groups containing large variances. You can then analyze relevant
account assignment objects individually, using the cost element reports. This means that you do
not have to analyze each account assignment object individually.
Summarization hierarchy
You use characteristics to define the individual levels of the summarization hierarchy. These
characteristics refer to the fields in the master data for the account assignment object.
The controlling area is always the top node in the summarization hierarchy. To summarize
account assignment objects, you need to differentiate between those and the others in the same
controlling area. You do this by using a characteristic in the corresponding hierarchy
identification.
For more information on summarization hierarchies, see Summarization Hierarchies [Ext.] or the
IMG for the relevant summarization object.
For more information on classification and order summarization, see Cost Object Controlling
[Ext.].
Summarization Reports
The following standard summarization reports are available:
• Summarization objects: Actual/plan/variance
52 December 1999
SAP AG CO Component Short Description
Summarization
Compares the plan and actual costs for the selected subhierarchy.
• Summarization objects: Actual/plan/commitment
Compares the costs already assigned and those still available. The value in the Assigned
column is calculated by adding actual cost and commitment values. The difference
between the plan costs and the assigned costs is displayed in the last column as
available costs.
• Summarization objects: Curr. Period/Cum./Total
Compares the plan and actual costs for a selected period, the entire fiscal year, and
cumulated.
December 1999 53
CO Component Short Description SAP AG
PS Project System
PS Project System
Purpose
Both large scale projects, such as building a factory, and small-scale projects, such as organizing
a trade fair, require precise planning of the many detailed activities involved. The project
manager has the job of ensuring that the project is executed efficiently, on time, and within
budget - which he or she achieves by ensuring that the required resources and funds are
available as and when needed.
Projects are generally part of the internal processes of a company. To be able to control all tasks
in project execution, you need an organizational form that is specific to the project and which is
shared by all departments involved. Before you can carry out a project in its entirety, the project
goals must be precisely described and the project activities to be carried out must be structured.
A clear, unambiguous project structure is the basis for successful project planning, monitoring,
and control.
You structure your project per the following points of view:
• By structures, using a work breakdown structure (WBS)
• By process, using individual activities (work packages)
Project managers usually distinguish between two types of project:
• Externally financed projects
− Customer projects
• Internally financed projects
− Overhead cost projects
− Capital investment projects
For further information on capital investment projects, see Investment Management [Ext.].
Integration
The high degree of integration between the Project System (PS) and other R/3 application
components means that you can plan, execute, and account for projects as part of your normal
commercial procedures. This means the Project System has constant access to data in all the
departments involved in the project.
Features
The R/3 Project System guarantees close and constant monitoring of all aspects of your project.
This includes both technical and commercial aspects of the project.
54 December 1999
SAP AG CO Component Short Description
Master Data
Master Data
Definition
You can use the master data to define the structure of your overhead cost project, and enter
neutral settings on a cross-project basis.
December 1999 55
CO Component Short Description SAP AG
Standard WBS
Standard WBS
Definition
A template that can be used several times to create work breakdown structures. Standard work
breakdown structures are not specific to a project.
Selection criteria
If you choose this component, you can copy standard work breakdown structures to create new
work breakdown structures. In addition, you must select this component if you use the Sales and
Distribution component (SD) and you want to create a customer project from a customer inquiry,
quotation or sales order within assembly processing.
56 December 1999
SAP AG CO Component Short Description
WBS Maintenance
WBS Maintenance
Definition
“WBS maintenance” includes creating or changing control parameters, standard values and other
data in work breakdown structures.
December 1999 57
CO Component Short Description SAP AG
PS Text Management
PS Text Management
Definition
“PS Text Management” is a word processing program for project-specific texts and documents,
such as functional specifications, logs, or notes required for a project.
Selection criteria
If you choose this component, you can create and manage documents with SAP’s own word
processing program SAPScript. In addition, with this component you can upload and download
texts created with external word processing programs.
58 December 1999
SAP AG CO Component Short Description
Cost Planning
Cost Planning
Purpose
Cost planning deals with the costs you expect to incur in connection with your project as it is
executed.
Cost planning has different aims at different stages of the project:
• At the concept and rough planning stage, cost planning acts as the base for an initial cost
estimate.
• At the approval stage, it forms the basis for the budget allocation.
• During project execution, you use cost planning to monitor and control cost variances.
Cost planning in the Project System is effected by means of the WBS and networks.
In the network, the emphasis is on planning not costs, but dates, human resources, and
operating resources. The costs are calculated automatically on the basis of an existing
price/quantity structure. You always use cost planning by means of networks if you are using
complex project processing - that is, if dates and resources, as well as costs, are relevant to you.
If planning and monitoring of costs is most important, as in, say, capital investment projects or
overhead cost projects, you should plan your costs using manual cost planning in the WBS.
Integration with Controlling and Financial Accounting is effected by means of the WBS.
Features
• Manual Cost Planning in the Work Breakdown Structure [Page 60]
• Planning Costs in Networks [Ext.] , based on price and quantity structures
• Planned costs from assigned orders recorded in the project.
• Cost forecast for calculated plan costs, based on variances during project execution.
December 1999 59
CO Component Short Description SAP AG
Manual Cost Planning in the Work Breakdown Structure
Implementation Considerations
Depending on when you plan and the information then available, you can enter different versions
and forms of project cost planning.
Integration
You use budget management [Page 64] to manage the approved cost framework for a project.
The graphic below shows how cost planning and budgeting complement each other.
Cost Planning
Budget Budget
applied for approved
Budget
Overall plan
Top down-
Bottom up- distribution
Summation
Features
Various ways of planning costs in the WBS are available, as are functions which cover the
various degrees of detail at the various stages of project execution.
Plan Integration
Within the framework of integrated project planning, you can settle plan data or business
processes, and pass them on to profit centers and the general ledger.
Plan integration in projects is the same as plan integration in internal orders.
See also Plan Integration for Internal Orders [Ext.] .
60 December 1999
SAP AG CO Component Short Description
Manual Cost Planning in the Work Breakdown Structure
Plan-Integrated Projects
Plan-integrated projects offer integrated planning of cost elements and activity inputs with cost
centers and business processes in one plan version. The system updates allocations directly in
the cost center or business process.
Non-Plan-Integrated Projects
In projects which are not plan-integrated, you can only plan costs and activities locally. No
planning takes place in the performing cost centers or business processes.
Planning Methods
The WBS includes various planning methods in the WBS element, from which you can choose
depending on the state of the project and the degree of detail you need.
December 1999 61
CO Component Short Description SAP AG
Overheads
Overheads
Purpose
You use overhead costing to allocate overhead through percentage-based or quantity-based
overhead rates. The basis for the allocation are the primary cost elements that you post as
overhead costs. In the manufacturing industry, for example, these are usually the labor and
material costs.
Integration
To make an overhead costing, you need to define control data in customizing for the
corresponding application, and include this in a Costing sheet [Ext.].
Features
You can apply overhead to both plan and actual costs, or on the basis of commitment data.
Constraints
You start Overhead Calculation [Ext.] using its own transaction. This means that you cannot carry
out transaction-based overhead calculation.
62 December 1999
SAP AG CO Component Short Description
Orders for Projects
• Internal orders
Internal orders are used at the level of cost and service accounting - for example, to
monitor costs
• Production orders
Production orders are used in the manufacture of goods.
• Sales orders
Sales orders are contractual agreements between a sales organization and a sold-to
party concerning the supply of materials or the rendering of services at defined prices
and times, and in defined quantities.
You can assign sales order items or customer quotation items to a WBS element (billing
element). If you do, revenue and cost controlling takes place wholly within the project.
The quotation/order does not bear either costs or revenues.
In the following, the term “orders for the project” covers networks and activities too. You cannot
enter a budget for orders for networks.
December 1999 63
CO Component Short Description SAP AG
Budget Management
Budget Management
The budget is the approved cost structure for a project.
It differs from project cost planning in that it is binding. While you must estimate costs as
accurately as possible during the planning phase, it is in the approval phase that you prescribe
your project funds, in the form of a budget. The budget is the device by which the management
approves the expected development of project costs over a given timeframe.
Budget Allocation
Submitted Approved
budget budget
Budget
Total planned costs
Top-down
Bottom-up distribution
summation
• Original budget
The original budget is the budget originally allocated - that is, the budget before any updates
were carried out. From a point in time which you stipulate, it can only be amended by means
of budget updates.
• Budget updates
Unforeseen events, additional requirements, prices rises, and so on, may mean that you
need to correct the original budget - that is, budget updates are necessary. These take the
form of:
– Supplements
– Returns
– Transfers
• Current budget
The current budget is calculated as follows:
Original budget
+ Supplements
- Returns
64 December 1999
SAP AG CO Component Short Description
Budget Management
+/- Transfers
= Current budget
• Releases
In many businesses, budget distribution is not the same as releasing the funds. For this
reason, the Project System includes a separate funds release facility, which you can use to
make successive budget releases. The release is based on the current budget - that is, the
original budget as amended by budget updates.
This section describes:
• How you can carry out budget updates [Page 67] in the form of supplements, returns,
and transfers
December 1999 65
CO Component Short Description SAP AG
Allocating the Original Budget
66 December 1999
SAP AG CO Component Short Description
Updating the Budget
• Supplements
• Returns
• Transfers
You can also make budget updates using the change function. The system logs the
changes as line items. The time at which you “freeze” the original budget and enter
budget update depends on when you want to log proofs of origin - that is, sender-
receiver relations - for your budget updates. You thus use the budget updates, when
you want to record where supplements, returns, and transfers came from and where
they went to.
You use status management to control this. For example, the business transaction
Budgeting is allowed in the Created system status. You then create a system status
that forbids this transaction, but allows budget supplements, returns and transfers.
Having defined your original budget, you set this user status, so that budget updates
are only possible using supplements, returns, and transfers. For more information,
read the status management section.
If availability control is active for a project, each budget update is subject to
availability control. For more information, read the section on Availability Control
The current
budget is
calculated as
follows:
Original budget
+ Supplements
- Returns
+/- Transfers
= Current budget
December 1999 67
CO Component Short Description SAP AG
Updating the Budget
68 December 1999
SAP AG CO Component Short Description
Releasing the Budget
You can release the budget of a project or for a single WBS element. Simply enter
the appropriate WBS element.
This brings you to the screen Change Release: WBS Element Overview.
The further procedure for releasing the budget is the same as that for allocating the original
budget. You can make releases at overall and/or annual level (as defined in the budget profile).
All the budget allocation functions, such as copying views are available for releasing budget.
See also: Allocating Original Budget [Page 66]
Checking Releases
As in budget allocation, you can access a checking function at any time. The system checks
releases automatically when you post them. If availability control is not active, you can save your
budget releases without any check taking place. If, however, availability control is active, this is
no longer possible. The system will then only permit the budget release if there are no errors in it.
• Project structure
Within the project structure, the system ensures that the funds released in lower-level WBS
elements (distributed values) do not exceed those in the higher-level elements. The check is
in controlling area currency, but includes budget line items entered in other currencies.
• Time
In each WBS element, the system checks that the total of annual releases (accumulated
releases) does not exceed the overall release. This check is made in the current currency.
Budget line items entered in other currencies are not checked.
• If availability control is active In Project System configuration, you can define whether
availability control checks activities against the overall budget, annual budget, overall
December 1999 69
CO Component Short Description SAP AG
Releasing the Budget
release, or annual releases. If availability control is active, the following checks are also
made:
– Availability control against overall releases
In this case, the system checks whether assigned values (actual + commitment)
exceed the overall release.
– Availability control against annual releases
In this case, the system checks whether values assigned in a year exceed the
budget released for that year.
The check is in controlling area currency, but includes budget line items entered in other
currencies.
For more information on how to activate availability control, see Activating Availability
Control [Ext.].
70 December 1999
SAP AG CO Component Short Description
Availability Control
Availability Control
Availability Control [Ext.]
Online [Ext.]
December 1999 71
CO Component Short Description SAP AG
Actual Costs
Actual Costs
Definition
“Actual costs” are the costs incurred as the project is executed. You enter actual costs when you
enter commercial activities, such as goods receipts of confirmations, in WBS elements.
72 December 1999
SAP AG CO Component Short Description
Periodic Project Closing
December 1999 73
CO Component Short Description SAP AG
Periodic Transfer
Periodic Transfer
Definition
The “periodic transfer” is a posting tool which you can use to allocate the primary costs collected
in a clearing cost center to WBS element, using a key you have defined and retaining the original
cost element (the cost element in the sender cost center).
74 December 1999
SAP AG CO Component Short Description
Overhead Surcharges
Overhead Surcharges
Definition
Flat-rate, percentage, or fixed amount added to direct costs, which enables overhead costs to be
allocated accurately to the individual cost objects where they were originally incurred.
Selection criteria
You need to select overhead surcharges if you want to include them in cost planning.
December 1999 75
CO Component Short Description SAP AG
Interest Calculation
Interest Calculation
Definition
The interest calculation is based on the payment, down payment and internal activity documents.
In projects, only the balance interest calculation on a daily basis is available.
Selection criteria
If you select this component, you must also select the Cash Budget Management component in
Treasury.
76 December 1999
SAP AG CO Component Short Description
Project Settlement
Project Settlement
Definition
The actual costs arising in a WBS element, network order or network activity are settled, in whole
or in part, to one or more receivers.
Selection criteria
You need to select project settlement if you want to transfer the costs determined in results
analysis periodically to Profitability Analysis, Financial Accounting and Profit Center Accounting.
December 1999 77
CO Component Short Description SAP AG
Cost Information System
Selection criteria
The cost information system can supply evaluations at any time, in differing degrees of detail and
summarization, showing cost, budget and actual values from the overhead cost project.
78 December 1999
SAP AG CO Component Short Description
Information System
Information System
Purpose
The R/3 System offers a comprehensive, flexible information system to analyze cost flows in an
organization. With the information system functions, you can carry out standard recurring
evaluations; you can also construct special reports for unique situations. Following their entry into
the SAP System, you can analyze all costs online and in real-time, and trace them right back to
the original document. You can execute all reports available online in background runs as well.
This is especially helpful for large amounts of data.
For hierarchically grouped objects, such as cost centers, you can create separate reports for all
hierarchy nodes and individual objects, or you can create all the relevant reports in a single
selection run through the database. The second option allows you to navigate within a hierarchy.
This enables particularly flexible monitoring of cost center areas.
Features
The information system includes functions:
• For report callup
• For report processing
• For defining reports using Report Painter [Ext.] and Report Writer [Ext.]
See also:
Report Callup with Extract Management [Ext.]
Creating a Report Painter Report [Ext.]
December 1999 79
CO Component Short Description SAP AG
Information System
Information System
Use
The information system supports speedy evaluations across all system application components.
You can use the reports supplied by SAP or define your own reports to suit your individual
requirements.
80 December 1999
SAP AG CO Component Short Description
Important Standard Reports in Cost Center Accounting
December 1999 81
CO Component Short Description SAP AG
Information system For Internal Orders
Features
Report/Report Interface
Most reports allow you to mark given rows and then, using the Report call function, to branch to
another report containing detailed information.
You can branch from a total cost report to a cost element report, from where you can
start a line item report.
82 December 1999
SAP AG CO Component Short Description
Business Process Reports
Selection criteria
The standard reports can be divided roughly into the following areas, where multiple reports exist
for each area:
• Cost center reports
• Business process reports
• Cost object reports
• Master data directories
• Line item reports
December 1999 83
CO Component Short Description SAP AG
Report Definition
Report Definition
Use
The CO information system has the task of formatting the postings created in the application
component according to various criteria. However, it is not possible to cover all user
requirements through the information system. Minor adjustments to the reports are often required
or new reports have to be created.
Features
Report Painter
The central tool for defining reports within the information system is the Report Painter [Ext.].
With Report Painter you can define reports quickly and easily across rows and columns. During
the definition process, the system displays the report as it will appear when it is displayed on the
screen.
For minor modifications to the standard report delivered by SAP you can use this as a model.
The R/3 System also provides a variety of row and column models as modules for your own
report definition. These models enable you to create reports simply and flexibly.
You do not need to create sets [Ext.] when working with Report Painter. You can enter
characteristic values directly. Reports can be divided into sections and column blocks during
definition.
To access the Report Painter menu from Cost Center Accounting, choose Information system →
Tools → Report Painter.
For more information about Report Painter, see the R/3 Library, under FI Financial Accounting
→==FI Special Purpose Ledger →=Report Writer Reports. (see: Report Painter Reports [Ext.]).
Report Writer
If you want to define a report that differs from the standard, you can use the Report Writer [Ext.]
report definition.
Report Writer lets you define reports that are structures on the basis of sets. A set is an arranged
quantity of similar elements, such as cost centers, cost elements and posting periods. The
modules available for use in the reports are summarized by the R/3 System in a report table. This
allows you to use the sets in any reports of a report table.
Working with Report Writer involves a longer learning process than Report Painter. Since Report
Painter covers the majority of the functions of Report Writer, but is easier to use, you should
generate as many of your reports as possible through Report Painter.
To access the Report Writer menu from Cost Center Accounting, choose Information system →
Tools → Report Painter → Report Writer.
For more information about Report Painter, see the R/3 Library, under FI Financial Accounting
→==FI Special Purpose Ledger →=Report Writer Reports. (see: Report Writer Reports [Ext.]).
84 December 1999
SAP AG CO Component Short Description
Report Definition
December 1999 85
CO Component Short Description SAP AG
Activity-Based Costing
Activity-Based Costing
Purpose
You can use the Activity-Based Costing component (CO-OM-ABC) to provide a process-oriented,
cross-functional view of overhead in addition to the traditional, location-oriented view provided by
the Cost Center Accounting component (CO-OM-CCA). The Activity-Based Costing component
thus enhances the Cost Center Accounting component.
The Activity-Based Costing component allocates process quantities based on resource and
process drivers , allowing you to define cost allocation more exactly along the Value Added
Chain [Ext.] that is possible with overhead rates. Activity-Based Costing (ABC) likewise
enhances product costing by assigning the sources of costs to their originating business
processes. Cost center resources can allocate to business processes based on their true
utilization of activities.
CO-OM-
ABC
Product Families
Products ABC Customers
Distribution Channels
CO
...
-P
-PC
CO
By including ABC in profitability analysis, you create more realistic views of your revenue
position.
The primary goal is not just improving individual aspects of processes, but rather the optimization
of entire process chains. Other goals of ABC include shortening lead times and improving quality.
86 December 1999
SAP AG CO Component Short Description
Activity-Based Costing
Features
As of R/3 System Release 4.0, you can use the Activity-Based Costing component parallel to the
existing traditional cost accounting system, or you can use it as an operational component
integrated with product costing and profitability analysis in the Controlling component (CO).
See also:
Parallel Activity-Based Costing [Ext.]
Integrated Activity-Based Costing [Ext.]
December 1999 87
CO Component Short Description SAP AG
Process Costs: Actual Postings
88 December 1999
SAP AG CO Component Short Description
Master Data in the Activity-Based Costing Component
You can use the relationships between business processes to mirror the flows and
allocation structure of your organization on a process-oriented basis. These
structures, as a rule, remain constant over long periods. Based on the business
process structure, you can carry out business process planning and create period-
based reports for business processes and areas, to be used by the responsible
manager for analysis. You can use these reports to locate unprofitable areas and
mistakes in planning for the individual business processes. In order to be able to
compare results, you should not change the master data they are based upon.
You generally maintain master data once before activating the Activity-Based Costing component
(CO-OM-ABC). You can enter master data manually, or you can use interface programs to
transfer data from non-SAP systems.
The master data for Activity-Based Costing is stored in master data tables.
When you transport master data (between clients, for example), you must use
additional master data tables not described in this section.
Integration
The concept of the R/3 System distinguishes between:
• Master data
• Transaction Data
Transaction Data
Transaction data is the information based on business transactions that the current R/3 System
continually accepts or changes during processing.
Transaction data for the Activity-Based Costing component (CO-OM-ABC) is found in line item and totals tables
where you can access the information as part of business process analysis and line item reports.
Line item tables receive the results of the following individual posting transactions:
• Financial Accounting component (FI) postings
December 1999 89
CO Component Short Description SAP AG
Master Data in the Activity-Based Costing Component
The financial accounting bookings are saved in the FI component and the line item
booking tables of the CO component, generating redundancies. However, this is
necessary due to the different evaluations in both areas. Financial Accounting
component evaluations are based on the connections between documents, whereas
Controlling component evaluations differentiate between primary and secondary
costs.
• Controlling postings in actual:
− Distribution
− Assessment
− Internal activity allocation
• Controlling postings in plan:
− Manual planning
− Price calculation
Actual postings generally update line items; updates are optional in plan.
For more information, see Line Items and Integrated Planning [Ext.]
Total tables receive the totals of all line items by cost element and serve as a summarization of
the line item tables.
90 December 1999
SAP AG CO Component Short Description
Business Process Planning
December 1999 91
CO Component Short Description SAP AG
Product Cost Controlling
92 December 1999
SAP AG CO Component Short Description
Product Cost Controlling
In the R/3 system, actual costing refers to materials, which are calculated using a
preliminary standard price. They are recalculated using the price variation of the actual
costs.
The system collects the preliminary standard price and its variances (such as price or
exchange variances) internally for every business transaction related to valuation (such
as goods receipt, invoice receipt or production order settlement). At the end of the
period, you can settle these variances to material stocks and consumption from the
previous period. This takes place at several manufacturing levels. This is how you
achieve a material valuation, which is based upon time-related actual values.
• Product Cost Controlling Information System
An efficient report range for the Product Cost Planning, Cost Object Controlling and
Actual Costing/Material Ledger areas is available in the information system in Product
Cost Controlling. You can evaluate data created in these components using standard
and special reports.
Selection Criteria
These components provide basic information for the following business functions:
• Price determination and price policy
• Inventory valuation
• Manufactured Goods Controlling
• Profitability Analysis
• Profit Center Accounting
December 1999 93
CO Component Short Description SAP AG
Product Cost Planning
Implementation Considerations
Costing must be performed at the plant level. The following figure provides an overview of the
organizational structures required for costing:
94 December 1999
SAP AG CO Component Short Description
Product Cost Planning
Client
Client
Controlling
Controlling area
area 11 Controlling
Controlling area
area 22
Company
Company code
code Company
Company code
code Company
Company code
code
11 22 33
Valuation
Valuation area
area Valuation
Valuation area
area Valuation
Valuation area
area
11 22 33
Plant
Plant 11 Plant
Plant 22 Plant
Plant 33
Materials are always valuated at the level of the valuation area. You define whether the material
valuation is to be carried out plant level or at company code level in the step Define valuation
level in Customizing under Enterprise Structure → Definition → Logistics - General.
If, for example, you want to use the Product Cost Planning (CO-PC-PCP) component to access
the costing results for material valuation purposes, you must first define in Customizing that
valuation is to be carried out at plant level. This ensures that each plant has its own valuation
area, which is especially important from the costing point of view because all the costing data is
saved with reference to a particular plant.
Integration
In order to carry out costing, Product Cost Planning accesses master data in other SAP
components, such as BOMs, routings, and work centers from Production Planning, and cost
centers, activity types, and business processes from Overhead Cost Controlling. After costing,
you can use the cost estimate results to update the data in other components, such as by
transferring the results to the material master as the standard price and use this price to valuate
the material(s).
For more information, see Information for Other R/3 Applications [Ext.].
Because of this high integration of data, SAP recommends that you make a thorough check to
make sure that the correct data is accessed for the quantity and value structures before starting
Product Cost Planning, in order to ensure that the costing results are reliable.
For more information about integration, see Origin of Quantities, Prices, and Dates [Ext.].
Features
The following table gives you an overview of the menu and functions of Product Cost Planning:
December 1999 95
CO Component Short Description SAP AG
Product Cost Planning
Reference and Base object cost Is created using data that you enter
Simulation Costing estimate [Page 102] manually (unit costing)
96 December 1999
SAP AG CO Component Short Description
Product Cost Planning
You use the costing tools provided by Product Cost Planning according to the availability of data
in Production Planning (PP and/or PP-PI) and to the type of reference object that you want to
cost (see graphic below) :
X
Base
planning
object (PCP) Reference and Reference and
Simulation Costing Simulation Costing
December 1999 97
CO Component Short Description SAP AG
Product Cost Planning
Activities
You can access the functions of Product Cost Planning from either the Accounting menu or the
Logistics menu:
• Accounting → Controlling → Product Cost Controlling → Product Cost Planning
• Logistics → Production → Product Cost Planning
• Logistics → Production - process → Product Cost Planning
You make all the settings for Product Cost Planning in Customizing for Product Cost Controlling.
For more information, see Preparing for Costing: Customizing [Ext.] and the Implementation
Guide (IMG) for Product Cost Controlling.
98 December 1999
SAP AG CO Component Short Description
Material Cost Estimate with Quantity Structure
Implementation Considerations
The cost estimate with quantity structure presupposes that a bill of materials and routing (PP) or
a master recipe (PP-PI) exist for the material to be costed . For more information about this, see
Master Data for the Cost Estimate with Quantity Structure [Ext.].
Features
The cost estimate with quantity structure [Ext.] uses the PP or PP-PI master data to determine
the material consumption and internal activities required to produce the product. The cost
estimate is created automatically using this data.
You can use the costing run [Ext.] to process mass data.
There are a number of reports in the cost estimate itself and in the information system for
Product Cost Controlling [Page 131] that you can use to display the costing results together with
the relevant quantity structure:
• Costed multilevel BOM [Ext.]
• Itemization [Ext.]
In addition to the PP-oriented displays of the costing results mentioned above, there is a cost
component split for each material that divides the costs into cost components [Ext.]:
• Cost component split for the cost of goods manufactured [Ext.]
• Primary cost component split [Ext.]
• Partner cost component split [Ext.]
See also:
Purpose of Product Cost Planning [Ext.]
Calculation of Cost of Goods Manufactured and Cost of Goods Sold [Ext.]
December 1999 99
CO Component Short Description SAP AG
Material Cost Estimate Without Quantity Structure
Integration
A cost estimate without quantity structure can access data in the following components of the R/3
System:
• Materials Management (MM), such as material master records and services
• Production Planning (PP), for example work centers and resources
• Controlling (CO), such as cost centers and activity types
For further information ,see Master Data for Unit Costing [Ext.].
Features
If you want to carry out costing without a quantity structure (consisting of BOMs and routings)
existing in the R/3 System, you can create the material cost estimate as a unit cost estimate (cost
estimate without quantity structure) and enter the data manually.
You can thus calculate the costs for a multilevel production structure without access to the BOMs
and routings from PP. You create the quantity structure manually using unit costing [Ext.]. For
each semifinished product, you create a cost estimate that assigns the costs to cost elements
and cost components. You specify these semifinished products as material items when costing
the highest-level material. The costing results of the highest-level material then contain the costs
of the lower materials.
You create a spreadsheet, which can consist of materials, internal activities, external activities,
services, processes, variable items and overhead. The system determines the prices for the
costing items entered.
Because the cost elements remain transparent in the itemization [Ext.], you can compare the cost
estimate with the following:
• The preliminary cost estimate of a production order
• With actual postings from other areas of the R/3 System
See also:
Creating a Material Cost Estimate Without Quantity Structure [Ext.]
Unit Costing [Ext.]
Master Data for Unit Costing [Ext.]
Creating Costing Items [Ext.]
Valuation of Costing Items [Ext.]
Integration
In base object costing, you can access data in the Controlling, Materials Management and
Production Planning modules.
You can access data that already exists in the R/3 System, such as:
• Data from Controlling (CO), such as cost centers, activity types and prices, process costs,
base planning objects
• Data from Materials Management (MM), such as materials, and prices for materials
For further information ,see Master Data for Unit Costing [Ext.].
Features
You create base planning objects to plan new products or services. They provide the data
required for management decisions as to the manufacture of products, the provision of services,
or whether the product should be produced internally or externally.
You enter the additive costs manually in the form of a unit cost estimate.
You can use the base planning object as follows:
• As a building block in other cost estimates, such as other base object cost estimates, or
material cost estimates without quantity structure
• As a reference when planning other objects in the R/3 System, such as WBS elements, CO
production orders
• To simulate the effects on costs following changes to production factors or to the exchanging
of materials or internal activities
You can use a base planning object in the costing of the following objects in the R/3 System:
• Other base planning objects
• Materials (material cost estimate without quantity structure and additive cost estimate for the
material)
• General cost objects
• Production orders without quantity structure
• Sales document items
• WBS elements (projects)
• Network components
• General costs activities
• Internal orders
• Primary cost elements
Price Update
Purpose
Once you have carried out a cost estimate for a material, you can transfer the costing results to
the material master as prices (see graphic).
Material
Cost est. for
master
the material:
You can update the results of the various material cost estimates, depending on the purpose of
costing [Ext.], in selected price fields in the material master [Ext.]:
Type of price updated in Cost estimate
material master
Future and current Standard cost estimate (see Updating the Standard Prices [Ext.])
standard price
Commercial or tax-based Inventory cost estimate (see Tax-Based Prices and Commercial
prices 1-3 Prices [Ext.])
Other planned prices 1-3 Modified standard cost estimate, current cost estimate, standard or
inventory cost estimate (see Update of Other Planned Prices
[Ext.])
Prerequisites
The Saving allowed indicator has been set for the costing variant. For more information, see
Saving the Costing Results [Ext.].
The setting has been made in the costing type specifying that the costing results can be updated
in the material master.
• Indicator Standard price:
The costing results can be updated as the standard price in the material master.
• Indicator Tax-based price or Commercial price:
The costing results can be updated as the tax-based or commercial price in the material
master. In such cases, the determination of lowest value applies. This means that the
prices are only updated if they represent the lowest value.
Integration
First, you can update the costing results in the material master. Second, within the cost estimate
you can access the various prices in the material master in order to valuate the materials for the
cost estimate (see graphic). You can specify these prices from the material master in the
valuation variant in Customizing, and use them in further cost estimates, such as inventory prices
for inventory cost estimates. You can find further information under Valuation of Materials [Ext.].
+ Material costs
Material + Production costs
master + Overhead
You can also use the costing results in other applications. For more information, see Purpose of
Product Cost Planning [Ext.] and Information for Other R/3 Applications [Ext.].
You can cost three parallel values (legal valuation view, group view, profit center view). You can
update the results of all three valuation views. For further information about multiple valuation
approaches, see Multiple Currencies and Valuations for Materials [Page 129] in the R/3 Library
under Actual Costing/Material Ledger (CO-PC-ACT).
See also:
• Standard cost estimate [Ext.]
• Inventory cost estimate [Ext.]
• Modified standard cost estimate [Ext.]
• Current cost estimate [Ext.]
Implementation Considerations
Here are some of the ways you can utilize the Cost Object Controlling component:
• To determine whether the actual cost of an order matched or exceeded the planned cost
• To determine the production variances between actual costs and target costs, and why these
occurred
• To decide whether to accept a particular sales order (whether the sales order will be
profitable or not)
• To determine where your company has particularly low costs and therefore which cost
objects it should concentrate on
• To decide whether it would be more profitable to manufacture a cost object in-house or to
outsource it
• To determine whether and how the cost of goods manufactured can be optimized
Cost Object Controlling also can provide special information on:
Integration
Before you use the Cost Object Controlling (CO-PC-OBJ) component in the R/3 System, you
establish the planned (budgeted) costs for each product in a cost estimate. You can use various
costing methods in Product Cost Planning (CO-PC-PCP) for this purpose.
Cost Object Controlling accesses master data and transaction data in Production Planning (PP),
Production Planning - Process Industries (PP-PI), Materials Management (MM), Sales and
Distribution (SD), and Overhead Cost Controlling (CO-OM).
You can view the data of Cost Object Controlling in the Product Cost Controlling Information
System (CO-PC-IS).
When you settle, you can transfer the data of Cost Object Controlling to other components in the
system:
• Actual Costing / Material Ledger (CO-PC-ACT)
• Financial Accounting (FI) for purposes such as capitalizing unfinished and finished products
and automatically creating reserves
• Profitability Analysis (CO-PA) to analyze the costs by market segment
• Profit Center Accounting (EC-PCA) to analyze the results by profit center
See also: Integration of Cost Object Controlling [Ext.]
Features
All postings of actual data that refer to a cost object result in an immediate debit of the cost
object.
The closing activities at the end of the period allow you to do the following:
• Revaluate activities at actual prices
• Allocate overhead using template allocation and by defining overhead rates for cost objects
• Determine the work in process (the value of unfinished goods)
• Determine the variances between target costs and actual costs
• Transfer the calculated data to other objects and application components
• Compile periodic reports on a regular basis
Reporting functions are supported by the Cost Object Controlling Information System.
In the R/3 System, you can analyze planned costs, target costs, actual costs, and quantity
information at various levels, such as that of the plant, product group, or individual cost objects.
The data are always available in real time.
Drilldown capabilities enable you to access detailed information.
From the evaluations at plant level, you drill down to the product groups and from
there down to materials/products or individual orders.
See also:
The sections following this one tell you:
• Which cost objects you can use in the R/3 System
• The relationship between Product Cost Planning and Cost Object Controlling
• Which master data you use
• The different forms of Cost Object Controlling available
This documentation also provides detailed background information on the functions provided in
Cost Object Controlling and the different scenarios available.
Cost Object Controlling in the R/3 System is divided into the following subcomponents:
• Product Cost by Order [Page 113]
• Product Cost by Period [Page 109]
• Product Cost by Sales Order [Page 116]
• Costs for Intangible Goods and Services [Page 120]
For detailed information on creating material cost estimates, such as for the purpose of
calculating the standard costs of your materials, see the document Product Cost Planning.
For detailed information on evaluating data in the information system, see the document Product
Cost Controlling Information System.
The present documentation does not contain detailed information on cost accounting for projects.
For information on cost accounting in engineer-to-order environments, refer to the document
Project System.
Implementation Considerations
You normally use the Product Cost by Period component in the following situations:
• In repetitive manufacturing environments
In repetitive manufacturing environments, you always collect and analyze your costs on
product cost collectors.
• In make-to-order or process manufacturing when you are not interested in managing your
costs at the order level In this case, instead of using the manufacturing orders as the basis
for Cost Object Controlling, you create a product cost collector.
• When you have costs that you cannot (or do not want to) assign to particular orders
You then assign these costs to the cost object nodes in a cost object hierarchy.
Integration
For general information on Cost Object Controlling, refer to the section Cost Object Controlling
[Ext.].
You can use both the Product Cost by Period component and the Product Cost by Order
component in conjunction with the Product Cost by Sales Order [Page 116] component.
When production orders or process orders are assigned to a cost object hierarchy, you use the
Product Cost by Order [Page 113] component in conjunction with the Product Cost by Period
component.
You can see the costs in the Product Cost Controlling Information System (see also: Information
System for Product Cost by Period [Ext.]).
Features
You analyze the costs of product cost collectors in the Product Cost by Period component.
Product cost collectors enable realization of lean cost management scenarios that are not
integrated with the logistics components.
The use of product cost collectors does not prevent you from performing logistical functions on
the manufacturing order or production version (such as goods issues, confirmations, and goods
receipts). The costs incurred from the logistical transactions are updated directly on the product
cost collector.
– You enter reporting point backflushes in repetitive manufacturing. The product cost
collector is charged with actual costs.
– You create a goods receipt in repetitive manufacturing. The product cost collector is
credited.
If you are in a sales-order-related production environment and are using a valuated sales order
stock in repetitive manufacturing, you can collect the costs for individual requirements materials
on product cost collectors. (See also: Product Cost Collectors in Sales-Order-Related Production
[Ext.])
You can use cost object hierarchies in addition to collecting costs at the level of product cost
collectors. You can distribute the costs assigned to the cost object nodes to the orders on the
basis of keys. You can then calculate and analyze the variances on the orders. It is also possible
to calculate the variances on the cost object nodes instead of distributing the costs.
In the Product Cost by Period component you always calculate the work in process at target
costs. All orders used in the Product Cost by Period component have the settlement type PER
(periodic).
You can do the following at the end of the period:
• Allocate process costs to product cost collectors and to the cost object hierarchy.
• Revaluate activities and business processes at actual prices
• Allocate overhead
• Distribute the actual costs if you are using a cost object hierarchy
• Calculate work in process for the product cost collector
• Calculate variances for the cost object hierarchy or for the product cost collector
• Transfer data to other application components such as FI, EC-PCA, CO-PA, and CO-PC-
ACT
Constraints
Period-based cost management at the level of manufacturing orders is not recommended. At the
level of manufacturing orders, you should perform lot-based cost controlling in the Product Cost
by Order component.
In sales-order-related production, product cost collectors are possible if you are using a valuated
sales order stock and the production environment is repetitive manufacturing. If you are
manufacturing on the basis of production orders and process orders in sales-order-related
production, you cannot use product cost collectors as cost objects.
You cannot use the Product Cost by Period component together with the Product Cost by Sales
Order component in sales-order-related production environments when you are using a
nonvaluated sales order stock [Ext.]. The reason for this is that all orders in which the sales order
item is the settlement receiver have the settlement type FUL (full settlement).
See also:
Recommendations for repetitive manufacturing environments are provided in the following
section:
Recommendations for Repetitive Manufacturing [Ext.]
For detailed information on the Product Cost Controlling Information System, see the
documentation Product Cost Controlling Information System [Page 131].
For detailed information on Profitability Analysis (CO-PA), see the document CO Profitability
Analysis.
For detailed information on Profit Center Accounting (EC-PCA), see the document EC Enterprise
Controlling.
Implementation Considerations
You can use the Product Cost by Order component in the following situations:
• In sales-order-related production [Ext.] environments when you are using complex make-
to-order production [Ext.] with valuated sales order stocks [Ext.] and want to calculate the
work in process and variances at the level of the logistical orders (production orders and
process orders)
In this case you use the Product Cost by Order component together with the Product
Cost by Sales Order component.
• In sales-order-related production environments with mass production on the basis of
sales orders [Ext.] when you are using valuated sales order stocks and you want to
concentrate your cost-management efforts more on the costs of the logistical orders than
on the cost of the products
• In make-to-stock environments [Ext.] when you want to focus on the cost of the order
When based on manufacturing orders, the Product Cost by Order component is particularly
suitable for measuring the cumulative cost of lots (that is, when the settlement rule specifies full
settlement).
You can implement Product Cost by Order with production orders and process orders in order-
related production or process manufacturing environments.
Integration
For general information on Cost Object Controlling, refer to the section Cost Object Controlling
[Ext.].
You can use both the Product Cost by Order component and the Product Cost by Period
component in conjunction with the Product Cost by Sales Order component.
You can use the Product Cost by Order component with projects.
You can look at the costs in the Product Cost Controlling Information System.
Features
You can analyze costs of manufacturing orders by period. However, SAP recommends lot-based
cost controlling for manufacturing orders. The manufacturing order must have settlement type
FUL (full settlement) in this case.
You can implement Product Cost by Order with or without the Production Planning application
component. If the Production Planning component is not installed, you can create a production
order without a quantity structure [Ext.] in Controlling.
In Product Cost by Order, you can link production orders and process orders into a collective
order [Ext.].
You can represent joint production with process orders and production orders. (See also: Special
Requirements in Joint Production [Ext.]).
When you are costing by lot, you calculate the work in process using the actual costs (difference
between debits and credits for the order). When you are costing by period, you calculate the work
in process at target costs based on the confirmed operations or reporting points.
You can do the following at the end of the period:
• Allocate process costs to the manufacturing orders
• Revaluate activities and business processes at actual prices
• Allocate overhead
• Calculate the work in process, variances, and scrap
• Transfer data to other application components such as FI, EC-PCA, CO-PA, and CO-PC-
ACT
The information system allows you to summarize the data in various ways, so that you can view
the costs by material, by order type, or by plant.
Constraints
If you are using the Product Cost by Sales Order component with a nonvaluated sales order
stock [Ext.], you cannot calculate work in process or variances for production orders or process
orders assigned to a sales order item. Variance calculation is not supported by the system when
you are using a nonvaluated sales order stock. Standard costing is therefore not possible in this
case. However, all these functions are available if you are using a valuated sales order stock.
See also:
You can cost production orders and process orders by period. For information on the Product
Cost by Period functions, such as on using cost object hierarchies, refer to the documentation on
the application component Product Cost by Period [Page 109].
You can use production orders and process orders in conjunction with the Product Cost by Sales
Order component. It is advisable to use the Product Cost by Sales Order component together
with cost object controlling on the basis of lots. For more information, refer to the documentation
on the application component Product Cost by Sales Order [Page 116]. This document also
provides information on the special aspects of valuated sales order inventories, such as
calculating standard prices.
For detailed information on logistical processing, see the documentation PP Production Planning
and PP-PI Production Planning Process Industries.
You can view the data of the Product Cost by Order component in the information system in a
number of different formats. For more information, see the document Product Cost Controlling
Information System.
For detailed information on Profitability Analysis (CO-PA), see the document CO Profitability
Analysis.
For more information on Profit Center Accounting, see the document EC Enterprise Controlling.
For more information on engineer-to-order environments, see the document Project System.
For information on rework, see the following sections:
Integration of Rework for Production Orders [Ext.]
Representing Rework in the System [Ext.]
Rework Operations and Rework Quantities [Ext.]
Rework and Confirmations [Ext.]
Preliminary Settlement for Co-Products, Rework [Ext.]
Preliminary Settlement for Rework [Ext.]
Performing Preliminary Settlement for Co-Products, Rework [Ext.]
The Product Cost by Sales Order component enables you to do the following:
• Calculate and analyze planned costs and actual costs by sales document item
• Calculate and analyze planned revenues and actual revenues by sales document item
• Revaluate the activities and business processes allocated to the cost objects with actual
activity prices
• Allocate the overhead costs to the cost object using overhead calculation or dynamic
process allocation
• Calculate the value of goods that have been delivered to your customer but not invoiced
• Create reserves automatically
• Transfer data to Financial Accounting (FI)
• Transfer data to Profitability Analysis (CO-PA)
• Transfer data to Profit Center Accounting (EC-PCA)
Implementation Considerations
You use the Product Cost by Sales Order component in the following situations:
• When you want to analyze costs and revenues for sales document items
• When you are using a nonvaluated sales order stock
Integration
Product Cost by Sales Order accesses master data and transaction data in Controlling (CO),
Sales and Distribution (SD), and Materials Management (MM). In manufacturing enterprises,
Product Cost by Sales Order also accesses data in Production Planning (PP) or Production
Planning for the Process Industries (PP-PI).
If you are a manufacturing enterprise, you normally use Product Cost by Sales Order in
conjunction with Product Cost by Order or Product Cost by Period.
To estimate the costs for materials, you use the Product Cost Planning component (CO-PC-
PCP).
You can display planned costs, target costs and actual costs in the Product Cost Controlling
Information System (CO-PC-IS).
Features
With the Product Cost by Sales Order component you can collect and analyze costs for:
• The manufacturing orders (production orders and process orders) and product cost
collectors assigned to a sales order item
• The purchase orders assigned to a sales order item
• Funds commitments in inventory
You can supplement the display of these funds commitments with the purchase
requisition commitment and the purchase order commitment for the sales order item.
• The trading goods in a sales order item
If you are not using Sales and Distribution, you can create a customer
requirement for the material in Production Planning. The costs and revenues can be
assigned to this requirement and analyzed in the information system.
Constraints
You cannot determine variances for the sales document item.
See also:
For information on valuated sales order stocks, read the following sections:
Valuated Sales Order Stock [Ext.]
Update of Valuated Sales Order Stock [Ext.]
Standard Price with Valuated Sales Order Stocks [Ext.]
Viewing Valuated Special Stocks [Ext.]
Example for Valuated Sales Order Stock Without Product Cost by Sales Order: Quantity and
Value Flow [Ext.]
Product Cost Collectors in Sales-Order-Related Production [Ext.]
Variances with a Valuated Sales Order Stock [Ext.]
For information on sales order items that carry costs and revenues, refer to the following section:
Sales Order Item That Carries Costs and Revenues [Ext.]
Features
This component allows you to do the following:
• Determine the costs for a general cost object over its entire life or by period
When you cost a general cost object by period, you can plan your costs on the basis of
statistical key figures. You can also calculate your actual costs in this case on the basis
of statistical key figures.
You can analyze the difference between the planned costs and the actual costs in the
Product Cost Controlling Information System.
• Collect actual costs on a general cost object when the actual costs were incurred from:
− Goods movements
− Postings in Financial Accounting
− Postings in Controlling
• Collect revenues on internal orders if the internal orders can carry revenues
• Perform results analysis for the internal order when you are using internal orders that carry
revenues
In the period-end closing activities you can:
• Allocate process costs to the cost objects
• Revaluate activities and business processes at actual prices
• Allocate overhead
• Perform results analysis if you are using internal orders that carry revenue
• Transfer data to other application components such as FI, EC-PCA, and CO-PA
Constraints
If you are using a general cost object in the Costs for Intangible Goods and Services component,
you cannot assign revenues to this cost object.
See also:
You can view the data of the Costs for Intangible Goods and Services component in the
information system in a number of different reports. For more information, refer to the document
Product Cost Controlling Information System [Page 131].
For more information on internal orders, refer to the documentation CO Internal Orders [Page
33].
For more information on results analysis, refer to the following documentation:
Product Cost by Sales Order [Page 116]
For more information see Periodic Material Valuation [Ext.] and Multilevel Actual Costing [Ext.].
Prerequisites
The material ledger is active.
The price determination indicator 3 is set in the material master.
The price control indicator 3 is set in the material master.
Level
Finished Level
product
Level
Semi-
Level
finished
product
Level
Raw Level
material
The differences that arise during the procurement of a material are included in single-level
material price determination.
• Price differences
These occur when the amount posted for a movement differs from the standard price in
the material master record. The following transactions can cause these differences:
− Goods receipts resulting from a purchase order
− Invoice receipts
− Settling production orders, process orders, and run schedule headers
− Transfer postings
− Initial entry of stock balances with values
− Free delivery
− Inward movements from consignment stock to the company’s own stock
• Exchange rate differences
These occur when an amount in a foreign currency is translated using different exchange
rates. This is the case, for example, when the exchange rate at the time of the invoice
entry differs from the exchange rate at the time of the goods receipt.
• Differences from revaluations
These occur, for example, from a credit/debit to a material, a price change, or a posting
to a prior period.
The price calculated through price determination is updated as a moving average price (V price)
in the Accounting 1 view of the material master record. The price control indicator S remains set.
The standard price does not change.
Constraints
Materials whose prices are determined with transaction-based price determination cannot be
considered later in multilevel actual costing.
See also:
Periodic Material Valuation [Ext.]
Multilevel Actual Costing [Ext.]
Transaction-Based Material Price Determination [Ext.]
Features
In multilevel actual costing, the system calculates a new valuation price for a material using both
the material ledger master data and quantity structure data across all manufacturing levels.
Price changes
Use
Using this function, you can change prices, mark prices for change and release prices for
material valuation.
If the material ledger is active, a price change for a material with price determination 3 (single-
and multi-level material price determination) is only possible if there have been no goods
movements relevant to valuation and no incoming invoices for the material in the period.
If the material ledger is not active, it is always possible to change material prices, regardless
which price control has been set for the material.
• If a material is valuated at the standard price, it is always valuated at the same price. The
development of delivered prices is included in the material master for statistical purposes, but
not used for material valuation. The price differences are posted to a price difference
account.
• If a material is valuated at the moving average price, the price changes with every goods
movement and incoming invoice if the purchase order price or invoice price varies from the
moving average price. In other words, the price automatically reflects the delivered price.
You can make a price change in the following two ways:
• In a processing step with immediate effect
For more information, see Changing Material Prices [Ext.].
• In a two-step procedure
For more information, see Determining Future Prices [Ext.] and Releasing Planned Prices
[Ext.].
When making changes with immediate effect, you can post a price change to the previous period
or year. For more information, see Posting Price Changes to the Previous Period or Year [Ext.].
Features
If you activated the material ledger, you can maintain valuation prices independent of one
another in up to three currencies and/or valuations. If the material ledger is not active, you only
maintain the valuation prices in company code currency with legal valuation. You can perform the
following functions:
Future planned prices are calculated in the standard cost estimate. The results of a standard cost
estimate take first priority as the valuation price for materials with price control S. For more
information, see Product Cost Planning [Ext.].
If multiple planned prices exist for a material, they will be treated by the system according to the
following priorities:
1. Marked standard cost estimate
Release
Standard
Cost Estimate
Future Current
Standard
Plan
Stück -
Standard
liste
Price Price (S)
Period 1
Manual
Release
Future
Valuation Price
Current
Future
Valuation
Valuation
-
Price
Price (S/V)
Maintaining future valuation prices in the material master record is possible in all set
currencies. Translation into further currencies is performed with the exchange rate
set in Financial Accounting.
See also:
Debiting / Crediting Materials [Ext.]
Determining Future Prices [Ext.]
Releasing Planned Prices [Ext.]
Changing Material Prices
[Ext.]Displaying Price Changes [Ext.]
Material Valuation in the SAP System [Ext.]
Integration
The system makes historical currency translation possible for valuation-relevant transactions.
This means that items are translated using the exchange rate that was valid at the time of posting
that item.
Currency amounts that come from stock valuation, invoice verification, cost estimates, and order
settlement are translated into the other currencies in the respective areas and updated in the
material ledger.
You post an invoice receipt. The system translates the amount into the currencies
specified in the material ledger at the current exchange rate.
You settle a production order that is carried in two currencies/valuations. The values
in the production order correspond to currencies/valuations that are carried in the
material ledger. These values are not translated in the material ledger, but rather
transferred directly. The amount in the third currency is translated from the company
code currency using the average rate.
You mark a standard cost estimate, which has results in two currencies/valuations.
The results are not translated in the material ledger, but rather transferred directly.
The amount in the third currency is translated using the amount in the company code
currency and the exchange rate at the time of marking.
During actual costing, the system calculates new valuation prices and new inventory values
independent of each other in the different currencies/valuations.
Material Settlement
This procedure also means that over the course of time, the price of a material could rise in one
currency while falling in another.
Features
In the standard system, exchange rate differences are calculated in which the exchange rates at
goods receipt and invoice receipt are compared. In Customizing for Invoice Verification, you can
specify that exchange rate differences should not be translated using the exchange rate at goods
receipt, but rather with an assumed exchange rate, which can be held constant for a period of
time (such as a year or a season). Using these Customizing settings, you can also specify that all
exchange rate differences are to be regarded as price differences.
See also:
Multiple Value Flows in Financials [Ext.]
Multiple Values for Material Stocks Using the Material Ledger [Ext.]
Integration
The information system is a part of Product Cost Planning, the application component Cost
Object Controlling, and Actual Costing / Material Ledger.
Features
The standard setup of the Product Cost Controlling Information System is a structured report list
from which you can choose the reports you need.
The standard reports provided in the R/3 System are presented in a tree structure. You can
change this SAP tree structure to suit your own needs, and add your own custom reports. For
more information, see: Customer Modification to the Information System [Ext.]
The documentation for the Product Cost Controlling Information System is oriented around the
structure of the SAP report tree. This ensures easy access to the desired information in the
documentation, as navigating through the documentation mirrors navigating through the report
tree.
See also:
Information System for Product Cost by Period [Ext.]