sap s-4 hana simple finance sap se or an sap affiliate company. all rights reserved
TRANSCRIPT
SAP S/4HANA Simple Finance
SAP Forum, 29.5.2015 Bratislava
© 2015 SAP SE or an SAP affiliate company. All rights reserved. 2 Customer Disclaimer: This road map represents SAP’s current plan, but is subject to change without any prior notification.
Certain planning constraints, such as regulatory and licensing issues, are outside of our control and may impact the timelines.
Disclaimers
DISCLAIMER
This presentation outlines our general product direction and
should not be relied upon in making a purchase decision.
This presentation is not subject to your license agreement or
any other agreement with SAP. SAP has no obligation to
pursue any course of business outlined in this presentation
or to develop or release any functionality mentioned in this
presentation. This presentation and SAP’s strategy and
possible future developments are subject to change and may
be changed by SAP at any time for any reason without
notice. This document is provided without a warranty of any
kind, either express or implied, including, but not limited to,
the implied warranties of merchantability, fitness for a
particular purpose, or noninfringement. SAP assumes no
responsibility for errors or omissions in this document,
except if such damages were caused by SAP intentionally or
grossly negligent.
SAFE HARBOR STATEMENT
This document is intended to outline future product
direction, and is not a commitment by SAP to deliver any
given code or functionality. Any statements contained in this
document that are not historical facts are forward-looking
statements. SAP undertakes no obligation to publicly update
or revise any forward-looking statements. All forward-looking
statements are subject to various risks and uncertainties that
could cause actual results to differ materially from
expectations. The timing or release of any product described
in this document remains at the sole discretion of SAP. This
document is for informational purposes and may not be
incorporated into a contract. Readers are cautioned not to
place undue reliance on these forward-looking statements,
and they should not be relied upon in making purchasing
decisions.
© 2015 SAP SE or an SAP affiliate company. All rights reserved. 3 PUBLIC
SAP’s Next Big Thing
R/2
1979
R/3
1992
ERP
2004 2015
© 2015 SAP SE or an SAP affiliate company. All rights reserved. 4 PUBLIC
SAP S/4HANA, the next generation business suite
Cloud
edition
On-premise
edition
SAP S/4HANA applications and extensions instant insight-driven applications for all lines of business and industries
SAP HANA platform in-memory platform for all data
SAP Fiori UX role-based user experience for all devices
Ariba Concur Fieldglass hybris Software SuccessFactors
Native integration for hybrid scenarios
People
Devices
Big Data
Internet
of Things
Business
networks
Social
networks
© 2015 SAP SE or an SAP affiliate company. All rights reserved. 5 PUBLIC
SAP S/4HANA, the great simplifier of enterprise software
SAP HANA
SAP Business
Warehouse
powered
by SAP HANA
SAP Business
Suite powered
by SAP HANA
SAP Simple
Finance
powered
by SAP HANA
Real-time analysis
Real-time reporting
Real-time business
OLAP and OLTP together
SAP HANA Enterprise
Cloud for SAP Business
Suite on SAP HANA
In-memory platform Instant financial insight
No aggregates
Single source of truth Simplified data model
New user experience
Advanced processing
Choice of deployment
Multitenancy
2011 2013 2012 2014 2015
© 2015 SAP SE or an SAP affiliate company. All rights reserved. 6 PUBLIC
SAP S/4HANA Functional Scope as of today
• Full ERP scope
• Full SAP Simple Finance
• Integrates with SuccessFactors Employee
Central, Fieldglass, hybris for Marketing,
Concur and Ariba network
• Industry roadmap
• CRM, SRM, SCM co-deployed w/ ERP
• Key scenarios
• Embedded ERP scenarios*
(Business All in One scope)
• Integrates with SuccessFactors
Employee Central, Fieldglass, hybris
for Marketing, Concur and Ariba
network
• Industry roadmap
SAP S/4HANA
SAP S/4HANA
On-Premise Edition
SAP S/4HANA
Cloud Edition
• Customer extensions
• Partner extensions
Extensions
HANA Cloud Platform
*Note: HCM default = SuccessFactors Employee Central
© 2015 SAP SE or an SAP affiliate company. All rights reserved. 7 PUBLIC
Roadmap
Disclaimer: This map represents SAP’s current plan but is subject to change without any prior notification. Certain planning constraints such as regulatory and licensing issues are outside our control and may impact the timelines.
For detailed roadmap please visit: SAP Service Marketplace
SAP S/4HANA
cloud edition
SAP S/4HANA
On-premise edition
Continuous innovations
without disruption
Yearly innovation cycle
Quarterly innovation cycle
SAP S/4HANA
cloud edition
SAP S/4HANA
on-premise edition
Available
update
update
update
Planned Future Direction
© 2015 SAP SE or an SAP affiliate company. All rights reserved. 8 PUBLIC
SAP S/4HANA, cloud edition free trial
Project Manager Scenario
Easily create, plan, staff, and bill customer projects
Cash Manager Scenario
Instantly monitor cash movements, balances and liquidity
General Ledger Accountant Scenario
Effortlessly review financial statements, account balances, and
individual line items
Accounts Receivable Accountant Scenario
Quickly process incoming payments, collect cash, and clear
customer accounts
Accounts Payable Accountant Scenario
Efficiently review and manage vendor accounts and invoices
Marketing Expert
Effortlessly analyze contact data, create target groups, and
trigger campaigns
Start Your Free
Trial Today
Public Cloud Trial
sap.com/s4hana-trial
© 2015 SAP SE or an SAP affiliate company. All rights reserved. 9 PUBLIC
Customer journey to SAP S/4HANA 3 situations, 3 deployment options
Choice of deployment
Innovation without disruption
Supported by predefined
migration, system conversion in
the cloud and deployment
packages from partners and SAP
Compatibility with SAP ERP 6.0
deploy new installation On Premise Cloud Hybrid
New
customer up and running with best
practices in two days
Starting point A
On Premise Cloud Hybrid SAP Business Suite
on anyDB customer upgrade to latest EHP, migrate database to
SAP HANA, deploy exchange innovation
transfer data to the cloud
Starting point B
On Premise Cloud Hybrid
SAP Business Suite
powered by SAP
HANA customer deploy exchange innovation transfer data to the cloud
Starting point C
© 2015 SAP SE or an SAP affiliate company. All rights reserved. 10 PUBLIC
Guided Configuration Simplified Data Model New User Experience
SAP S/4HANA – Innovations
no indices I no aggregates I no redundancies
Cloud and On Premise
© 2015 SAP SE or an SAP affiliate company. All rights reserved. 11 PUBLIC
SAP S/4HANA – Fiori
Completely Fiori
Cloud and On Premise
© 2015 SAP SE or an SAP affiliate company. All rights reserved. 12 PUBLIC
SAP Fiori – Intuitive User Experience and a responsive design
Today Functional-based applications
Target Role-based applications
to: One entry point for the User and UX following
common design directions
from: Multiple entry points for the user and inconsistent user
experience
from: One transaction for multiple roles with too much and
complex functionality
to: Decomposed apps for each role with simple functions
This is the current state of planning and may be changed by SAP at any time.
© 2015 SAP SE or an SAP affiliate company. All rights reserved. 13 PUBLIC
Decision Support
Simulation
SAP Fiori – Key Capabilities of a responsive design
Key capabilities of a FIORI Designed Screen
Example: SAP Simple Finance
Consolidation of activities, Intelligent navigation
patterns, Intuitive usability
Trends & analytics
at a glance
Personalized
post-it notes
Contact data Credit data:
UKM_BP
Full customer
contact history
Context-
dependent actions
Personalize layout
variants Example: MRP Cockpit - Material Shortage
© 2015 SAP SE or an SAP affiliate company. All rights reserved. 14 PUBLIC
Decision Support
Simulation
SAP Fiori – Key Capabilities of a responsive design
Key capabilities
Consolidation of activities, Intelligent navigation patterns,
Intuitive usability
Trends & analytics
at a glance
Personalized
post-it notes
Contact data Credit data:
UKM_BP
Full customer
contact history
Context-
dependent actions
Personalize layout
variants
© 2015 SAP SE or an SAP affiliate company. All rights reserved. 15 PUBLIC
SAP S/4HANA User Experience Consumer-grade user experience to end-users
The SAP Fiori design paradigm applies to the entire SAP S/4HANA suite
All new SAP S/4HANA business scenarios are delivered in Fiori Apps, examples:
SAP S/4HANA Simple Finance
SAP S/4HANA Public Cloud Edition (10 core scenarios)
SAP has a roadmap to leverage Fiori for other important processes in SAP S/4HANA
© 2015 SAP SE or an SAP affiliate company. All rights reserved. 16 PUBLIC
Guided Configuration
Cloud and On Premise
SAP S/4HANA – Guided Configuation
17 © 2015 SAP SE or an SAP affiliate company. All rights reserved.
© 2015 SAP SE or an SAP affiliate company. All rights reserved. 18 PUBLIC
BSIS BSAS BSIK BSAK LFC1 KNC3 BSID BSAD GLT0 KNC1 LFC3 BKPF BSEG BSIS BSAS BSIK BSAK LFC1 KNC3 BSID BSAD GLT0 KNC1 LFC3
Simplified Data Model
Cloud and On Premise
SAP Simple Finance - Removed aggregates and indices
SAP S/4HANA – Simplified Data Model in Finance
© 2015 SAP SE or an SAP affiliate company. All rights reserved. 19 PUBLIC
Doc Header + Line Items
Avoid Redundancy Non disruptive with equally named views for previous total/index tables
• BKPF, BSEG/BSEG_ADD and FAGLFLEXA unchanged
• Index and totals tables replaced by compatibility views (aka equally named views)
• Enable a smooth transition to the new data model in the standard as well as in the partner and customer coding.
Classic GL +
OPS Totals
Views (5)
Index Tables
BSXX (6)
GLT0, KNC1
KNC3, LFC1
LFC3 FAGLFLEXT
NewGL Delta Classic GL +
OPS Delta (3)
FAGLBSIS,
FAGLBSAS
Classic GL +
OPS Index
Views (7)
NewGL Totals
View
BSEG_ADD BKPF BSEG FAGLFLEXA
Legacy Data
Equally
Named Views
Document
Header + Line Items
NewGL Index
Views (2)
© 2015 SAP SE or an SAP affiliate company. All rights reserved. 20 PUBLIC
MSTQH
MSTEH
MSTBH
MSSQH
MSSAH
MSPRH
MSLBH
MSKUH
MSKAH
MKOLH
MCHBH
MARDH
MARCH
MSTQ
MSTE
MSTB
MSSQ
MSSA
MSPR
MSLB
MSKU
MSKA
MKOL
MCHB
MKPF
MSEG
MARD
MARC
Master Data
MSEG New
SAP Logistics with aggregates and indices SAP Simple Logistics
SAP S/4HANA – Simplified Data Model in Logistics
© 2015 SAP SE or an SAP affiliate company. All rights reserved. 21 PUBLIC
Traditional DB
Column store
Any attribute as an index
OLAP + OLTP together
Compression
on HANA
593 GB
118.6 GB
Data Footprint
© 2015 SAP SE or an SAP affiliate company. All rights reserved. 22 PUBLIC
Traditional DB on HANA S/4HANA
593 GB
118.6 GB
42.4 GB
BKPF BSEG BSEG BSEG BSIS BSIS BSIK BSET
COBK COEP LFC1 GLT0 GLT0 GLT0 COSP
MSTQH
MSTEH
MSTBH
MSSQH
MSSAH
MSPRH
MSLBH
MSKUH
MSKAH
MKOLH
MCHBH
MARDH
MARCH
MSTQ
MSTE
MSTB
MSSQ
MSSA
MSPR
MSLB
MSKU
MSKA
MKOL
MCHB
MKPF
MSEG
MARD
MARC
Master
Data
MSEG
New
SAP Logistics with aggregates and indices SAP Simple Logistics SAP Finance with aggregates and indices SAP Simple Finance
Data Footprint
© 2015 SAP SE or an SAP affiliate company. All rights reserved. 23 PUBLIC
on HANA S/4HANA Traditional DB
593 GB
118.6 GB
42.4 GB
Actual
8.4 GB
Data Footprint
The new Universal Journal
© 2015 SAP SE or an SAP affiliate company. All rights reserved. 25 PUBLIC
Accounting Before Simple Finance: Multiple sources of truth
Challenges:
The combined content of several
tables represents “the truth”.
Reconciliation efforts are enforced
by design
Need “to move” data to the
appropriate table for reporting (e.g.
“settlement”)
Different level of detail stored in the
respective components/tables
Components are structured
differently (e.g. fields/entities differ)
Different capabilities in the
components (customer fields,
currencies, multi-GAAP etc.)
Multiple BI extractors needed to
cover the complete truth in BI.
© 2015 SAP SE or an SAP affiliate company. All rights reserved. 26 PUBLIC
The New Architecture with Simple Finance: Universal Journal as
the Single Source of Truth
The new architecture
Motto: “Take the best of all worlds” (e.g.
ledger, market segment, coding block
etc.)
Secondary cost elements are G/L
accounts
One line item table with full detail for all
components
Data stored only once: no reconciliation
needed by architecture
Reduction of memory footprint through
elimination of redundancy.
Fast multi-dimensional reporting on the
Universal Journal possible without
replicating data to BI.
If BI is in place anyway, only one single
BI extractor needed (instead of many
today)
Technical preparation done to enhance
important structural capabilities of the
Financials solution (e.g. multi-GAAP,
additional currencies)
© 2015 SAP SE or an SAP affiliate company. All rights reserved. 27 PUBLIC
The new journal entry (header and item)
The new journal entry consists of a
header (table BKPF) and the respective
items (table ACDOCA)
There are rare cases, where entries in
ACDOCA are written without a document
header (e.g. carry forward, corrections in
migration). These entries do not represent
standard business processes.
The corresponding line items have ‘artificial
document numbers’ beginning with letters (e.g.
‘A’).
Table ACDOCA contains all fields needed
for G/L, CO, AA, ML, PA
Multi-GAAP capability through “RLDNR”
dimension
6 digit field for line item numbering
23 digits for currency fields
BKPF
ACDOCA
© 2015 SAP SE or an SAP affiliate company. All rights reserved. 28 PUBLIC
Simpler IT with SAP Simple Finance architecture
Before After
Separate systems with objects created in
advance and updated in batch
Consolidated financial system with no need for pre-
computed aggregates or ETL replication
Interface
Combined FI-CO Document
HANA Views on-the-fly
Interface
OM PA GL Cons SL A/P A/R
GL A/P A/R
FI CO
Aggregates
Indices
Financial
Documents
© 2015 SAP SE or an SAP affiliate company. All rights reserved. 29 PUBLIC
Non disruptiveness due to compatibility views
Safeguarding customer investments:
We provide so called “compatibility views”.
Via this views the select is redirected to the
new persistency in HANA
In the example given, an access to table
COEP is redirected via the view V_COEP to
the new Universal Journal Entry
Effect: Customer ABAP programs that read
directly “COEP” via select statements
continue to run as before
From the perspective of an ABAP program
“COEP” exists as before (read access)
© 2015 SAP SE or an SAP affiliate company. All rights reserved. 30 PUBLIC
Unified Master Data Maintenance for GL Account and Cost Element
– Details
Chart of Accounts covers balance sheet and all P&L accounts
Cost elements move into GL account logic that means
No time dependency for cost elements any longer
No default account assignments in cost element master
P&L accounts can be classified as cost elements that means cost elements
became GL accounts with a specific semantic
Cost element type remains. So secondary cost elements are still only posted from
CO allocations
Default account assignments maintained in cost element master are migrated to
OKB9
© 2015 SAP SE or an SAP affiliate company. All rights reserved. 31 PUBLIC
Merge of Cost Elements and Accounts –
Effects in Reporting
• Secondary cost elements appear in GL reporting.
• Postings on secondary cost elements are always balanced to zero
• In the past postings on secondary cost elements effecting GL reporting entities
(e.g. profit center, functional area) created real time integration postings.
• The real time integration mapped secondary to primary accounts.
• In the past postings on secondary cost elements appeared in GL reporting on
primary accounts.
• With SAP Accounting postings on secondary cost elements appear directly on the
secondary cost element in GL reporting.
• The P&L versions have to be updated accordingly
© 2015 SAP SE or an SAP affiliate company. All rights reserved. 32 PUBLIC
General Ledger: Technical Changes with Simple Finance 2.0
Comments
Data previously stored in FAGLFLEXA, FAGLFLEXT (carry
forward) is now stored in table ACDOCA.
Data of New G/L industry tables for Public Sector and Joint
Venture Accounting ( FMGLFLEXA/T, PSGLFLEXA/T,
JVGLFLEXA/T) is now stored in table ACDOCA.
Data of customer created New G/L tables ZZ<CUST>T,
ZZ<CUST>A is now stored in table ACDOCA.
A compatibility view is provided for table FAGLFLEXA:
FGLV_FAGLFLEXA. This compatibility view redirects select
statements to FAGLFLEXA to ACDOCA.
Compatibility views for the New G/L industry tables are
provided: V_<Industry>A, V_<Industry>T
Compatibility Views are provided for customer created New
G/L tables. The views are numbered sequentially:
ZFGLV_GLTT_Cx (totals) and ZFGLV_GLSI_Cx (line
items), where x is a number.
FAGLFLEXT
FAGLFLEXA
ACDOCA
ZZ<CUST>T
<Industry>T
ZZ<CUST>A
<Industry>A
© 2015 SAP SE or an SAP affiliate company. All rights reserved. 33 PUBLIC
FI Postings with Simple Finance 2.0
Accounting
Interface FI
“ACDOCA”
PCA
FI-SL
EC-CS
Comments
■ ACDOCA posted via the Accounting
Interface similarly to FAGLFLEXA (New
G/L) in the past. ACDOCA stores full
detail.
■ Former COEP, FAGLFLEXA, ANEP,
MLIT etc. data are stored in ACDOCA.
■ BSEG as before Simple Finance 2.0
■ PCA, FI-SL, EC-CS technically
untouched and work as before.
■ Components that have been build with FI-
SL technology like Joint Venture
Accounting, Public Sector etc. are
untouched and work as be fore.
■ Cost based CO-PA works as before.
“BSEG”
Cost Based CO-
PA
© 2015 SAP SE or an SAP affiliate company. All rights reserved. 34 PUBLIC
New Fixed Asset Accounting in the SAP Simple Finance add-on technical changes
ANEK
ANEP
ANEA
ANLP
ANLC
ACDOCA
BKPF
FAAT_DOC_IT
FAAT_PLAN_VALUES
Actual items
Actual data of ANEK, ANEP, ANEA,
ANLP, ANLC is now stored in table
ACDOCA. ANEK data is stored in
BKPF.
Compatibility views
FAAV_<TABLENAME> (e.g.
FAAV_ANEK) are provided to enable
non-disruptive reporting on old tables
After migration: access to content of
old tables is still possible via views
FAAV_<tablename>_ORI.
Non actual items: Statistical data (e.g. calulation or tax purposes)
is now stored in table FAAT_DOC_IT.
Plan data (previously ANLP and ANLC) is now
stored in FAAT_PLAN_VALUES
Year-dependent attributes of Fixed Assets are
now stored on FAAT_YDDA.
FAAT_YDDA
© 2015 SAP SE or an SAP affiliate company. All rights reserved. 35 PUBLIC
Controlling (CO): Technical Changes with SAP Simple Finance Add-On 2.0
Actual Items
Actual data of COEP (WRTTP = ‘04’ and ‘11’) is now
stored in ACDOCA
Needed actual data for long running orders/projects from
COSP_BAK, COSS_BAK is stored in table ACDOCA.
Currently, COBK is written as before. Target is to replace
COBK through BKPF.
Compatibility views V_<TABLENAME> (e.g. V_COEP)
are provided in order to reproduce the old structures.
Access to old data in tables still possible via the views
V_<TABLENAME>_ORI (e.g. V_COEP_ORI)
Non actual items
• Value types other than ‘04’ and ‘11’ are still stored in
COEP, COSP_BAK, COSS_BAK
COEP
COSP_BAK
COSS_BAK
COBK
ACDOCA
BKPF
© 2015 SAP SE or an SAP affiliate company. All rights reserved. 36 PUBLIC
Modify Operations on table COEP
Before Simple Finance 2.0:
With Simple Finance 2.0*:
With simple Finance, data previously
stored in table COEP is now stored in
table ACDOCA for value types ‘04’ and
‘11’. Other value types are still stored in
table COEP.
If customers have written programs
manipulating data in COEP directly e.g.
via INSERT statements , the
corresponding statements must be
replaced.
SAP provides the class
CL_FCO_COEP_UPDATE with the
methods INSERT, UPDATE, MODIFY,
DELETE for this purpose
On the left, you can find a coding example.
© 2015 SAP SE or an SAP affiliate company. All rights reserved. 37 PUBLIC
Material Ledger: Technical Changes with Simple Finance 2.0
Usage of Material Ledger for parallel currencies and
parallel valuation purpose
Contents of tables MLIT, MLPP, MLPPF, MLCR, MLCRF,
MLCD, CKMI1, BSIM is now stored in ACDOCA. MLHD
data is stored in BKPF
Compatibility views V_<TABLENAME> (e.g. V_MLIT) are
provided in order to reproduce the old structures
Access to old data in tables still possible via the views
V_<TABLENAME>_ORI (e.g. V_MLIT_ORI)
MLHD, MLIT, MLPP, MLCR still keep prima nota
information, in case of manual price changes or material
debit/credit.
Usage of Material Ledger for Actual Costing purpose
MLIT, MLIT, MLPP, MLPPF, MLCR, MLCRF, MLCD are
used as before Simple Finance 2.0
MLHD
MLIT
MLPP
MLPPF
MLCR
MLCRF
BSIM
CKMI1
MLCD
ACDOCA
BKPF
© 2015 SAP SE or an SAP affiliate company. All rights reserved. 38 PUBLIC
Prima Nota in Simple Finance 2.0
The Prima Nota is the source document that triggers the creation of Journal Entries. The Prima
Nota is the single anchor that allows e.g. to reverse the complete process triggered by the Prima
Nota.
The Prima Nota keeps the information that has been entered to the system, before derivations,
enrichments, splits etc. take place in Accounting in order to create Journal Entries.
In many cases the Prima Nota is a document outside Financials. Examples are Expense Reports,
Invoices, Payroll documents.
For posting within the Financials world a Prima Nota is needed as well.
For classical FI postings (FB01, FB50, FB60, FB70 etc.) the Prima Nota is still stored in table
BSEG and the corresponding Journal Entries (can be several due to the multi GAAP capability)
are written to table ACDOCA.
© 2015 SAP SE or an SAP affiliate company. All rights reserved. 39 PUBLIC
Prima Nota in Simple Finance 2.0
For classical (manual) “CO postings” like
• Re-posting of costs and revenues (KB* transactions)
• Manual activity allocation in CO ( AWTYP = “COBK” and VRGNG = “RKL”)
• Manual re-posting with reference (KB61, KB65)
• Manual allocations (KB15)
the Prima Nota is still written to table COEP. The corresponding journal entries are written to table
ACDOCA. The used value type for the Prima Nota in table COEP is
• U4 ‘Source Document - Actuals’
Note: A proper “CO document number” – using a CO number range object - is only needed for the described
case of a Prima Nota. In other cases, we use a transaction number (see section below).
For allocation postings (assessment, settlement etc.) no Prima Nota is required and data is
written to table ACDOCA only. The allocation process has its own history management, i.e.
canceling an allocation journal entry is done this way.
© 2015 SAP SE or an SAP affiliate company. All rights reserved. 40 PUBLIC
Prima Nota in Simple Finance 2.0
A Prima Nota is written as well in cases, where “CO” is triggered via BAPI interfaces (AWTYP <>
AFRU, CATS)
Material price changes (MR21) or Material Debit/Credit (MR22) create a Prima Nota in the
material ledger (tables MLHD, MLIT etc. ). The respective journal entries are posted to ACDOCA.
© 2015 SAP SE or an SAP affiliate company. All rights reserved. 41 PUBLIC
Result: Trial Balance with Many Drill-Downs
© 2015 SAP SE or an SAP affiliate company. All rights reserved. 42 PUBLIC
Result: Multi-Dimensional Income Statement
P&L Statement by Account
(structured by financial statement
version) Drill-down options provided by
SAP Simple Finance
Accounts and Cost Elements
© 2015 SAP SE or an SAP affiliate company. All rights reserved. 44 PUBLIC
ERP and SAP Accounting 1.0 Master Data for P&L Postings
Balance Sheet Accounts
P&L Accounts
Primary Cost Elements
Secondary Cost Elements
GL Accounts
Cost Elements
© 2015 SAP SE or an SAP affiliate company. All rights reserved. 45 PUBLIC
Merge of Account/Cost Element in Chart of Accounts
Balance Sheet Accounts
Non Operating Expenses/Revenues
Primary Cost Elements
Secondary Cost Elements
GL Account
Account Types:
• X: Balance Sheet
• N: Non operating
expenses/reveneus
• P: Primary costs /revenues
• S: Secondary cost elements
© 2015 SAP SE or an SAP affiliate company. All rights reserved. 46 PUBLIC
Unified Master Data Maintenance for GL Account and Cost Element – Account Type and Cost Element Specific Attributes
Asset Accounting
© 2015 SAP SE or an SAP affiliate company. All rights reserved. 48 PUBLIC
SAP Simple Finance add-on for SAP Business Suite powered by
SAP HANA 2.0 Scope
The new architecture prerequisites are
Usage of New Depreciation Calculation Engine is mandatory
Universal Entry is active (automatic migration)
The new architecture does not support (and vice-versa)
Joint Venture Accounting (JVA) (officially released for ledger-solution via Business Function as of EhP6) (2)
Lease Accounting Engine (LAE)
Real Estate Classic (RE Classic)
Public Sector Management – Funds Management (PSM-FM) using requests (1)
Application Link Enabling (ALE): transfer of assets
Transaction ABUB
Transition to new Asset Accounting by migration of
customizing data
transactional data
Can be activated after completed period end
(1) SAP Accounting powered by SAP HANA package 1.0 cannot be installed if any industry component is active / switched on
(2) Will be investigated to be supported in a future support package
© 2015 SAP SE or an SAP affiliate company. All rights reserved. 49 PUBLIC
New Fixed Asset Accounting in the SAP Simple Finance add-on technical changes
ANEK
ANEP
ANEA
ANLP
ANLC
ACDOCA
BKPF
FAAT_DOC_IT
FAAT_PLAN_VALUES
Actual items
Actual data of ANEK, ANEP, ANEA,
ANLP, ANLC is now stored in table
ACDOCA. ANEK data is stored in
BKPF.
Compatibility views
FAAV_<TABLENAME> (e.g.
FAAV_ANEK) are provided to enable
non-disruptive reporting on old tables
After migration: access to content of
old tables is still possible via views
FAAV_<tablename>_ORI.
Non actual items: Statistical data (e.g. calulation or tax purposes)
is now stored in table FAAT_DOC_IT.
Plan data (previously ANLP and ANLC) is now
stored in FAAT_PLAN_VALUES
Year-dependent attributes of Fixed Assets are
now stored on FAAT_YDDA.
FAAT_YDDA
© 2015 SAP SE or an SAP affiliate company. All rights reserved. 50 PUBLIC
New architecture in FI-AA - Overview From Operational Entry to multiple accounting-principle-specific Parallel Documents (Integrated Asset Acquisition)
Rules:
Operational Entry Document posts to technical clearing account.
Operational Entry Document never updates the asset, asset is used for checks only
The entry document triggers the creation of (1 to n) accounting principle specific documents.
The accounting principle specific documents clear the technical clearing account in each view (balance zero)
post to the asset reconciliation account and update the asset subledger
© 2015 SAP SE or an SAP affiliate company. All rights reserved. 51 PUBLIC
Document Entry: 31 K Vendor 160000 (Payable) 10.200
70 A Asset FIAA-1000-0 PRCTR1 KOSTL1
Generated documents:
Financial Accountant
40 S GL 4xxxxxx (freight expense) 200
75 A Asset 13000 (Machines) PRCTR1 KOSTL1
LGAAP Freight costs are not capitalized in the local
GAAP (New Transaction: Post only to accounting
principle LGAAP)
Integrated Acquisition with ledger approach to parallel valuation (different amounts to be capitalized due to accounting principle) (1)
© 2015 SAP SE or an SAP affiliate company. All rights reserved. 52 PUBLIC
Integrated Acquisition with ledger approach to parallel valuation (different amounts to be capitalized due to accounting principle) (2)
Asset Reconcilation. Tech.Clear.Acc.Acqu.
Asset Reconcilation
AP Reconcilation
Transaction vendor invoice
1) „‘Technical Clearing Account Acquisition‘ to Vendor“ LG Blank
2a) „Asset to ‘Technical Clearing Account Acquisition‘“ LG IFRS
2b) „Asset to ‘Technical Clearing Account Acquisition‘“ LG LGAAP
Transaction (AB01L) correction freight cost
3) „Freight expenses to Asset“ LG LGAAP
2a) 10.200 2a) 10.200 1) 10.200 1) 10.200
1) 10.200 1) 10.200 2b) 10.200 2b) 10.200
IFRS
LGAAP
Freight expenses
3) 200 3) 200
Technical account balances to zero
Accounting Principle specific documents
Using different reconciliation account per accounting
principle is possible
© 2015 SAP SE or an SAP affiliate company. All rights reserved. 53 PUBLIC
New Fixed Asset Accounting in the SAP Simple Finance add-on Changes for the user
Document Entry:
Accounting principle and/or depreciation area can be entered on the screen
Transaction types restricted to areas not necessary and not supported anymore
Optional display of asset-view of journal entries/complete business transaction
Document Display:
Optional display of asset-view of journal entries/complete business transaction
Asset Explorer:
Hierarchical view on depreciation areas
Seamless drilldown to valuating journal entries
Depreciation Run:
Selection screen is simplified
posting document is updated in Financial Accounting at asset level
Period end closing can be performed even if there are errors on individual assets
© 2015 SAP SE or an SAP affiliate company. All rights reserved.
Martin Schmidt
SAP Slovensko s.r.o.
Plynárenská 7/A
Bratislava, Slovensko
Thank You!