Smart Financials

Release Notes for

Smart Financials 1.0

SAP® What's New? – Release Notes

Smart Financials 1.0 Page 2 of 49

Copyright

© 2014 SAP AG or an SAP affiliate company. 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.

National product specifications may vary.

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 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. Please see http://www.sap.com/corporate-en/legal/copyright/index.epx#trademark for additional trademark information and notices.

http://www.sap.com/corporate-en/legal/copyright/index.epx#trademark

http://www.sap.com/corporate-en/legal/copyright/index.epx#trademark



Smart Financials (New) .................................................................................... 4

Migration from SAP ERP to Smart Financials package 1.0 (new) ................... 6

Financial Accounting (FI) ................................................................................. 7

New General Ledger Accounting in Smart Financials (New) .................................. 7

Functions for Accounts Receivable and Accounts Payable (Changed) .................. 9

New Asset Accounting: Ledger Approach and Accounts Approach (New) ........... 11

New Asset Accounting: Migration and Customizing (New) .............................................. 17

New Asset Accounting: Postings (New) ........................................................................... 21

New Asset Accounting: Transactions with Integrated Postings (New) ............................ 27

Financial Supply Chain Management (FSCM) ............................................... 30

FIN-FSCM-CLM: Business Function SAP Smart Cash Management (New) ......... 30

FIN-FSCM-CLM: Local BI Content for SAP Smart Cash Management (New) ...... 32

Controlling (CO) ............................................................................................. 35

Line Item Based Controlling with Period Close Optimizations (Enhanced) ........... 35

Variance Calculation for Cost Centers (Changed) ................................................ 37

WIP Calculation and Results Analysis (Changed) ................................................ 39

Variance Calculation for Production Orders (Changed) ........................................ 44

Smart Financials Reporting (New) ................................................................. 46

Integrated Business Planning (New) .............................................................. 48

Data Aging of Financial Accounting Documents (New) .................................. 49



Smart Financials (New)

Use

Smart Financials package 1.0 extends the scope of typical financial applications in

order to serve various internal and external stakeholders. In times of volatile markets,

margin pressure, and sophisticated regulatory requirements, companies need a precise

view of the past, immediate insight into the present, and a clear perspective of the

future. Smart Financials comes with optimized financial accounting processes and

supports the operational finance experts driving efficiency and compliance.

This requires a new way to run the business in real-time based on real-time processes

and data. Smart Financials package 1.0 provides lean data architecture, real-time

insights, and a beautiful user experience.

Smart Financials package 1.0 is based on line items as a single source of truth for

operational reporting and planning. This model provides all transactional details to

reporting in real-time without the need to extract and duplicate data in reporting-

oriented data structures. As all data is available on this granularity, reporting requests

can be handled on an ad-hoc basis. Combining line items in accounting, ongoing

transactions not yet reflected in accounting, and planning data helps to answer

questions such as "What has happened?", "Why did it happen?", "What is happening

now?", "What will happen next?".

Based on SAP HANA technology, the system provides all kinds of requested

aggregated financial information on the fly using views, which are based on granular

line item data. There is no need to keep persistent storage of aggregates and indices.

Due to this, it is much simpler and faster to adapt the system to cope with changes in

business and corporate structures. Business flexibility on one hand and accounting

stability on the other are no longer a contradiction.

For operational processes especially in financials, a high degree of automation is a

clear target. Transferring operational data into the financial application is based on

rules defined once, which also include complete exception-based error handling and

correction. Smart Financials package 1.0 assists the experts in finding the root cause

for the exceptions with advanced search and rules engine support.

See also

For more information about Smart Financials package 1.0, see the following release

notes:

o Migration from SAP ERP to Smart Financials package 1.0 (new)

o Data Aging of Financial Accounting Documents (New)

o New General Ledger Accounting in Smart Financials (New)

o New Asset Accounting: Ledger Approach and Account Approach (New)

o Functions for Accounts Receivable and Accounts Payable (Changed)

o Line Item Based Controlling with Period Close Optimizations (Enhanced)

o Integrated Business Planning (New)

o Variance Calculation for Cost Centers (Changed)



o Variance Calculation for Production Orders (Changed)

o WIP Calculation and Results Analysis (Changed)

o Smart Financials Reporting (New)

o FIN-FSCM-CLM: Business Function SAP Smart Cash Management (New)

o FIN-FSCM-CLM: Local BI Content for SAP Smart Cash Management (New)



Migration from SAP ERP to Smart Financials package 1.0 (new)

Use

As of Smart Financials package 1.0, both general and application-specific Customizing

activities are available which you can use for the migration from SAP ERP to Smart

Financials package 1.0.

Effects on Existing Data

With Smart Financials package 1.0, classic General Ledger Accounting is no longer

available. If you use classic General Ledger Accounting and want to migrate to Smart

Financials package 1.0, you must first activate General Ledger Accounting (new).

Setting up General Ledger Accounting (new) during migration to Smart Financials

package 1.0 includes different Customizing activities, for example, to define a leading

ledger, or to define valuation areas for foreign currencies. It also includes data transfer

from General Ledger Accounting to General Ledger Accounting (new).

Effects on System Administration

You can monitor the status of each migration step by using a migration monitor.

Effects on Customizing

You can find the new Customizing structure in the SAP Customizing Implementation

Guide under Smart Financials Migration.

See also

For additional information, see:

o Migration Guide on SAP Help Portal

o Administrator's Guide on SAP Service Marketplace



Financial Accounting (FI)

New General Ledger Accounting in Smart Financials (New)

Use

As of Smart Financials package 1.0, new General Ledger Accounting offers the

following functions:

o Balance Carryforward

The program for carrying forward balances enables you to initialize data carried

forward previously when you want to repeat a balance carryforward.

Furthermore, you can save results lists and then use the program to display

them at a later point in time.

o Integration with Materials Management: Account Determination for Cost of Sales

You can specify that the cost of sales is posted to different accounts on the basis

of the cost component assignments. For more information, see the relevant

release note for Controlling.

o Data Aging

Archiving accounting documents now is data aging. For more information, see

the release note for Data Aging.

Index Tables and Totals Tables

The data model of new General Ledger Accounting has been simplified to enable

integration with Smart Financials package 1.0. All data in new General Ledger

Accounting is stored in document tables and line item tables. The system calculates the

aggregated data in the relevant views.

The new data model eliminates the need to save redundant data (for example, in totals

tables or index tables). Furthermore, inconsistencies can no longer arise between FI

documents and totals tables.

The following tables have been replaced by views:

o BSIS

o BSAS

o GLT0

o FAGLFLEXT

o FAGLBSIS

o FAGLBSAS

Tables GLT1 and GLT2 are no longer available for new General Ledger Accounting

within Smart Financials package 1.0. Consequently, ledgers for these tables are no

longer updated and can no longer be processed or analyzed in the Special Purpose

Ledger (FI-SL). If you still need to use one of these ledgers, contact SAP Development

Support (message component FI-SL-SL).

The new data model allows you to continue to use programs to access the database as

before. This also applies for user-defined programs.



Roles

You can use the following new roles as copy templates:

o SAP_SFIN_ACC_ACTUALPOSTING

o SAP_SFIN_ACC_CLOSING

o SAP_SFIN_ACC_MASTERDATA

o SAP_SFIN_ACC_REPORTING

The new roles contain applications for both new General Ledger Accounting and

Overhead Cost Controlling.

Constraints

With Smart Financials package 1.0, the following functions are no longer available:

o Balance Sheet Planning

o Reports for comparing planning data and actual data in Profit Center Accounting

o Destruction of data or deletion of FI documents (Information Lifecycle

Management)

o Average balance ledger


Due to the changed data model used in Smart Financials package 1.0, classic

General Ledger Accounting is no longer available. If you have previously been using

classic General Ledger Accounting, you can transfer your data to new General Ledger

Accounting during the migration to Smart Financials package 1.0.

You can use a range of migration programs to migrate your existing data to the new

data structure.


Since Customizing for classic General Ledger Accounting is no longer available with

Smart Financials package 1.0, the following Customizing activities have been

included in Customizing for new General Ledger Accounting:

o Closing Cockpit

You find the Closing Cockpit in Customizing for General Ledger Accounting

(New) under Periodic Processing -> Closing Cockpit (Manage Templates

and Task Lists).

o Reclassifying Accounts

You now find all Customizing activities for reclassifying P&L accounts and

balance sheet accounts as account assignment objects (such as business areas

and profit centers) in Customizing for General Ledger Accounting (New) under

Periodic Processing -> Reclassify.

See also

For more information about performing the migration to new General Ledger

Accounting as part of Smart Financials package 1.0, see the release note on

Migration to Smart Financials package 1.0.



Functions for Accounts Receivable and Accounts Payable (Changed)

Use

As of Smart Financials package 1.0 (SAP_FIN 700), the following features and

changes are available in Accounts Receivable and Accounts Payable:

Index and Totals Tables

From a technical perspective, the following tables have been replaced by views:

o BSID

o BSAD

o BSIK

o BSAK

o KNC1

o KNC3

o LFC1

o LFC3

The advantage of this change is that you no longer have to store redundant data, thus

saving space on your database. You can still use reports that read the database,

including your own reports. A further advantage is that inconsistencies can no longer

arise between the single documents and the totals.

Replaced Transactions

For information about the transactions that are replaced by newer ones, see SAP Note

1946054.

Roles

The following new roles are available as a copy template:

o Role SAP_SFIN_AR for accounts receivable

