Utilities_Building_Blocks_China_Additional Cost Elements _225_BB_ConfigGuide.doc

SAP ECC 6.0 EhP3

August 2008

English

Additional Cost Elements (225)

SAP AGDietmar-Hopp-Allee 1669190 Walldorf

Building Block Configuration Guide

Germany

SAP Best Practices Additional Cost Elements (225): Configuration Guide

Copyright

© Copyright 2008 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, OS/2, Parallel Sysplex, MVS/ESA, AIX, S/390, AS/400, OS/390, OS/400, iSeries, pSeries, xSeries, zSeries, System i, System i5, System p, System p5, System x, System z, System z9, z/OS, AFP, Intelligent Miner, WebSphere, Netfinity, Tivoli, Informix, i5/OS, POWER, POWER5, POWER5+, OpenPower and PowerPC are trademarks or registered trademarks of IBM Corporation.

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, xApps, xApp, 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 in several other countries all over the world. 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 of 10


Icons

Icon MeaningCaution

Example

Note

Recommendation

Syntax

External Process

Business Process Alternative/Decision Choice

Typographic Conventions

Type Style Description

Example text Words or characters that appear on the screen. These include field names, screen titles, pushbuttons as well as menu names, paths and options.

Cross-references to other documentation.

Example text Emphasized words or phrases in body text, titles of graphics and tables.

EXAMPLE TEXT Names of elements in the system. These include report names, program names, transaction codes, table names, and individual key words of a programming language, when surrounded by body text, for example, SELECT and INCLUDE.

Example text Screen output. This includes file and directory names and their paths, messages, source code, names of variables and parameters as well as names of installation, upgrade and database tools.

EXAMPLE TEXT Keys on the keyboard, for example, function keys (such as F2) or the ENTER key.

Example text Exact user entry. These are words or characters that you enter in the system exactly as they appear in the documentation.

<Example text> Variable user entry. Pointed brackets indicate that you replace these words and characters with appropriate entries.

© SAP AG of 10


Contents

1 Purpose................................................................................................................................... 5

2 Preparation.............................................................................................................................. 5

2.1 Prerequisites..................................................................................................................5

2.2 Distributed Accounts Handling.......................................................................................5

3 Configuration........................................................................................................................... 6

3.1 Creating CO Elements Foundation Layer Independent.................................................6

3.1.1 Making Default Settings for Primary Cost Elements - Costs......................................6

3.1.2 Creating Primary Cost Elements: Create Batch Input Session..................................7

3.1.3 Text Maintenance Cost Elements Costs....................................................................8

3.1.4 Maintaining cost element group.................................................................................8

© SAP AG of 10


Additional Cost Elements

1 PurposeThis configuration guide provides the information you need to set up the configuration of this building block manually.

This building block provides additional cost elements needed if CO-PA is activated.

Cost elements with cost element category 11 or 12 (revenues and sales deductions) should only be maintained if an appropriate cost object can be assigned. In baseline the assigned cost objects for revenues and sales deductions are CO-PA value fields and characteristics. It is not allowed to post revenues and sales deductions to cost centers. If CO-PA is not activated these kind of cost elements should not be added to CO since no appropriate cost objects can be found.

With activation of CO-PA revenues and sales deductions are needed in CO because of the assignment of CO-PA values and characteristics to sales and sales deductions. This building block is therefore required if CO-PA is to be activated.

2 Preparation

2.1 PrerequisitesBefore you start installing this building block, you must install prerequisite building blocks. For more information, see the building block prerequisite matrix (Prerequisites_Matrix_[xx]_EN_CN.xls; the placeholder [xx] depends on the SAP Best Practices version you use, for example, BL refers to the SAP Best Practices Baseline Package: Prerequisites_Matrix_BL_EN_CN.xls). This document can be found on the SAP Best Practices documentation DVD in the folder ..\BBLibrary\General\.

2.2 Distributed Accounts HandlingBaseline provides one central chart of accounts but it is possible to maintain industry specific accounts. These means that in certain circumstances it is necessary to create own accounts for trading/manufacturing or services. In these cases it depends on the activation of the foundation layer (industry layer) whether these accounts are created or not.

Since of the demand of integration and requirements of cross industry scenarios it is necessary to provide a technical solution which combines central chart of accounts maintenance with distributed creation of industry specific accounts.

In Baseline following approach is implemented:

1. all accounts (including industry specific accounts) are created in central chart of accounts in layer 0 (see building block 102: External Accounting).

