FI SETTINGS:-

 Creation of Company
 Company Code
 Assignment of Company code to Company
 Business Area
 Credit Control Area
 Fiscal Year Variant & Assignment of FSV to Company
 PPV & assignment of PPV to Company
 Opening of the periods
 Tolerance Groups & its assignment
 Global Parameters
 Creation of GL Masters records
 Creation of Ledgers (Standard, Appendix, Extension) and assign to Base Ledger

CONTROLLING SETTINGS:-

 Maintain Controlling Area

 Maintain Number Ranges
 Maintain Versions

Note 1:- First & the foremost important point is, Controlling area should be activated, in your
company code, before posting of journal entries. If else, after postings are done, we cannot activate
the Controlling in our Company code.

Explanation 1: As Controlling activities are integrated from CO to FI, so it is mandatorily

required to activate the Controlling Area.

Explanation 2:- All the postings data is stored in Universal Journal, called ACDOCA.

Note 2: - Before the Journal entries are posted in Simple Finance below are the steps which need to
performing mandatorily:-

=================================================================================

Step No 1: Activate Business Functions

Navigation: - SAP Customizing Implementation Guide Activate Business Functions

 Click on activate business function

Click on Continue

Click on “Enterprise Business Functions” (Folder)

NOTE:- Make sure the above accounting activities are to be activated if not & FINS are the activities a
related to Financial Activities

HOW TO ACTIVATE A PARTICULAR ACTIVITY:-

 Select the particular activity and select & Needs to re-start the server
to replicate the changes made.

Step No 2:- Select Simple finance Add-on for SAP Business Suite powered by SAP HANA

Click on Preparations and Migration of Customizing for GL:-

General Ledger:- Before migrating you must perform the
necessary preparations and corresponding activities in Customizing.  

Step No 3:- Check & Adopt Fiscal Year Variants

Purpose: - By performing this step we are cross-checking that the same fiscal year variant is assigned

both in FI & CO.

In this activity, you compare the fiscal year variants between controlling areas and their assigned
company codes. The report reconciles the fiscal year variant of the controlling areas and their
assigned company codes. It creates a proposal for the configuration change. The columns 'Det. FYV
for CoAr' (determined fiscal year variant for controlling area) and 'Det. FYV for CoCd' (determined
fiscal year variant for company code) provide the proposal for the configuration change.

The report must be executed for all controlling areas used in production.

Customizing Path
Transaction: FINS_MIG_FYV or IMG activity: Check and Adopt Fiscal Year Variants.

Give your Controlling Area = KK11 & Click on Execute:-

Note: - You need to get the message as shown below, else necessary changes to be performed
individually.
 Click on “Enter”
Click on back arrow once

STEP NO 4: Migrate General Ledger Customizing

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

The following are migrated:

 Company code assignments

 Currency settings

 Fiscal year variant

 Open period variant

 Settings for real-time integration of CO-FI

Click on Enter until you get the message as “SUCCESS” as shown below:

Click on back arrow

STEP NO 5:- Regenerate CDS Views & Field Mappings:- (One time activity)

Purpose: - You use this Customizing activity to do the following:

Navigation:- SPRO – IMG Activity – Financial Accounting (New) – FAGS (New) – Regenerate CDS.

 Regenerate the compatibility and data migration views so as to adapt them to the
configuration of customer-specific entities. The following applications are considered during
generation:

 General Ledger
 Controlling
 Material Ledger
 Cash Management
 Asset Accounting

 Generate the redirection of SELECT-statements from the concerned data base tables to the
corresponding compatibility views.
 Regenerate the mapping of customer-specific fields in the data migration procedure .

Note:- SAP recommends to execute this step in batch mode.

Note2: After the above activity is performed, we need to get the message as shown in the screen shot.

STEP NO 6:- Migrate General Ledger Customizing

Purpose: - In this Customizing activity, you define the ledgers that you use in Accounting. Only one
ledger can be designated leading ledger (standard leading ledger is 0L).

There are two types of ledgers:

  Standard: A standard ledger contains a full set of journal entries for all business transactions.

 Appendix: An appendix ledger is assigned to a standard ledger and inherits all journal entries