o Role SAP_SFIN_AP for accounts payable

Portfolio Adaptation for Credit Management

While FI-internal Credit Management (FI-AR-CR) is still available for existing customers

with SAP Smart Financials package 1.0, as a legacy and to help in migration efforts,

please use the SAP Credit Management (FIN-FSCM-CR) component that offers an

integrated, cross-system form of credit management. FI-internal Credit Management

(FI-AR-CR) is not a functionality provided with SAP Smart Financials and will be

removed in a further version thereof.

Vendor Information System

The Vendor Information System application in SAP NetWeaver Business Client

(NWBC) allows you to make the following three types of analyses for vendor invoices:

o Due date analysis

o Overdue items analysis

o Currency analysis

Effects on Data Transfer



If you are already using SAP ERP and want to use the functions in Smart Financials

package 1.0, you have to migrate data. For additional information, see release note

Migration from SAP ERP to Smart Financials (New).


You can use the Data Aging function for financial accounting documents to increase

memory capacity. Data archiving for financial accounting documents is no longer

possible. For additional information, see release note Data Aging of Financial Accounting Documents (New).

See also

Central release note Smart Financials (New)



New Asset Accounting: Ledger Approach and Accounts Approach (New)

Use

As of Smart Financials 1.0 (EA-FIN 700), you can use new Asset Accounting. You can

handle parallel valuation of your assets using both the ledger approach and the

accounts approach.

To be able to use new Asset Accounting, you have to also use new General Ledger

Accounting. The values in new General Ledger are managed in at least one ledger.

You can record parallel valuation using the accounts approach or the ledger approach:

o With the accounts approach, you manage parallel valuation using valuation-

specific accounts. The values of all types of valuation are then managed in one

single ledger.

o With the ledger approach, you manage parallel valuation using multiple ledgers.

In that case, you do not need any alternative accounts; the values of each

valuation are managed separately in separate ledgers.

In addition to using new General Ledger Accounting, there are other prerequisites for

using new Asset Accounting in Smart Financials 1.0. These are explained in the Effects

on Customizing section.

Note:

Asset Accounting prior to this is referred to in the following as "classic Asset

Accounting" in order to distinguish the two.

New Asset Accounting replaces classic Asset Accounting. Classic Asset Accounting is

no longer available with Smart Financials 1.0. This applies across your entire system.

Characteristics and Use of New Asset Accounting

You can record the leading valuation of Asset Accounting in any depreciation area of

new Asset Accounting. It is no longer necessary to use depreciation area 01 for this.

The system now posts both the actual values of the leading valuation and the values of

parallel valuation in real time. The means the posting of delta values has been

replaced; as a result, the delta depreciation areas are no longer required.

New Asset Accounting makes it possible to post in real time in all valuations (that is, for

all accounting principles). You can track the postings of all valuations, without having to

take into account the postings of the leading valuation, as was partly the case in classic

Asset Accounting. The following details the advantages you gain by using new Asset

Accounting:

o Choice of using the ledger approach or accounts approach

o Real time postings in all valuations

o Leading valuation made more flexible

o Parallel documents for each valuation that post correct values from the beginning

o Abolition of delta areas for parallel valuation

o Simplification of your chart of depreciation

o Valuation-specific postings by means of restriction to accounting principles or

depreciation areas; the restriction of transaction types to depreciation areas no

longer applies



o Different fiscal year variants for each valuation (restriction: beginning and end

date of the fiscal year variant have to match)

o Straightforward assignment of accounts for each valuation within an asset class

o Simplified management of goods that are to be capitalized in accordance with

one set of accounting principles, but are to be posted to expense in accordance

with a different set

Constraints

In SAP enhancement package 7 for SAP ERP 6.0 SP02, business function

FIN_AA_PARALLEL, the restriction applies that you can only use new Asset

Accounting for the ledger approach. With Smart Financials 1.0, this restriction does not

apply, since new Asset Accounting in Smart Financials also supports the accounts

approach.

ALE transfer is not available in new Asset Accounting.

The batch input method for transactions based on AB01 is no longer available; you

can use the changed and new BAPIs for postings instead. For more information on

these BAPIs, see the Postings Release Note.

Reversal using a document with reversed positive/negative signs (an inverse posting)

is possible; a real reversal (negative posting) is no longer available.

Impairments from the business function New General Ledger Accounting 3

(FIN_GL_CI_3), SAP enhancement package for SAP ERP 6.0 are no longer

available.

Joint Venture Accounting, the Lease Accounting Engine, Classic RE, and requests

from component PSM-FM and IS-PS are not compatible with new Asset Accounting.

For more information, see the section "Prerequisites for the Migration to New Asset

Accounting".

Other Release Notes

For more information about new Asset Accounting, see the following release notes:

o Migration and New Customizing

o Postings

o Transactions with Integrated Posting


Existing Data

Already existing master data and transaction data is not changed by your activating

new Asset Accounting. However, you might possibly have to migrate and adjust your

Customizing data. This depends on your situation before the migration.

Existing Customizing settings from classic Asset Accounting or from new Asset

Accounting are transferred; this means that to the extent you have already been

working with classic or new Asset Accounting, you do not have to make all the

Customizing settings again.

You have to migrate, to some extent check, change and add to your Customizing data

in these two cases: you are migrating from classic General Ledger Accounting with

classic Asset Accounting, or from new General Ledger Accounting with classic Asset

Accounting.

If you are migrating from new General Ledger Accounting with active new Asset



Accounting - that is, you activated business function FIN_AA_PARALLEL with new

Asset Accounting in SAP enhancement package 7 for SAP ERP 6.0 SP02 - then you

have perform a smaller part of the migration of Customizing data.

Note:

o You cannot reverse documents that originated before the changeover from

classic to new Asset Accounting. Instead, you have to make an inverse posting.

o It may no longer be possible to process worklists that have been created before

the changeover to the new Asset Accounting. This involves worklists that create

transaction data (however, not master data changes), such as worklists for

retirement without revenue, retirement with revenue, intercompany asset

transfer, and impairment posting. You should therefore either process these

worklists before you activate the Customizing switch, or create them again once

you have activated new Asset Accounting in Smart Financials 1.0.

Regarding the restriction of transaction types to depreciation areas, note the

Postings release note. See release note Migration and New Customizing for

information about the new and changed Customizing settings.

Business Functions of Asset Accounting

The following business functions do not exist in Smart Financials. The functions

belonging to these business functions are, however, available, and you do not need to

activate them specifically (such as by using a Customizing switch):

o FI-AA, Asset Accounting (FIN_AA_CI_1), SAP enhancement package 6 for

SAP ERP 6.0

The following applies if you use different fiscal year variants with differing start

and/or end dates for your ledgers in General Ledger Accounting: As before, the

system only minimally supports the use of differing start and end dates of a fiscal

year. In Asset Accounting, you have to use a ledger group, the representative

ledger of which uses a fiscal year variant with a start and end date that is the

same as that of the leading ledger. As a workaround solution, you can assign an

additional ledger with a non-calendar fiscal year in the ledger group. You can use

this ledger for reporting. Note in connection with this that the restrictions

described in SAP Note 844029 remain in effect. If you have assigned different

fiscal year variants to your general ledger ledgers, you can only use them in new

Asset Accounting if you have assigned the appropriate fiscal year variant to the

depreciation areas that manage APC and post in real time.

o FI-AA, Parallel Valuation (FIN_AA_PARALLEL_VAL), SAP enhancement

package 7 for SAP ERP 6.0, SP02

User Interface

Implementation Guide

New Asset Accounting uses its own IMG structure in the SAP Reference IMG under

Financial Accounting (New): Asset Accounting (New). This IMG structure contains

some of the same activities as are in classic Asset Accounting, some changed

activities, and some new activities; a few of the classic Asset Accounting activities are

no longer contained in the Asset Accounting (New) IMG structure at all.

The Asset Accounting (New) IMG structure is based on the structure of new Asset

Accounting that is available with business function FIN_AA_PARALLEL starting from

SAP enhancement package 7 for SAP ERP 6.0 SP02.



Transactions

Some of the classic Asset Accounting transactions have been replaced by

corresponding new ones. So that you can make accounting-principle-specific postings,

the input fields Depreciation Area and Accounting Principle can be found on the

screen for the new transactions. The name of the relevant new transaction ends in "L".

Example: The previous transaction AB01 (Create Asset Transactions) is replaced by

the new transaction AB01L.

The new transactions are: AB01L, ABAAL, ABAKL, ABAOL, ABAVL, ABAWL,

ABCOL, ABGFL, ABGLL, ABIFL, ABMAL, ABMRL, ABNAL, ABNEL, ABNKL,

ABSOL, ABSTL, ABUML, ABZEL, ABZOL, ABZPL, ABZUL.

If you enter the transaction familiar from classic Asset Accounting (that does not end in

L), you are automatically transferred to the new transaction (that ends in L).

Transaction ABSO_OLD from classic Asset Accounting is no longer available in new

Asset Accounting; you can use transaction AB01L instead.

SAP Easy Access Menu

The SAP Easy Access Menu for new Asset Accounting remains the same as for classic

and new Asset Accounting. You can continue to find it under SAP Menu ->

Accounting -> Financial Accounting -> Fixed Assets .

The only difference is that you use it to access some new transactions (see the

explanation about transactions above).

Effects on Data Transfer

Programs for asset postings that supplied classic Asset Accounting with data using

