1

2

3

4

5

What are the capabilities of an accounting system based on SAP HANA ? There is only one single source of truth for Financial and Managerial Accounting. All General Ledger will be stored in one repository, the revenue and cost part of the P&L has all relevant detail like as to customers, products and regions. The processing and analysis is based on line items rather than pre-configured totals. Thus you have the highest granularity available, your analysis is not restricted by first setting up aggregates in order to evaluate data fast enough. The aggregates would limit the kind of analysis you can do fast. With HANA you can do all analysis fast, you have all dimensions available which you have in your line items. The solution is easy to adapt. Any number of customer specific dimensions can be added consistently in Accounting. Some industries like banking and insurance see more and more regulations, which require to add fields to accounting, sometimes 30 or even 80 fields. Reporting based on this data is fast and flexible. State of the art BI frontend tools can be used for operational reporting, thus the benefits of BI tools are inherited to the transactional system. The month end closing process is accelerated, some steps can even be run on a daily/weekly basis rather than just at period end. Thus the accounting system can give you insight on a daily/weekly basis. Finally consolidations could also be run on the original accounting data. Data replication would become obsolete, some consolidation functionality could even be run on the fly in reporting. ! Achtung Demo ! Receivables Manager

6

Throughput Boost data throughput by overcoming the lock issue

and reducing data volume to be posted

(Non)-Reconcialition No reconciliation because of ‚One Document‘

Flexibility One starting point to extend and adapt simply and

straightforwardly

Data Volume Reduce data volume dramatically by eliminating

redundancies Performance Expectation: achieve identical response times as

before plus optimize

7

8

9

10

11

12

Fin OPS Tabelle für Saldenvortrag: FINS_BCF_FY wird durch den SAPF010

automatisch gefüllt

13

14

15

With SAP Simple Finance 1.0, the tables COSP and COSS have been deleted.

No data will be written into this tables.

With SAP Simple Finance 1.0, there are the new tables COSP_BAK for primary

costs and COSS_BAK for secondary costs. Planned values and summarized

data for other values like commitments and other special value types are

written into these new tables. Actual costs do not update the tables COSP_BAK

and COSS_BAK. All actual costs are stored only in the line item table COEP.

Actual data will no longer be stored on the summarized level.

That means, that all data with value types 04 (actuals) and 11 (statistical

data) will be removed from the summarized level.

The tables COSP_BAK and COSS_BAK cannot be updated directly, but via

ABAP classes. For further information, please see the RKT material for the

topic ‘Removal of Agregates’.

16

Two new CDS views exist with the names COSP and COSS.

These views are used to read data but they cannot be updated directly.

View COSP is a union of table COEP and COSP_BAK, view COSS is a union

of table COEP and COSS_BAK.

All actual data are retrieved directly from the line item table COEP via the CDS

views. All necessary aggregation is done on-the-fly by request.

17

For reporting purposes the line item table COEP has been enhanced by the

additional fields listed above.

During this migration step the object number in the CO line item table COEP is

broken down into their single components like object type and object number.

Afterwards this informations are filled in the new fields in table COEP

accordingly.

Example

Object number KSC0100000001110 creates the following entries in table

COEP:

-> Object type: cost center

-> cost center number: 0000001110

18

19

Interrogate - untersuchen

20

21

22

23

24

FI-AA: note 1939592 for pre-check includes check report

RASFIN_MIGR_PRECHECK

The following components are not compatible with SAP Simple Finance New

Asset Accounting: Joint Venture Accounting (JVA) is not compatible with New Asset Accounting (and

vice versa). This is also valid for the Business Function JVA, Integration with New

General Ledger Accounting (JVA_GL_INTEGRATION).

Lease Account Engine (LAE) included in the Enterprise Extension Financials

Extension (EA-FIN) is not compatible with New Asset Accounting.

Classic Real Estate (RE classic) is not compatible with New Asset Accounting.

Public Sector Management – Fund Management (PSM-FM) respectively IS-PS: it is

not allowed to have posted any requests with reference to an asset in any period of

an open year.

