EHP4 for SAP ERP 6.0

March 2010

English

Create Accounts and Account Groups (155.01)

SAP AGDietmar-Hopp-Allee 1669190 WalldorfGermany

Master Data Procedure

SAP Best Practices Create Accounts and Account Groups (155.01): MDP

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, Clear Enterprise, SAP BusinessObjects Explorer, 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 SAP France in the United States and in other countries.

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 8

SAP Best Practices Create Accounts and Account Groups (155.01): MDP

Icons

Icon Meaning

Caution

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 Page 3 of 8

SAP Best Practices Create Accounts and Account Groups (155.01): MDP

Contents

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

2 Prerequisites.......................................................................................................................... 5

2.1 Roles............................................................................................................................... 5

3 Scenario................................................................................................................................. 5

3.1 Creating GL Account.......................................................................................................5

3.2 Creating Cost Element and Cost Element Group............................................................6

3.3 Updating Appropriate Financial Statement Version/s......................................................7

3.4 Updating Relevant GL Account Sets...............................................................................7

4 Appendix................................................................................................................................ 8

4.1 Reversal of Process Steps..............................................................................................8

© SAP AG Page 4 of 8

SAP Best Practices Create Accounts and Account Groups (155.01): MDP

Create Accounts and Account Groups

1 PurposeIn this document, you create and maintain a general ledger account.

2 Prerequisites

2.1 Roles

UseThe following roles must have been installed to allow the relevant activities to be carried out in the SAP NetWeaver Business Client (NWBC). In addition, they must be assigned to the user or users who will perform the process steps described in this document. You do not need these roles if you are not using the NWBC interface, but the standard SAP GUI.

PrerequisitesThe business roles have been assigned to the user who is testing this scenario.

Business role Technical name Process step

Employee (Professional User)

SAP_NBPR_EMPLOYEE-S Assignment of this role is necessary for basic functionality.

Finance Manager SAP_NBPR_FINACC-M Maintain G/L accounti

3 Scenario

3.1 Creating GL Account

After you run this activity:

Option A: If the account is a balance sheet item, go to step 3.3.

Option B: If the account is not a balance sheet item, make the following choice:

Option B1: If the P&L account requires a cost element, go to step 3.2.

Option B2: If the P&L account does not require a cost element, go to step 3.3.

UseIn this activity, you create a GL account.

Procedure1. Access the transaction choosing one of the following navigation options:

Option 1: SAP Graphical User Interface (SAP GUI)

SAP ECC menu Accounting Financial Accounting General Ledger Master Records G/L Accounts Individual Processing

© SAP AG Page 5 of 8

SAP Best Practices Create Accounts and Account Groups (155.01): MDP

Centrally

Transaction code FS00

Option 2: SAP NetWeaver Business Client (SAP NWBC) via Business Role

Business role Finance Manager

(SAP_NBPR_FINACC-M)

Business role menu General Ledger Master Records G/L Accounts Maintain G/L Account

2. On the Edit GL Account Centrally screen, enter new GL account number, company code.

3. Choose Create with template to create a new GL account with reference to an existing GL account. In this case, most of the fields are copied from the reference GL account.

4. Choose Create to create a new account from scratch.

5. Choose the Type/ description tab.

6. Enter the Account group and select if the account is a P&L account or Balance Sheet Account. Enter the account short text and long text.

7. On the Control data and Create/bank/interest tabs, enter values in the appropriate required fields on those tabs (most importantly, currency, sort key, field status group).

8. On the Kew word/translation tab page enter the languages and texts (short and long texts) for all required languages.

The texts of the accounts are created in the maintenance language (see tab Type/Description). Therefore you can see in tab Key Word/translation at least one entry in the maintenance language. Here you can add the translations of other required languages.

9. Choose Save.

It is generally advisable to create new GL accounts with reference to existing GL accounts which are in the same number range and are similar.

Result The GL Account is created in the chart of accounts and company code. To view that the GL Account is created in the chart of accounts and company code, run the transaction FS00 or the menu path Accounting Financial Accounting General Ledger Master Records G/L Accounts Individual Processing Centrally.

3.2 Creating Cost Element and Cost Element Group

Referenced Process

UseThis activity will create cost element and cost element group.

PrerequisiteBefore the creation of a primary cost element the corresponding account is to be created as P&L account in the chart of accounts.

© SAP AG Page 6 of 8

SAP Best Practices Create Accounts and Account Groups (155.01): MDP

ProcedureTo execute this activity, run the 155.05 – Create Cost Element and Cost Element Group scenario using the master data in this document.

3.3 Updating Appropriate Financial Statement Version/s

UseIn this activity, you update the appropriate financial statement versions.

Procedure1. Access the transaction choosing one of the following navigation options:

Option 1: SAP Graphical User Interface (SAP GUI)

SAP ECC menu Accounting Financial Accounting General Ledger Master Records G/L Accounts Individual Processing Centrally

Transaction code FS00

Option 2: SAP NetWeaver Business Client (SAP NWBC) via Business Role

Business role Finance Manager

(SAP_NBPR_FINACC-M)

Business role menu General Ledger Master Records G/L Accounts Maintain G/L Account

2. On the Edit GL Account Centrally Screen, choose Edit Financial Statement Version.

3. In the Financial Statement Version dialog box, enter the appropriate Financial Statement Version, and then choose Enter.

4. Open the appropriate financial statement version nodes. Place the cursor on the node where the account is to be added.

5. Choose Assign Accounts. Enter the new account number, select the D or/and C indicators and choose Enter.

You may be asked, depending on the systems settings, to create a customizing order.

6. Choose Save.

Result The financial statement version is updated with the new account. To view new cost element group, run the transaction FS00 or choose Accounting Financial Accounting General Ledger Master Records G/L Accounts Individual Processing Centrally.

3.4 Updating Relevant GL Account Sets

UseIn this activity, you update the relevant GL account sets (or account groups).

Procedure

© SAP AG Page 7 of 8

SAP Best Practices Create Accounts and Account Groups (155.01): MDP

1. Access the transaction choosing one of the following navigation options:

Option 1: SAP Graphical User Interface (SAP GUI)

SAP ECC menu Accounting Financial Accounting General Ledger Master Records G/L Accounts Individual Processing Centrally

Transaction code FS00

Option 2: SAP NetWeaver Business Client (SAP NWBC) via Business Role

Business role Finance Manager

(SAP_NBPR_FINACC-M)

Business role menu General Ledger Master Records G/L Accounts Maintain G/L Account

2. On the Edit GL Account Centrally screen, choose Edit Set.

3. On the Set dialog box, enter the appropriate Set and choose Enter.

4. Enter the new account number and choose Enter.

5. Choose Save.

Result The financial statement version is updated with the newly created account. To view the updated financial statement version, run the transaction FS00 or use the menu path Accounting Financial Accounting General Ledger Master Records G/L Accounts Individual Processing Centrally.

4 Appendix

4.1 Reversal of Process StepsIn productive mode it is not possible to delete accounts; in test clients accounts can be deleted with the report sapf019 (IMG configuration).

© SAP AG Page 8 of 8