batch input (for example, interfaces to non-SAP systems) can no longer be used (as

mentioned above). You have to change over these programs to the new BAPIs. See

the corresponding section in the Postings release note.


Prerequisites for New Asset Accounting under Smart Financials 1.0

For you to be able to use new Asset Accounting under Smart Financials 1.0, the

following prerequisites must be met:

o You have activated and configured the General Ledger Accounting (FI-GL)

(New) application component (either before the migration to Smart Financials, or

as a part of the migration to Smart Financials).

- To handle parallel accounting principles, use the ledger approach or the

accounts approach.

o You have activated the Financials Extension (EA-FIN) business function.

o As relates to Asset Accounting, one of the following is your starting situation:

- You have configured the classic Asset Accounting (FI-AA) application

component.

From the Financials Extension (EA-FIN), you use the new depreciation

calculation with the depreciation calculation program (DCP).

- Or: You are already using new Asset Accounting that is available with

business function FIN_AA_PARALLEL starting from SAP enhancement

package 7 for SAP ERP 6.0 SP02.

- Or: If you are not using either classic Asset Accounting or new Asset



Accounting, you need to make all of the necessary Customizing settings

for new Asset Accounting.

Prerequisites for the Migration to Asset Accounting (FI-AA) (new)

If you want to use new Asset Accounting, you are not allowed to use any of the

following components, business functions, or functions:

o Joint Venture Accounting (JVA)

You cannot activate new Asset Accounting in company codes in which JVA is

active, and the reverse is also true.

The business function JVA, Integration with New General Ledger Accounting

(JVA_GL_INTEGRATION)) is also not compatible with new Asset Accounting.

o From the Financials Extension (EA-FIN): Lease Accounting Engine (LAE)

The LAE controls postings for the lessor scenario; this scenario consists of the

components CRM Leasing (CRM-LAM) and Leasing Accounting (FI-LA).

o Real Estate (RE), that is, classic Real Estate Management

o From Funds Management (PSM-FM) or Industry-Specific Component Public

Sector (IS-PS): Requests with Reference to Asset

If you are already using classic Asset Accounting, the following additional prerequisites

also apply:

o Make sure that the periodic asset postings (with program RAPERB2000) are

completed.

o Also ensure that there are no update terminations from direct postings in the

system.

o Perform a complete period-end closing before the migration. Post the

depreciation (with the RAPOST2000 program), and reconcile your asset

accounting subsidiary ledger with the general ledger (with the RAABST02

program).

The following applies for all depreciation areas that post changes in APC and

depreciation to the general ledger with the "Area Posts in Realtime" indicator

(BUHBKT=1):

For the leading valuation of the ledger approach and accounts approach and for

parallel valuation 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 congruent. 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 can migrate to Smart

Financials 1.0. Contact your consultant.

Relationship of New Asset Accounting to Existing Business Functions

New Asset Accounting relates as follows to the business functions listed:

o CO, CO, Parallel Valuation of Cost of Goods Manufactured (FIN_CO_COGM),

SAP ERP 6.0 enhancement packages 5 and upwards

If this business function is active, you can also use different valuation for

investment measures according to different accounting principles. These

valuation approaches are activated for each depreciation area when you settle

investment measures for assets under construction (AUC) and for the full

settlement to completed assets, depending on the accounting principle. Differing

capitalization percentage rates from the Customizing activity for calculating the

capitalization value of investment measures (transaction OKGK) are taken into



account.

o Materials Management - Enhancements in Procurement (LOG_MM_CI_3),

SAP enhancement package 5 for SAP ERP 6.0

If you use purchase orders for low-value assets (LVA) in Asset Accounting, then

in the future it is not possible to note purchase orders if the LVA maximum

amount is exceeded. If you want to use the function for noting purchase orders,

we recommend that you activate the business function Materials Management -

Enhancements in Procurement (LOG_MM_CI_3).

Time of Migration to New Asset Accounting

You can migrate to new Asset Accounting in Smart Financials 1.01.0 at any point in

time.

The prerequisite is, however, that you have completed all periodic and current posting

processes that involve Asset Accounting. You must not make any postings during the

changeover. You should reconcile your asset accounting subsidiary ledger with the

general ledger.

We recommended that you carry out the changeover after period closing has been fully

completed.

If you also migrate from classic General Ledger Accounting to new General Ledger

Accounting as par of the migration to Smart Financials 1.0, then, at the time of the

changeover, you have to observe the rules for the migration to new General Ledger

Accounting.

See also

You can find the application documentation for new Asset Accounting in the new

structure Asset Accounting (New) in the SAP Library.



New Asset Accounting: Migration and Customizing (New)

Use

In Smart Financials 1.0, only new Asset Accounting is available. There are several

preparatory steps before you migrate from classic Asset Accounting to new Asset

Accounting. the migration of charts of depreciation and also new Customizing settings.

There are two possible starting situations: either you are migrating from classic Asset

Accounting or you have already activated the business function FI-AA, Parallel

Valuation (FIN_AA_PARALLEL_VAL) in SAP enhancement package 7 for SAP ERP

6.0. Depending on which applies for you, the migration to Smart Financials 1.0 involves

a different number of steps.

If you are also migrating from classic General Ledger Accounting to new General

Ledger Accounting, then there are additional steps that are explained separately in the

following.

All of the steps relevant for the migration are displayed in an overview below.

Application Customizing for new Asset Accounting can mainly be differentiated from

classic Asset Accounting in the following areas:

o Settings for depreciation areas

o Settings for posted transactions using integration

o Settings for transaction types

Settings in Customizing

To be able to use new Asset Accounting, you have to follow the steps below:

You can find details in the SAP Implementation Guide (IMG) under Financial

Accounting (New) -> Migration: Asset Accounting (New) -> Prepare New Asset

Accounting.

Check the Prerequisites Before Migrating to Smart Financials 1.0

Before you import Smart Financials 1.0 into your system, you have to follow these

steps if you have been using classic Asset Accounting.

1. Check the prerequisite for using Smart Financials 1.0 with new Asset

Accounting:

Import report RASFIN_MIGR_PRECHECK that is provided with SAP Note

1939592, and execute this report. For more information, see the documentation

for the report.

1. Perform a complete period-end closing in Asset Accounting in your system.

Ensure that there are no update terminations from direct postings in the system.

Migration of Customizing/Charts of Accounts to New Asset Accounting

Notes

If you were using new Asset Accounting with the ledger approach that you activated

with business function FI-AA, Parallel Valuation (FIN_AA_PARALLEL_VAL) with SAP

enhancement package 7 for SAP ERP 6.0 SP02 (EA-FIN 617 SP02), then steps 1, 2.1,

2.2, 2.3 are nonetheless mandatory.

1. After you import Smart Financials 1.0, the system shows the new IMG structure

Asset Accounting (New) in the SAP Reference IMG under Financial

Accounting (New). You use the new IMG structure Asset Accounting (New) to

set up and prepare the Customizing for new Asset Accounting in the client.



2. Start migration for new Asset Accounting (Customizing activity Migration for

New Asset Accounting):

For each valuation that is managed in the chart of depreciation, check the

existing accounting principles and create new ones, if necessary (in Customizing

under Financial Accounting (New) -> Financial Accounting Global Settings

(New) -> Ledgers -> Parallel Accounting -> Define Accounting Principles).

The following applies to the ledger approach: For each valuation that is managed

in the chart of depreciation, assign the accounting principles to ledger groups (in

Customizing under Financial Accounting (New) -> Financial Accounting

Global Settings (New) -> Ledgers -> Parallel Accounting -> Assign

Accounting Principle to Ledger Groups).

The following applies for the accounts approach: For each parallel valuation that

is managed in the chart of depreciation, the migration report generates a ledger

group for the leading ledger. For each valuation, the (generated) accounting

principle has to be assigned to the ledger group. If you want to have the system

generate the necessary ledger groups, then execute the migration report before

you perform this activity.

The other option is for you to create the ledger groups manually for the leading

ledger.

Convert charts of accounts, so that they meet the requirements of new Asset

Accounting with Smart Financials 1.0 (Customizing activity Migrate Charts of

Depreciation).

During this step, the system also determines whether the chart of depreciation

relates to the ledger approach or the accounts approach. Therefore, this step is

absolutely mandatory, even if new Asset Accounting was active in your system.

Check conversions made to the chart of depreciation. This concerns the

following activities:

- For the depreciation areas, the indicator for posting to the general ledger

was adjusted as needed (Customizing activity Integration with General

Ledger Accounting ->Define How Depreciation Areas Post to General

Ledger)

- An accounting principle (and ledger group) was assigned to all

depreciation areas (Customizing activity Integration with General Ledger

Accounting ->Define How Depreciation Areas Post to General

Ledger)

