b98 bb config_guide_en_cn

EHP4 for SAP ERP 6.0

March 2011

English

Activating New General Ledger (B98)

SAP AGDietmar-Hopp-Allee 1669190 WalldorfGermany

Building Block Configuration Guide

© SAP AG of 57

SAP Best Practices Activating New General Ledger (B98): Configuration Guide

Copyright© 2011 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 of 57


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 of 57


Contents

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

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

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

3 Configuration................................................................................................................................ 5

3.1 Enterprise Structures.............................................................................................................5

3.1.1 Defining Segment...........................................................................................................5

3.2 Ledger................................................................................................................................... 6

3.2.1 Defining Ledgers for General Ledger Accounting..........................................................6

3.2.2 Fiscal Year and Posting Periods....................................................................................6

3.2.3 Defining and Activating Non-Leading Ledgers...............................................................7

3.2.4 Assigning Scenarios and Customer Fields to Ledgers...................................................7

3.2.5 Defining Document Types for General Ledger View......................................................8

3.3 General Ledger Accounting (New)........................................................................................9

3.3.1 Document Splitting.........................................................................................................9

3.3.2 Defining Field Status Variants (Part 'Field Status Groups')..........................................13

3.4 Master Data......................................................................................................................... 14

3.4.1 Creating Profit Center Group........................................................................................14

3.4.2 Changing Profit Center Group......................................................................................15

3.4.3 Assigning Standard Hierarchy to Controlling Area.......................................................16

3.4.4 Creating and Activating Profit Centers.........................................................................17

3.4.5 Assigning Profit Centers to Cost Centers.....................................................................18

3.4.6 Assigning Segments to Profit Centers..........................................................................21

3.5 Editing Constants for Non-assigned Processes..................................................................22

3.6 Activating Document Splitting..............................................................................................23

4 Appendix.................................................................................................................................... 24

4.1 Smart Forms........................................................................................................................ 24

4.2 Programs for Smart Forms..................................................................................................24

© SAP AG of 57


Activating New General Ledger

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

If you do not want to configure manually and prefer an automated installation process using BC Sets and other tools, refer to the installation guide of this building block.

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]_[yy]_ [zz].xls; the placeholder [xx] depends on the SAP Best Practices version you use, e.g. BK refers to the SAP Best Practices Banking Package, [yy] depends on the language version, e.g. EN for English language, and [zz] depends on the country version, e.g. CN for Chinese Countires: Prerequisites_Matrix_BK_EN_CN.xls). This document can be found on the SAP Best Practices documentation DVD in the folder ..\[xx]_[zz]\Documentation\; ([xx] depends on the SAP Best Practices version and [zz] depends on the country version).

3 Configuration

3.1 Enterprise Structures

3.1.1 Defining Segment

UseIn this IMG activity, you define your segments.

Procedure 1. Access the activity using one of the following navigation options:

Transaction code SPRO

IMG menu Enterprise Structure Definition Financial Accounting Define Segment

© SAP AG of 57


2. On the Change View “Segments for Segment Reporting”: Overview” screen, choose New Entries.

3. On the Change View “Segments for Segment Reporting”: Overview” screen, make the following entries:

Segment Text

1000_A Dummy Segment

© SAP AG of 57


4. Choose Save.

5. Choose Back to return to the IMG.

Result You have now created the segments.

3.2 Ledger

3.2.1 Defining Ledgers for General Ledger Accounting

UseIn this IMG activity, you define the ledgers that you use in General Ledger Accounting. :

You can define non-leading ledgers are parallel ledgers to the leading ledger.

Procedure1. Access the activity using one of the following navigation options:


IMG menu Financial Accounting (NEW) Financial Accounting Global Settings (New) Ledgers Ledger Define Ledgers for General Ledger Accounting

© SAP AG of 57


2. On the Change View ‘Define Ledgers for General Ledger Accounting”’: Overview screen, , make the following entries:

LD Ledger Name Totals Table Leading

DB DB FAGLFLEXT

© SAP AG of 57


3. Choose Save.

4. Chose Back.

3.2.2 Fiscal Year and Posting Periods

3.2.2.1 Maintaining Fiscal Year Variant (Maintaining Shortened Fisc. Year)

UseIn this activity, you define Fiscal year variants for 366 posting periods.



IMG menu Financial Accounting (NEW) Financial Accounting Global Settings (New) Ledgers Fiscal Year and Posting Periods Maintain Fiscal Year Variant (Maintain Shortened Fisc. Year)

© SAP AG of 57


2. On the Change View ‘Fiscal year variants’: Overview screen, make the following entries:

Field name Description User action and values Note

FV F1

Description 366 periods

Number of posting

366

© SAP AG of 57


3. On the Dialog Structure, select F1 and then double-click Periods from Fiscal year variants, make the following entries

Month Day Period Year shift

1 1 1 0

1 2 2 0

1 3 3 0

1 4 4 0

1 5 5 0

…. …. …. …

12 31 366 0

© SAP AG of 57


4. Save your entry.

3.2.3 Defining and Activating Non-Leading Ledgers

UseIn this IMG activity, you define and activate non-leading ledgers that you use in General Ledger Accounting. :



IMG menu Financial Accounting (NEW) Financial Accounting Global Settings (New) Ledgers Ledger Define and Activate Non-Leading Ledgers

© SAP AG of 57


2. On the Change View ‘Settings for Non-leading in General Ledger Accounting”’: Overview screen, , make the following entries:

CoCd C1 Crcy 1 FV Var

1000 10 CNY F1 0010

© SAP AG of 57


3. Choose Save.

4. Chose Back.

3.2.4 Assigning Scenarios and Customer Fields to Ledgers

Use In this IMG activity, you assign the following to your ledgers. This determines what fields in a ledger are updated when it receives posting from other application components.

Procedure 1. Access the activity using one of the following navigation option:


IMG menu Financial Accounting (NEW) Financial Accounting Global Settings (New) Ledgers Ledger Assign Scenarios and Customer Fields to Ledgers

© SAP AG of 57


2. On the Display View ‘Ledgers’. Overview screen, choose Leading Ledger (0L) and double-click Scenarios.

3. On the Change View ‘Scenarios’: Overview screen, choose New Entries.

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

Scenarios for General Ledger Accounting Long Text

FIN_CCA Cost Center Update

FIN_PCA Profit Center Update

FIN_SEGM Segmentation

© SAP AG of 57


5. Make following entries for Ledger DB

Scenarios for General Ledger Accounting Long Text

FIN_CCA Cost Center Update

FIN_PCA Profit Center Update

FIN_SEGM Segmentation

© SAP AG of 57


6. Choose Save.

Result You have now assigned the scenarios to Ledgers.

3.2.5 Defining Document Types for General Ledger View

UseIn this IMG activity, you define for non-leading ledgers the document types for the documents in the General Ledger view. At the same time, you assign for each document type a number range to be applied in the assignment of document numbers.



IMG menu Financial Accounting (NEW) Financial Accounting Global Settings (New) Document Document Types Define Document Types for General Ledger View

© SAP AG of 57


2. Make following settings are on the system:

Type Number range

AB 90

SA Z1

© SAP AG of 57


3.3 General Ledger Accounting (New)

3.3.1 Document Splitting

3.3.1.1 Classifying G/L Accounts for Document Splitting

UseIn this step, you specify for each business transaction that is entered and analyzed during the document splitting procedure. In this analysis, the system determines for each line item whether it is an item that remains unchanged or an item that should be split.

Procedure

1. Access the activity using one of the following navigation options:


IMG menu Financial Accounting (NEW) General Ledger Accounting (New) Business Transactions Document Splitting Classify G/L Accounts for Document Splitting