of the standard ledger for reporting. Postings made explicitly to an appendix ledger are
visible in that appendix ledger but not in the underlying standard ledger. This concept can be
used to avoid duplication of journal entries. If many business transactions are valid for both
ledgers and only a few adjustments are required in the appendix ledger.

You can also assign company code to ledger, and define currency settings and fiscal year variant.

In our example, ledger L1 was added to company code KK11 because ledger configuration must be
consistent between all company codes using the same Asset Accounting Chart of Depreciation.
Additional Ledger L2 is added to treat shifted fiscal year in Asset Accounting.

Important points to noted:-

1. Standard Ledger: - It Consist of Leading Ledger (0L) & Non – Leading Ledger (N1),
(N2) and so on…,

2. Appendix Ledger: - (Change in 1511)

Note:- Features of Leading Ledger, Non – Leading Ledger & Appendix Ledger:-

Leading Ledger:-
 There must be exactly one leading ledger
 It is assigned to all company codes
 Defines document number (BELNR) for all ledgers
 Ledger 0L is delivered with as leading ledger (default setting)
 It is in sync with FIN OP processes (AR/AP open item management)
 Basis for actual CO data (assigned to actual version 0)
 Contains full set of line items in ACDOCA.

Additional Non-leading Standard Ledgers:-

 Can be assigned to selected company codes.
 Contains full set of line items in ACDOCA.
 Inherits currency configuration of leading ledger (in sFIN 1503).
 Deviating fiscal year variant / open period variant possible

Appendix Ledger:-
 Is defined on top of a base ledger, which is a standard ledger.
 Inherits in reporting all transaction data of underlying base ledger.
 Contains physically only line items posted to appendix ledger only.
 Inherits currency settings and fiscal year variant of base ledger.
 Separate company code assignment (subset of base ledger)
 Separate Open Period Variant
 Can be used e.g. to create management views without influencing the data in the base
ledger.
 Cannot be part of ledger groups, except generated group containing the ledger itself.
 Only manual postings are allowed to the appendix ledger (FB01L, FBB1, KB11, KB41)
 You can define several appendix ledgers onto the same base ledgers, but not on top of an
appendix ledger (no stacking).
Attention point:

 SAP Note 1951069 - Different fiscal year variants in General Ledger Accounting (New)
(NewGL) under the new Asset Accounting (FIN_AA_PARALLEL_VAL)

Customizing Path
Transaction: SM30 FINSV_LEDGER or IMG activity: Define Settings for Journal entry Ledger.

Click on “New Entries”

STEP NO 777777:- Creation of Leading Ledger, Non – Leading & Appendix Ledger:- (******)

Navigation :- SPRO->IMG ACTIVITY--> Migration from SAP ERP to SAP Accounting powered by SAP
HANA-->Preparations and Migration of Customizing for General Ledger-- Define Settings for Ledgers
and Currency Types -- Click on Execute

Click on "New Entries"

Create a New Appendix / Extension Ledger and assign them to the Base Ledger (OL) -- click on enter
& Save
Select the Appendix ledger MM, double click on Company Code Settings (Folder), and click on New
Entries” Enter the Company code and click on enter and assign the Posting Period Variant & select
the Parallel Accounting using G/L Accounts

Note: By selecting Parallel Accounting, we can assign more than one accounting principle to an
appendix or extension ledger

TO ASSIGN THE ACCOUNTING PRINCIPLE TO A LEDGER:-

Double click on Accounting Principles (folder)

Click on New Entries -- Assign the relevant accounting principle and save.

TO ASSIGN A new currency to an appendix ledger or extension Ledger:-

Procedure: - Select the particular ledger, double click on Currency conversions Settings for Company
Code and assign the relevant different type of currency which you want to assign.

Assignment of Accounting Principles to different ledgers:-

Select the Ledger type MM (Appendix Ledger)

Double click on “Accounting principles for Ledger and Company Code

Give the Ledger Name: - MM

Company Code = KK11