- Check and adjust names of accounting principles (Customizing activity

Financial Accounting (New) -> Financial Accounting Global Settings

(New) -> Ledgers -> Parallel Accounting -> Define Accounting

Principles.

- Check and adjust names of ledger groups (Customizing activity Financial

Accounting (New) -> Financial Accounting Global Settings (New) ->

Ledgers -> Parallel Accounting -> Define Accounting Principles.

- The transfer of APC values was adjusted as needed (Customizing activity

Valuation -> Depreciation Areas -> Specify Transfer of APC Values)

- The transfer of depreciation terms was adjusted as needed (Customizing

activity Valuation -> Depreciation Areas -> Specify Transfer of

Depreciation Terms)

- An indicator was set internally for each chart of depreciation for whether it

is for the ledger approach or the accounts approach.



If it is not possible to migrate the chart of depreciation manually, or you want to

migrate it manually, then you can make the conversion manually (perform the

substeps listed above).

1. Manual steps: Make the Customizing settings (application Customizing) for new

Asset Accounting (Customizing activity Migration: Asset Accounting (New) ->

Migration for New Asset Accounting ->Perform Additional Manual

Activities).

2. Execute Customizing activity Check Prerequisites for Activating Asset

Accounting (New).

3. Activate the Customizing switch (Customizing activity Activate New Asset

Accounting)

4. In the production system:

a) Lock the production system for postings.

b) Check the prerequisites. (See section "Check Prerequisites for Changing

to Smart Financials 1.0")

5. Import the new Customizing settings into your production system.

6. Check in the production system whether the transport successfully imported the

activated Customizing switch.

7. Unlock the production system for postings.

About 2) Start migration/conversion for new Asset Accounting: define

depreciation areas.

An accounting principle (and ledger group) are assigned to each depreciation area,

even to the non-posting depreciation areas. The following applies for each set of

depreciation areas, to which the same accounting principle is assigned (that is, for each

valuation):

o Ledger approach: Only one depreciation area is allowed to manage acquisition

and production costs (APC) and at the same time have the Area Posts in

Realtime indicator set for it. This applies both for the leading valuation and for

parallel valuations.

o Accounts approach: Only one depreciation area is allowed to manage acquisition

and production costs (APC) and (1) have the Area Posts in Realtime indicator

set for the leading valuation or (2) have the Area Posts APC Realtime and

Depreciation (or instead Area Posts APC Periodically and Depreciation).

The asset values are updated at the full value in accordance with the relevant

accounting principle. For each accounting principle, this results in a complete and

independent view of the asset values with the respective valuation. An additional

derived depreciation area for each accounting principle (and currency and valuation),

meaning a delta area, is no longer required for a parallel valuation of asset balances.

About 3) Manual steps: Make the Customizing settings (application Customizing)

for new Asset Accounting.

You make the Customizing settings for new Asset Accounting in Customizing under

Financial Accounting (New) -> Asset Accounting (New). The settings apply in the

given client.



If you have already been using new General Ledger Accounting with classic Asset

Accounting, then you only have to make settings for the new and changed functions.

These include:

1. Define depreciation area for quantity update (if necessary)

2. Define technical clearing account for acquisitions (mandatory, if posted using

integration).

3. Specify alternative document type for accounting-principle-specific documents (if

posted using integration and document splitting is active).

4. Check transaction types (mandatory).

5. Check, and if necessary adapt, revenue distribution for asset acquisition (by net

book value or APC).

6. Retirement posting with net book value: Restriction to specific depreciation areas

(mandatory, if you are using this posting logic)

7. The following applies in addition for the accounts approach: For depreciation

areas that represent the parallel valuation, you have to enter reconciliation

accounts for the acquisition and production costs (APC) and accumulated

depreciation accounts.

For details on these activities, see Customizing for Asset Accounting (New) under

Migration: Asset Accounting (New) -> Migration for New Asset Accounting -

>Perform Additional Manual Activities.

If you were using classic General Ledger Accounting with new Asset Accounting, you

have to perform the following steps so that the integration between Asset Accounting

and new General Ledger Accounting is implemented fully:

1. Specify addition account assignment objects that are relevant when posting an

asset transaction. This applies both for APC postings as well as for the

depreciation run.

2. Check document splitting (in Customizing for General Ledger Accounting

(New))

3. Define post-capitalization of discounts on assets (in Customizing for General

Ledger Accounting (New)).


See the corresponding section in the central release note for new Asset Accounting

New Asset Accounting: Ledger Approach and Accounts Approach.

See also

For more information, see:

o The central release note for new Asset Accounting New Asset Accounting:

Ledger Approach and Accounts Approach..

o SAP Library under Asset Accounting (New)



New Asset Accounting: Postings (New)

Use

Using Smart Financials 1.0, you can use the new functions for postings both for the

ledger approach and for the accounts approach.

In a new Asset Accounting posting transaction, the system creates a document for

each accounting principle in the general ledger.

Parallel Valuation in Realtime

For each asset-related transaction (acquisition, capitalization of assets under

construction (AUC), retirement, post-capitalization and so on), the asset values for all

posting depreciation areas are updated in realtime. Periodic APC values posting is

consequently now only required for special depreciation areas.

Separate Document for each Valuation

Different accounting principles or valuations are represented - as in new General

Ledger Accounting - in separate ledgers (for the ledger approach) or in a separate set

of accounts (for the accounts approach).

The depreciation areas have equal status. Separate accounting-principle-specific

documents are posted for each accounting principle or valuation.

A business transaction created using integration is split by the system into the

operational part and the valuating part. A posting is made in each case against a

technical clearing account. For the asset acquisition using integration you require a

new technical clearing account for integrated asset acquisition; however, for the

asset retirement using integration the existing clearing accounts asset retirement with

revenue and asset retirement clearing are used. The operational part is posted

across accounting principles, the valuating part is posted accounting-principle-

specifically.

For more information, see the Transactions with Integrated Posting release note.

Entry of Value Differences for Each Depreciation Area or Accounting Principle

(Ledger Group).

Value differences for each accounting principle or depreciation area can be entered in

a separate transaction (AB01L) for an asset acquisition, a post-capitalization, and a

manual depreciation or write up. This has the following consequences:

o It is no longer necessary to restrict the transaction types to individual

depreciation areas (see below).

o User exit APCF_DIFFERENT_AMOUNTS_GET is no longer supported.

Entry of a Business Transaction

Using the appropriate fields, you can restrict the posting to an accounting principle and

depreciation areas, or limit it to certain areas using the selection of a depreciation area.

When you make the entry, the system always uses the last confirmed entry (limit) for

the posting.



In addition, you can adjust the line items of particular depreciation areas for certain

transactions using the Change Line Items function. If you have changed basic fields

(such as account principle, depreciation areas, posting amount), the line items are

genrated again.

A business transaction is always entered in local currency. If you limit the posting to

one or more depreciation areas in the same foreign currency, then the entry (and

posting) is made in this foreign currency. If you select depreciation areas to which

differing foreign currencies are assigned and no depreciation area was selected in local

currency, the system issues an error message; you have to enter several postings for a

business transaction like this.

Unilateral Assets

Depending on the legal requirements, it may be necessary to manage a fixed asset in

one accounting principle (such as local valuation) as an asset, but in a different

accounting principle (for example, IFRS) not to manage it as an asset, but post the

costs directly to profit and loss instead. You can map these differing capitalization rules

in new Asset Accounting using 'unilateral' assets.

Transaction Types

In new Asset Accounting, it is not possible and also not necessary to restrict

transaction types to depreciation areas. This is not necessary since, when you enter a

transaction, you can restrict it to a depreciation area or accounting principle. In addition,

in a posting transaction, you can select the depreciation areas to be posted. This can

significantly reduce the number of transaction types that need to be defined in the

system.

If you nonetheless have migrated transaction types that are restricted to depreciation

areas (table TABWA or view cluster V_TABWA), this is rejected by the system.

Investment support and also revaluation and new valution are an exception:

o The transaction types for investment support and revaluation are automatically

generated by the system when you create a corresponding measure, and

therefore are restricted to the depreciation area to be posted to.

o The transaction types for revaluation and new valuation that relate to transaction

type group 81/82/89 can continue to be restricted to depreciation areas.

Post-Capitalization

You enter post-capitalization both gross and net in the same transaction (transaction

ABNAL). The system always calculates the depreciation values, meaning in the

standard system it assumes that you are entering gross values. If you want to enter the

post-capitalization net, you have to specify the net amount in the transaction, and reset

the depreciation values in the line items.

Revaluation

A revaluation is always posted accounting principle-specific. The Accounting

Principle field in transaction ABAWL is therefore a required entry field.



Document Display

A business transaction is split (1) into an operational part that creates an accounting-

principle-independent or ledger-group-independent document and (2) into a valuating

part that creates an accounting-principle-specific/ledger-group-specific document for

each valuation. Several documents are posted, therefore. These documents are

displayed together in the document display. The system displays the complete

business transaction in accordance with a valuation that you have selected.