© SAP AG of 57


2. Make the following entries: Enter YHKM, the chart of account for SAP Best Practices Baseline. Choose Continue.

3. On the following screen table make the following entries:

Account from Account to Overrd. Category Description

10010101 11119901 04000 Cash Account

11220101 11220101 02000 Customer

11220199 12219901 01000 Balance Sheet Account

12220101 12229901 02000 Customer


16010101 16020199 select 07000 Fixed Assets


16040101 16049901 07000 Fixed Assets


17010101 17029901 07000 Fixed Assets


18010101 18029901 07000 Fixed Assets


22020101 22020101 03000 Vendor


22210101 22210301 05100 Taxes on Sales/Purchases


60110101 63110199 30000 Revenue

64020101 69010199 20000 Expense

© SAP AG of 57


3.3.1.2 Defining Zero-Balance Clearing Account

Use For account assignment, objects for which you want to have a zero balance setting, the system checks whether the balance of account assignment object is zero after document splitting.

If this is not the case, the system generates additional clearing items. In this activity, you have to create a clearing account for these additional clearing items.

Procedure



IMG menu Financial Accounting (NEW) General ledger accounting (NEW) Business transactions Document splitting Define Zero-Balance Clearing Account

© SAP AG of 57


2. Select the entry with account key 000. Double-click Accounts on the left hand side.

3. Enter the chart of account YHKM. Choose Continue.

4. Make the following entry:

GL Account Remarks

19990909 零余额清算科目

© SAP AG of 57


5. Save your entry.

6. Choose Back to leave the IMG activity.

3.3.1.3 Classifying Document Types for Document Splitting

Use Every business transaction that is entered is analyzed during the document splitting process. In this process, the system determines which splitting rule is applied to the document. For the system can determine the splitting rule, you have to assign a business transaction variant to each document type.

To ensure that a splitting rule is used appropriately, the relevant documents have to meet certain requirements. These requirements relate in particular to certain item categories that either must or must not be available. This information is specified for each business transaction variant and is checked against the current document during posting. If the document does not meet these requirements, the system rejects the posting.

All document types are to be classified for document splitting. It may be possible, that the standard customizing is not completely defined for all standard document types. In this case the missing document types are also be defined for document splitting in this step.



IMG menu Financial Accounting (NEW) General Ledger Accounting (New) Business Transactions Document Splitting Classify Document Types for Document Splitting

© SAP AG of 57


2. Make the following entries:

Document Type Transaction Type Variant

AA 0000 0001

AB 0000 0001

AF 0000 0001

AN 0000 0001

AP

CH

DA 0200 0001

DG 0200 0001

DR 0200 0001

DV

DZ 1000 0001

EU

EX 0000 0001

KA 0300 0001

KG 0300 0001

KN 0300 0001

KP 1010 0001

KR 0300 0001

KZ 1000 0001

ML 0000 0001

PR 0000 0001

RA 0000 0001

RB

RE 0300 0001

RK

RN 0300 0001

RV 0200 0001

SA 0000 0001

SB 0000 0001

SK 0000 0001

SU 0000 0001

SX

UE 0000 0001

WA 0000 0001

© SAP AG of 57


Document Type Transaction Type Variant

WE 0000 0001

WI 0000 0001

WL 0000 0001

WN 0000 0001

Y1

ZP 1000 0001

ZR 0400 0001

ZS 1000 0001

ZV 1010 0001

© SAP AG of 57


3.3.1.4 Defining Document Splitting Characteristics for General Ledgers

Use In this step, you specify for which characteristics you want to perform document splitting in General Ledger Accounting.

In Best Practices two fields (Profit Center and Segment) are used for document splitting.

Field segment is specified that a zero balance setting should be applied in the document for the characteristic. Field segment is specified that the field must be filled with a value after document splitting. This is necessary that a financial statement with segments can be processed.



