B31 ConversionGuide 600 En

7/14/2019 B31 ConversionGuide 600 En

http://slidepdf.com/reader/full/b31-conversionguide-600-en 1/34

SAP ECC 6.00

June 2008

English

SAP Best Practices

Chart of Accounts (CoA)Conversion Tool

SAP AGDietmar-Hopp-Allee 1669190 Walldorf Germany

Conversion Guide



SAP Best Practices CoA Conversion Tool: Conversion 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 purposewithout the express permission of SAP AG. The information contained herein may be changedwithout prior notice.

Some software products marketed by SAP AG and its distributors contain proprietary softwarecomponents of other software vendors.

Microsoft, Windows, Excel, Outlook, and PowerPoint are registered trademarks of MicrosoftCorporation.

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 registeredtrademarks 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 aretrademarks or registered trademarks of Citrix Systems, Inc.

HTML, XML, XHTML and W3C are trademarks or registered trademarks of W3C®, World WideWeb 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 BusinessByDesign, and other SAP products and services mentioned herein as well as their respectivelogos 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 AGand its affiliated companies ("SAP Group") for informational purposes only, without representationor warranty of any kind, and SAP Group shall not be liable for errors or omissions with respect tothe materials. The only warranties for SAP Group products and services are those that are setforth 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 34




Icons

Icon Meaning

Caution

Example

Note or Tip

Recommendation

Syntax

Typographic Conventions

Type Style Description

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

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 keywords 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 asnames 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 thesystem 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 34




Contents

Copyright........................................................................................................................ ........ 2

Chart of Accounts (CoA) Conversion Tool: Conversion Guide.......................................................6

1 Purpose........................................................................................................................................ 6

2 Preparation................................................................................................................................. . 7

2.1 Prerequisites......................................................................................................................... 7

2.1.1 SAP Notes...................................................................................................................... 7

2.2 Uploading the Conversion Role.............................................................................................8

2.3 Client Administration..............................................................................................................8

3 Creating the Conversion Package............................................................................................... 9

4 Creating a Mapping Table..........................................................................................................10

4.1 File Structure for Account Numbers.....................................................................................10

4.2 File Structure for Account Descriptions .............................................................................. 11

4.3 File Content......................................................................................................................... 14

4.3.1 Templates and Examples for Mapping Table................................................................15

4.3.2 Merge............................................................................................................................ 15

5 Create / Copy Financial Statement Version............................................................................... 16

6 Resolve Cost elements and account groups..............................................................................16

7 Conversion Procedure............................................................................................................... 17

7.1 Start IMG Conversion.......................................................................................................... 19

7.2 Display Procedure Monitor................................................................................................. .197.3 Package Settings.................................................................................................................20

7.3.1 Find additional tables and fields....................................................................................20

7.3.2 Exclude non-relevant tables..........................................................................................20

7.3.3 Maintain customer-defined and generated tables.........................................................20

7.3.4 Maintain customer-defined and generated fields..........................................................21

7.3.5 Save changed tables and fields.................................................................................... 22

7.3.6 Check package and flag empty tables.......................................................................... 22

7.3.7 Determine derivation paths for organizational units ....................................................22

7.3.8 Check organizational unit-dependent conversion.........................................................23

7.3.9 Place sets in transparent tables....................................................................................23

7.3.10 Carry out initialization..................................................................................................24

7.4 Mapping Tables................................................................................................................... 24

7.4.1 Enter accounts and chart of accounts for conversion...................................................24

7.4.2 Check participating company codes.......................................................................... ...25

© SAP AG of 34




7.4.3 Determine scenario....................................................................................................... 26

7.4.4 Find undefined B segment and implicit merges............................................................26

7.4.5 Maintain B segment merges................................................................................... ......26

7.4.6 Check B segment merges.............................................................................................26

7.4.7 Check accounts for conversion.....................................................................................267.4.8 Specify descriptions for conversion...............................................................................27

7.4.9 Check descriptions for conversion................................................................................27

7.4.10 Specify P&L statement structures for conversion........................................................27

7.4.11 Check P&L statement structures.................................................................................27

7.4.12 Confirm settings.......................................................................................................... 28

7.4.13 Make scenario-related optimization............................................................................28

7.4.14 Check package settings..............................................................................................28

7.5 Preprocessing Programs BEFORE System Lock................................................................28

7.6 Generation........................................................................................................................... 28

7.6.1 Generate conversion programs.....................................................................................28

7.6.2 Define jobs....................................................................................................................28

7.7 Preprocessing Programs DURING System Lock.................................................................29

7.7.1 Load object table...........................................................................................................29

7.8 Conversion.......................................................................................................................... 29

7.8.1 Start conversion............................................................................................................ 29

7.9 Postprocessing Programs DURING System Lock...............................................................29

7.9.1 Reset table buffers ......................................................................................................29

7.9.2 Adapt validity date for cost element groups.................................................................. 29

7.9.3 Create/change descriptions.......................................................................................... 29

8 Follow-Up Activities....................................................................................................................30

8.1.1 Manual Activities...........................................................................................................30

9 Optional Activity: Register Users for Package............................................................................30

10 Attachment: List of Tables included in conversion..................................................................31

© SAP AG of 34




Chart of Accounts (CoA) Conversion Tool:Conversion Guide