Click on “Enter”
Click on “New Entries”
Select the required Accounting principle by pressing “F4”

Click on “SAVE”

Click on back arrow two times and select the another ledger (If required)

Click on Save

STEP 8 :- Define Ledger Group:-

Navigation:- SPRO – IMG (Activity) – Financial Accounting (New) – FAGS (New) – Ledgers – Ledger –
Define Ledger Group:-

In this activity, you define ledger groups. A ledger group is a combination of ledgers for the purpose
of applying the functions and processes of general ledger accounting to the group as a whole. You
can combine any number of ledgers in a ledger group. In this way, you simplify the tasks in the
individual functions of General Ledger Accounting. A ledger group does not have to contain more
than one ledger.

The system uses the representative ledger of a ledger group to determine the posting period and to
check whether the posting period is open. If the posting period for the representative ledger is open,
the system posts in all ledgers of the group, even if the posting period of the non-representative
ledgers is closed. Each ledger group must have exactly one representative ledger:

Attention point:

 SAP Note 1951069 - Different fiscal year variants in General Ledger Accounting (New) (New
GL) under the new Asset Accounting (FIN_AA_PARALLEL_VAL)

Customizing Path
Transaction: SM30  V_FAGL_LDGRP_MAPor IMG activity: Define Ledger Group.

STEP NO 9 A:- Creation of new Accounting Principle

Navigation:- SPRO – IMG activity –FAGS (New) – Ledger – Parallel Accounting – Define Accounting
Principle

Click on Accounting Principle

Assign Accounting Principle to Ledger Group:- (Path is same as above)

Click on “New Entries” and assign the relevant accounting principle to your ledger & Save.

Step No 10 :- Define Ledger for CO Version

In this activity, you define a ledger that represents Controlling. That is, a ledger that contains all
postings of actual data that is relevant to Controlling. This is done by assigning the version 000 to a
ledger. You do this on a company code level, but you have to use the same ledger for all company
codes.

The current restriction is that the version 000 must be assigned to the leading ledger. You have to
assign the version 000 to the leading ledger for all company codes that are assigned to a Controlling
area.

As a requirement, the fiscal year variant of the company code must be identical to that of the
Controlling area.

Navigation: - SPRO

Transaction: FINSV_LD_CMP_COV or IMG activity: Define Ledger for CO

Version.
Select “Position” Give your Company Code = KK11

Click on “SAVE”

STEP NO 11:- Define Document Types for Posting in Controlling

In this activity, you can create new document types for postings in Controlling, for example you can
create a document type that you can use for the manual reposting of primary costs. For documents
types used in Controlling, the indicator G/L account must be set.

In our example document type CO is defined.

Customizing Path
Transaction: SM30  V_T003 or IMG activity: Define Document Types for Posting in Controlling.
Select the Document type CO, Click on Details. Click on Number Range Information, click on Change
Intervals, ---- This step needs to be cross verified as we are already giving the number range to
Controlling by using T. Code:- KANK

Click on “Number Range Information”

Input your company code:- KK11 & Click on Interval button

STEP NO 12:- Define Document Type Mapping Variants for CO Business Transactions

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

NEW CONFIGURATION PROCEDURE FOR FI – CO INTEGRATION

 GL Account Mapping of CO-Real-time Integration with New GL is obsolete

Secondary cost elements are no longer mapped to GL Accounts
Secondary cost elements are part of chart of account and also used General Ledger
  Configuration for document type document types that you want to use for
postings in Controlling need to be defined and require the indicator G/L to be
flagged. These document types need to be linked to the CO business transaction via
a variant.

Click on Define Document type

Select -00000000100  Double click on Mapping of Co. Bus. Transactions to Document Types
Migrated From Co-Fi Real Time Integration

Double click on “Mapping of CO Bus. Transactions to Document Types

Click on “SAVE”

Note:- From the above step it is clearly visible that all the CO activities are integrated with that of FI
Module, being document type assigned as to SA and Cross - Company code is also SA, with CO
business transactions RKP1, COIN, RKP3 and the like.

STEP NO 13:- Check and Define Default Values for Postings in Controlling