IMG menu Financial Accounting (NEW) General ledger accounting (NEW) Business transactions Document splitting Define Document Splitting Characteristics for General Ledger Accounting

© SAP AG of 57



Field Zero Balance Partner Field Mandatory

PRCTRProfit Center

√ PPRCTR √

SEGMENT Segment PSEGMENT

© SAP AG of 57


3.3.1.5 Defining Document Splitting Characteristics for Controlling

Use In this IMG activity, you specify which additional characteristics you intend to apply for document splitting. The additional characteristics are not relevant for General Ledger Accounting. Instead, they are relevant for other application components (such as subcomponents in Controlling) that use documents transferred from General Ledger Accounting.



IMG menu Financial Accounting (NEW) General ledger accounting (NEW) Business transactions Document splitting Define Document Splitting Characteristics for Controlling

© SAP AG of 57


2. On the screen make the following entries:

Field Zero balance Partner field Mandatory Field

KOSTL Cost Center

3.3.2 Defining Field Status Variants (Part 'Field Status Groups')

UseYou can combine several field status groups in a field status variant. The field status group specifies which fields are active when you enter documents, which are mandatory, and which are suppressed (field status). For segment reporting the fields for segments and profit centers are to be enabled for input entries.

You can assign the field status variant to a company code. This enables you to work with the same field status groups in as many company codes as you require.

SAP Best Practices uses field status variant 0010 (copy from standard field status variant 0001).

If you perform this step because of a failed installation, the field status variant has to be deleted before you execute this configuration step manually. Otherwise you will have to create all of the field status groups manually instead of using the copy function.

PrerequisitesThe field status variant 0010 already exists (see building block 102 External Financial Accounting).



IMG menu Financial Accounting (NEW) Financial Accounting Global Settings (New) Ledgers Fields Define Field Status Variants

2. On the Change View “Field status variants”: Overview screen in the left hand frame, double-click Field status variants.

3. In the right hand frame select the line with the field status variant 0010 and choose Enter.

FStV Field status name

0010 Field Status BP Banking

If you install Best Practices with the Installation Assistant and personalized values, use the personalized value for the field status variant instead of the values stated above

4. In the left hand frame, double-click Field status groups.

Maintaining Field Status Groups:

© SAP AG of 57


In all field status groups, the field status for the fields Profit Center has to be set to Mandatory Entry and Segment has to be set to Opt. Entry. To do so proceed as described below for each field status group:

5. In the right hand frame, double-click the field status group that you want to maintain.

6. On the Maintain Field Status Group: Overview screen, double-click the entry Additional account assignments.

7. Set the field status for the fields Profit Center for Mandatory Entry and Segment to Opt. Entry.

8. Choose Save.

9. Choose Back twice to return to the Change View “Field status variants”: Overview screen.

Repeat steps 6 to 7 for each field status group!

10.Choose Save and leave the transaction.

3.4 Master Data

3.4.1 Creating Profit Center Group


SAP ECC menu Accounting Controlling Profit Center Accounting Master Data Profit Center Group Create

Transaction code KCH1

© SAP AG of 57


2. On the Create Profit Center Group: Initial screen, in the Profit Center Group field enter the key and choose Enter.

3. On the Create Profit Center Group: Structure screen, enter the description and choose Save.

4. Choose Back.

5. Create the following profit center groups:

Key Description

YBPH BP for Banking

YBJ BP Banking for Beijing

YSH BP Banking for Shanghai

© SAP AG of 57


ResultYou have created the profit center groups.

3.4.2 Changing Profit Center Group

UseThe purpose of this activity is to assign the profit center groups one to another to build up a hierarchy.

Procedure1. Access the activity using on of the following navigation options:

SAP ECC menu Accounting Controlling Profit Center Accounting Master Data Profit Center Group Change

Transaction code KCH2

© SAP AG of 57


2. On the Change Profit Center Group: Initial screen, in the Profit Center Group field enter the key for the father and choose Hierarchy.