1 PurposeThis conversion guide provides the information needed to set up the SAP Best Practicesconversion tool and convert the delivered SAP Best Practices chart of accounts and accountdetermination to any other chart of accounts.

The SAP Best Practices conversion tools convert accounts directly in SAP data base tables. Theaccounts are replaced by new accounts which are maintained through a chart of accountsconversion table.

Since the conversion tools are restricted to SAP Best Practices, there are some limitations on theuse of the tools. Please note the following before applying the tools:

• The conversion tools can only be used for a SAP Best Practices solution . The

solution has to be completely installed before the tools can be applied.

• The tools can only be used in development or demo environments without productive

data. It is not possible to convert transactional or productive data.

• Existing accounts are converted into new accounts. If there are new accounts which do

not correspond to SAP Best Practices accounts, additional configuration settings mustbe performed manually.

• The conversion tool does not change documentation. If you want to reuse SAP Best

Practices Business Process Documentation after conversion, chart of accounts relatedentries have to be changed manually.

Before applying the tools, a chart of accounts conversion table must be maintained. Examplesare provided with SAP Best Practices.

The persons responsible for the conversion of the chart of accounts define the targets of theconversion in detail and finalize the mapping table. In addition, they define test procedures,which are to be carried out after the test conversion. In particular, they specify the centralbusiness processes within the company that are affected by the conversion. The personsresponsible in the related departments perform these processes after the test conversion usingrepresentative test data.Decisions on how many and what kinds of tests are required depend largely on the specificfeatures of your SAP system. Consequently, SAP can provide only general information on testing,and the project team is solely responsible for the detailed definition of the test procedures as wellas the execution of the tests.

A detailed guide through the steps of the conversion (IMG) is provided as part of the ConversionPackage.

© SAP AG of 34




2 Preparation

2.1 PrerequisitesBefore using this guide, conversion programs must be imported into the development client. If the

conversion programs are missing, please refer to “How-To-Order SAP Best Practices ConversionTool”.

Conversion can only be done in a development system or a demo system without productivedata. The entire SAP Best Practices solution must be installed before the conversion can beperformed.

It is recommended to activate the transport request handling before performing theconversion tool (transaction scc4). In this case, the changed configuration settingsare added to transport requests and can be transported within the existing landscape.

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

IMG Menu (SPRO) Financial Accounting (New) General Ledger Accounting (New) Tools Transport Transport Chart of Accounts.

Transaction Code OBY9

2. Maintain the transport request manually by adding the table for the company code chartof accounts table SKB1, and selecting all table entries referring to your company code(e.g. BP01).

It is strongly recommended to make a back-up before starting the conversion (for example,send a client copy to another client before converting the accounts).

Additionally, you can activate logging table changes (this is not a prerequisite for applying thetools).

2.1.1 SAP Notes

Before you convert the chart of accounts, you must implement the following SAP Note:

Note No. # Component Description

#922148 SV-SMB-AIO-BP-ACCSAP Best Practices Chart of Accounts ConversionTool

© SAP AG of 34




2.2 Uploading the Conversion Role

Use

Before you start with the conversion according to the manual procedures described in this guide,upload the conversion role and assign it to your user.

The following role is available:

Technical name Description File name for upload

/SMB99/B31_01I SAP Best Practices CoA Conversion Tool Role _SMB99_B31_01I.SAP

The role is attached to the note #922148 and can be downloaded here.

Procedure

1. To import the role into the SAP system, choose one of the following navigation options:

Transaction code PFCG

SAP Menu Tools→ Administration→ User maintenance → Role

Administration → Roles

2. Choose Role → Upload .

3. Confirm the warning message.

4. Select the relevant _SMB99_B31_01I.SAP file from the relevant subfolder and choose Open.

5. Confirm the information screen indicating which roles already exist in the system.

6. Import the appropriate role into the system.

7. To assign the role to a user, choose Change and go to the User tab page.

8. Enter the user ID of your (or another) installation user.

9. Save the conversion role.

Result

The conversion role can be displayed in the system and any user assigned to it can start using it.

2.3 Client Administration

In client maintenance (transaction SCC4), check the following settings:

Fields Values

Client <Your client>

Client Role Customizing

© SAP AG of 34




Fields Values

Changes and Transport of Client-Specific Objects

Automatic Recording of Changes (recommended)

3 Creating the Conversion Package

Use

The purpose of this activity is to create a package for the conversion in the relevant developmentclient.

The SAP Best Practices conversion packages and related package modules are delivered bySAP and must have been imported into client 000 before starting the conversion. In this step, theprogram copies predefined table entries from client 000 into the client to be used for conversion.The program then creates a SAP Best Practices project-specific IMG. You have to use the projectIMG to execute the entire conversion.

Procedure


SAP R/3 Role Menu CoA conversion → Preparation→ Conversion package

Transaction Code CNV_20130_START

2. On the Program for loading CoA “light” screen, enter the following information:

Field name User action and values Comment

Source Client 000

TargetPackage

Any number allocated. This will be the package number for the conversion. This number has tostart with 9 to differentiate it from thestandard packages.

New PackageName

A short text that provides moredetails of the conversion to beexecuted.

3. Select New Copy of CNVRIELDREF. This is required for the first conversion.

4. Create this new package by choosing F8 . This step is performed once for every conversion.