Purpose:- In this activity, you define default values for use in CO business transactions whose user
interfaces do not allow you to enter a document type or a ledger group for posting purposes.
Standard setting: If you do not enter a default ledger group, all CO postings will be done to all G/L
ledgers.

Note :- In our example 0L Default Ledger Group is assigned.

Customizing Path
Transaction: SM30 -> FINS_CO_DOCT_CC or IMG activity: Check and Define Default Values for
Postings in Controlling.

Select “Position”
Company Code = KK11
Click on “Enter” & Input the Default Ledger Group “OL”

Click on “SAVE”

STEP NO 14: - Define Offsetting Account Determination Type

Description: - In this customizing activity you define how the system calculates the offsetting account
in all applications. SAP recommends choosing the option "As case 2, but including line items
generated automatically".

Customizing Path
Transaction: SM30 -> FINS_CO_DOCT_CC or IMG activity: Define Offsetting Account Determination
Type
click on New Entries --> select the option as "As case 2, but including line items generated
automatically. click on save.

Click on “SAVE”

STEP NO 15:- Define Source Ledger for Migration of Balance ******

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

In our example, 0L is defined as a source ledger for KK11, because ledger MM & SS was not active in
that company code.
 Customizing Path
Transaction: SM30 -> FGLV_MIG_SOURCE or IMG activity: Define Source Ledger for Migration of
Balances.

Click on “New Entries”

Click on “Save”

Click on Next button

Click on “SAVE”

STEP NO 16:- Execute Consistency Check of General Ledger Settings

Description:- In this activity, the Customizing settings for the ledgers are checked. This check must
run without error messages before migration of transaction data. In our example, there were some
errors with SAP delivered organizational units which had to be resolved.

Customizing Path
Transaction: FINS_CUST_CONS_CHK or IMG activity: Execute Consistency Check of General Ledger
Settings.

After the above steps are executed we need to get the message as:-
 CONFIGURATION OF NEW GENERAL LEDGER

Step No 1:- Define document type’s entry view in ledger.

Path: SPRO – financial accounting (new) - financial accounting global settings (new) – document -
document type – define document types for entry view.

Note: - Document types are defined by SAP by default (No further configuration required)
Click on back arrow once

Step 2: Define ledgers for general ledger accounting.

Path.: SPRO – IMG – Financial Accounting (New) – financial accounting global settings (new) -
Ledgers - ledger – Define Settings for Journal Entry Ledger

Click on “new entries”

Ledger = MM
Ledger name = GAAP Ledger
Totals table =FAGLFLEXT (This table is updated as ACDOCA)
Ledger = SS
Ledger name = Appendix Ledger
Totals table = FAGLFLEXT (This table is updated as ACDOCA)
Step No: - Click on “Define document types for entry view in a ledger

Ledger = MM click on enter

Click on “new entries”

Step 3: Define ledger group

Path: SPRO – financial accounting new(new) - financial accounting global settings (new)- ledgers -
define ledger group
Select ledger group: OL
Double click on “ledger assignment” folder
Click on “new entries” button
Ledger = MM click on save
Ignore the warning message by clicking on enter.

Step No 4:- Define Document Types: -

A) Define document types for Entry View: - ( This is defaulty defined by SAP)
 B) Define Document Types for Entry View in General Ledger

Input the Ledger = MM

Click on “Enter”

Click on “New Entries”

Click on save

Define Number Ranges for in Entry View:-

Click on enter

Click on “Intervals”

Note: - Also define a number range for MM & SS i.e. 40

Display balances

To display the balance in the share capital account in leading ledger

Path: accounting – financial accounting – general ledger – account – display balances. (New)
T.Code:FAGLB03

Account = 400100
Company code = GG11
Fiscal year = 2016
Ledger = OL (leading ledger or representative ledger)
Click on “execute”

To display the balance in the share capital account in non leading ledger1

Click on back arrow

Click on “choose ledger” button
Ledger = MM
Click on “enter”
Account = 400100 (share capital account)
Fiscal year = 2016
Click on “execute”