3. On the Change Profit Center Group: Structure screen, choose Lower Level.

4. Enter the key of son profit center and choose Save.

Maintain the hierarchy as follows:

Key Father Key Son

YBPH

P990100 SAP中国金融机构-北京分行

P990101

SAP中国金融机构-北京分行支行 1

P990102


P990200 SAP中国金融机构-上海分行

P990201

SAP中国金融机构-上海分行支行 1

P990202

SAP中国金融机构-上海分行支行 2

P999900 SAP中国金融机构-总行

PSHProfit Center Group for Shanghai

P990102


P990101


P990100 SAP中国金融机构-北京分行

PBJ Profit Center Group for Beijing

© SAP AG of 57


ResultYou have created the profit center hierarchy YBPH.

3.4.3 Assigning Standard Hierarchy to Controlling Area

UseThe profit center hierarchy is to be assigned to the controlling area. So the profit center hierarchy is defined as standard hierarchy and can be assigned to cost centers.

Profit Center Accounting is not activated in controlling area. This activity is required for maintenance of cost centers and can be executed without activating profit center accounting in controlling.

PrerequisitesThe controlling area 1000 is set.


SAP ECC menu Financial Accounting(New) General Ledger Accounting (New) Master Data Profit Center Define Profit Center Standard Hierarchy in Controlling Area

Transaction code SAPLFAGL_PC_STHR

© SAP AG of 57


2. On the Change View “Define Profit Center Standard Hierarchy in Controlling Area screen, make the following entries:

Field name User action and values

Controlling area 1000

Hierarchy Area YBPH

© SAP AG of 57


3. Save your entries.

ResultThe standard hierarchy YBPH is assigned to controlling area.

3.4.4 Creating and Activating Profit Centers

UseProfit centers are maintained for application FI only. Profit center accounting is not activated in controlling area. Profit centers are needed for derivation of segments.

PrerequisitesProfit center standard hierarchy has to be created and maintained in the controlling area settings.

Procedure


SAP ECC menu Accounting Controlling Profit Center Accounting Master Data Profit Center Define Profit Center EC-PCA: Create profit center

Transaction code KE51

© SAP AG of 57


2. In the Set Controlling Area dialog box, enter controlling area 1000 and choose Continue.

3. On the Create Profit Center screen, enter the Profit Center and choose Master Data.

4. On the following screen, on the Basic data tab page enter the necessary data (see table below) and choose Save.

5. Choose Activate.

Data Records:

Profit Center

Analysis Period from

Analysis Period to

Name Long TexPerson Respons.

Profit Ctr Group

P990100 01.01.2009 31.12.9999 Best Practices YBPH







P99999901.01.2009 31.12.9999

Common Profit Center

Best PracticesYBPH

© SAP AG of 57


ResultYou have now created the profit centers.

3.4.5 Assigning Profit Centers to Cost Centers

UseProfit Centers are to be assigned to all cost centers which exist in the client. Because of different scope selections, it is possible that some of the below listed cost centers do not exist or alternatively that cost centers exist which are not maintained in the list.

Listed cost center does not exist: no further actions necessary

Cost centers exist in the client, but are not listed below: add profit center depending from scope

1.4.5.1 Message Control: Adding Message (Warning)

Use

If you try to change the profit center in the cost center master data and some transactional data exist the error message Changing profit center from … to … is not permitted is displayed. In SAP Best Practices tariffs for activity types are planned before activating the Activate Document Splitting. Therefore this message can be disregarded. A change has no effect on postings already made.

You can change the message type of this message.

You can

determine whether a message is output as a note in a dialog box or in the footer

change warnings to error messages

deactivate warnings and error messages

You can make different settings for dialog processing and batch input processed in the background.

You can maintain these settings for a client, and if necessary, for individual users.

You should only change the message in the test phase of the configuration. Be careful in a productive system! If you use new general ledger accounting, you have to manually repost any documents that have already been posted.