Example: With an integrated asset acquistion posted, both the operational part (debit

technical clearing account for integrated asset acquisition, credit vendor (ledger group

INITIAL) and also the valuating part (debit asset, credit technical clearing account for

integrated asset acquisitions) (accounting principle XY) are displayed together in the

Asset Accounting document display.

If a business transaction in Asset Accounting is not entered using integration, then only

the valuating documents are posted by the entry. For each valuation that an asset

manages, a valuation-specific document is created.

For each valuation, an accounting-principle-specific document is displayed in the

document display. The operational document is not linked with the valuating document,

and therefore cannot also be displayed.

This document display in Asset Accounting is available in both document simulation

and in the document display. You can switch the view between the individual valuations

(choose the Change Accounting Principle pushbutton) and between the currency

types (choose the Change Display Currency pushbutton).

Asset Explorer

In the navigation area, the depreciation areas of the relevant assignment are displayed

grouped according to accounting principles. The accounting principle with the leading

ledger ("group view") appears uppermost.

Reconciliation with the General Ledger

For the reconciliation of Asset Accounting with General Ledger Accounting, program

Consistency Check of General Ledger and Asset Accounting (RAFABST01) is

available in classic Asset Accounting. In new Asset Accounting, this has been replaced

by program Consistency Check for FI-AA (New) and FI-GL (New) (FAA_GL_RECON).

From transaction ABST (program RFABST01) the system branches to transaction

ABSTL (program FAA_GL_RECON); the same applies for the menu option in the SAP

Easy Access menu.

BAPIs

Changed BAPIs

In the BAPIs that already existed in classic Asset Accounting, the fields Accounting

Principle/Ledger Group and Depreciation Area have been added. You are only

allowed to fill these fields if the Customizing switch for new Asset Accounting is active.

The following BAPIs from classic Asset Accounting have been adapted for new Asset

Accounting:



Business Object:

Short Description

Business Object:

Object Name

Function Modules

Asset Acquisition AssetAcquisition BAPI_ASSET_ACQUISITION_CHECK,

BAPI_ASSET_ACQUISITION_POST

Asset Retirement AssetRetirement BAPI_ASSET_RETIREMENT_CHECK,

BAPI_ASSET_RETIREMENT_POST

Asset Post-

Capitalization

AssetPostCapitaliztn BAPI_ASSET_POSTCAP_CHECK,

BAPI_ASSET_POSTCAP_POST

Asset Document

Reversal

AssetReversalDoc BAPI_ASSET_REVERSAL_CHECK,

BAPI_ASSET_REVERSAL_POST

New BAPIs

There are the following new BAPIs:

Business

Object: Short

Description

Business Object:

Object Name

Function Modules

Assets: Down

Payment

AssetDownPayment BAPI_ASSET_DOWNPAYMENT_CHECK,

BAPI_ASSET_DOWNPAYMENT_POST

Assets:

Investment

Support

AssetInvestSupport BAPI_ASSET_INV_SUPPORT_CHECK,

BAPI_ASSET_INV_SUPPORT_POST

Assets:

Revaluation

AssetRevaluation BAPI_ASSET_REVALUATION_CHECK,

BAPI_ASSET_REVALUATION_POST

Assets:

Subsequent

Costs and

Revenues

AssetSubCostRev BAPI_ASSET_SUB_COST_REV_CHECK,

BAPI_ASSET_SUB_COST_REV_POST



Assets: Transfer AssetTransfer BAPI_ASSET_TRANSFER_CHECK,

BAPI_ASSET_TRANSFER_POST

Assets:

Depreciation

AssetValueAdjust BAPI_ASSET_VALUE_ADJUST_CHECK,

BAPI_ASSET_VALUE_ADJUST_POST

Assets: Write-Up AssetWriteUp BAPI_ASSET_WRITEUP_CHECK,

BAPI_ASSET_WRITEUP_POST





The following changes apply for Customizing, if you have been using classic Asset

Accounting up to now.

Transaction Types

Customizing for restricting transaction types to depreciation areas is - aside from the

above exceptions - now completely superfluous. Therefore the activites for this are no

longer included in the Asset Accounting (New) IMG structure. The exceptions to this

rule are the Customizing activities for investment support, revaluation and

revaluation/new valuation.

Default Transaction Types for Down Payments

Default transaction types for down payments are no longer defined in Customizing

activity Determine Transaction Types for Internal Transactions (table TABWV) as

previously the case, but in Customizing activity Specify Default Transaction Types

(table TABWD). The system moves existing entries.

Retirement: Distribute the proportional value percentage rate to prior-year asset

acquisitions and current-year acquisitions

If you have been using user exit AFAR0004 to date, you have to move your

enhancement to the following BAdI methods: BAdI: FAA_DC_CUSTOMER, method

PROPVAL_PERCENT_ON_SPECIAL_RET. You can copy the code from the user exit 1:1

when doing so, since the enhancement interface has not been changed.

Retirement: Posting with net book value

If up to now you have been using the "Post Net Book Value at Retirement" logic, note

the following: The restriction of posting logic to certain depreciation areas is done in

classic Asset Accounting using area types (as set out in SAP Note 1069166). In new

Asset Accounting, this setting is replaced by the new Customizing activity Post Net

Book Value Instead of Gain/Loss -> Subactivity Specify Depreciation Areas for

Net Book Value Posting.



Standard Layout for Document Display

There is the following standard layout for the document display in new Asset

Accounting: Standard: Asset Accounting (New) (3SAP).

We recommend that you use this standard layout or a copy of it adapted to meet your

requirements, since the layout supports you in interpreting the accounting-principle-

specific documents.

See also



Ledger Approach and Accounts Approach.




New Asset Accounting: Transactions with Integrated Postings (New)

Use

As of Smart Financials 1.0, you can use parallel valuation for integrated postings in

new Asset Accounting.

For the following transactions, the integrated posting is made to a special clearing

account:

o Asset acquisition and

o Investment support measures

A business transaction posted using integration (such as an asset purchase from a

vendor or an asset sale to a customer) is split by the system into an operational part

and a valuating part. An accounting-principle-independent document is created in the

operational part. An accounting-principle-specific document is created for the valuating

part for each valuation that is managed for the asset. Asset balances are only updated

to specific accounting principles.

Example (acquisition)

You create financial statements in accordance with both IFRS and a local accounting

principle. In new General Ledger Accounting, you have set up the appropriate

accounting principles (accounting principle IFRS and accounting principle LGAAP) and

assigned ledger groups. In new Asset Accounting, you have set up the appropriate

depreciation areas.

Warning

For technical reasons, you also have to create ledger groups in the accounts approach

and assign them to accounting principles. Since no general ledgers are required for

representing parallel valuation and none are configured, these ledger groups contain

only the ledger 0L.

An asset acquisition is created in an integrated posting.

Document entry:

Dr 70 A Asset Tech. clearing account for acquisition 10,000 Cost center 1

Cr 31 K Vendor Payables from L+ L 10,000

Document creation and posting:

The system generates the following three documents:

(1) Ledger group INITIAL (that is, without specifying a ledger group)

Dr 70 Tech. clearing account for acquisition 10,000 Profit center 1

Cr 31 Payables from L+ L 10,000 Profit center 1

(2) Ledger group IFRS

Dr 70 Equipment 10,000 Profit center 1

Cr 75 Tech. clearing account for acquisition 10,000 Profit center 1

(3) Ledger group LGAAP

Dr 70 Equipment 10,000 Profit center 1



Cr 75 Tech. clearing account for acquisition 10,000 Profit center 1

Explanation:

o Any valuation differences that could arise during the activation, are not taken

into account in the example. They can be entered by a separate, accounting-

principle-specific or depreciation-area-specific posting.

o The profit center assigned to cost center 1 is updated for the integrated

acquisition both in the fixed assets accounts and in the Technical Clearing

Account for Integrated Asset Acquisition

o The new Technical Clearing Account for Integrated Asset Acquisition

always displays a balance of zero at the level of the accounting principle and

additional account assignment (profit center), due to technical reasons. Open

item management is neither necessary nor supported. You are not allowed to

make manual postings to the account. The account is displayed in the balance

sheet attachment. In order to ensure a balance of zero also for postings in a

foreign currency, the system also updates the asset items of the generated FI

documents in the foreign currency, in the case of an integrated posting.

o With the accounts approach for parallel accounting, the asset documents for

integrated asset acquisition or retirement are updated in the local currency, but

not in the foreign currency. Instead the foreign currency amounts remain zero.

Example

Document entry:

Dr 70 A Asset Tech. clearing account for

acquisition

CNY

10,000

Cost center

1

Cr 31 K Vendor Payables from L+ L CNY

10,000

Document creation and posting:

The system generates the following three documents:

(1) Ledger group INITIAL (that is, without specifying a ledger group)

Dr 70 Tech. clearing account for acquisition CNY 10,000 Profit center 1

Cr 31 Payables from L+ L CNY 10,000 Profit center 1

(2) Ledger group IFRS

Dr 70 Equipment CNY 0.00 Profit center 1

Cr 75 Tech. clearing account for acquisition CNY 0.00 Profit center 1

(3) Ledger group LGAAP

Dr 70 Equipment CNY 0.00 Profit center 1

Cr 75 Tech. clearing account for acquisition CNY 0.00 Profit center 1







You create at least one Technical Clearing Account for Integrated Asset

Acquisition, and define this in Customizing for Asset Accounting (New) under

Integration with the General Ledger -> Define Technical Clearing Account for

Integrated Asset Acquisition.

If you require different field control behavior depending on the asset balance sheet

account to be posted or on the given business transaction (acquisition APC or

investment support), you have to reflect this using different technical clearing

accounts for integrated asset acquisition. You make the relevant settings under

Define Different Technical Clearing Account for Required Field Control.

See also



Ledger Approach and Accounts Approach.




Financial Supply Chain Management (FSCM)

FIN-FSCM-CLM: Business Function SAP Smart Cash Management (New)

Use

As of Smart Financials package 1.0 (SAP_FIN 700), the business function SAP Smart

Cash Management is available. With this business function, SAP Smart Cash

Management provides the following new features, which are not available in the old

Cash and Liquidity Management:

o Bank Account Management

o Cash Position and Short-Term Cash Forecast

o Embedded Liquidity Planning

o Cash flow and liquidity forecast calculation powered by SAP HANA

o New user experiences with the NetWeaver Business Client (NWBC)

o A pre-defined PFCG role for cash managers (SAP_SFIN_CASH_MANAGER)

Bank Account Management

With Bank Account Management, customers in Cash or Treasury departments are able

to centralize the management of bank accounts by using the following features.

o Hierarchy view and table view of bank and bank accounts

o A new bank account master data that supports

- Common properties of bank accounts

- Signatories for payments approvals

- Overdraft limits

o Workflow process for opening, closing, or changing bank account master records

o Periodic bank account review process

o Status monitor for bank statement imports (only available with the Bank

Communication Management component enabled)

Cash Position and Short-Term Cash Forecast

With the new Cash Position and Short-Term Cash Forecast report, you are able to:

o View cash position and short-term cash forecast based on bank statements,

payment documents, memo records, and TRM deals (money market and FX).

o Customize the report by using the WebDynpro FPM and the embedded BEx

queries.

Embedded Liquidity Planning

With the embedded liquidity planning, you are able to conduct daily or monthly liquidity

planning by liquidity item, bank account, planning level, or other dimensions.

The following data can be embedded into your liquidity planning as reference data to

help you create liquidity plans and make variance analysis:

o Cash position

o Actual cash flow



o Forecasted cash flow


Database tables of the old Cash and Liquidity Management are no longer used.

Therefore, there is no need to migrate existing Cash and Liquidity Management data.

However, you may need to perform the following actions in order to prepare the

existing data for the new calculation logic:

Cash Position and Short Term Cash Forecast

o Cash position gets the data from accounting document line item table directly.

The accounting document line item table is enhanced with an additional field

Flow Type.

o To use the report, you must complete the necessary configuration and execute

the rebuild tool (transaction FQM_UPD_FLOW_TYPE) to fill the flow type for

accounting document line items.

o To include TRM deals in Exposure Hub into calculation, you must build the

existing TRM deal information into Exposure Hub. To do this, execute the initial

load tool (transaction FQM_INITIALIZE).

Bank Account Management

Bank account master data works together with the house bank account data in the

Bank Master Data (FI-BL-MD) component. You can generate bank account master

data and assign house bank accounts by using the following transactions:

o Migrate house bank accounts (transaction FCLM_BAM_MIGRATION)

o Manually assign house bank accounts (transaction FCLM_BAM_ACCLINK)


Customizing activities and Business Add-Ins (BAdIs) are placed under Financial

Supply Chain Management -> Cash and Liquidity Management.

See also

o FIN_FSCM_CLM: BI Content



FIN-FSCM-CLM: Local BI Content for SAP Smart Cash Management (New)

Use

As of Smart Financials package1.0 (SAP_FIN 700), you can configure or enhance the

following local BI objects according to your business needs for SAP Smart Cash

Management.

To view the BI content predefined by SAP, in transaction RSA1, choose InfoPackage

Financial Management & Controlling (/ERP/FMCO) -> Cash & Liquidity

Management (/ERP/FCLM).

Virtual InfoProviders

The following Virtual InfoProviders are based on HANA Views:

o Cash Position (/ERP/FC_VP06): calculates balance amounts of bank accounts.

o Cash Flow and Short Term Cash Forecast (/ERP/FC_VP07): provides short-term

cash flow and cash forecast based on the payments on the bank clearing

accounts, memo records, and forecast from TRM deals (FX and Money Market).

o Cash Flow Analysis (At Bank Clearing Level) (/ERP/FC_VP01): analyzes actual

cash flows based on the payments on the bank clearing G/L accounts and

derives liquidity items.

o Cash Flow Analysis (At Invoice Level) (/ERP/FC_VP09): analyzes actual cash

flows based on the invoices and derives liquidity items.

o Liquidity Forecast (ERP/FC_VP04): forecasts cash flows based on the open

items at invoice level and derives liquidity items accordingly.

o Liquidity Forecast (Light Version) (ERP/FC_VP05): forecasts cash flows based

on the open items of bank clearing G/L accounts and derives liquidity items

accordingly.

o Bank Account Overdraft Limit (/ERP/FC_VP92): retrieves the overdraft limit

amounts of bank accounts from the bank account master data.

ODPs

o 0FCLM_CP_REAL_ITEM

- ODP ID: 0FCLM_CP_RLI

This ODP provides the line item details can be used in the Cash Position

and Short Term Forecast report.

o 0FCLM_CP_BS_IMP_CMP

- ODP ID: 0FCLM_CP_BIC

This ODP monitors the status of bank statement imports on bank or bank

group level. You can only use it together with the Bank Account

Management component.

Planning Real-Time Cubes & Aggregation Levels

o Planning Real-Time InfoCube

Liquidity Planning Cube (/ERP/FC_IC04): stores the results of liquidity planning.

o Aggregation Level

- Monthly Planning (/ERP/FC_AL06): provides aggregation level to monthly

planning.



- Planning by Liquidity Item (/ERP/FC_AL05): provides aggregation level to

daily planning by liquidity item.

- Planning by Planning Level (/ERP/FC_AL07): provides aggregation level

to daily planning by planning level.

- Planning by Liquidity Item and Bank Account (/ERP/FC_AL08): provides

aggregation level to daily planning by liquidity item and bank account.

MultiProvider

o Planning & Forecast & Actual (/ERP/FC_MP05): combines planned data,

forecast data, and actual data all together, allowing you to define queries with all

the relevant information together.

BEx Queries

The following BEx queries are based on ODPs:

o Cash Position Line Item (FCLM_CP_LIT_Q1001): defined on ODP

0FCLM_CP_REAL_ITEM.

o Bank Statement Import: Status (Tree) (FCLM_CP_BIC_Q1001): defined on ODP

0FCLM_CP_BS_IMP_CMP.

o Bank Statement Import: Status (Table) (FCLM_CP_BIC_Q1002): defined on

ODP 0FCLM_CP_BS_IMP_CMP.

The following BEx queries are based on MultiProvider:

o Planning & Forecast & Actual (/ERP/FC_MP05)

o Cash Position and Short-Term Cash Forecast (/ERP/FCLM_MP05_Q0003)

o Cash Flow Analysis (/ERP/FCLM_MP05_Q0021)

o Liquidity Forecast (/ERP/FCLM_MP05_Q0020)

o Monthly Planning by Liquidity Item (/ERP/FCLM_MP05_Q0001): input query for

monthly planning.

o Monthly Variance Report by Liquidity Item (/ERP/FCLM_MP05_Q0002):

analyzes the monthly variances between actual, planning, and forecast data by

liquidity item.

o Monthly Variance Overview (/ERP/FCLM_MP05_Q0005): analyzes the monthly

variances between actual, planning, and forecast data.

o Cash Position (/ERP/FCLM_MP05_Q0003): provides data for the Cash Position

and Short-Term Cash Forecast report.

o Daily Planning by Planning Level (/ERP/FCLM_MP05_Q0009): input query for

daily planning by planning level.

o Daily Variance by Planning Level (/ERP/FCLM_MP05_Q0008): analyzes the

daily variances between the actual and the planning data by planning level.

o Daily Planning by Liquidity Item (/ERP/FCLM_MP05_Q0006): input query for

daily planning by liquidity item.

o Daily Variance by Liquidity Item (/ERP/FCLM_MP05_Q0007): analyzes the daily

variances between actual, planning, and forecast data by liquidity item.


You can copy the corresponding objects out, and make adjustments as needed.



See also

FIN-FSCM-CLM: Business Function Cash and Liquidity Management



Controlling (CO)

Line Item Based Controlling with Period Close Optimizations (Enhanced)

Use

As of Smart Financials package 1.0, period close and reporting processes in

profitability and cost analysis are based on line items rather than persistent aggregates.

Complex calculations that are performed at period close, for example, the calculation of

work in process at actual costs, determination of production variances for production

orders, and results analysis for sales orders, are pushed down to the SAP HANA

database in order to accelerate the close. In addition the selection of the relevant data

for period close processes such as overhead calculation and settlement has been

adjusted to take advantage of the SAP HANA database in-memory capabilities.

Reporting uses a logical document that links the financial accounting (FI) line item, the

CO line item, and the CO-PA dimensions (where available) to provide an income

statement broken down by market segments.

The profit and loss planning process brings financial accounting (FI) and management

accounting (CO) together. This allows target setting by company code and profit center

with an automated disaggregation to the associated cost objects, detailed planning by

cost center, order, project, and CO-PA dimensions with the ability to automatically roll

this data up to the higher level. The ability to aggregate and disaggregate data quickly

makes it possible to perform simulations and forecasting much faster than was

previously possible.


Changes that affect existing data include the following:

o Line item tables are extended to provide a connection between CO and FI.

o Period close processes are adjusted to read line items rather than totals tables.

o The following tables have been replaced by views:

- CO Object: Cost Totals for Internal Postings (COSS)

- CO Object: Cost Totals for External Postings (COSP)

The advantage of this change is that you no longer have to store redundant data,

thus saving space on your database. You can still use reports that read from the

database, including your own reports.

o For SAP HANA in-memory optimizations, new transactions have been created to

support certain standard scenarios in results analysis for sales orders, variance

calculation, and work in process calculation at actual costs. This can mean that

some existing Customizing options are not supported.


There are new period close transactions for results analysis for sales orders, variance

calculation, and work in process calculation at actual costs.

You must adjust the close schedule to include new jobs.


The following roles are delivered with Smart Financials and you can change these as

required:



o Cost Center Manager (SAP_CO_COSTCENTER_MANAGER)

o Project Planner and Cost Estimator (SAP_CO_PROJECT_PLANNER)

o Internal Controller (SAP_CO_INTERNAL_CONTROLLER)

o SFIN Accounting: Actual Costing (SAP_SFIN_ACC_ACTUAL_COSTING)

o SFIN Accounting: Actual Postings (SAP_SFIN_ACC_ACTUAL_POSTINGS)

o SFIN Accounting: Budgeting (SAP_SFIN_ACC_BUDGETING)

o SFIN Accounting: Capital Investment Management

(SAP_SFIN_ACC_CAP_INVEST)

o SFIN Accounting: Closing (SAP_SFIN_ACC_CLOSING)

o SFIN Accounting: Master Data (SAP_SFIN_ACC_MASTERDATA)

o SFIN Accounting: Planning (SAP_SFIN_ACC_PLANNING)

o SFIN Accounting: Product Cost Planning (SAP_SFIN_ACC_PRODUCT_COST)

o SFIN Accounting: Reporting (SAP_SFIN_ACC_REPORTING)

To take full advantage of the SAP HANA in-memory architecture, you should adjust

your assessment cycles and settlement rules to ensure they are working with account-

based profitability analysis. You can do this in Customizing for Controlling under

Profitability Analysis, Flows of Actual Values.

You need to configure the new accounts for cost of goods sold and the cost

components that determine the breakdown of these costs.

To take best advantage of the SAP HANA in-memory selection capabilities, you must

create selection variants in the Customizing activity Create Selection Variants for Projects and WBS Elements.

See also

Planning (New)



Variance Calculation for Cost Centers (Changed)

Use

As of Smart Financials package 1.0, variances are calculated on cost centers with

transaction code KSS1H.

Note that not all messages related to the splitting rule will be logged.

Accelerated collective variance calculation is supported for cost centers and cost center

groups at period-end closing. The calculated variances are assigned to variance

categories.

The following scenarios are supported:

o Variance calculation for cost centers with one or more activities

o The fiscal year variant matches the month of the calendar year

To improve performance, you can now choose whether you want to process the

controlling area currency only or both the controlling area currency and the cost object

currency. The execution time for processing the controlling area currency only is

around half that required for processing the controlling area currency and object

currency.


You need to check your Customizing settings and ensure that they are adapted for the

new variance calculation transaction. For detailed information see below under Effects

on Customizing.

To ensure that the splitting logic works correctly, you also need to maintain at least one

activity in the cost center for plan activity quantity or planned capacity with the Activity

Type/Price Planning transaction (KP26).


The following Customizing activities need to be carried out to enable variance

calculation for cost centers:

o Define Activity Type Master Data

In the activity type master data, predistribution of fixed costs is not supported for

sender cost centers.

o Define Actual price calculation: Determination method

In the tab of price calculation in Settings for Each Fiscal Year, the actual method

should be set as Periodic price.

o Define Splitting Structures

Note the following:

- In the assignments of the splitting structure configuration, multiple splitting

assignments are not supported.

- In the Selection for assignment, Group is not supported.

- In the splitting rules, only splitting methods 12, 21, 22, 23, 24, and 25 are



supported. The Weighting indicator is not supported.

- In the selection for splitting rules configuration, version 0 is supported.

o Primary Data for Input Price Variances

Primary price variances are not supported.

o Define Variance Variants

Minor differences are not supported.

o Fiscal Year Variant

The fiscal year variant must match the month of the calendar year.



WIP Calculation and Results Analysis (Changed)

Use

As of Smart Financials package 1.0, the functionality and transaction codes for the

calculation of WIP and results analysis have changed.

o WIP Calculation

Transaction: KKAOH

This transaction values production orders only. The production orders are valued

at actual cost for the selected plant with the defined legal valuation for a single

result analysis version. Customer enhancement and WIP calculation for product

cost collectors and process orders are not supported. Multiple valuation is not

supported.

In contrast to the classic transaction code for WIP calculation KKAO, the options

With Product Cost Collectors, With Process Orders, and All RA Versions

cannot be selected since the corresponding functionality is not available.

You can therefore select only With Production Orders, and you can only

specify one results analysis version.

o Results Analysis

Transaction: KKAKH

Only the following results analysis methods are supported:

- Revenue-based results analysis (method 01)

All costs that cannot be directly assigned to the revenue are treated as

work in progress until the contract is completed. Reserves may be created

if the costs are not sufficient to match the revenue.

- Cost-based results analysis based on the percentage of completion

(method 03)

Revenue is calculated in accordance with the percentage of costs

incurred. A balance sheet posting is created for revenue in excess of

billings. A revenue surplus (a type of reserve) may be created if billings

are higher than the percentage of completion indicates to be appropriate.

Customer enhancement and the other 15 methods are not supported.

Expert Mode is partially supported.

The KKAKH front end is the same as with the classic transaction KKAK.


Customizing activities are affected as follows.

WIP Calculation KKAOH



o Define Result Analysis Versions

KKAOH only supports results analysis versions that are defined for legal

valuation.

Multiple valuation is not supported.

Extended Control:

- KKAOH supports the options Generate Line Items, Assignment/RA Key,

and Update/RA Key. The other checkboxes are not supported.

- The subtab Calculate WIP or Result Analysis For is supported.

Planned Results Analysis is not supported.

Cost Elements: Only the Cost Elements: Result Analysis Data group is

supported. The other groups are not supported.

o Define Valuation Method (Actual Cost)

Work in process at actual costs functions as follows:

a) For the status PREL, the status number is "1" (the order is partially

released). For the status REL, the status number is "2"(the order is

released).