To see balance in the share capital account in non leading ledge no 2

Click on back arrow

Click on “choose ledger” button
Ledger = SS
Click on “enter”
Account = 400100
Fiscal year = 2016
Click on “execute”

Document Splitting (NOT REQUIRED IN S/4 HANA)

 Currencies- Basic Principles:-

 Currency setting for Universal Journal Entry need to be compatible with CO and FI
currency setting
 FI still supports max. 3 local currencies.
 CO still supports max. 2 currencies.
 Currency settings for leading ledger define also settings for non-leading ledgers.
 Transfer prices are not yet supported (SAP sFIN OP 1503).

 Amount fields of Universal Journal Entry:-

 These are the most important amount field of database table ACDOCA:
 WSL Original Transaction Currency (Document Curr) (BSEG-WRBTR)
  TSL Line Item Currency (BSEG-PSWBT)
 HSL Local currency (BSEG-DMBTR)
 KSL Global Currency for FI and CO (special case: Currency in Controlling)
 OSL 1st additional currency in FI
 VSL 2nd additional currency in FI (only in the aforementioned special case!)
 CO_OSL Object currency of CO

 Document Types:

 Document type / number in General Ledger View (FAGL_DOCNR) per ledger is

obsolete.
 Document type and number of entry view (RF_BELEG) is used for all ledgers

4. User Interface Apps - FIORI

4.1 Transactional Apps

Here is the list of Transactional FIORI applications.

App Id App Name Description Priority

F0706 Display G/L You can use this app to check G/L account line items. You can switch Medium
Account Line between the general ledger view and entry view. In both views you
Items can use filter criteria to choose whether the app should display open
and cleared items for OI-managed accounts, or all of the items for an
 account. You can select the line items based on a key date or after
the clearing date in connection with a key date. In the entry view,
you can also choose whether the app should display normal, noted,
or parked items only, or all items. You can group, sort and filter the
results list using various characteristics. You can show numerous
additional characteristics, and also swap the order of the columns in
the list.

F0707 Display G/L With this transactional app, you can check and compare the Medium
Account balances, and the credit and debit amounts of a ledger in a company
Balances code for each period of a fiscal year. You can restrict the data to a
single general ledger account, or other selection criteria (for
example, profit center). In a further view, you can compare the
balances relating to several fiscal years with each other. To make an
additional detailed check of the data, you can call the related line
items in the Display G/L Account Line Items app

F0708 Display G/L With this transactional app, you can check and compare the Medium
Account balances, and the credit and debit amounts of a ledger in a company
Balances code for each period of a fiscal year. You can restrict the data to a
single general ledger account, or other selection criteria (for
example, profit center). In a further view, you can compare the
balances relating to several fiscal years with each other. To make an
additional detailed check of the data, you can call the related line
items in the Display G/L Account Line Items app

F0717 Manage G/L With the transactional app G/L Documents you can analyze your Low
Documents accounting documents and create reversals in order to make
adjustments. Filtering and selection criteria enable you to quickly find
documents, for example based on the document type or the user.
The information provided includes the G/L accounts posted, other
account assignment objects, and any sales or purchase taxes. You can
create new G/L documents based on other G/L documents. Display
variants allow you to add or remove fields. You can enter notes or
add attachments to explain the posting. Information is shown on any
related documents, such as purchase orders or incoming invoices.
Amounts can be displayed in different currencies, such as local
currency or transaction currency

F0718 Post G/L With the transactional app Post G/L Document you enter manual Low
Document postings to G/L accounts. For example you can make adjusting
entries during period-end closing, or record business transactions
that have no source document (such as expenses paid with petty
cash). Applicable taxes can optionally be calculated automatically as
you enter the items. You can specify additional account assignment
objects such as cost centers, orders, or materials. You can enter
 notes or add attachments to explain the reason for a posting.
Postings can be made in all relevant ledgers for the accounts for
which you are responsible

F0731 Manage G/L With the transactional app Manage G/L Account Master Data, you Low
Account Master can search, create, display, and edit the master data of G/L accounts.
Data You can also easily add new G/L accounts from scratch or based on
existing accounts.