Transaction code OBA5

IMG menu Controlling General Controlling Change Message Control

© SAP AG of 57

sapevent:DOCU_LINK%5CDS:RELN.FI_ECC500_GL_NEW

sapevent:DOCU_LINK%5CDS:DE.FKBER


2. On the Maintain Table Views: Initial Screen, maintain the following entry in the Determine Work Area: Entry dialog box:

Work Area

Application Area FAGL_ORG_UNITS

© SAP AG of 57


3. Choose Continue (Enter).

4. On the Change View “Message Control by User”. Overview screen, choose New Entries.

5. On the New Entries. Overview of Added Entries screen, enter the following values:

Msg. Message Text User Name Online Batch Standard

011 W W

© SAP AG of 57


6. Choose Save.

3.4.5.1 Assigning Profit Centers to Cost Centers


SAP ECC menu Accounting Controlling Cost Center Accounting Master Data Cost Center Single Processing Change

Transaction code KS02

© SAP AG of 57


2. On the Cost Center Change: Entry View screen, provide the necessary data and choose Master Data.

3. On the Change Cost Center: Basic screen screen, provide the necessary data and choose Save.

Key Profit Center

C0101A0300 P990101

C0101B0400 P990101

C0101C0100 P990101

C0101C0200 P990101

C0101D0100 P990101

C0102A0300 P990102

C0102B0400 P990102

C0102C0100 P990102

C0102C0200 P990102

C0102D0100 P990102

C0201A0300 P990201

C0201B0400 P990201

C0201C0100 P990201

C0201C0200 P990201

C0201D0100 P990201

C0202A0300 P990202

C0202B0400 P990202

C0202C0100 P990202

C0202C0200 P990202

C0202D0100 P990202

C9901A0300 P990100

C9901A0500 P990100

C9901A0700 P990100

C9901B0100 P990100

C9901B0200 P990100

C9901B0300 P990100

C9901B0400 P990100

C9901C0100 P990100

C9901C0200 P990100

C9901C0300 P990100

C9901C0400 P990100

© SAP AG of 57


Key Profit Center

C9901D0100 P990100

C9902A0300 P990200

C9902A0500 P990200

C9902A0700 P990200

C9902B0100 P990200

C9902B0200 P990200

C9902B0300 P990200

C9902B0400 P990200

C9902C0100 P990200

C9902C0200 P990200

C9902C0300 P990200

C9902C0400 P990200

C9902D0100 P990200

C9999A0300 P999900

C9999A0500 P999900

C9999A0700 P999900

C9999B0100 P999900

C9999B0200 P999900

C9999B0300 P999900

C9999B0400 P999900

C9999C0100 P999900

C9999C0200 P999900

C9999C0300 P999900

C9999C0400 P999900

C9999D0100 P999900

© SAP AG of 57


ResultProfit centers are assigned to all cost centers.

3.4.5.2 Deleting Message from Message Control

UseIn this step, you delete the warning message in order to reactivate the standard error message.


Transaction code OBA5

IMG menu Controlling General Controlling Change Message Control

© SAP AG of 57


2. On the Maintain Table Views: Initial Screen, make the following entry in the Determine Work Area: Entry dialog box:

Work Area

Application Area FAGL_ORG_UNITS

© SAP AG of 57



4. On the Change View “Message Control by User”. Overview screen, maintain the following values:

Msg. Message Text User Name Online Batch Standard

011 W W

© SAP AG of 57


5. Choose Delete (Shift + F2).

6. On the Change View “Message Control by User”. Overview screen, the Information Number of deleted entries: 1 dialog box appears.


8. Choose Back (F3).

9. On the Maintain Table Views: Initial Screen, choose YES in the Exit Maintanance dialog box.

3.4.6 Assigning Segments to Profit Centers

UseSegments are derived form the profit centers. This is required for Activate Document Splitting based on segment splitting.

