1

NECAM SHE MIGRATION

CONFIG IN 110 & MIGRATION IN 100
 2

In this Customizing activity, you compare the fiscal year variants between controlling areas and their assigned
company codes.

The migration to the unified journal entry requires a unique fiscal year variant in controlling and financial. The
report reconciles the fiscal year variant of the controlling areas and their assigned company codes. It creates a
proposal for the configuration change.See IMG activity documentation for more information

In this activity, you migrate all new G/L ledgers to the new configuration.

The following are migrated:

 Company code assignments

 Currency settings
 Fiscal year variant
 Open period variant
 Settings for real-time integration of CO-FI

SHE 110 ERROR

SU53
 3

BEVERLY ASSIGNED “FINS_MIGR” ROLE AND NOW ABLE TO PROCEED.

SHE 100 ERROR

 4

In this Customizing activity, you define the ledgers that you use in Accounting.

Only one ledger can be designated leading ledger.

There are two types of ledger:

 Standard Ledger: A standard ledger contains a full set of journal entries for all business transactions.
 Extension Ledger: An extension ledger is assigned to an underlying ledger and inherits all journal entries of
the underlying ledger for reporting. The underlying ledger must be a standard ledger. Postings made
explicitly to an extension ledger are visible in that extension ledger but not in the underlying ledger. This
concept can be used to avoid duplication of journal entries if many business transactions are valid for both
ledgers and only a few adjustments are required in the extension ledger.

See IMG activity documentation for more information on Requirements, Standard Settings, and Activities.
 5

DID THIS COMPANY CODES 1038, 1045, 1856, 1905.

 6

In this activity, you define a ledger that represents Controlling. That is, a ledger that contains all postings of actual
data that is relevant to Controlling.

This is done by assigning the version 000 to a ledger. You do this on a company code level, but you have to use the
same ledger for all company codes.

See IMG activity documentation for more information

 7

In this activity, you can create new document types for postings in Controlling, for example you can create a
document type that you can use for the manual reposting of primary costs.

Standard settings

For documents types used in Controlling, the indicator G/L account must be set.
8
9
 10

In this activity, you define a mapping variant that maps CO business transactions to document types. This mapping
must be done for all CO business transactions that do actual postings.

Upgrades: The migration of the ledger Customizing generates a default mapping variant in which all CO business
transactions are mapped to the document type that was entered in the variant for real-time CO-FI integration.
11
 12

In this activity, you define default values for use in CO business transactions whose user interfaces do not allow you
to enter a document type or a ledger group for posting purposes.

Requirements: You have defined a mapping variant that maps CO business transactions to document types.

Standard setting: If you do not enter a default ledger group, all CO postings will be done to all G/L ledgers.

In this customizing activity you define how the system calculates the offsetting account in all applications.

You have to carry out this activity before you perform any migration activities that affect the offsetting account.

Note: This activity is a prerequisite for the activities after migration task “Fill the Offsetting Account in FI
Documents” See the
 13

In this customizing activity you define the source ledger (and by doing so the source database table) of the balances
for general ledger accounting using the following:

 Target Ledger
 Company Code (you can specify * to apply the settings to all company codes)
 Starting Fiscal Year (by specifying year 0001 you apply the settings for all fiscal years)

See IMG activity documentation for more information

In this activity, the Customizing settings for the ledgers are checked. This check must run without error messages
before you continue, for example with the migration of transaction data or any other activities.
 14

ASSIGNED MX03 TO FYV V3

EXECUTED TRANSACTION “KEA0” FOR OPERATING CONCERN 1038.

 15

If you are already using classic Asset Accounting and want to migrate to new Asset Accounting, you have to
migrate the charts of depreciation from classic Asset Accounting. This activity supports you in this migration.

Using this activity, you can (among other things) assign depreciation areas to an accounting principle.

See IMG activity documentation for more information on requirements and standard settings
 16

AA CONFIG IN 110
 17