F0763 Display Chart of With the transactional app Display Chart of Accounts, you can display Low
Accounts G/L accounts according to where they are assigned in the financial
statement version you selected. You can also display accounts that
are as yet not assigned anywhere in the financial statement version.
From an individual account number, you can also access an app
where you can edit that account.

F0806 Open Posting With the transactional app Open Posting Periods you can define the Medium
Periods open and close posting periods

F0862 My Inbox With the transactional app, you can make important decisions via Very
mobile or desktop devices anywhere and anytime. Using this app, High
you can process your standard and custom workflow tasks based on
the decision options defined in the back-end system

4.2 Analytics Apps

Here is the list of Analytical FIORI applications:

App App Name Description Priority

Id

NA

4.3 Fact Sheet(Master Data) Apps

Here is the list of Fact Sheet FIORI applications:

App App Name Description Priority

Id

F0125 Cost Element This fact sheet displays contextual information about the Cost Very Low
Element. You can navigate to its related business objects and you
can access related transactions in operational systems.

F0126 Cost Element This fact sheet displays contextual information about the Cost Very Low
Group Element Group. You can navigate to its related business objects and
you can access related transactions in operational systems.
F0129 G/L Account This fact sheet displays contextual information about the G/L Low
Account. You can navigate to its related business objects and you
can access related transactions in operational systems.

F0130 G/L Accounting This fact sheet displays contextual information about the G/L Low
Document Accounting Document. You can navigate to its related business
objects and you can access related transactions in operational
systems.

F0727 Functional Area This fact sheet displays contextual information about the Functional Low
Group Area Group business object. You can navigate to its related business
objects, and you can access related transactions in operational
systems. & lt;/ p & gt;

F0728 Functional Area This fact sheet displays contextual information about the Functional Low
Area Group business object. You can navigate to its related business
objects, and you can access related transactions in operational
systems.

Asset Accounting:
New Asset Accounting Overview : - SAP Simple Finance add-on 2.0 is based on SAP Accounting
powered by SAP HANA, where classic Asset Accounting is no longer available. New Asset Accounting
must be used in place of classic Asset Accounting. Because of this, you have to migrate the
Customizing for fixed assets in order to then be able to migrate documents.
1 New Architecture: - There is change to the underlying table structure
in Asset Management area

Points to be noted:-

 Upon asset creation/changes, planned depreciation values are calculated (real-time) &
stored in FAAT_PLAN_VALUES. If there are any errors (e.g. inconsistent Depreciation
Key) while calculating planned depreciation that particular asset’s planned depreciation
value will be empty / not updated.
 Upon month-end depreciation run, actual postings will use the “planned depreciation”
values from the above table. Assets with errors will not stop the full depreciation run.
Asset having issues/errors will not have actual depreciation postings and will be
reflected in Depreciation Run Log .
 All actual asset accounting line item postings will be stored in ACDOCA. Header info will
be stored in Table BKPF.
 All Statistical info related to assets will be stored in table FAAT_DOC_IT
 Plan data previously stored in ANLP and ANLC is now stored in
FAAT_PLAN_VALUES.                         
 Posting document is updated in Financial Accounting at asset level.
 For each accounting principle (no matter if account or ledger approach) a corresponding
depreciation area is required. For each currency in a G/L ledger a corresponding derived
depreciation area is required. Fiscal Year Variants differing in start-or end date
supported by a work around only (note 1951069), which requires thorough test before
the upgrade.

2. Summary of Changes in Transactions (T-codes)

OLD Transaction NEW Transaction
“ABST2” Removed , not required “FAGLGVTR” will perform the GL close process

AB01Create Asset postings AB01L