PrerequisitesThe segments are maintained.


SAP ECC menu Accounting Controlling Profit Center Accounting Master Data Profit Center Individual Processing Change

Transaction code KE52

© SAP AG of 57


2. In the Set Controlling Area dialog box, enter controlling area 1000 and choose Continue.

3. On the Create Profit Center screen, enter the Profit Center and choose Master Data.

4. On the following screen, on the Basic data tab page, enter the necessary data (see table below) and choose Save.

Data Records:

Profit Center Segment

P990100 1000_A

P990101 1000_A

P990102 1000_A

P990200 1000_A

P990201 1000_A

P990202 1000_A

P999900 1000_A

P999999 1000_A

© SAP AG of 57


3.5 Editing Constants for Non-assigned Processes

UseA default segment is to be assigned in processes for which it is not possible to derive the correct account assignments at the time when the document is posted. This is the case if the required information for segment derivation is not yet available when the posting occurs.



IMG menu Financial Accounting (NEW) General Ledger Accounting (NEW) Business Transactions Document Splitting Edit Constants for Nonassigned Processes

© SAP AG of 57


4. Select the new entry.

5. In the left hand frame double-click Assignment of Values.


Field Value

SEGMENT Segment 1000_A

© SAP AG of 57


7. In the left hand frame double-click Assignment of Profit Centers.


CO Area Default PrCtr

1000 P99999999

© SAP AG of 57



10. Choose Back twice to leave the IMG activity.

3.6 Activating Document Splitting

UseIn this IMG activity, you have to activate document splitting. The used splitting method is the SAP standard one, which contains the splitting rules for the different business transactions. If this splitting method does not meet your requirements, you can first define and then select your own method in Customizing for document splitting. You can do this by choosing Extended Document Splitting Assign Splitting Method.

The activation then applies for the entire client. You can explicitly exclude individual company codes from document splitting. This means, however, that you are then no longer able to create any cross-company-code transactions containing company codes that have divergent settings for document splitting.



IMG menu Financial Accounting (NEW) General Ledger Accounting (NEW) Business Transactions Document splitting Activate Document Splitting

© SAP AG of 57


Field name User action and values

Document Splitting √

Inheritance √

Standard A/CAssgnmnt √

Constant Z001

© SAP AG of 57


3. Choose Enter.


Field Method is filled automatically with the value 12.

4 Appendix

4.1 Smart Forms

UseIn this activity, you can check the developed Smart forms for China legal requirements.


SAP ECC menu Tools Form Printout Smart Forms

Transaction code Smartforms

© SAP AG of 57


2. Below smart forms have been created to fulfill china legal reporting requirements or common practices.

Smart forms Description

/SMB12/BALANCE_SHEET_CN_CAS China Balance Sheet

/SMB12/PROFIT_SHEET_CN_CAS China Profit Sheet

/SMB12/CASH_FLOW China Cash Flow statement

/SMB12/FI_R3_FORM China Ledger print forms for Bank, Cash, sub-ledger

/SMB12/FI_DOC_FORM Accounting Document

4.2 Programs for Smart Forms

UseIn this activity, you can check the developed ABAP Programs to call the above smart forms.


SAP ECC menu Tools ABAP Workbench Development ABAP Editor

Transaction code SE38

2. The below ABAP programs are developed to run reports using the above smart forms.

ABAP Program Smart forms

/SMB12/BALANCE_SHEET_CAS /SMB12/BALANCE_SHEET_CN_CAS

/SMB12/BALANCE_SHEET_CAS /SMB12/PROFIT_SHEET_CN_CAS

/SMB12/CASHFLOW_SHEET /SMB12/CASH_FLOW

/SMB12/FI_R3 /SMB12/FI_R3_FORM

/SMB12/FI_DOC /SMB12/FI_DOC_FORM

© SAP AG of 57

b98 bb config_guide_en_cn

Documents