Parallel crcy area (crcy type 20) missing for area 01 ch. of deprec. ZUS
Message No. ACC_AA116

Diagnosis
For the leading valuation of the ledger approach and accounts approach and for parallel valuations of the
ledger approach, the following is valid: The parallel currencies in the leading ledger in General Ledger
Accounting and in the depreciation areas in Asset Accounting must be the same.

Procedure
If you have previously been using parallel currencies in General Ledger Accounting, but you have not
implemented the corresponding parallel currency areas in Asset Accounting for all depreciation areas, you
must first implement these depreciation areas before you install SAP Simple Finance. Contact your system
specialist.

Caution: generic values for real depreciation area (refer to long text)
Message No. AC246

Diagnosis
You set up depreciation area 90 in chart of depreciation ZUS so that all types of acquisition values are allowed.

However, this only makes sense for derived depreciation areas.

The system allows the setting, but note that it can lead to undesired effects for real depreciation areas.

Procedure
Check your settings and change them if necessary.
 18

Check passed after assignment of FINS_MIGR.

SHE110

If you are already using classic Asset Accounting and want to migrate to new Asset Accounting, you have to
migrate the charts of depreciation from classic Asset Accounting. This activity supports you in this migration.

Using this activity, you can (among other things) assign depreciation areas to an accounting principle.

See IMG activity documentation for more information on requirements and standard settings
 19

Created a transport for the migration of Chart of Depreciation.

20
 21

Transport to remove Sample Chart of Depreciation from Company Code only ZUS is left.
 22

OAOB
In Asset Accounting, you can only use company codes that have already been defined in Financial Accounting as
being generally valid. In addition to the general FI data for a company code, you have to make additional
specifications that apply for Asset Accounting. One of the most important of these specifications is the assignment
of a chart of depreciation to the company code.

ANDREAS CREATED A TRANSPORT TO FIX AA ISSUES. AFTER WHICH THE ABOVE ERRORS WENT
AWAY.See CSS message 780945/2015

SHE100 MIGRATION
23
 24

You are already using new Asset Accounting. This activity supports you in adjusting the parameters for charts of
depreciation.

See IMG activity documentation for more information on requirements and standard settings
 25

IN SHE 100

Customizing inconsistency (contact your system administrator)

Message No. AC496
 26

Diagnosis
Company code 1038 manages parallel currencies in Asset Accounting. For each area that posts automatically
online to FI, you have to define one dependent depreciation area that adopts both identical values and
depreciation terms from depreciation area 01, and which is assigned to currency type 20 and currency USD.
There is no depreciation area of this type defined for depreciation area 01.

Procedure
Check your Customizing settings.

Customizing inconsistency (contact your system administrator)

Message No. AC496

Diagnosis
Company code 1046 manages parallel currencies in Asset Accounting. For each area that posts automatically
online to FI, you have to define one dependent depreciation area that adopts both identical values and
depreciation terms from depreciation area 01, and which is assigned to currency type 20 and currency USD.
There is no depreciation area of this type defined for depreciation area 01.

Procedure
Check your Customizing settings.

Transport to correct this setting.

 27

OADB

In this activity, you define your depreciation areas. You can change the definition of depreciation areas adopted
from the standard chart of depreciation, and you can add new depreciation areas if needed
28
29
30
 31

In this activity, you activate your operating concerns for account-based Profitability Analysis, if not yet done.

If this setting is not made, the new profitability reporting will not be available. Furthermore error messages may
appear, for example when posting to profitability segments. You can, however, deactivate these messages in
Customizing. The message long texts contain instructions on how to do this.
 32

In this Customizing activity, you create number range intervals for bank account technical IDs. The system
automatically assigns a technical ID to a bank account once it is created in the bank account master data.

In this Customizing activity, you create number range intervals for change requests used in Bank Account
Management. The system automatically assigns a number to a change request once it is created in Bank Account
Management.
 33

