171 BB ConfigGuide en US Configuration: Cost Object Controlling by Period

EHP4 for SAP ERP 6.0 June 2010 English Cost Object Controlling Repetitive (171) Building Block Configuration Guide SAP AG Dietmar-Hopp-Allee 16 69190 Walldorf Germany SAP Best Practices Cost Object Controlling – Repetitive (171): Configuration Guide Copyright © Copyright 2010 SAP AG. All rights reserved. No part of this publication 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, Excel, Outlook, and PowerPoint are registered trademarks of Microsoft Corporation. IBM, DB2, DB2 Universal Database, System i, System i5, System p, System p5, System x, System z, System z10, System z9, z10, z9, iSeries, pSeries, xSeries, zSeries, eServer, z/VM, z/OS, i5/OS, S/390, OS/390, OS/400, AS/400, S/390 Parallel Enterprise Server, PowerVM, Power Architecture, POWER6+, POWER6, POWER5+, POWER5, POWER, OpenPower, PowerPC, BatchPipes, BladeCenter, System Storage, GPFS, HACMP, RETAIN, DB2 Connect, RACF, Redbooks, OS/2, Parallel Sysplex, MVS/ESA, AIX, Intelligent Miner, WebSphere, Netfinity, Tivoli and Informix are trademarks or registered trademarks of IBM Corporation. Linux is the registered trademark of Linus Torvalds in the U.S. and other countries. Adobe, the Adobe logo, Acrobat, PostScript, and Reader are either trademarks or registered trademarks of Adobe Systems Incorporated in the United States and/or other countries. Oracle is a registered trademark of Oracle Corporation. UNIX, X/Open, OSF/1, and Motif are registered trademarks of the Open Group. Citrix, ICA, Program Neighborhood, MetaFrame, WinFrame, VideoFrame, and MultiWin are trademarks or registered trademarks of Citrix Systems, Inc. HTML, XML, XHTML and W3C are trademarks or registered trademarks of W3C®, World Wide Web Consortium, Massachusetts Institute of Technology. Java is a registered trademark of Sun Microsystems, Inc. JavaScript is a registered trademark of Sun Microsystems, Inc., used under license for technology invented and implemented by Netscape. SAP, R/3, SAP NetWeaver, Duet, PartnerEdge, ByDesign, SAP Business ByDesign, and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG in Germany and other countries. Business Objects and the Business Objects logo, BusinessObjects, Crystal Reports, Crystal Decisions, Web Intelligence, Xcelsius, and other Business Objects products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of Business Objects S.A. in the United States and in other countries. Business Objects is an SAP company. All other product and service names mentioned are the trademarks of their respective companies. Data contained in this document serves informational purposes only. National product specifications may vary. These materials are subject to change without notice. These materials are provided by SAP AG and its affiliated companies ("SAP Group") for informational purposes only, without representation or warranty of any kind, and SAP Group shall not be liable for errors or omissions with respect to the materials. The only warranties for SAP Group products and services are those that are set forth in the express warranty statements accompanying such products and services, if any. Nothing herein should be construed as constituting an additional warranty. © SAP AG Page 2 of 21 for example. transaction codes. EXAMPLE TEXT Keys on the keyboard. These include report names. <Example text> Variable user entry. when surrounded by body text. Example text Emphasized words or phrases in body text. EXAMPLE TEXT Names of elements in the system. Cross-references to other documentation.SAP Best Practices Cost Object Controlling – Repetitive (171): Configuration Guide Icons Icon Meaning Caution Example Note Recommendation Syntax Create Work Center Typographic Conventions Type Style Description Example text Words or characters that appear on the screen. source code. titles of graphics and tables. program names. These include field names. paths and options. pushbuttons as well as menu names. These are words or characters that you enter in the system exactly as they appear in the documentation. screen titles. names of variables and parameters as well as names of installation. function keys (such as F2) or the ENTER key. Example text Screen output. table names. for example. upgrade and database tools. messages. SELECT and INCLUDE. Pointed brackets indicate that you replace these words and characters with appropriate entries. Example text Exact user entry. This includes file and directory names and their paths. © SAP AG Page 3 of 21 . and individual key words of a programming language. .......................3...............3.......................1.................1..1.....................1...................5........3...7...................1..............1....1..................................1....1....1..................2 Preparation..1..1 1.......1...........................5 1...............5.................................1....11 Define Assignment for Results Analysis...2 Plants Define Cost-Accounting-Relevant Default Values for Order Types and 20 Page 4 of 21 ...................3 Create Settlement Profile.....5.................11 Define Line ID’s.................5 1................................... 5 1.......3....................3..1..........................2 1........7 1............................3............5..3....1..........5..................................... 5 Configuration...................4 Define Goods Received Valuation for Order Delivery...3 1...........2 Create Costing Variant for Preliminary Costing on PCC................3.......8 1.1.14 Define Results Analysis Version........1....................9 1..................18 1......8 1..3...........5.............................9 Define Results Analysis Version..............3 Prerequisites..........................3....................3..7.16 1.......................... 5 1.......................................................1................................1 1............18 CO-PC-OBJ Manufacturing Orders......5 1....................................2..............1 Check Order Types (YBMR).......3.................................................1 Cost Object Controlling – Repetitive...................16 1..........5............................................2. 5 1................3... Check Settlement Profile.................5..19 1.....3...........................5 Period End Closing.......3...12 Define Update for Results Analysis............5.......4 1............6..................15 Variances & Settlement.....7 © SAP AG Define Summarization Hierarchy..................3..............................14 Define Posting Rules for Settling Work in Process.................3.1..3........5 1.........1 1.................2...10 Define Valuation Method (Target Costs)........3....5..............................1 Define Default Variance Keys for Plants..................5...1 Work in Process (WIP Calculation)........1........1..........................1 Purpose....................................2 Create Results Analysis Key.................. 9 1...............5...1..................6 1............7 1......15 1............................19 1......................................1..........1...........1...3..1..............1....1 Create Valuation Variants for Product Cost Collector.........................................1..............1..................3...1..........3 Create Costing Variant for Simultaneous Costing on PCC......6 Information System.........3......5.....SAP Best Practices Cost Object Controlling – Repetitive (171): Configuration Guide Content Cost Object Controlling – Repetitive: Configuration Guide.......................8 1.1................3.....2 Define Target Cost Versions.....2..........3......15 1............ The matrix (an Excel file) is linked on the solution's DVD/website in one of the following two locations:  Content Library  Site Map 1. 1.1 Prerequisites Before you start installing this building block.2 Preparation 1. see the Building Block Prerequisite Matrix for Baseline. It consists of preliminary costing.3 Configuration 1.SAP Best Practices Cost Object Controlling – Repetitive (171): Configuration Guide Cost Object Controlling – Repetitive: Configuration Guide 1. refer to the SAP Best Practices Quick Guide. If you do not want to configure manually and prefer an automated installation process using BC Sets and other tools. Access the activity using one of the following navigation options: IMG Menu © SAP AG Controlling  Product Cost Controlling  Cost Object Contolling  Product Cost by Period  Product Cost Collectors  Check Valuation Variants for Product Cost Collectors Page 5 of 21 .1 Cost Object Controlling – Repetitive Cost Object Controlling calculates the costs that incur during a concrete manufacturing situation. Preliminary Costing calculates the target costs of the order. you must install prerequisite building blocks. variance calculation and settlement.1 Create Valuation Variants for Product Cost Collector Use The Valuation Variant controls various parameters regarding the valuation of input items for the object for which costs are being determined.3.2. simultaneous costing and period-end closing.3.1. Simultaneous costing provides an overview over the actual costs incurred on the order so far and compares them to the target costs.  Procedure 1. located on the SAP Note. reconciliation between Controlling and Financial Accounting. For more information.1 Purpose This configuration guide provides you with the information you need to set up the configuration of this building block manually. 1. Period-end closing deals with allocation of overhead costs. master Activity Types / Processes Prio Strategy sequence P/A Version Y06 1 2 Plan price as average of all fiscal year periods 0 YR M 1 1 Plan price for the period 0 Subcontracting: quotation in purchasing Y06 3 Net Quotation Price Quot. YPP-PC Baseline Costing Sheet Not set YPP-PC Baseline Costing Sheet Not set Page 6 of 21 . Order: Planned YRM BP: REM Order: Actual Material Val. to price control in mat. in purchasing : Actual Quota Arrangement YRM 3 Net Quotation Price Quot. Mat. master YR M 1 incl add co 7 Valuation price acc. For each new entry choose Details and enter remaining data.SAP Best Practices Cost Object Controlling – Repetitive (171): Configuration Guide 2. Overview of data records: Valuation Variant Name Y06 BP: Prod. in purchasing : Actual Quota Arrangement External processing Prio Strategy sequence Y06 1 1 Price from Operation Y06 2 3 Net quotation price YRM 1 1 Price from Operation YRM 2 7 Net purchase order price Overhead Materials Y06 YRM © SAP AG Components OH on subc. Choose New Entries and enter header data. to price control in mat. Prio Strategy sequence Y06 1 7 Valuation price acc. choose New Entries and enter header data. Procedure 1. Ctrl Transf. Overview of data records: Valuation Variant Name YPRM BP: Preliminary PCC Control YPRM Costing Type Val. On the Change View ”Costing Variants”: Overview screen. SCE No not set set not set Additive Costs YPRM 1 Ignore Additive Costs YPRM Include Additive Costs with Stock Transfers: not set Update YPRM Saving allowed Save Itemization Save Error Log Defaults changes set set set set Misc. YPRM © SAP AG 3 Log Messages But Do Not Save Them. Then for each new entry choose Details and enter remaining data.3.1. act. On the Choose Activity screen. Access the activity using one of the following navigation options: IMG Menu Controlling  Product Cost Controlling  Cost Object Controlling  Product Cost by Period  Product Cost Collectors  Check Costing Variants for Product Cost Collectors Transaction Code OKKN 2. Variant Date Control Qty. Str.SAP Best Practices 1. Mail Inactive Page 7 of 21 . choose Costing Variants to Determine Activity Quantities. Ctrl 19 Y06 PC01 PC01 PC02 Quantity Structure YPRM Pass on Lotsize Ignore PCE TrCtrl can be chd Transf. such as the costing type or the valuation variant used. 3.2 Cost Object Controlling – Repetitive (171): Configuration Guide Create Costing Variant for Preliminary Costing on PCC Use The Costing Variant controls various parameters when costs for a cost object or a material are being determined. 1. Access the activity using one of the following navigation options: IMG Menu Controlling  Product Cost Controlling  Cost Object Controlling  Product Cost by Period  Product Cost Collectors  Check Costing Variants for Product Cost Collectors Transaction Code OPL1 2. Access the activity using one of the following navigation options: © SAP AG Page 8 of 21 . Procedure 1.3 Cost Object Controlling – Repetitive (171): Configuration Guide Create Costing Variant for Simultaneous Costing on PCC Use The Costing Variant controls various parameters when costs for a cost object or a material are being determined.4 Define Goods Received Valuation for Order Delivery Use This activity determines how the material that is transferred to stock from a production order is valuated. On the Choose Activity screen. Costing Variant Gen. Overview of data records: Costing Variant Name YSRM Product Cost Collector Control YSRM Costing Type Valuation variant 07 YRM Assignment YSRM Misc. On the Change View ”Costing Variants”: Overview screen. choose New Entries and enter header data. choose Costing Variants for Valuation of Internal Activities. costs activity Network component YSRM 1. Then for each new entry choose Details and enter remaining data.3.SAP Best Practices 1.3. Procedure 1.1. such as the costing type or the valuation variant used. 3. Choose New Entries and provide data.3. Overhead surcharge allocates overhead costs to the order as specified in the costing sheet assigned to the order.1 Create Results Analysis Key Use The RA key is a key field in most customizing tables for results analysis. whereby a reconciliation between Controlling and Financial Accounting is achieved. 1.3.The total variance can be transferred to profitability segments in CO-PA. The computed order inventories are then transferred to Financial Accounting.5.1.5 Period End Closing Period end closing consists of several steps.SAP Best Practices Cost Object Controlling – Repetitive (171): Configuration Guide Transaction Code SPRO IMG Menu Controlling  Product Cost Controlling  Cost Object Controlling  Product Cost by Order  Define Goods Received Valuation for Order Delivery 2. Settlement transfer the difference between the debit and credit of the Product Cost Collector to FI. Overview of data records RA Key Text YBMF03 BP WIP target costs © SAP AG Page 9 of 21 . 1.5. It is used differentiate different types of results analysis / WIP calculation and to assign them to the orders.1.1 Work in Process (WIP Calculation) WIP calculation is used to valuate order inventories in period-end closing. WIP calculation reconciliates Controlling and Financial Accounting by valuating and then capitalizing goods that have been produced but not transferred to stock yet. Make the following entries: Valuation Area 1000 1100 Valuation Variant Y01 Y01 1. Access the activity using one of the following navigation options: Transaction Code OKG1 IMG Menu Controlling  Product Cost Controlling  Cost Object Controlling  Product Cost by Period  Period-End Closing  Work in Process  Define Results Analysis Key 2.1.3. Variance Calculation determines variances between he actual costs incurred on the Product Cost Collector and the standard costs of the material produced.1. Procedure 1. Choose Details and provide remaining data.5.2 Define Results Analysis Version Use The RA Version controls various settings related to WIP calculation. this indicator should not be set. The indicator for Transfer to Financial Accounting will be set in step 3. Access the activity using one of the following navigation options: Controlling  Product Cost Controlling  Cost Object Controlling  Product Cost by Period  Period-End Closing  Work in Process  Define Results Analysis Versions IMG Menu Transaction Code OKG9 2. Choose New Entries and provide general data.SAP Best Practices Cost Object Controlling – Repetitive (171): Configuration Guide 1.2007 Actual RA X Planned Results Analysis Cutoff period for planned RA 0 Cost Elements Technical RA cost Element © SAP AG 931000 Page 10 of 21 .1. Procedure 1.1. For Define posting rules for settling WIP step.1.1.5. Overview of data records: CoArea RA Version Text 1000 0 BP: WIP/Results Analysis (Standard) Actual Results Analysis / WIP Calculation Version relevant to Settlement X Transfer to Financial Accounting Multiple Valuation Legal Valuation Extended control Assignment/RA Key X Update/RA Key X Update Plan Values X Status control A Cutoff period for actual 1.8.3. 4 Define Line ID’s Use Cost Elements are grouped to line ID’s in WIP calculation.1.1. Data records to be set for each new entry: WIP Method COAr RA-Version RA key Target Costs 1000 0 YBMF03 Create a New Entry item as in the table below: Co Area RA Version RA Key Status Status RA Type Nr 1000 0 YBMF03 PREL 1 WIP Calculation on Basis of Target Costs 1000 0 YBMF03 REL 2 WIP Calculation on Basis of Target Costs 1000 0 YBMF03 DLV 3 Cancel Data of WIP Calculation and Results Ana 1000 0 YBMF03 TECO 4 Cancel Data of WIP Calculation and Results Ana 1. Procedure 1. RA Key Procedure 1. Access the activity using one of the following navigation options: IMG Menu Transaction Code Controlling  Product Cost Controlling  Cost Object Controlling  Product Cost by Period  Period End Closing  Work in Process  Define Valuation Method (Target Costs) OKGD 2. Prerequisites RA Version.3.3 Cost Object Controlling – Repetitive (171): Configuration Guide Define Valuation Method (Target Costs) Use The valuation method controls various parameters related to WIP calculation. Choose New Entries. enter remaining data and choose Enter. On the New Creation WIP Valuation screen.5.1.1. Access the activity using one of the following navigation options: Transaction Code © SAP AG SPRO Page 11 of 21 .3.SAP Best Practices 1. Further processing then is defined separately for each line ID. 3. then choose WIP method.5. Line IDs Procedure 1. RA Version.5.5 Define Assignment for Results Analysis Use Cost Elements and Cost Element intervals are assigned to line ID’s.1.SAP Best Practices Cost Object Controlling – Repetitive (171): Configuration Guide Controlling  Product Cost Controlling  Cost Object Controlling  Product Cost by Period  Period-End Closing  Work in Process  Define Line IDs IMG Menu 2. Choose New Entries and provide data.1. 1. Prerequisites Cost elements. Access the activity using one of the following navigation options: Transaction Code OKGB Controlling  Product Cost Controlling  Cost Object Controlling  Product Cost by Period  Period-End Closing  Work in Process  Define assignment IMG Menu 2.3. Overview of data records: CoArea Line ID Name 1000 LBR Labor Costs 1000 MAT Material Costs 1000 OVH Overhead Costs 1000 REV Revenues 1000 STL Settled Costs You must not create Line IDs for settlement and revenues. Choose New Entries and provide the following data: Overview of data records: CoArea 1000 1000 RA Version 0 0 RA Key YBMF03 YBMF03 Masked CoEl 0000 510000 Origin ++++ © SAP AG 1000 1000 1000 1000 1000 1000 0 0 0 0 0 YBMF03 YBMF03 YBMF03 YBMF03 YBMF03 YBMF03 0000 510005 0000 510006 0000 510010 0000 510020 0000 510080 0000 610020 0000 510086 ++++ ++++ ++++ ++++ ++++ ++++ ++++ 0 Page 12 of 21 . 2007 001.2007 RecToCap MAT OVH LBR LBR OVH OVH App.2007 001.2007 RecToCap MAT MAT MAT MAT MAT MAT MAT MAT CoArea 1000 1000 1000 1000 1000 1000 RA Version 0 0 0 0 0 0 RA Key YBMF03 YBMF03 YBMF03 YBMF03 YBMF03 YBMF03 Masked CoEl 0000650085 0000943010 0000943030 0000943110 0000943020 0000941+++ Origin ++++ ++++ ++++ ++++ ++++ ++++ Masked CC ++++++++++ ++++++++++ ++++++++++ ++++++++++ ++++++++++ Masked AT ++++++ ++++++ ++++++ ++++++ ++++++ App.2007 001.2007 001. 001.SAP Best Practices Cost Object Controlling – Repetitive (171): Configuration Guide Masked CC Masked AT Bus Proc. + + + + + + Vble/Fix ind.2007 001.2007 001.2007 001. + + + + + + + + Acc ind.2007 001. Reason Bus Proc.2007 001.2007 001. ++ ++ ++ ++ ++ ++ Val-from Per.2007 001.2007 001. D/C ind. + + + + + + Acc ind. ++ ++ ++ ++ ++ ++ ++ ++ Val-from Per. 001. + + + + + + + + Vble/Fix ind. D/C ind. Reason © SAP AG Page 13 of 21 . Access the activity using one of the following navigation options: IMG Menu Controlling  Product Cost Controlling  Cost Object Controlling  Product Cost by Period  Period-End Closing  Work in Process  Define Update Transaction Code OKGA 2. under which RA is performed.6 Cost Object Controlling – Repetitive (171): Configuration Guide Define Update for Results Analysis Use For each line ID a cost element.3.7 Creation WIP Reserves K 931130 931140 MAT K 931110 931120 OVH K 931150 931160 UM Define Posting Rules for Settling Work in Process Use For each RA Category a P/L.5.1. is assigned.3.1. Choose New Entries and enter data. Overview of data records: Co Area Vers RA Key LID Cat 1000 0 YBMF03 LBR 1000 0 YBMF03 1000 0 YBMF03 1.5.1. Prerequisites RA Versions.1. Line IDs Procedure 1. Cost Elements. Access the activity using one of the following navigation options: Transaction Code OKG8 IMG Menu Controlling  Product Cost Controlling  Cost Object Controlling  Product Cost by Period  Period-End Closing  Work in Process  Define Posting Rules for Settling WIP 2.and a balance sheet account is defined where the calculated WIP is posted to when WIP is transferred to Financial Accounting.SAP Best Practices 1. Choose New entries and enter the following values: COArea Company Code RA version RA category Rec number P/L Acct BalSheetAcct 1000 1000 0 WIPR 0 520050 132000 1000 1000 0 RUCR 0 520055 217000 © SAP AG Page 14 of 21 . Procedure 1. Variances are calculated not at once. From the material master the variance key then is transferred to the order when an order for the material is created. Access the activity using one of the following navigation options: Controlling  Product Cost Controlling  Cost Object Controlling  Product Cost by Order  Period-End Closing  Work in Process  Define Results Analysis Versions IMG Menu Transaction Code OKG9 2.5. Access the activity using one of the following navigation options: Transaction Code OKVW IMG Menu Controlling  Product Cost Controlling  Cost Object Controlling  Product Cost by Period  Period End Closing  Variance Calculation  Variance Calculation for Product Cost Collectors  Define Default Variance Keys for Plants © SAP AG Page 15 of 21 .8 Cost Object Controlling – Repetitive (171): Configuration Guide Define Results Analysis Version Use The RA Version is already created in steps before. The variances computed are then transferred to CO-PA.5. but now the transfer to FI will be activated. but for different variance categories.3.2 X Variances & Settlement Variance Calculation determines differences between the actual costs incurred on a production order and the standard costs of the material produced.1.1.3. Procedure 1.3. Choose Details. Select the following data. The system selects the value set by this step as default value when a material master is created. CoArea RA Version Text 1000 0 BP WIP/Results Analysis (Standard) 3.2.SAP Best Practices 1.1.1. 1.1 Define Default Variance Keys for Plants Use The Variance Key is part of the order header and controls variance calculation.5. Procedure 1. Actual Results Analysis / WIP Calculation Transfer to Financial Accounting 1. Set X in the active box for Transfer to Financial Accounting. 3. Access the activity using one of the following navigation options: Transaction Code OKV6 IMG Menu Controlling  Product Cost Controlling  Cost Object Controlling  Product Cost by Period  Period End Closing  Variance Calculation  Variance Calculation for Product Cost Collectors  Define Target Cost Versions 2.5.2 Define Target Cost Versions Use The target cost version controls various parameters related to calculation of target costs in variance calculation. Prerequisites Allocation Structure Procedure 1.5. Access the activity using one of the following navigation options: © SAP AG Page 16 of 21 .2.1.1.3 Create Settlement Profile Use The settlement profile controls various parameters related to settlement. Procedure 1. target costs are needed as a comparison to the actual costs incurred.SAP Best Practices Cost Object Controlling – Repetitive (171): Configuration Guide 2. In variance calculation. Make the following entries: Plant Variance Key 1000 000001 1.3.2. Choose New entries and enter the following values or copy from default settings of CoArea 0001 to 1000: CoArea TgtCostVsn Text Variance Variant Control Cost Target Cost 1000 0 Target Costs for Total Variances 001 Actual Costs Current Std cost Est 1000 1 Target costs for production variances 001 Actual Costs Plan Costs / Preliminary Cost Estimate 1000 2 Target costs for planning variances 001 Plan Costs Current Std cost Est 1. Y1 Default object Type Indicators 100% Validation X %-Settlement X Equivalence No’s X Amount Settlement Var. Then for each new entry choose Details and enter remaining data. Overview of data records: Profile Text YBMFP1 BP: PP Valuated to COPA YBMFP1 Actual costs/costs of sales To be settled in full X Can be settled Not for settlement Default Values Allocation Structure YP Source Structure PA Transfer Struct.SAP Best Practices Transaction Code IMG Menu Cost Object Controlling – Repetitive (171): Configuration Guide SPRO Controlling  Product Cost Controlling  Cost Object Controlling  Product Cost by Period  Period-End Closing  Settlement  Create Settlement Profile 2. bsd. PA X Valid receivers G/L account N Cost center N Order O WBS Element N Fixed asset N Material O Network N Profit. to co. 3. Choose New Entries and enter header data. Segment O © SAP AG Page 17 of 21 . 6 Information System For Cost object controlling. Access the activity using one of the following navigation options: IMG Menu Controlling  Product Cost Controlling  Information System -> Cost object Controlling  Settings for Summarized Analysis/Order Selection  Maintain Summarization Hierarchies Transaction Code KKR0 2. the system collects data on the levels of the summarization hierarchy you defined so that your reports can be executed more quickly.dist.1 Define Summarization Hierarchy Use It is useful to have a summarization hierarchy of all production orders/product cost collectors so that you can start your analysis at higher levels like e.SAP Best Practices Cost Object Controlling – Repetitive (171): Configuration Guide Sales order O Cost objects O Order item O Business proc. Choose New Entries and enter: Hierarchy Description YBMF0001 Best Practice: Manufacturing Orders 3. plant. you can use standard reports for analyzing production variances.1. material number. work in progress (WIP) and line items on single orders. you start a data collection.3. Procedure 1.1.3. 1. order type.rls 3 Residence time 3 1. N Real est. Flag the objects you would like to summarize on the left-hand side of the screen:  Production orders  QM orders  product cost collectors © SAP AG Page 18 of 21 .no. 4. Double click on Data Scope (object types) on the right-hand side of the screen. During this run. After period-end closing.g.6. object N Other parameters Document type SA Max. choose New Entries and enter the following information:: Hierarchy Level Hierarchy Field Name Total Offset Length Blank YBMF0001 1 KOKRS Controlling Area 4 0 4 YBMF0001 2 BUKRS Company code 4 0 4 flag YBMF0001 3 WERKS Plant 4 0 4 flag YBMF0001 4 AUART Order type 4 0 4 flag YBMF0001 5 MATNR Material number 18 0 18 flag YBMF0001 6 AUFNR Order number 12 0 12 flag Save your entries.3. Secondary Costs.1 Check Order Types (YBMR). Do not flag the first column. Primary Costs.1. There is already an entry for the Controlling area. 1.7 CO-PC-OBJ Manufacturing Orders In this section. e. Flag the column no origin for the lines Variances/Results Analysis Data. Primary Costs. settlement profile. 8. 1. 6.SAP Best Practices Cost Object Controlling – Repetitive (171): Configuration Guide 5. Check Settlement Profile Use The order types contain various settings that are transferred to the order when an order of the respective type is created. To enter the lower levels of the Summarization Hierarchy. Do not enter a status. Prerequisite is that the indicator for variances is set. Access the activity using one of the following navigation options: Transaction Code © SAP AG KOT2_PKOSA Page 19 of 21 . Mark the line with the production orders and double-click on Data Scope (totals record tables) on the left-hand side of the screen. Mark the lines Variances/Results Analysis Data. The total variance can be transfered to profitability segments in CO-PA during order settlement. Secondary Costs and double-klick Hierachy Levels on the left-hand side of the screen. 9.3.7. 7. Activity Quantities.g. order types are set up. Prerequisites Settlement Profiles Procedure 1. Enter priority 1 for the production order line. Activity Quantities.1. Mark the number range group by clicking in the checkbox b. Choose the order type with ‘Select element F2’. To assign the order type to a number range group. RA Keys Procedure 1. 4. Assign the Settlement profile to the order type Type Name Settlement prof./Vers. Access the activity using one of the following navigation options: IMG Menu Transaction Code Controlling  Product Cost Controlling  Cost Object Controlling  Product Cost by Period  Product Cost Collectors  Define CostAccounting-Relevant Default Values for Order Types and Plants SPRO 2.) c. YBMR BP: Product Cost Collector YBMFP1 3. Choose Assign/Change Intervals for assignment of the number range. Prerequisites Costing Variants. Make the following entries: Plant Order Type Default Rule Prel. Make the following entries: a. Make a copy of type RM01 to YBMR b.2 Define Cost-Accounting-Relevant Default Values for Order Types and Plants Use This activity configures various settings that are transferred to the order when an order of the respective plant/type is created. Cstg Simul.1. choose the Element Group button (F5) Order Type Number Range group Number Range Intervall YBMR Investment 700000 – 799999 1.3.7.SAP Best Practices Cost Object Controlling – Repetitive (171): Configuration Guide Controlling  Product Cost Controlling  Cost Object Controlling  Product Cost by Period  Product Cost Collectors  Check Order Types IMG Menu 2. Costing RA key 1000 STR YPRM YSRM YBMF03 © SAP AG YBMR Page 20 of 21 . To assign the Order Type to the related Number Ranges Group perform the following steps: a. (The color of the order type is changing from black to blue. SAP Best Practices © SAP AG Cost Object Controlling – Repetitive (171): Configuration Guide Page 21 of 21 .