Académique Documents
Professionnel Documents
Culture Documents
SAP S4 Hana represents the next generation & latest evolution of SAP’s core
application platforms with redesign & reengineering to exploit the in-memory
capabilities of the SAP Hana Data base. SAP Hana database with in-memory
computing power to process huge amount of data for analysis in a very short
period. SAP database supports columnar database tables and can move the logic
to the database layer through stored procedures.
S/4 HANA is natively built on SAP HANA with simplified data model, without
indices, aggregates and no redundancies. It leverages the multi tenancy
functionality of SAP HANA. It can be deployed on premise, cloud or
mixed/hybrid. It is natively designed with SAP Fiori offering an integrated user
experience.
The Design of SAP HANA allows it to drastically boost speed for both Online
Transaction Processing (OLTP) and Online Analytical Processing (OLAP). HANA,
on the other hand, is column-oriented and combines OLAP and OLTP into a
single structure, cutting memory usage by a factor of 10 or more and improving
performance.
S/4HANA is designed to use Fiori UX. Customers can still use the old user
interface during the transition, however they’ll be able to take advantage of the
power and flexibility offered in HANA S/4 with Fiori. For some organizations, the
current S/4 features may not outweigh the added complexity of moving past
ECC. As time passes and new SAP S/4HANA functions are added, the benefits of
moving away from Business Suite on HANA to S/4 will increase for a greater
range of organizations.
Enhanced functionality of SAP S/4HANA
The greatest benefits of SAP S/4HANA over Business Suite on HANA lie in
financial management and accounting. SAP S/4HANA Finance is designed to
cover the full range of finance tasks, including planning, analysis, accounting,
compliance and risk management. According to SAP chairman Hasso Plattner,
the HANA S/4 finance app can shrink data more than 10 fold, from 593 GB to 42
GB, “with only 8.4 GB being dynamic, current-year data requiring high
availability and backups.”
SAP S4 Hana builds on the well proven functional base of SAP Business Suite
and can be introduced in an evolutionary, gradual and selective way into an
existing SAP environment.
Key benefits of S4 Hana:
Providing real time reporting & single version of truth via SAP Hana live,
SAP Fiori applications & Universal Journal.
Bringing many data sources from inside & outside the business into SAP
Hana platform for real insight.
Building business rules in the platform, including embedded analytics, to
create new optimized & innovative business process.
Optimizing & simplifying the business model that is embedded SAP BPC
for S4 Hana Finance, including removal of unnecessary steps & batch
processing.
Using simplified user interface (UI)
Universal journal
Universal journal is the single source of truth for the accounting in SAP S/4 HANA
Finance (Simple finance). It combines documents journals from Financial Accounting
(FI) and Controlling (CO), removing the necessity of reconciliation between these
modules.
Following components are using the Universal Journal:
General ledger
Asset Accounting
Controlling
Profitability analysis (account based)
Material ledger
Single journal entry with all required information is created for the relevant components
(figure 2).
From the technical perspective the universal journal entry consists of the header (table
BKPF) and related items (table ACDOCA, figure 1). The items table is ledger dependent,
which enables a multi GAAP capability. No totals tables are used as aggregated
information can be calculated on the fly due to SAP HANA superior performance
capabilities. This allows to have a very detailed level of information for reporting and
analysis purposes.
Figure 1: ACDOCA table combines data fields from various components.
Figure 2: Depreciation posting example in ACDOCA table (fields related to GL, AA, CO).
The creation of an entry in the Universal journal is based on the source document. The
source document stores the initial information entered into the system before any
derivations, enrichments or splitting take place in Accounting for the purpose of the journal
entry creation. Below are the examples of the source documents and their respective
tables in FI/CO:
For the FI postings source document is stored in BSEG table. The BSEG table has
been converted to a transparent table.
For the manual CO postings source document is stored in COEP table. Entries can
be viewed via the V_COEP_ORI view.
For the Material price change transaction source document is stored in material
ledger tables (MLHD, MLIT, MLCR, …). BSEG document is also created.
For all these documents corresponding entries are created in the Universal journal.
Old FI/CO totals and index tables were removed to avoid data redundancy. But in order to
maintain compatibility with the traditional programs, corresponding compatibility views were
created.
Business Benefits:
The role of the CFO today is broader & more complex than ever before. The CFO
is not restricted to optimizing operations such as paying bills, closing the books
& producing financial results. Today CFOs are expected to develop new
approaches to manage their organisation, produce business insights on a daily
basis, spot market opportunities, predicting changes in business environment &
driving business to growth. With a view to addressing the information
requirements due to this shift, SAP has introduced S4 Hana finance its first
module for transactional simplicity & advanced analytics in the new SAP S4 Hana
offering. Although covering key functionalities such Universal Journal, Appendix
ledger, the new asset accounting, accelerated close, SAP S4 Hana finance is all
about creating a simplified UX.
Impact on Controlling:
Controlling contains internal accounting data & the account assignment objects
needed to produce management-oriented reports & analysis.
In S4 Hana, Accounting docs are posted using common doc number. The
FI document for P&L account still generates CO documents. To maintain
CO consistency & Compatibility views, the document type & document
number customizing settings are maintained for internal CO postings & to
assign actual version of CO to the Ledger. With the integration of FI & CO,
there is no requirement for reconciliation ledger going forward.
With the S4 Hana Finance, Totals table (COSP & COSS) are no longer
required. Only Line Item Table COEP to store actual data. Two new tables
COSP_BAK & COSS_BAK have been created to store planned data related
to primary & secondary costs, respectively.
Cost elements are no longer required in SAP S4 Hana, because they are
created as GL accounts using transaction FS00 & are part of chart of
accounts. A new field for the cost element category has been introduced
in the GL master record. The default account assignment is maintained
using transaction OKB9.
With the introduction of UNIVERSAL JOURNAL in SAP S4 Hana Finance, all
the CO postings are posted directly to the Universal Journal entries.
Secondary Cost elements are now part of GL accounts in FI & do not
require separate assignment in CO. So there is only One Allocation.
T codes like KA01, KA03, KA06, KKC1, etc. are no longer required.
In SAP S4 Hana, you need to define a ledger that represents CO that by
assigning version 0 to a ledger. This is done at co-code level but needs to
be same for all co-codes.
In SAP S4 Hana, Leading ledger is assigned to version 0 for all Co-Codes
which are assigned to a controlling area.
General Ledger Planning & Cost element planning are now part of SAP
business Client.
Post-migration Testing:
Test SAP Hana optimized transactions
Test Multi-dimensional Reporting Capability
Test data base Foot print reduction.
Test Inter-Co reconciliation.
Test Closing environment
Test Universal Journal
Execute Change Management