Documenti di Didattica
Documenti di Professioni
Documenti di Cultura
Introduction
• The SAP Simple Finance solution marked the first step in our SAP
S/4HANA road map for customers. The solution has demonstrated
the value of simplification (for example, no indexes, no aggregates,
and no redundancies) and instant insight in Finance. SAP S/4HANA,
on premise edition leverages the full scope of SAP Accounting
powered by SAP HANA included in SAP Simple Finance.
Central journal to get a consolidated, real-time view of the Separate entries in each process.
state of the business across all entities; this was simply not Integration via reports
possible before
71% faster batch input processing in financial close Only extensive transactions and
40% less posting corrections in financial close batch processing, no real-time
400 hours less processing time at quarter-end close simulation
AP GL JV
CO Universal
Custom
FA Journal
CO-
ML AR PA
SAP S/4HANA: FINANCE CAPABILITY
Please explain Simple Finance architecture
• 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.
• 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
SAP S/4HANA: UNIVERSAL JOURNAL
Please provide the architecture of Universal Journal
Architecture
Concept: “Take the best of all
worlds” (e.g. ledger, market
segment, coding block, etc.)
ONE line item table with full detail
for all applications - for instant
insight & extensibility
This replaces the “logical
document” of release 1.0.
Secondary cost elements are G/L
accounts.
Data stored only once: no
reconciliation needed by design
Reduction of memory footprint
through elimination of
redundancy.
Fast multi-dimensional reporting
possible without replicating data
to business warehouse (BW).
If BW is in place anyway, only one
single BI extractor needed
(instead of many today).
SAP S/4HANA: NEW ASSET ACCOUNTING
• Removal of redundancies:
• Reconciliation between G/L and AA is ensured by design!
• No reconciliation-step in financial close needed anymore.
• All non-statistical items are updated as Universal Journal Entries.
• Reporting based on line items – removal of totals
• Depreciation in full detail
• Depreciation posting per single asset
• Reporting on any CO-object by single asset enabled
• Fast close and Soft close
• Plan values at real-time – updated with every master data change and every asset
transaction
• Speed up of depreciation run by a factor of 4,7
• Posting run fully obsolete: real-time update of assets in all cases.
SAP S/4HANA: CASH MANAGEMENT
What are the New features in Cash Management?
Classic Cash Management is replaced by the new SAP Cash Management powered by SAP HANA.
Following areas have improved usability , new Fiori apps are available
• Embedded end-to-end planning process utilizes real time operational data from
ERP, eliminating redundancy / reconciliations between forecasting and operational
systems.
• All data stored in a single table in memory allowing for various data forms,
volumes, and configurations at the desired level of granularity.
• Complete planning app that supports plan development as well as the ability to
enter and report upon planned data.
• Migration of financial data (for GL/AP/AR/CO) – due to dropped totals tables, etc.
Data Migration • Reconciliation & checks after migration
• http://scn.sap.com/community/s4hana
• http://s4hana.sapjourneymap.com
• https://training.sap.com/shop/learninghub
FOLLOW US
Follow us on at @ASUG365
APPENDIX – S/4HANA TECHNICAL CHANGES
• Index tables removed Aggregate tables removed
BSIS Index for G/L Accounts GLT0 General Ledger: Totals
BSAS Index for G/L Accounts (Cleared Items) GLT3 Summary Data Preparations for Consolidation
BSAD Index for Customers (Cleared Items) KNC1 Customer master (transaction figures)
Actual items
ANEK
Actual data of ANEK, ANEP, ANEA, ANLP, ANLC
is stored in table ACDOCA. ANEK data is stored
in BKPF.
ANEP Compatibility views FAAV_<TABLENAME> (e.g.
BKPF FAAV_ANEK) are provided in order to
reproduce the old structures.
Access to old data in tables still possible via the
ANEA ACDOCA views FAAV_<TABLENAME>_ORI (e.g.
FAAV_ANEA_ORI)
Non actual items
ANLP FAAT_DOC_IT
Statistical data (e.g. for tax purposes)
FAAT_PLAN_VALUES previously stored in ANEP, ANEA, ANLP, ANLC
is now stored in table FAAT_DOC_IT
ANLC Plan data previously stored in ANLP and ANLC
is now stored in FAAT_PLAN_VALUES
CONTROLLING (CO): TECHNICAL CHANGES WITH SIMPLE FINANCE 2.0
Actual Items
COBK Contents of COEP,
Needed actual data for long running
orders/projects from COSP_BAK, COSS_BAK is
BKPF stored in table ACDOCA. Currently, COBK is
COEP written as before. Target is to replace COBK
through BKPF.
ACDOCA Compatibility views V_<TABLENAME> (e.g.
V_COEP) are provided in order to reproduce
COSP_BAK the old structures.
Access to old data in tables still possible via the
views V_<TABLENAME>_ORI (e.g.
V_COEP_ORI)
COSS_BAK Non actual items
Value types other than ‘04’ and ‘11’ are still
stored in COEP, COSP_BAK, COSS_BAK
GENERAL LEDGER: TECHNICAL CHANGES WITH SIMPLE FINANCE 2.0