Reconciliation Reports for data consistency: SAPF190 /TFC_COMPARE_VZ (Totals <-> Line items and Totals <-> Indizes, entry

view with GL view…)

RAABST01/RAABST02 (FI-GL with FI-AA)

RCOPCA44 (checks GL and profit center values)

RFINDEX/RFINDEX_NACC (generell consistency checks)

RM07MBST/ RM07MMFI (Consistency check FI and MM)

RGUCOMP4 (TA GCAC) (Legder comparison)

25

26

27

28

29

30

31

32

33

34

35

36

37

38

39

40

41

42

43

44

45

46

As just mentioned, with SAP Simple Finance 1.0 the line items in FI and CO

are linked together on line item level via new fields.

Therefore the header table COBK has been enhanced by the additional field

AWKEY.

The line item tables BSEG and COEP have been enhanced by the fields

AWSYS, AWTYP, AWKEY and POSNR.

The new fields AWKEY, AWSYS and AWTYP have been filed in the migration

step ‚Migrate Transaction Data and Documents‘.

The migration step ‚Set Links between CO and FI Documents ‘fills the new field

POSNR.

This migration step has to be executed after the main part of the migration.

47

The migration step ‚Migrate Profit Center and Partner Profit Center into CO

Documents‘ is available with SAP Simple Finance SP 02.

This customizing step of the SAP Simple Finance Migration is an optional step

and has to be executed after the main part of the migration. It fills the fields

Profit Center (PRCTR) and Partner Profit Center (PPRCTR) in table COEP in

order to allow Profit Center Reporting within the CO data.

If you execute this transaction the system checks for each line item in table

COEP, if the fields PRCTR and PPRCTR are filled. In the case that they are not

filled the system checks, if this data can be derived from master data records

(for example from the master data of a cost center). Then the fields will be filled

according to the information found.

In the case that the data can not be derived from master data records, the

fields will not be filled. The system does not check the validation and

substitution.

You can check the status of this migration step with the transaction ‚Display

Status of Migrate Profit Center and Partner Profit Center into CO Documents‘.

48

49

During the migration steps ‘Migrate Transaction Data and Documents’ and ‘Set

Links between CO and FI Documents’ the system enters the relevant

information in the new fields for the accounting document line items tables

(COEP and BSEG) and the header table COBK.

This test report checks if the migration was successful for all documents.

It checks the followings entries in the line item and header tables:

- Do the new fields for the logical document have been filled correctly?

- Is the object number broken down correctly into its single components and

have the corresponding fields in table COEP been filled correctly?

In order to check single erroneous documents, you can activate a detailed list

by specifying the number of line items to be displayed.

If the test shows errors in the migrated documents, the reason for this migration

failure must be investigated and corrected. When you completed the

corrections, you must start the migration step again!

50

With SAP Simple Finance 1.0, it was realized that actual data are only stored in

the line item table and no longer in totals tables. So all actual data are stored

only in one place and data redundancies are avoided. In case of structural

changes or extensions, there is only one place where changes have to be

done.

In the past, all CO-relevant postings were stored in the totals tables COSP and

COSS.

With SAP Simple Finance 1.0, there are the new tables COSP_BAK for primary

costs and COSS_BAK for secondary costs. Planned values and summarized

data for other values like commitments and other special value types are

written into these new tables. Actual costs do not update the tables COSP_BAK

and COSS_BAK. All actual costs are stored only in the line item table COEP.

Actual data will no longer be stored on the summarized level.

This test report compares the balances in the original totals tables COSP_BAK

and COSS_BAK against the new totals calculated from the individual line items

in table COEP.

The following differences can occur:

51

A balance record exists only in the original totals table but there are no

corresponding line items.

Line items exist without a corresponding entry in the totals table.

Line items and corresponding records from the totals table exist, but there are

differences in the amount or quantity fields.

You can ignore differences that are introduced by postings made after the

migration by specifying a migration date.

If differences occur, you must determine if these differences existed before the

migration.

You execute the report after the migration before you post any new CO-

documents to SAP Simple Finance .

52

53

54

55

56

57

58

59

60

61

62

63

64

65

66