ASKB<RAPERB200> Periodic APC run
ABST(L) < RABST01 > Reconciliation program
GL / AA
ABST2 < RABST02> Reconciliation program GL /
AA
AB02 < Change asset document>
AW01_AFAR Asset Explorer (old depreciation)
ABF1/ABF1L (Post differences in asset accounting)
OASV (Transfer balances)
RAALT**11 (Direct Data Import - Asset
Accounting)
FAA_GL_RECON. Consistency Check for FI-AA
(New) and FI-GL (New)
RAGITT01. Asset History Sheet
Obsolete, posting now performed direct to GL
Obsolete, no AA tables anymore in sFIN 2.0 to
reconcile with GL, just ACDOCA
Obsolete, no AA tables anymore in sFIN 2.0 to
reconcile with GL, just ACDOCA
Changes in asset documents will be done via FB02 in
future
Not available anymore (This is replaced by AW01N)
This is not required as we enter Ledger directly in
transaction
Functionality not required. Its real-time now.
Not available anymore –Not sure what is this T code
Functionality not required. Its real-time now.
New program: S_ALR_87011990

2.3 Summary of Table Changes

2.3.1 New Tables introduced in Simple Finance 2.0

 ACDOCA
 FAAT_DOC_IT
 FAAT_YDDA
 FAAT_PLAN_VALUES                               

2.3.2Obsolete Tables because of Simple Finance 2.0

 ANEK, ANEP, ANEA are replaced by ACDOCA but still supported by means of compatibility
views.
 Statistical items are moved to FAAT_DOC_IT, but still supported by means of compatibility
views.
 ANLC replaced by ACDOCA and FAAT_YDDA but still supported by means of compatibility
views

Actual items:-

 Actual data of ANEK, ANEP, ANEA, ANLP, ANLC is stored in table ACDOCA. ANEK data is
stored in BKPF.
 Compatibility views FAAV_<TABLENAME> (e.g. FAAV_ANEK) are provided in order to
reproduce the old structures.
 Access to old data in tables still possible via the views FAAV_<TABLENAME>_ORI (e.g.
FAAV_ANEA_ORI)

Non actual items:-

  Statistical data (e.g. for tax purposes) previously stored in ANEP, ANEA, ANLP, ANLC is
now stored in table FAAT_DOC_IT
 Plan data previously stored in ANLP and ANLC is now stored in FAAT_PLAN_VALUES         

Note: Compatibility views correspond to historical data prior implementation of Simple Finance. After
SFin, all data will be in new Table.

2.5 Configuration Changes:-

 “Reset posted depreciation” is obsolete and has been removed (Asset Accounting (New)->
Preparations for going live -> Tools -> Reset Posted Depreciation).
 With Asset Accounting (New), the Posting Indicator supports four (4) different values. For
the depreciation areas the Posting Indicator need to be adjusted:-

3 GAPs impact
CPF-G-089 – Explore Asset Explorer now it can satisfy the Gap Requirement.

4. Closing process impact

 Real time integration of Asset Accounting with General Ledger Accounting
 Elimination of reconciliation steps
 No separate program to be executed for balance carry forwarding asset accounting
 Planned depreciation will automatically be calculated for the new year after having
performed the balance carry forward (Year-end Close)
 Fast depreciation posting run due to simple processing logic.
 New data structures and parallel processing

NOTE:- For all prerequisites and details regarding the migration from classic to new Asset Accounting
refer to the SAP Help Portal:
http://help.sap.com/saphelp_sfin200/helpdata/en/35/64d652bc8fbe66e10000000a441470/content
.htm

Note 2:-The steps described in the following chapters are critical for the migration to Simple Finance
2.0. They are based on:
http://help.sap.com/saphelp_sfin200/helpdata/en/6a/62d85213071742e10000000a44176d/conten
t.htm?
frameset=/en/7e/61d85213071742e10000000a44176d/frameset.htm&current_toc=/en/d7/bf6052
e7d1ea5fe10000000a423f68/plain.htm&node_id=32
5.0 Customization:-
      5.1  Determine Active Charts of Depreciation:- 

Documents can only be migrated after all active charts of depreciation are migrated. You must
therefore migrate all active charts of depreciation in your system, that is, charts of depreciation that
are assigned to a company code. You can use this activity to check which charts of depreciation are
active in your system.

Attention points:

 Check that real company codes are assigned the correct chart of depreciation;

 Delete assignment for not used charts of depreciation.