The system creates work in process in the amount of the actual costs with

which the order is debited.

a) For the status DLV, the status number is "3" (the order has been

completely delivered). For the status TECO, the status number is "4"(the

order is technically completed).

The system cancels the work in process. The difference between the debit

through actual costs postings and the actual credit of the order from goods

receipts is interpreted as a variance with this status.

o Define Line IDs SPRO

The work in process and reserves for unrealized costs are calculated as a total

for each order and distributed to the line IDs.

The line IDs divide the costs incurred for the order into specific groups, such as

direct material costs, production costs, and indirect costs.

o Assignment of Cost Elements for WIP and Result Analysis

KKAOH only supports the following configuration:

- Only the ReqToCap column (requirement to capitalize) is supported.

- The columns Debit/Credit Indicator, Vble/Fixed Indicator, and

Accounting Indicator must be marked as "+" (all).

o Update of WIP Calculation and Results Analysis



The ApptNo UM field (Capitalized Costs Apportionment Number) is not

supported. Hence WIP apportionment to line IDs is not supported.

o Posting Rules in WIP Calculation and Results Analysis

KKAOH calculates WIP at actual cost, but doesn't include the CO88 settlement

function. If you want to speed up settlement, you can use CO88H.

Two basic situations will determine different accounts based on posting rules:

- WIP greater than 0: WIPR (WIP with requirement to capitalize)

- WIP less than 0: RUCR (reserves for unrealized costs)

Result Analysis KKAKH

o Define Result Analysis Versions

KKAKH only supports results analysis versions that are defined for legal

valuation. Multiple valuation is not supported.

Extended Control:

- Checkboxes supported: Generate Line Items, Assignment/RA Key,

Update/RA Key.

- Checkboxes not supported: Split Creation/Usage, Legacy Data

Transfer, Deletion Allowed, Update Plan Values. Thus if you select one

of these options when running KKAKH, an error message will be issued.

The sub-tab Calculate WIP or Result Analysis For is supported. Status control

A, B and blank are supported. We recommend status control B for better

performance when running KKAKH.

Planned Results Analysis is not supported.

Cost Elements: All accounts are supported.

o Define Valuation Method (Actual Cost)

Result Analysis for sales orders functions as follows:

Currently, two commonly used methods 01 and 03 are supported with standard

mode. Expert mode is partially supported.

Be aware of the detailed settings of that part of Expert Mode that is supported:

- Profit Indicator

Only M and Q are supported as the profit indicator.

If the Result Analysis Method is 01: Revenue- based method, for each

status, the RA type E: Revenue-Based Results Analysis and Profit

Indicator M: With Profit Realization are supported.

If the Result Analysis Method is 03: Cost-based results analysis, the RA



type E: Revenue-Based Results Analysis and the Profit Indicator Q:

Percentage-of-Completion are supported.

Valuation:

- Plan Version

Only plan version 0 is supported.

Note that for sales order items, you always plan the costs in plan version

0. If you want to execute results analysis on sales order items, therefore,

you should always enter plan version 0.

- Profit Basis

For results analysis and WIP, only support C and E are supported as the

profit basis.

- Commitments

In results analysis, only OBLIA = blank. is supported.

- Final Results Analysis

Only X (for last status) or blank (for other statuses) is supported.

Setting Final Results Analysis to "X" means that cost of sales is set equal

to the actual costs, and calculated revenue is set equal to the actual

revenue. The final profit is actual revenue less actual costs. If the resulting

profit is negative, a loss is posted. Anything else, such as revenue in

excess of billings, revenue surplus must be zero.

- Sales Order Structure

In results analysis, only sales order structure BLANK or E (Process Items

Individually) are supported.

Extended Control:

- Valuation Level

Only valuation level S (Valuation at Totals Level) is supported.

- Cutoff Period

Only D (Cutoff Period = Period Before Results Analysis Period) is

supported as the cutoff period.

- End Indicator

Only E (Perform RA up to RA period and Ignore remainder) is supported.

- Method for Including Manual Results Analysis Data

Only E (Manual Change) and Z (Manual Addition) are supported.

- Input and Output Quantities in Results Analysis

Only BLANK (No Quantities) is supported.

- Time Frame

Only OBLIR = blank (No Restrictions) is supported.

o Define Line IDs