5. Ignore the message numbers CNV107 and CNV106, for example, “Package 0001 is valid for Release 40B. – 46C ” or “Delimitation by organizational unit arises by making additional settings” .

6. Confirm the message Syst.Release differs from package rel .

7. Add the license key provided by SAP Best Practices and confirm.

Result

The package number 9xxxx and IMG have been successfully created.

© SAP AG of 34




The conversion package has been installed. The conversion can now be performed. You mustuse transaction CNV_IMG to access the IMG Menu.

The package has been assigned to the user who created the package. To allow other users to do the conversion, please see description in the chapter Optional Activities.

4 Creating a Mapping Table

Use

Mapping tables contain the references between the SAP Best Practices and the new accountnumbers. Mapping tables are to be maintained individually for each conversion project. SAP BestPractices delivers examples which can be used as samples.

Mapping tables are to be saved in the file format .TXT and then uploaded into the tool.

To create a mapping table, refer to the tables SKA1, SKAT, SKB1, CSKA, CSKB,CSKU, and check if the numbers and values of the objects are the same in themapping table and in the master data tables in the system.

4.1 File Structure for Account Numbers

In the mapping table (see sample files provided by SAP Best Practices), you define therelationships (mapping) between the old and the new values for the accounts and cost elements.The final version of the table will then be uploaded to the respective SAP system before theconversion so that the relevant fields can be converted in accordance with the information definedin the mapping table.

Create a separate mapping table for each old chart of accounts that is relevant for theconversion. If you want to convert secondary cost elements as well, create one mapping table for accounts with primary cost elements included, and a separate mapping table for secondary costelements respectively.

The table can be uploaded only if the number and sequence of the columns is exactlythe same as in the template.

Procedure

Enter the values in the following order:

Column A Column B Column C

Enter the previous ID(number) of the account or cost element that you want tochange

Enter the ID (number) of theaccount or cost element that willbe valid after the conversion

Set an ‘X’ in this column onlyif you want to mergeaccounts or cost elements ina new account

© SAP AG of 34




The table can only be uploaded if its structure is exactly as described here. If you do notplan to merge any accounts or cost elements, and consequently do not need the priorityindicator, leave column C empty and do not enter any other information in this column.

If you want to merge accounts or cost elements, you need to specify the source account

or cost element, the settings of which will be valid for the new account or cost element.For this purpose, enter an 'X' (priority indicator) in the column for the account (costelement), the settings of which shall be valid for the new account.

Examples:

1. You would like to rename account 1234 in chart of accounts ZNEW to 4711:


1234 4711

2. You would like to merge accounts 1234 and 1235 in chart of accounts IKR in a newaccount, 4711. The new account 4711 must have the same settings as the old account,1235 :


1234 4711

1235 4711 X

4.2 File Structure for Account DescriptionsUse

This documentation shows you how to fill in the mapping table for language dependent texts,through which you can change existing descriptions for charts of accounts, as well as short textsand long texts for accounts and cost elements, or you can create new ones in any availablelanguage.

The final version of the table will then be uploaded to the respective SAP system before theconversion, so that the relevant fields can be converted in accordance with the informationdefined in the mapping table.

© SAP AG of 34




The table can be uploaded only if the number and sequence of the columns areexactly the same as in the template.

Account descriptions of the old chart of accounts are copied automatically if thefile for account description is not included into conversion. If single accounts aremissing in the file, the program also copies automatically the old description.If you want to copy the old descriptions completely, this step can be omitted.

Procedure

Enter the values in the following order:

Column A (New CoA) Column B (New Account) Column C (Type)

Enter the ID (number) of thechart of accounts that will bevalid after the conversion

Enter the ID (number) of theaccount or cost element that willbe valid after the conversion. If you want to change thedescription for a chart of accounts,leave this field empty

Specify the type of the objectthat you want to change.Enter P for a chart of accounts, S for a G/Laccount or K for a costelement

If a given account is used as a G/L account and as a primary cost element, and if youwant to change the texts for the G/L account as well as for the cost element, youneed to make two entries for the same account number – one with 'S' for the G/Laccount and one with 'K' for the cost element.

Column D (Language) Column E (Short Text New) Column F (Long Text New)

Enter the language ID (two-character, in uppercase) of

the required language (ISO-Code)

Enter the short text in the specifiedlanguage which will be valid after

the conversion. If you want tochange the description for a chartof accounts, leave this field empty

Enter the long text in thespecified language which will

be valid after the conversion

You would like to rename chart of accounts X into Y and merge accounts a and b into4711. Account 4711 is also used as a cost element. To define the texts for the newaccount 4711 in English, enter the following data in the mapping table:

Column A Column B Column C Column D Column E Column F

Y 4711 S EN <short text EN> <long text EN>

To change the cost element texts for the new cost element 4711, make the following additionalentry:


Y 4711 K EN <short text EN> <long text EN>

© SAP AG of 34




To change the description for new chart of accounts y, make the following additional entry(leaving the fields 'account' and 'short text' empty):


Y P EN <long text EN>

© SAP AG of 34




4.3 File Content

Use

The purpose of this activity is to include all the account numbers and secondary cost elements for

one CoA in the mapping table. For additional CoA, additional mapping tables must be created asdescribed before.

Procedure