See IMG activity documentation for more information

 34

Took 30 min in SHE110. Green Status. Online 15 min in SHE 100.

35
 36

In this Customizing activity you check whether the G/L accounts and cost elements are consistent with each other.

An inconsistency could be for example that no G/L account exists for a primary cost element.

You need to correct the indicated inconsistencies, otherwise the G/L account master records will have the wrong
account types after migration.
 37

Creating the account in FSP0, Make it Primary and P&L Group and Delete the language in the Translation
Tab.
 38

We created the GL accounts in FSP0 and re-checked. Check passed.

In sFIN 2.0 the master data of G/L accounts and cost elements were merged. Cost elements are now special
G/L accounts and must be maintained in the same transaction as for maintaining G/L accounts: Edit G/L
Account Centrally (FS00).

G/L accounts share a chart of accounts and a number range. Before the merge, only primary cost elements
were represented as G/L accounts.

See IMG activity documentation for more informationstandard settings and activities.
39
 40

In sFIN 2.0 the master data of G/L accounts and cost elements were merged. Cost elements are now special G/L
accounts and must be maintained in the same transaction as for maintaining G/L accounts: Edit G/L Account
Centrally (FS00).

The fields of the cost element master have undergone a review and not all fields have been retained. In particular,
the fields for default assignment on cost center or internal order were omitted from the joint master data record.

Starting from existing cost element master data, the migration process transfers the default assignments from the
master data table CSKB to the Customizing table TKA3A.

After migration, the default assignment settings are accessible via transaction OKB9.
 41

In this Customizing activity you analyze in a test system if all transactional data is complete and correct.

See IMG activity documentation for more information

42
 43

In this Customizing activity of the migration to the SAP Simple Finance, on-premise edition, you check that the
FI documents are consistent and ready to be migrated.

See IMG activity documentation for more information

44
 45

Executing transaction FINS_RECON_RC0 in SHE 100 after Andreas Transports

 46

Executing transaction FINS_RECON_RC1 in SHE 100 after Andreas Transports (780945/2015)

47
 48

In this Customizing activity, you enrich transaction data and documents and migrate them to SAP Accounting
powered by SAP HANA.

See IMG activity documentation for more information on the steps that this program consists of.
 49

In this Customizing activity you check if all documents are enriched correctly.

See IMG activity documentation for more information

 50

The migration of the transactional data to the SAP Simple Finance, on-premise edition is a prerequisite for
productive use. It populates the entries in of the universal journal entry (UJE) by combining the transactional
data of the applications FI, FI-GL, CO and FI-AA.

Additionally, the characteristics of account-based CO-PA are added to UJE items which are assigned to a
profitability segment.
 51

Ran in Delta mode with 8 parallel threads.

 52

In this Customizing activity you check if all accounting documents have been migrated correctly.

You execute this reconciliation step after the migration of line items of the different applications into ACDOCA.
In case of NewGL Line Items, CO-line items, and AA-line items, the compatibility view which reproduces the
original line item table is compared to the original values. In case of BSEG no compatibility view exists and the
check is executed directly.

See IMG activity documentation for more information

 53

SAP Note 2138644

 54

Restart Migrate into UJE

55
56
 57

Short Dump.
 58

Restarted.

Short Dumps

Implemented SAP Note 2197469.

 59

Multiple SAP Notes implemented. 2197469, 2205453, 2206814, 2182515 2208424.

60
61
 62

All issues are for 1785. Ignoring them and moving on.
63
 64

WE WILL IGNORE ERRORS IN 1785. ASKING NECAM TO APPLY THE FOLLOWING SAP NOTES 2197244,
2136070, 2208200.

Ran a Delta run still the errors are remaining. Doing a Reset of Migration of Balances.
 65

Errors Remain applying notes 2178120, 2157195.

Errors Still. Deciding to complete the next activities in case of false positives.
66
67
68
 69

Escalated Incident 925580– Define CO Doc Types

70