2. Industry specific accounts are blocked for creation in layer 0 and are therefore not created in the company code specific part of the chart of accounts. Therefore they can not be used.

3. Each foundation layer removes the block indicator from the needed industry specific accounts and creates these accounts in the company code specific part. So they can be used in FI.

© SAP AG of 10


4. Each foundation layer adds cost elements referring to these industry specific accounts.

5. Because CO-PA is not part of the foundation layers of revenue and sales deduction accounts used in the SD interface to CO-PA are to be added later, together with the activation of CO-PA. This building block refers to this part.

3 Configuration

3.1 Creating CO Elements Foundation Layer Independent

UseHere all revenues and sales deductions are created as cost elements in CO which are to be used by all industry foundations (layers). These cost elements are industry independent and are to created in any case together with CO-PA.

3.1.1 Making Default Settings for Primary Cost Elements - Costs

UseThe ranges of cost elements to be created are defined.

PrerequisitesThe respective P&L accounts must have been created in FI. This has been done during installation of layer 0.

Procedure1. Access the activity using the following navigation options:

Transaction code OKB2

IMG menu Controlling Cost Element Accounting Master Data Cost Elements Automatic Creation of Primary and Secondary Cost Elements Make Default Settings

2. On the Determine Work Area: Entry screen provide chart of accounts YACN and choose Enter.

3. On the Change View ‘Automatic Generation of Cost Elements: Default Setting’: screen, choose New Entries (F5).

4. On the New Entries: Overview of Added Entries screen make following entries:

Acct from Account to CElem cat.

60010101 60010101 11

© SAP AG of 10


60010501 60010501 12

60010201 60010201 11

60010901 60010901 11

60010502 60010502 12

60010506 60010506 12

60010503 60010503 12

5. Save your entries.

ResultCost elements for revenues and sales deductions are created.

3.1.2 Creating Primary Cost Elements: Create Batch Input Session

UseThe batch input session is created with the cost elements assigned in the previous step.


Transaction code OKB3

IMG menu Controlling Cost Element Accounting Master Data Cost Elements Automatic Creation of Primary and Secondary Cost Elements Create Batch Input Session

2. On the Create Batch Input Session to Create Cost Elements screen make following entries:

Field name Description User actions and values Note

Controlling Area 1000

Valid from Valid from date 1.1. from previous year Maintain previous year so that postings concerning previous year can be made.

Valid to Valid to date 31.12.9999

Session Name <User-ID>

Batch input user <User-ID>

3. Choose Execute.

© SAP AG of 10


3.1.2.1Creating Primary Cost Elements: Execute Batch Input Session

Use


Transaction code SM35

IMG menu Controlling Cost Element Accounting Master Data Cost Elements Automatic Creation of Primary and Secondary Cost Elements Execute Batch Input Session

2. On the Batch Input: Session Overview screen select session <User-ID> and process the session.

ResultYou have created the primary cost elements in Controlling Area 1000.

3.1.3 Text Maintenance Cost Elements Costs

UseTexts are to be maintained in local language. For this it is necessary to logon with this language. See chapter ‘Text Translation’ in this document in order to find out how to translate the texts.

3.1.4 Maintaining cost element group

UseThe new accounts are to be added to cost element groups.

PrerequisitesThe cost element groups are already created with layer 0 activation (see building block 103: Basic Overhead Cost Controlling).

Cost element group Description

5100_CE Revenues (Type 11)

5200_CE Sales deductions (type 12)


SAP ECC menu Accounting Controlling Cost Center Accounting Master Data Cost Element Group Change

Transaction code KAH2

© SAP AG of 10

SAP Best Practices Additional Cost Elements (225): Configuration Guide 2. On the Change Cost Element Group: Initial Screen, provide cost element group and choose

Hierarchy.

3. On the Change Cost Element Group: Structure screen, choose Insert Cost Element.

4. Provide minimum and maximum value of cost element range to be assigned.

5. Choose Save.

6. Make the following sets of entries:

Cost Element Group From Value To Value

5100_CE 60010101 60010101

5200_CE 60010501 60010501

5100_CE 60010201 60010201

5100_CE 60010901 60010901

5200_CE 60010502 60010502

5200_CE 60010506 60010506

ResultCost elements for revenues and sales deductions are added to the cost element groups.

© SAP AG of 10

Utilities_Building_Blocks_China_Additional Cost Elements _225_BB_ConfigGuide.doc

Documents

Transcript of Utilities_Building_Blocks_China_Additional Cost Elements _225_BB_ConfigGuide.doc