1. Secondary cost elements of other controlling areas are also included in the conversion if they belong to the same chart of accounts.

• If you do not want these accounts to be included, please add an additional line to

the file which converts this account to a new dummy account (for example, 1).The dummy account can be deleted after conversion.

2. If the numbers of new secondary cost elements in the new chart of accounts already existas G/L account or primary cost element in the old chart of accounts, this could cause

errors.

• In this case, you have to change the account numbers in the new chart of

accounts (for example, the account numbers of the secondary cost elements canbe changed).

3. Within the conversion, the operation not only converts the account numbers that are inthe mapping table, but it also copies all the other account numbers from the source chartof accounts.

• Since you only want to convert the account numbers that are in the mapping

table, this copy operation may cause conflicts with the account number.

For example, account 400100 (which is in the mapping table) is converted intoaccount 200200 in accordance with the mapping. If there is already an account withthe number 200200 in the target chart of accounts (not conversion-relevant), therewill be a conflict.

To avoid the number conflict, assign new numbers.

4. If you do not want to copy accounts from the old chart of accounts you can proceed asfollows:

• Map all the accounts that are not to be converted to one dummy account. These

source accounts are then merged into the dummy account within the conversion. After conversion the dummy account can then be deleted.

5. If there are different categories of accounts, mapping will be prevented.

• In this case different dummy accounts must be used (for example, 1 for balancesheet accounts, 2 for revenue accounts …).

The account descriptions of all Chart of Accounts can be included in one file only.

© SAP AG of 34




4.3.1 Templates and Examples for Mapping Table

A mapping table between the CoA IKR (source) and ZNEW (target) is delivered with this tool asan example (text file and worksheet file). The texts are in English only.

The example does not make merges between the account numbers (only 1:1 assignments).

You can use these files as a template to create your own mapping, as required for your solution.

Additionally you find templates for creating the mapping tables (empty fields) which you can useas well. In these templates more information about how to maintain the mapping tables areprovided. The new mapping tables created should be saved as txt files.

4.3.2 Merge

Set the priority flag “X” for the account number whose settings are to be prioritized.

Before the conversion, the system checks whether the marked accounts and cost elements canbe merged.

If the following criteria of the accounts to be merged are not met, the program issues warningmessages. This means that a merge is possible, but you should check the entries again.

Table Field

SKA1 G/L account group

SKA1 Partner company IDs

SKB1 Tax category in account master record

SKB1 Indicator: Tax code is not a required field

SKB1 Indicator: Line item display of account possible?

SKB1 Key for sorting by allocation number

SKB1 Authorization group

SKB1 Field status group

SKB1 Cash receipt account / cash disbursement account

SKB1 Indicator: account only to be posted to automatically?

CSKB Validity period differs

If any of the following criteria of the accounts to be merged are not met, the programissues error messages. This means a merge of these accounts is not possible. Inthis case please change mapping.

Table Field

SKA1 Indicator: Account is a balance sheet account?

SKA1 P+L statement account type

SKA1 Merge of a mere g/l accounts and a g/l account with aprimary cost element

SKB1 Account currency

© SAP AG of 34




Table Field

SKB1 Account is a reconciliation account

SKB1 Indicator: Open item management?

SKB1 Indicator: Only manage balances in local currency?

CSKB Cost element category

.

5 Create / Copy Financial Statement Version

Use

Before converting the chart of accounts it is recommended to copy the existing financialstatement version as backup version. It is possible to select chart of accounts for conversionseparately. Thus the backup version can be excluded from conversion.

Procedure

1. Access the activity as follows:

IMG Menu Financial Accounting (NEW) → General Ledger Accounting

(New)→ Master Data → GL Accounts → Define Financial

Statement Versions

2. Choose your Financial Statement Version and choose Copy as (F6).

3. Make the following entries:

FIN.Stmt.Version Name

Your financial statementversion

Backup financial version

Example For Example: YIKR

4. Choose Enter.

Result

You have copied the financial statement version.

6 Resolve Cost elements and account groupsUse

The purpose of this activity is to assign cost elements separately to groups, if intervals have beenassigned. After this step, intervals will be deleted completely.

Each cost element in the group which is included in the interval will be assigned separately for each group.

© SAP AG of 34




Procedure


Transaction Code <CNV_20100_SETS_RESOL >

2. On the Interval downbreak screen, make to following entries:

Field name User action and values

Chart of Accounts <IKR >

3. Deselect “Single values are also checked ” and “Cost Element/GL account texts”.

4. Ensure that Test run is selected.

5. Choose Execute (F8 ).

6. Check the log. If you are satisfied with the result do the final resolving by following steps (6-7).

7. Choose Back (F3).

8. Deselect Test run and click Execute to resolve the cost element groups and account groups.

7 Conversion Procedure

Use

The purpose of this activity is to start the conversion procedure. Following steps must be runsuccessfully in the order listed:

1 Package settings (phase P)

2 Mapping tables (phase R)

3 Preprocessing programs BEFORE system lock (phase Y)

4 Generation (phase G)

5 Preprocessing programs DURING system lock (phase B)

6 Conversion (phase C)

7 Postprocessing programs DURING system lock (phase A)

Ignore warnings. You can proceed with the next step if the procedure monitor statusshows green or yellow.