Navigation:- SPRO – Financial Accounting (New) – Asset Accounting (New) – Organizational

Structures – Assign COD to Company Code.

5.2 Customizing Documents:-

Real company codes must be assigned to the correct chart of depreciation

All links between sample charts of depreciation and company codes must be deleted as they trigger
an error during new Asset Accounting activation:
5.3 Change definitions of depreciation areas

Description :- To support parallel accounting, the ledger approach for Fixed Assets is customized.
Steps from SAP Help:

1. Assign an accounting principle to each depreciation area. The system automatically assigns the
related ledger group to the depreciation area. The following information applies to this
assignment:

 All areas have to be assigned to an accounting principle.

 All areas that represent the same valuation have to be assigned to the same accounting
principle.

 The system automatically assigns the ledger group assigned to the accounting principle.

2. You have to modify the setting for Posting in G/L. Using this indicator, you specify if and how APC
and depreciation from the depreciation area are posted to the general ledger.

 The following applies for the accounts approach:

 Area Posts in Real-time is set for the leading area of the leading valuation.

 Either the option Area Posts APC Immediately, Depreciation Periodically or Area
Posts APC and Depreciation Periodically is set for the leading area of the parallel
valuation.

 The following applies to the ledger approach:

 Area Posts in Real-time is set for the leading area of the leading valuation.

 Area Posts in Real-time is also set for the leading area of the parallel valuation.

 Delta depreciation areas are no longer needed in Asset Accounting. For former
delta depreciation areas, set the indicator to Area Does Not Post. In addition, set
the Area for reporting purposes only indicator. In this way, you can continue to
use these areas for reports.

1.1. Customizing Path

Transaction: SM30  V_T093_00N or IMG activity: Define How Depreciation Areas Post to General
Ledger.
Customizing Documents :- The chart of depreciation is migrated in such a way that there is no longer
any area that posts periodically; all areas post immediately to the general ledger. This also applies
for reserves for special depreciation areas.

Specify Transfer of APC Values:-

1.2. Description: - The example is customized according to the ledger approach for 2 ledgers.

In this activity, you define transfer rules for the posting values of depreciation areas. These transfer
rules let you ensure that certain depreciation areas have identical asset values.

In the ValAd field, you specify the reference depreciation area that provides values to another
depreciation area. The system transfers the posting amounts of any transactions that affect
acquisition and production costs from this area to the dependent area. (Exception: if you specifically
enter an amount for the dependent area.)

Via the Ident. Field you can determine whether this transfer is:

 mandatory (= no opportunity for changing the values  box ticked) or

 optional (= possible to change the values during posting  box not ticked).

1.3. Customizing Path:- Transaction: OABC or IMG activity: Specify

Transfer of APC Values.
2. Specify Transfer of Depreciation Terms
2.1. Description:- The example is customized according to the ledger
approach for 2 ledgers.
One depreciation area can adopt depreciation terms from another depreciation area. In this activity,
you specify how the depreciation terms for a depreciation area are adopted from another
depreciation area. In the TTr field, you specify the depreciation area from which the depreciation
terms are adopted by the current depreciation area.

You can specify if the adoption of values is optional or mandatory via the Identical field. If you
specify an optional transfer (box not ticked), then you can change the proposed depreciation terms
in the dependent areas in the asset master record. In the case of a mandatory transfer (box ticked),
you cannot maintain any depreciation terms in the asset master record. In this way, you can ensure
that depreciation is uniform in certain depreciation areas.

1.1. Customizing Path

Transaction: OABD or IMG activity: Specify Transfer of Depreciation Terms

3. Activate New Asset Accounting

3.1. Description
This operation cannot be undone.

In the Customizing system, you activate the new functions for new Asset Accounting by selecting the
option Active in the New Asset Accounting group box in this activity. When you save, the system
performs various checks before it actually saves this setting. If the system has performed the checks
successfully and saved the settings, new Asset Accounting is active and you can post using the new
posting logic from this point on.

3.2. Customizing Path

IMG activity: Activate Asset Accounting (New).
 1.1. Customizing Documents
Select the option Active and then save