Unit 2.

1 : Overview of the SAP Simple Finance On-Premise Edition 1503

Providing a Technical Overview of the Implementation Prerequisites

Related Product Versions

Support Package Stack (SPS) Dependencies

Dependencies to other ERP components

Upgrade Paths to the SAP Simple Finance On-Premise Edition 1503

Required Admin Know-how
Unit 2.2 Describing the Architecture of SAP Simple Finance
SAP Accounting Architecture Rational

A true single source of truth for all accounting components.

Reconciliation is a topic of the past bringing large cost and time savings.

A simple but holistic data model.

HANA can be leveraged in the best possible manner bringing unprecedented
insight (in both speed and content!).

The universal journal combines and harmonizes the good qualities of all
accounting components.
The simplification of the application is a required step and a great foundation
for further enhancements.

Non-disruptive innovation and simplification.

SAP strives to provide a true next generation application with the least possible
Disruption, safeguarding customer investments and processes.

Traditional Architecture- Multiple Data Sources

New Architecture- Universal Journal as the Single Source

One line item table with full detail for all components.
Data stored only once, so no reconciliation needed by architecture.

Fast multi-dimensional reporting on the Universal Journal possible

without replicating data to Bl. If Bl is in place, one single Bl extractor
is needed.

Reduction of memory footprint through elimination of redundancy.

Technical preparation done to enhance important structural

capabilities of the Financials solution (e.g. multi-GAAP, additional
currencies)
Non-disruptiveness

Existing programs and interfaces can still be used access via compatibility
views:

Read access from custom ABAP programs or reports to prior tables will
work as before

Read access is automatically re-directed to the universal journal as the

new single source of truth

All programs with write access to those deleted tables replaced by CDS
views will make trouble and can't be used anymore without adaption.

Remove all write accesses in by views replaced tables.

Use the code inspector to find all affected parts of the code (see note
1976487).
List of Tables Replaced by Compatibility Views
Universal Journal extensibility

The Universal Journal can be easily extended with customer fields.

Extensibility is available for all components that use the Universal

Journal (G/L, CO, AA, ML).

P&L line extension using "CO-PA capabilities" is provided, both for

field definition (characteristics) and the rich derivation tools from
CO-P A.

The standard General Ledger coding block extensibility can be

used and affects the Universal Journal

The new HANA based reporting of all components (GIL, AA, ML,
CO) can access the customer fields.
 Unit 2.3 Analyzing the Universal Journal

Universal Journal Entry:

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 respective 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).

ACDOCA table contains all fields needed for GIL, CO, AA, ML, PA

All cost elements, including secondary cost elements are GL

accounts

Multi-GAAP capability through "RLDNR" dimension

6 digit field for line item numbering

23 digits for currency fields

Document Numbers in Simple Finance