Only leave transactions with F3 (Back ). If you delete the transaction without finishingwith F3, the status will be cancelled (sign shows lightning ). In this case, repeat thisstep and finish with F3.

© SAP AG of 34




The procedure monitor allows the status to be checked after each step. For moreinformation, see the section Display Procedure Monitor , below.

Activate transport request handling in SCC4

If manual maintenance is too complex, refer to SAP SLO Services.

© SAP AG of 34




7.1 Start IMG Conversion

Procedure

1. Access the activity using the following navigation option:

Transaction Code CNV_IMG

For information on how to use these steps and what they do, double-click on therelevant step texts. The help provided is the standard information from theConversion Services tool delivered by SAP SLO Services.

Specific help for the SAP Best Practices version is also provided in this document.

The conversion phases S (System settings before conversion), “F” (Manual postprocessing), O (System settings after conversion), and N (Postprocessing programsafter system lock) are not used for SAP Best Practices conversion.

7.2 Display Procedure Monitor

Use

This step enables you to check the status of each procedure. This activity must run parallel tothe other activities in an additional window. For more information on how to use this monitor, refer to the online help by clicking on the Info button (navigation in procedure monitor), or by enteringShift +F1.

All steps in the monitor are carried out for the conversion. Progress can be checked in themonitor, as well as the status of individual steps. To display updates, press the Refresh button.

Additional help is available in the standard information on the Conversion Servicestool, delivered by SAP SLO Services for all steps. For help, double-click on the textline.

To see the log for each step, double click on the Prt column in the relevant line.

Procedure

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

SAP menu CNV_IMG: R/3 Conversion Service Display ProcedureMonitor

Transaction code CNV_MONITOR

© SAP AG of 34




Ignore warnings. You can proceed with the next step if the procedure monitor statusshows green or yellow.

7.3 Package Settings

Additional help is available in the standard information on the Conversion Servicestool, delivered by SAP SLO Services for all steps. For help, double-click on the textline.

7.3.1 Find additional tables and fields

Use

The purpose of this program is to find the fields for conversion and their tables which are not yetincluded in the control tables. This can involve customer-specific and user-defined tables.

Procedure

1. Choose Execute. The task is executed as a background job.

2. After this step, display the procedure monitor.

The log shows all found tables. Tables generated in customer system are found, and areprepared for the next steps in conversion.

The status is usually green after this step.

7.3.2 Exclude non-relevant tables

Use

This version of the chart of account package only changes customizing tables. It might bepossible that the predecessor step detected tables of different type. These tables have to beexcluded from conversion.

Procedure

Execute the function.

7.3.3 Maintain customer-defined and generated tables

All user-defined and customer-specific tables are entered here. It is possible that, in tables whichrequire key fields to be converted, the new word appears in multiple records. This results induplicates for the key. The sentence which appears higher in the mapping hierarchy is givenpriority.

© SAP AG of 34




Customer-defined tables are converted, if they refer to the standard SAP domains for the chart of accounts, SAKNR, KSTAR, KKG_KSTAR, KONTO, or KKGCHR10.Otherwise, these tables must be maintained manually. Before proceeding withthe conversion, check whether this applies to your system.

SAP Best Practices for Baseline does not deliver customer-defined tables.

Procedure

1. On the Change View “CNV: maintenance of user-defined table information” Overview screen, maintain the table (column Totl only) as follows:

Table name Totl

ACERT52010008 A

ACESLN1000002 A

2. Save your settings.3. Display the procedure monitor by entering the transaction code CNV_MONITOR .

7.3.4 Maintain customer-defined and generated fields

Use

This contains all user-defined tables and fields, and their conversion routines.

All fields to be executed are added to the tables from the previous Step. These fields are

automatically assigned to conversion routines. If an automatic assignment to a conversion routineis not possible, then the field Routine name contains ‘??’. This field has to be excluded from theconversion for SAP Best Practices. In this case, place X in the column Non-Use.

If conversion routines are automatically assigned no further actions are required. In this case thesettings can be saved without any change.

Procedure

1. On the Maintain customer-defined and generated fields screen, make the followingentries:

Field name User action and values Comment

Non-Use X Function used to exclude this field from the

conversion.

1. Choose Save.

2. Display the procedure monitor by entering the transaction code CNV_MONITOR .

See attachment of this document in order to find out the tables which are includedin SAP Best Practices conversion tools.

© SAP AG of 34




7.3.5 Save changed tables and fields

1. Confirm data containing user-defined objects was transferred .

Now, user defined tables and fields (in previous steps) have been transferred to conversion tooltables.

2. Display the procedure monitor by entering the transaction codeCNV_MONITOR

.

7.3.6 Check package and flag empty tables

The adjustments in the conversion tables are checked by the system. Empty tables areautomatically assigned an internal indicator. This should not be changed.

Procedure

Ensure that an A has been placed in the Maintain Customer defined and generated Tables

screen, and that the Maintain customer defined and generated fields screen has been maintainedcorrectly, for example, the flag NO_USE has not been set for missing conversion routines,otherwise, errors will occur.

In the case of an error, make corrections and perform this step again. The conversionprocess can only continue if this step is completed correctly, that is, if the traffic lightin the monitor is green or yellow.