The line IDs put the costs incurred for the order into specific groups.

o Define Assignment for Result Analysis

In the assignment, KKAKH only supports the following configuration:

- Only the ReqToCap column (requirement to capitalize) is supported.

- The following columns must all be marked as "+" (all):



Debit/Credit Indicator

Vble/Fixed Indicator

Accounting Indicator

o Define Update for Result Analysis

Only the categories K (Costs), D (Special Costs), A (Settled Costs), E

(Revenue), and N (Costs Not to be Included) are supported.

The ApptNo UM field (Capitalized Costs Apportionment Number) is not

supported. Hence WIP apportionment to line IDs is not supported.

KKAKH calculates WIP at actual cost, but doesn't include the VA88 settlement function.

If you want to speed up the settlement, you can use VA88H.

With the four values Planned revenue R(p), Planned Cost C(p), Actual Revenue R(a)

and Actual Cost C(a) for sales order items, the system will calculate the Cos Costs

Affecting Net Income in 01 result analysis method, or calculate the Revenue Affecting

Net Income in 03 result analysis method.

You then settle the following:

- The cost of sales or change to CO-PA

- The revenues or change to CO-PA

- The change/ cancellation of the WIP or the reserves to FI and EC-PCA



Variance Calculation for Production Orders (Changed)

Use

As of Smart Financials package 1.0, variances are calculated on production orders with

transaction code KKS1H.

Note the following:

o Variances can only be calculated on production orders, not on product cost

collectors or process orders.

o The option All Target Cost Versions is not supported.

Accelerated collective variance calculation on production orders compares the target

costs (in the form of standard costs) with the control costs (actual cost less scrap cost)

of all production orders in the plant, and assigns the resulting variances to variance

categories.

The following scenarios are supported:

o Variance calculation on PP production orders with full settlement, production

order triggered by sales order (with marked sales order cost estimate).

o Target cost version 0 (Target Costs for Total Variances) is supported. The

control cost is based on the actual cost of the order, while the target cost is

calculated based on the current standard cost estimate of the order.

o Scrap variance is calculated based on the standard cost estimate.

o Calculation of the variance for a specified plant.

Processing can be optimized by means of an Auto Split option that divides the set of

orders into eight subsets. This option reduces processing time when the number of

orders is sufficiently large.


You need to check your Customizing settings and ensure that they are adapted for the

new variance calculation transaction. For detailed information see below under Effects

on Customizing.

You also need to check the following transactions:

o Define Material Master Data (transaction MM02)

Do not change the origin group of the delivered material.

o Define Routing Master Data (transaction CA01)

Multiple operation sequences and parallel sequence are not supported.

Operation split for scheduling is not supported.


The following Customizing settings need to be checked or carried out:

o Define Variance Keys

Write Line Items should be selected.

o Define Variance Variant



Minor differences are not supported.

o Define Valuation Variant for WIP and Scrap (Target Costs)

o Define Target Cost Version

Target Cost Version 0 is supported. Control cost is based on the order cost and

target cost is based on the current standard cost estimate of the order.

o Define Primary Data for Input Price Variances

Primary price variances are not supported.

o Define Costing Sheet

Note the following;

- In the Base configuration of the costing sheet:

From/To origin are not supported. All units of measure of the cost

elements defined in the Base must be compatible.

- In the Overhead Rate configuration of the costing sheet:

The standard dependencies (D000 - D080) are supported. The customer-

defined dependencies are not supported due to HANA technical

limitations.

A quantity-based overhead rate should not be referenced by another

quantity-based overhead rate.

Object currency conversion is not supported for quantity-based overhead

rates. Users need to configure the amount using the controlling area

currency in the Costing Sheet. In such cases, the object currency must be

the same as the controlling area currency.

For quantity-based overhead rates, the specified unit of measure should

be compatible with the unit of measure of the cost element that is grouped

by the corresponding Base configuration.

- In the Credit configuration of the costing sheet:

Origin Group is not supported. Order and Business Process are not

supported as the object to be credited.

o Define Cost Component Structure

In the cost component structure configuration, Origin Group is not supported.

o Fiscal Year Variant

The fiscal year variant must match the month of the calendar year.



Smart Financials Reporting (New)

Use

As of Smart Financials package 1.0 (SAP_FIN 700), you can use line item reports,

powered by SAP HANA, that have a simplified user interface. Most of these new Web-

based applications can be used instead of the corresponding SAP ERP reports and are

compatible with them from a business point of view.

The following reports are available:

o Financial Statement Report (Actual / Actual Comparison)

With this report, you can view your financial statements and compare data from

different fiscal periods.

This report replaces the SAP ERP transaction Financial Statement Report

(Actual / Actual Comparison) (S_PL0_86000028).

o G/L Accounts List in Chart of Accounts

With this report, you can view the list of all G/L accounts for a specific chart of

accounts.

This report replaces the SAP ERP transaction G/L Accounts List

(S_ALR_87012328).

o G/L Accounts Payable

With this report, you can check how much you owe to your vendors and navigate

to the line items to view detailed information.

This report replaces the SAP ERP transaction Payables: Profit Center

(S_AC0_52000888).

o G/L Accounts Receivable

With this report, you can check how much your customers owe you and navigate

to the line items to view detailed information.

This report replaces the SAP ERP transaction Receivables: Profit Center

(S_AC0_52000887).

o Line Item Browser

You can use 3 different reports for analyzing G/L account line items:

- G/L Account Line Item Display (Entry View)

- G/L Account Line Item Display for Leading Ledger (Entry View)

- G/L Account Line Item Browser (G/L View)

With these reports, you can analyze data from General Ledger Accounting (FI-

GL), Cost Center Accounting (CO-OM-CCA), and Profitability Analysis (CO-

PA) at line item level together in one report.

These reports replace the SAP ERP line item display reports, for example the

following transactions:

- FAGLL03

- FAGLL03H

- FBL3

- FBL3H

- FBL3N

o G/L Account Balance

You can use this report to display the balances of individual fiscal years for

selected G/L accounts.

This report replaces the SAP ERP report G/L Account Balance Display



(transactions FAGLB03 and FAGLB03A).

o Cash Flow Report (Indirect Method)

With this report, you can evaluate the cash flow and cash holdings of a company

based on the indirect method.

This report replaces the SAP ERP transaction Cash Flow (Indirect Method)

Variant 1 (S_ALR_87012272).

o Work Analysis

This report previews the effect of activity allocation to financial statement,

showing the activity costs grouped by overhead, investment, and production.

o WIP Analysis

This report shows the increase of WIP positions in G/L and the underlying

primary and secondary costs of the production orders. The analysis is technically

based on the linking of G/L WIP line items with settlement line items through the

order number in G/L line items.

o Income Statement by Market Segment

This report brings together different income statements showing P&L details on

the G/L account, together with details such as cost center or market segment

information at a glance.



Integrated Business Planning (New) As of SFIN Release 1.0, a new solution for financial planning is available. This solution is characterized by the following criteria:

o Microsoft Excel frontend. The planner can record plan data in a user friendly way by entering them in a normal MS Excel sheet that uses an Add-on from Analysis Office.

o Use of embedded BI. Plan data is stored in a BI cube that is an integral component of the ERP system. A sample cube is provided by SAP, but customers are encouraged to copy the cube and adopt it to their needs. Actual transaction data and master data are shown in the MS Excel sheet without replication - changes are immediately visible.

o The views feeding the BI cube make use of the latest HANA technology enabling seamless Top-Down and Bottom-Up planning scenarios.

SAP delivers sample content for the following:

o Cost Center planning

o Internal Order planning

o Project planning

o Profit Center planning

o Cost of Sales planning

o P&L planning

For each of these planning scenarios, two sample MS Excel workbooks have been created; one based on periods, and one based on the fiscal year.

To save effort during system setup, SAP also delivers a program that automatically analyzes existing customer-specific CO-PA dimensions and generates the corresponding BI objects.

Due to the fact that all planning processes write their data to a common data source, all resulting plans are integrated and aligned by design.

As this planning solution is completely new, it has no impact on existing plan data. SAP will not provide migration functionality.

In the first release of this new planning solution, the development of functionality has been focused on enabling plan data capturing in a very user-friendly way. If further plan data processing is necessary, releasing them to the classic FI/CO plan data tables may be considered in future releases.

An installation guide has been created to enable system administrators to install the solution smoothly. Please refer to this guide for detailed information about related authorization profile requirements, and so on.

To support the new Planning function, carry out the Customizing activities under Controlling -> General Controlling -> Planning.

For more information about Planning, see Help Portal under SAP Business Suite -> SAP HANA Innovations for SAP Business Suite -> Products powered by SAP HANA -> Smart Financials



Data Aging of Financial Accounting Documents (New)

Use

As of Smart Financials package 1.0 (SAP_FIN 700), the Data Aging function is

available for financial accounting documents. You can use this to transfer data to the

database cold area, in order to ease the load on the memory.

The archiving object for the accounting document (FI_DOCUMNT) is replaced by the

Data Aging object (FI_DOCUMENT), which means data archiving for accounting

documents is no longer possible. As the system no longer stores the transaction

figures, the archiving objects for transaction figures are also obsolete.


You can continue to access accounting documents that have been archived in the past.


For additional information, see the release note for the business function

DAAG_DATA_AGING: Data Aging


You make the settings for Data Aging of accounting documents in Customizing for

Financial Accounting under: Financial Accounting Global Settings (New) -> Tools ->

Data Aging.