If the traffic light is yellow, proceed and ignore warnings such as Unique secondary index of table SKAS can cause duplicates, or Unique secondary index 2 of tableSKB1 can cause duplicates, or For field EVCE-KAGRU parameters must be deleted from CNVFIPARS

After this step, display the procedure monitor by entering the transaction codeCNV_MONITOR .

7.3.7 Determine derivation paths for organizational units

Use

The system suggests a derivation path for organizational unit for every table.

Tables for which no organizational unit can be found are marked with a red symbol.For these tables, you manually determine if they are to participate in the conversion,and if so how the organizational unit can be found.

Table Name Field OrgUnit OrgUnit Selection Key Status

ACERT52010008 SOUR1_FROM BUKRS (red)

© SAP AG of 34




Table Name Field OrgUnit OrgUnit Selection Key Status

ACERT52010008 SOUR1_TO BUKRS (red)

ACERT52010008 TARGET1 BUKRS (red)

ACERT52010008 TARGET2 BUKRS (red)

ACESLN1000002 TARGET1 BURKS (red)

ACESLN1000002 TARGET2 BURKS (red)

Tables refer to the accrual engine delivered with SAP Best Practices. This table does not containfields referencing to organizational units such as company code. In this case, you can convertautomatically without assigning the chart of accounts. The found accounts are converted withoutchecking the chart of accounts.

Procedure

1. Select all entries.

2. Select Save.

3. Status shows Save.

Result

All accounts are converted.

If you have other tables with red status, decide whether or not you automaticallyconvert as described before. If not, exclude these tables from conversion and convertmanually.

1. Go to step Maintain Customer Defined and Generated Fields and execute this step

2. Deselect these fields with X in the column No use.

7.3.8 Check organizational unit-dependent conversion

This step checks that the settings for the organizational unit-dependent conversion for all tables inthe package are complete. The status should be green.

If the status is red, check activities previous to this step and ensure that they havebeen carried out as described, and that each entry has been saved.

After this step, display the procedure monitor by entering the transaction code CNV_MONITOR .

7.3.9 Place sets in transparent tables

Usually this step is not needed for release ECC600 (ERP 2005).

For further information, read the system documentation.

© SAP AG of 34




7.3.10 Carry out initialization

For reasons of consistency, in this step, several tables are emptied, and various backup copiesare made. Old package number data which was converted during repeat execution of theconversion program is erased.

In the case of repeated execution, all Steps must be performed again.

7.4 Mapping Tables

7.4.1 Enter accounts and chart of accounts for conversion

Use

In this step, you specify which G/L accounts or primary and secondary cost elements, as well aswhich charts of accounts you want to convert or copy. In addition, you specify the company codesto which these changes apply.

A mapping table with old chart of accounts IKR and new chart of accounts ZNEW isdelivered as example. Finally ZNEW will contain the same accounts as chart of accounts INT.

Procedure

1. On the Change View “Central chart of accounts conversion”: Overview screen, chooseNew Entries.

2. On the Central chart of accounts conversion screen, make the following entries:

Old CoA New CoA

IKR ZNEW

3. Choose Back (F3).

4. Select the line for the old chart of accounts (IKR ).

5. Choose New chart of accounts – Customizing from the menu.

6. The configuration data of old chart of accounts are transferred to new chart of accounts.Please change according to your requirements.

New CoA Length Maintenance Language

<CoA name>

(Example: ZNEW)

<Length of CoA>

(Example: 6)

<Language>

(Example: EN)

7. Choose Company code for chart of accounts from the menu.

8. Choose New Entries.

9. Enter following values:

CoCd Company name

<Company code> CoA name

© SAP AG of 34




BP01 Company code BP01

BP0X Company code BP0X (does not exist in some SAP Best Practices solutions, please check with F4)

The company codes are delivered with SAP Best Practices.

10. Choose Assignment of old/new accounts/primary cost element from the menu.11. Data from the mapping table (text file) will fill this table in the upload procedure. Before

the upload, compare the accounts in the mapping table with the accounts in tables SKA1,SKB1, and SKAT.

12. Choose Upload .

13. Choose the file where the account mappings for general ledger accounts and primarycost elements are maintained(example: Example_CoA_MappingTables_IKR_ZNEW.txt).

In the column “Short text acc old” the texts are shown in the maintenance language

of the old chart of accounts. For example the maintenance language of IKR isGerman (DE).

14. Choose Save.

15. Choose Assignment of old/new secondary cost element from the menu.

16. Before uploading, compare the accounts in the mapping table with the accounts in tablesCSKA, CSKB, and CSKU.

17. Choose Upload .

18. Choose the file where the account mappings for secondary cost elements are maintained(example: Example_CoA_MappingTables_IKR_ZNEW.txt).

19. Save your settings and choose Back .

In the example for SAP Best Practices Assignment of other accounts is not used.

7.4.2 Check participating company codes

You can create the chart of accounts conversion for either all company codes that use therespective chart of accounts, or for only some company codes.

If you use cross-company code cost accounting, the chart of accounts must be converted in allthe company codes that use a common controlling area, since the entire controlling area isallocated to one chart of accounts.

In this step, the mapping maintenance view is checked to ensure that all company codes that usethe chart of accounts have been maintained. For each company code not entered, an error iswritten in the log. No further user entries are required, this step is executed, and a background

job has been started. Check the status and log in the procedure monitor.

© SAP AG of 34




7.4.3 Determine scenario

Chart of accounts conversions must always be done for all company codes belonging to acontrolling area, because all company codes belonging to a controlling area must use the samechart of accounts.

Consequently, if you want to change the chart of accounts for one company code belonging to a

given controlling area, you must include all company codes that belong to this controlling area inthe mapping table.

No further user entries are required, this step is executed, and a background job has beenstarted. Check the status and log in the procedure monitor. Warning messages can be ignored.

7.4.4 Find undefined B segment and implicit merges

In this step, the implicit merges as well as undefined merges at B level are identified.

No further user entries are required, this step is executed, and a background job has beenstarted. Check the status and log in the procedure monitor.

7.4.5 Maintain B segment merges

Use

This step includes a check for undefined (critical) merges at B level. In this step, you can changethe entries that have a yellow traffic-light symbol.

In the separate mapping table, you can now define a G/L account or cost element for each criticalmerge. The target account of cost element will inherit the settings of these accounts or elementsduring the merge. For further information please see the online documentation in CNV_IMG.

Procedure1. For the example of SAP Best Practices the table is empty because there is no merge

defined.

2. Choose Back .


7.4.6 Check B segment merges

In this step, several checks regarding the entries in the B priority tables are made.


7.4.7 Check accounts for conversion

Execute the function. If the program shows information messages, warnings, or error messages,make the necessary changes in the mapping table.

© SAP AG of 34





7.4.8 Specify descriptions for conversion

In this mapping table, you can maintain the names of target charts of accounts, target accounts,and target cost elements in any language.

In the example of SAP Best Practices, descriptions are copied automatically. Please chooseback .

7.4.9 Check descriptions for conversion




7.4.10 Specify P&L statement structures for conversion

Use

Here you specify the financial statement structures that you want to change during theconversion.

Because of use of intervals in financial statement versions the conversion tool is not able toassign the new accounts correctly. Therefore financial statement versions should be excludedfrom conversion. After the conversion the financial statement versions have to be maintainedmanually. Via default all financial statement versions related to the old chart of accounts are

selected. This selection has to be removed.

If you decide to include the versions into the conversion please copy the financial statementversion as backup.

Procedure

1. On the Change View “Financial Statement Versions”: Overview screen, make thefollowing entries:

Field name User action and values

Convert deselect

2. Save.

7.4.11 Check P&L statement structures

Execute the function


© SAP AG of 34




7.4.12 Confirm settings

In this step, you check and finally confirm the settings and mapping which you have made in theprevious steps. Please select confirm for all activities and save changes.

Caution: after performing this step no changes of previous steps are possible. Account assignments can no longer be changed.

7.4.13 Make scenario-related optimization



7.4.14 Check package settings

Execute the function. After this step, display the procedure monitor by entering the transaction code CNV_MONITOR .

7.5 Preprocessing Programs BEFORE System Lock

Enter fields for selection



7.6 GenerationExecute the function. Conversion programs are generated and the jobs for conversion arecreated here. All related steps are also executed.

7.6.1 Generate conversion programs

Execute the function as a background job.


7.6.2 Define jobs

Execute this function as a background job.


© SAP AG of 34




7.7 Preprocessing Programs DURING System Lock

7.7.1 Load object table

Important: Only run this activity when no other activities are running in thesystem.

1. Execute the function.

2. After this step, display the procedure monitor by entering the transaction codeCNV_MONITOR .

3. Restart this activity and ensure that the traffic light is green in the procedure monitor.

7.8 Conversion

7.8.1 Start conversion

1. Execute the function.

Choose YES when Popup appears to start with optimization.

2. After this step, display the procedure monitor and ensure that all relevant tables havebeen converted. If they have not been converted, the relevant tables must be convertedmanually (customizing) when necessary. E.g. masked tables (T033G) have to bechecked manually.

7.9 Postprocessing Programs DURING System Lock

7.9.1 Reset table buffers



7.9.2 Adapt validity date for cost element groups



7.9.3 Create/change descriptions



© SAP AG of 34




8 Follow-Up Activities

8.1.1 Manual Activities

UseCertain activities must be performed manually, because some objects cannot be maintained bythe conversion tool. Manual activities may also be necessary if the conversion does not makesense from a business point of view.

For some tables, the maintenance of the chart of accounts assignments must beperformed manually. For example:

• Financial Statement Version

• Asset management – Financial statement version for asset reports

• Validations/substitutions

• Sample accounts

• Worklists

• Default value customizing, such as automatic cost element generation – table TKSKA, …

• Account assignment for electronic bank statement, account symbols such as in table

T033G, …

• Fields that do not refer to SAP standard domains, such as Y*, Z*, …

The details on all of these topics vary depending on the building blocks activated, and canbe found in the Configuration Guide of the relevant building block.

After the conversion, test scenarios must always be started to find out if all therelevant objects were converted.

9 Optional Activity: Register Users for Package

Use

At the Package settings stage, the user is automatically registered for the package. Onlyregistered users can run CNV_IMG. If an error message appears that the user is not registered,the stage can be repeated.

To assign the user, access the following navigation option:

Procedure

© SAP AG of 34




1. Access the activity using the following navigation option:

Transaction Code CNV_00001_REG_USER

2. On the register users screen, select user.

3. Choose Establish role (Shift +F4)

4. Choose Delivery .5. Enter license key.

10 Attachment: List of Tables included inconversion

The following list contains all tables which are included for conversion with the SAP BestPractices conversion tools.

If there are tables which are not listed here the conversion tool is notable to convert. Please exclude the tables from conversion (assign “NOTUSE”to the table, see chapter “Maintain customer-defined and generated fields”).The accounts in these tables have to be changed manually after conversion.

If you wish an automatic conversion of tables which are not included in this listplease contact the SLO department for further support. These additional servicesare not included into the charge free delivery of the SAP Best Practices conversiontools. Please ask SLO department for licencing information.

© SAP AG of 34




Tables included into automatic conversion:

Column 1 Column 2 Column 3 Column 4

AD01C_ATTR FMBUDBCS J_1IEXCACC T030

AD01C_SELA FMBUDDIS J_1IINDCUS T030C

ANKL FMBUDRES PAYAC01 T030D

ATPRA FMBUDREV PAYAC11 T030E

C000 FMBUDSTA PSO26 T030G

C001 FMCY_COPI REPPARMS T030H

C002 FMDERIVE001 RWSHEADER T030HB

C003 FMDERIVE002 RWSLINE T030I

C004 FMFD SETHEADER T030K

C005 FMFGF2FADT SETHEADERT T030R

C006 FMFGT_DIT_FBT SETHEADERTRANS T030S

C007 FMFGYECLAA SETLEAF T030U

C008 FMIAA SETLINET T030V

C009 FMITPOCT SETNODE T033G

C502 FMLGD_H_VG_03_01 SETO2N T033U

CBPL FMLGD_H_VG_04_01 SETUSE_BER T035D

CEFORMF GMCOUPD SETUSE_REP T035V

CESETS GMFIUPD SKA1 T037S

CRMC_CATS_CO HRP1270 SKAS T038

CSKA HRPAD23 SKAT T042I

CSKB ICRC04 SKB1 T042ICC

CSKU JBDFTPASSIGNMENT T001 T042K

DOCCHG_CLACCT JBSSKB1 T001B T042Y

EVCE J_1A030IF T001C T044D

EWUCUSAK J_1ASKB1 T001U T044Z

FIWF_ACGRP J_1ASKCLS T004 T045B

FIWF_MDRUL J_1ASKCLST T004T T045D

FLQACC_ACT J_1BLB08 T011 T045E

FLQACC_INFO J_1BLB09 T011Z T045P

FMAC J_1IEWTHKONT T012K T045W

FMAC2 J_1IEWTPROVISACC T018C T046A

FMBUDACL J_1IEWT_CUST T018V T049E

© SAP AG of 34





T049F T882 TBKKC_BUKRS TFIN201

T056A T882C TBKKC_GLACC_TEXT THKONT056D T882G TBP1C TINSB

T056S T884 TBPFK TISSR_MAB_LEDGER

T056U T8A00 TCA41 TIV65

T056Y T8A30 TCCAA TIV79

T071 T8A50 TCJ_C_JOURNALS TIV80

T074 T8G17 TCJ_TRANSACTIONS TIV84

T077S T8G30B TCKH2 TIV85

T077Z T8J1A TCKHA TIV8A

T095 T8J1B TCN41 TIV9I

T095A_MAP T8J1I TDACCOUNTDETS TIV9J

T095B T8J5A TDACCOUNT_DET_S TIVA1

T095C T8J6G TDG47 TIVBPVENDORCMP

T095P T8J6H TEBCO TIVEXFIACCPROP

T350 T8J6I TF002 TIVEXFIREPSYMB

T609IS T8J6J TF003 TIVFI

T77KB T8J8A TF103 TKA00

T77KL T8JB TF103A TKA01T801D T8JBS TF123 TKA08

T801E T8JDQ TF187 TKA30

T801L T8JDR TF410 TKA3A

T801M T8JDS TF556 TKA3C

T801S T8JDV TF556A TKA3P

T802G T8JK TF560 TKB5AL

T802GU_SET T8JN TF584 TKB5E

T803G T8JXC TF658 TKB6

T804F TABKT TFAVW TKB9E

T804FU_SET TAKOF TFE05 TKB9G

T811K TBKKCASS TFE18 TKEADPC00

T811S TBKKCCLR TFE19 TKECRMC

T820 TBKKCVAR TFIN200 TKFPA

© SAP AG of 34





TKKA2 TZB27

TKKAB TZD0B

TKKAK VIEA01TKKAP VIEA02

TKKAR VTBACCOUNT

TKKAZ WOSCR_EXI_001

TKSKA WOSCR_EXI_002

TKSR1 WOSCR_GRP_001

TKV11 WOSCR_GRP_003

TKZU1

TKZU3

TKZX3

TKZX9

TORB1

TPEXT

TPIK2

TPIK3

TQ80

TRACC_ACCSYMBREP

TRAC_ACCSYMBREP1TRAC_ACCSYMBREP2

TRRC_CA1

TRRC_CA3

TSC0C

TSC0I

TTRCD

TVRRUR

TWIC0250

TWPIF

TWPIW

TWWTK

TZ21

B31 ConversionGuide 600 En

Documents

Transcript of B31 ConversionGuide 600 En