S4F01
Financial Accounting in SAP
S/4HANA for SAP ERP FI
Professionals
.
.
PARTICIPANT HANDBOOK
INSTRUCTOR-LED TRAINING
.
Course Version: 17
Course Duration: 2 Day(s)
e-book Duration: 5 Hours
Material Number: 50155806
SAP Copyrights, Trademarks and
Disclaimers
© 2020 SAP SE or an SAP affiliate company. All rights reserved.
No part of this publication may be reproduced or transmitted in any form or for any purpose without the
express permission of SAP SE or an SAP affiliate company.
SAP and other SAP products and services mentioned herein as well as their respective logos are
trademarks or registered trademarks of SAP SE (or an SAP affiliate company) in Germany and other
countries. Please see http://global12.sap.com/corporate-en/legal/copyright/index.epx
for additional
trademark information and notices.
Some software products marketed by SAP SE and its distributors contain proprietary software
components of other software vendors.
National product specifications may vary.
These materials may have been machine translated and may contain grammatical errors or
inaccuracies.
These materials are provided by SAP SE or an SAP affiliate company for informational purposes only,
without representation or warranty of any kind, and SAP SE or its affiliated companies shall not be liable
for errors or omissions with respect to the materials. The only warranties for SAP SE or SAP affiliate
company products and services are those that are set forth in the express warranty statements
accompanying such products and services, if any. Nothing herein should be construed as constituting an
additional warranty.
In particular, SAP SE or its affiliated companies have no obligation to pursue any course of business
outlined in this document or any related presentation, or to develop or release any functionality
mentioned therein. This document, or any related presentation, and SAP SE’s or its affiliated companies’
strategy and possible future developments, products, and/or platform directions and functionality are
all subject to change and may be changed by SAP SE or its affiliated companies at any time for any
reason without notice. The information in this document is not a commitment, promise, or legal
obligation to deliver any material, code, or functionality. All forward-looking statements are subject to
various risks and uncertainties that could cause actual results to differ materially from expectations.
Readers are cautioned not to place undue reliance on these forward-looking statements, which speak
only as of their dates, and they should not be relied upon in making purchasing decisions.
© Copyright. All rights reserved.
iii
Typographic Conventions
American English is the standard used in this handbook.
The following typographic conventions are also used.
This information is displayed in the instructor’s presentation
Demonstration
Procedure
Warning or Caution
Hint
Related or Additional Information
Facilitated Discussion
User interface control
Example text
Window title
Example text
© Copyright. All rights reserved.
iv
Contents
vi
Course Overview
1
Unit 1:
Overview of Financials for SAP S/4HANA
2
Lesson: Explaining the Purpose and Functions of SAP HANA and
SAP S/4HANA
12
17
22
Lesson: Describing the New Architecture of Accounting
Lesson: Explaining the Purpose and Functions of SAP Fiori
Lesson: Outlining the Migration of Financials to SAP S/4HANA
32
Unit 2:
33
Lesson: Managing GL Accounts and Cost Elements in SAP S/
4HANA
Lesson: Managing Ledgers in SAP S/4 HANA
42
62
Unit 3:
63
72
79
Asset Accounting
Lesson: Analyzing the Posting Logic of New Asset Accounting
Lesson: Legacy Data Transfer Asset Accounting SAP S/4HANA
Unit 4:
80
87
91
General Ledger Accounting
Reporting Options
Lesson: Providing an Overview of Reporting Options
Lesson: Manage Global Hierarchies
Unit 5:
92
95
© Copyright. All rights reserved.
Basic Cash Management Capability
Lesson: The Basic Cash Management Capability
Lesson: Bank Account Processing with Bank Reconciliation
Accounts
v
Course Overview
TARGET AUDIENCE
This course is intended for the following audiences:
Application Consultant
Support Consultant
Super / Key / Power User
© Copyright. All rights reserved.
vi
UNIT 1
Overview of Financials
for SAP S/4HANA
Lesson 1
Explaining the Purpose and Functions of SAP HANA and SAP S/4HANA
2
Lesson 2
Describing the New Architecture of Accounting
12
Lesson 3
Explaining the Purpose and Functions of SAP Fiori
17
Lesson 4
Outlining the Migration of Financials to SAP S/4HANA
22
UNIT OBJECTIVES
Explain the purpose and functions of SAP HANA and SAP S/4HANA
Explain the idea and concept of the universal journal
Explain how SAP safeguards customer investments
Outline the architectural changes in SAP S/4HANA
Explain SAP Fiori applications and tools
Describe the migration process
© Copyright. All rights reserved.
1
Unit 1
Lesson 1
Explaining the Purpose and Functions of SAP
HANA and SAP S/4HANA
LESSON OBJECTIVES
After completing this lesson, you will be able to:
Explain the purpose and functions of SAP HANA and SAP S/4HANA
SAP S/4HANA Finance Learning Journey
Figure 1: Financial Accounting Learning Journey
Learning Journeys are visual guides, designed to help you complete the learning path for
particular SAP solutions. The easiest way to find learning journeys is to search for SAP
Learning Journeys in your browser.
© Copyright. All rights reserved.
2
Lesson: Explaining the Purpose and Functions of SAP HANA and SAP S/4HANA
SAP S/4HANA - The Digital Core
Figure 2: The Connected Digital World
The world has continued to change and presenting more and more business challenges and
opportunities. Today's world is digital and networked.
The pace of data generation is accelerating - in the last two years, 90% of world data has
been generated.
Over the next two years, there will be 40% growth in the adoption of business networks.
By the end of the decade, 212 billion things, from cars, to heavy equipment, to consumer
appliances, will be connected to the internet.
By 2020, there will be 9 billion mobile users in the world
Last year alone, 51% of workloads were processed in the cloud. That amount will only grow
for the foreseeable future.
© Copyright. All rights reserved.
3
Unit 1: Overview of Financials for SAP S/4HANA
Advances in Technology
Figure 3: Advances in Technology
In the last few years there have been significant advances in technology that application
developers are able to take advantage of to build smarter and more powerful applications.
The following are some examples of smarter and more powerful applications:
Multi-core processors enable parallelism of tasks, which means more throughput of data
and faster processing to give us real-time responses.
Large memory enables us to fit an entire organization's database in memory so that we
lose the mechanical spinning disk and the latency it brings.
Advances in the design of on-board cache means that data can pass between memory and
CPU cores rapidly. In the past, even with large memory, this was a bottleneck, as CPUs
were demanding more data and the journey from memory to CPU was not optimal.
We can now easily slot in more servers into our landscape to add more processing power
or memory in order to scale to any size.
SAP re-wrote their business application software to fully exploit the new hardware. SAP
worked closely with leading hardware partners who shared the product blueprints of their
new CPU architectures so that SAP knew how to write the very best modern software to
extract every drop of power.
Cloud computing technology has matured in the last few years and is now a compelling
deployment option for our customers who do not want to take on the complexity and cost
of the installation and maintenance of IT landscapes. Virtualizing machines means lower
costs of running enterprise-wide applications. Public cloud services based on subscription
models increase access to the latest solutions for everyone, reducing costs, and
simplifying everything.
© Copyright. All rights reserved.
4
Lesson: Explaining the Purpose and Functions of SAP HANA and SAP S/4HANA
Trade-Off – Broad and Deep or Speedy and Simple
Figure 4: Trade-Off – Broad and Deep or Speedy and Simple
With the traditional system architecture, you have to make a trade-off between Broad and
Deep Analysis or Speedy and Simple reporting.
With old technologies, optimizing across the five dimensions shown in the figure, Trade-Off –
Broad and Deep or Speedy and Simple, is not possible. Therefore, you can decide to go deep
and broad with your business warehouse systems or have high speed but simple reports from
your data.
In both scenarios, real time updates are difficult, almost impossible to design. In a data
warehouse environment, updates occur overnight with nightly batch jobs.
SAP HANA Handles Transaction and Analysis from a Single Data Model
Figure 5: SAP HANA Handles Transaction and Analysis from a Single Data Model
For more than 20 years, organizations have been using specialist software – usually with
additional hardware – to extract, transform, and load (ETL) data from transactional systems
© Copyright. All rights reserved.
5
Unit 1: Overview of Financials for SAP S/4HANA
to dedicated reporting systems. Based on the technology available at the time, this was the
optimal way to provide a holistic view of business data with good response times (especially
when you add accelerator software/hardware).
Online transactional processing (OLTP) was separated from online analytic processing
(OLAP). The reason for this lies in the database design of OLTP and OLAP. Quite simply, a
database model was either built for OLTP optimization or OLAP optimization, but not both.
However, this also bought with it complexity, redundancy, and, of course, latency. It was usual
for today’s business figures to be only available tomorrow for analysis once the data was
extracted and loaded to a reporting system.
A database that supports SAP S/4HANA (SAP HANA) can handle both OLTP and OLAP
processing from a single data model and, therefore, we do not need to move transactional
data to a separate system. This means transactional and analytical applications run off the
same tables and therefore data is available in real-time at every level of detail.
Remove Complexity with SAP S/4HANA
Figure 6: Remove Complexity with SAP S/4HANA
Traditional applications were built on a hierarchical data model. Detailed data was
summarized into higher level layers of aggregates to help system performance. On top of
aggregates we built more aggregates and special versions of the database tables to support
special applications. So, as well as storing the extra copies of data, we also had to build
application code to maintain extra tables and keep them up to date. Database indexes
improve access speed because they are based on common access paths to data. However,
they must be dropped constantly and rebuilt each time the tables are updated and therefore
more code is required to manage this process.
The traditional data model is complex, and a complex data model causes the application code
to be complex. It has been found that up to 70% of application code is built specifically for
performance of an application and adds no value to the core business function. With a
complex data model and complex code, integration with other applications and
enhancements are difficult. They are simply not agile.
Using the raw power of SAP HANA, we can aggregate on the fly in sub seconds from any line
item table. We don't need pre-built aggregates. SAP HANA can generate any view of the data
© Copyright. All rights reserved.
6
Lesson: Explaining the Purpose and Functions of SAP HANA and SAP S/4HANA
at runtime, all from the same source tables. SAP HANA organizes data using column stores,
which means indexes are usually not needed; they can still be created but usually offer minor
improvement. So, in addition to losing the aggregates and indexes from the database, we can
remove huge amounts of application code that deals with aggregates and indexes. We are left
with a simplified core data model and also simplified application code. Now, it is much easier
to enhance the applications and integrate additional functions.
SAP S/4HANA Core and Lines of Business Solutions
Figure 7: SAP S/4HANA Core and Lines of Business Solutions
SAP S/4HANA is not a single product but covers many applications. Customers can start with
the basic components and add to them later. S/4HANA is a great place to start. This is known
as the simplified core and can be considered as the replacement for SAP ERP. Here we find
support for all core business processes, such as quotation to cash, procure to pay, and so on.
For many customers, this is where their SAP S/4HANA adoption begins.
SAP S/4HANA can be easily integrated with SAP S/4HANA LOB solutions. These options can
be added at any time and provide best-in-class lines of business solutions and connections to
SAP Business Networks. Customers can choose the LOB solutions that suit their businesses.
SAP S/4HANA is built natively and optimally to run only on the SAP HANA platform.
© Copyright. All rights reserved.
7
Unit 1: Overview of Financials for SAP S/4HANA
SAP S/4HANA Deployment Options
Figure 8: Relationship Between SAP ERP and SAP S/4HANA
In SAP S/4HANA, there is the on-premise edition and the cloud edition. However, customers
often use hybrid scenarios. In the hybrid scenario, the customer has central base (an onpremise installation) as well as access to the cloud. An example of this hybrid scenario occurs
when new subsidiaries of the customer use the cloud installation for SAP S/4HANA (instead
of on-premise) for their own business areas.
An on-premise installation provides considerable control and flexibility. The customer informs
a consultant about the requirements of their project, and the consultant customizes the
platform based on these requirements. In the end, the customer has a highly customized
solution that matches their requirements. The solution fits to their existing processes as
closely as possible.
The cloud edition has a different installation process. In most situations, customers decide to
use the cloud solution because they want to eliminate all the customizing options. They want
to be more efficient in the implementation phase and to be even more efficient for future
upgrades.
Most importantly, the customer does not have access to the Implementation Guide in the
cloud edition. The personalization of an SAP S/4HANA cloud solution is performed with a selfservice configuration SAP Fiori Uniform Resource Identifier (URI). The URI is found in the
Manage Your Cloud User Interface in the SAP S/4HANA solution. That means that the
flexibility of the cloud solution is defined by self-configuration SAP Fiori URIs. While there are
also some possibilities of extensibility, the organization defines what changes are allowed with
extensibility.
© Copyright. All rights reserved.
8
Lesson: Explaining the Purpose and Functions of SAP HANA and SAP S/4HANA
Figure 9: SAP S/4HANA Consistent Choice for Cloud and On-Premise
The SAP S/4HANA simplified data model and modern user experience are consistent for both
cloud and on premise. When it's time to deploy SAP S/4HANA, the choices are on premise or
in the cloud. Either way, SAP S/4HANA maintains consistency with the data model, user
experience, and code line. SAP S/4HANA and SAP S/4HANA Cloud offer a consistent
solution, allowing you to benefit in any scenario or combination.
There are many factors in making the on premise or cloud deployment decision, but they can
be simplified into a few major dimensions:
IT Strategy:
Increasingly, customers are taking a "cloud first" approach to their ERP system landscape.
It is important to verify that the scope of the standard best practices in SAP S/4HANA
Cloud will serve your business requirements, and whether this should be complemented
with extended functionality (Lines of business, industry-specific) via a co-deployment with
SAP S/4HANA Cloud, single-tenant edition, for example.
Innovation Cycles:
Updates to SAP S/4HANA Cloud are provided on a quarterly innovation cycle. SAP
regularly delivers the latest in machine learning, natural language processing, predictive
analytics, and more in a non-disruptive, easy-to-consume manner. SAP S/4HANA Cloud,
single-tenant edition is offered with two upgrades per year, while SAP S/4HANA onpremise is offer with one annual upgrade.
Business Functionality:
The available scope for each deployment option will vary, allowing choices for licensing and
deployment.
Deployment times:
The deployment of SAP S/4HANA can be accelerated in the cloud for many customers,
since they do not need to acquire and maintain infrastructure.
Regulatory, industry, and regional requirements:
Some customers may have requirements in these areas that make cloud unsuitable. If this
is the case, then they can continue with traditional on premise deployment. Or, if they have
© Copyright. All rights reserved.
9
Unit 1: Overview of Financials for SAP S/4HANA
differing requirements for various subsidiaries, they can mix-and-match cloud and on
premise deployment in a two-tier strategy and still maintain consistency for IT and
business users.
SAP believes all customers will eventually run their ERP in the public cloud to take advantage
of the power of agile standardization.
Not every company is ready to make that move today, so SAP provides choices:
SAP S/4HANA Cloud: The fastest path to the intelligent enterprise.
SAP S/4HANA: Offers the customer complete control - on-premise, through hyperscalers,
on SAP HANA Enterprise Cloud.
All options utilize the same code line, data model, and user experience.
Figure 10: Three SAP S/4HANA Deployment Options
SAP S/4HANA deployment options are:
SAP S/4HANA Cloud option has highly standardized processes and allows only a limited
set of customizing.
SAP S/4HANA Cloud single - tenant edition options, which leverage the full functional
scope, extensibility options and localizations of the S/4HANA on premise code line in
combination with infrastructure and services in one subscription pricing. SAP offers
standardized system landscapes and functionality packages.
SAP S/4HANA as an on-premise next generation ERP system on top of the platform SAP
HANA. For a customer-specific cloud offering, the customer can either bring his own
licenses or license via subscription model. He can combine these with customer individual
infrastructure and optional application management services. This model will still be in
place and cover those cases, where the customer has very individual needs.
Please note, in the figure, the level of standardization decreases from left to right, while the
complexity and costs increase.
It is important for companies, especially installed base customers of SAP, considering S/
4HANA Cloud to review whether fit-to-standard based on the available scope of the solution
will serve their business needs by exploring the Best Practice Explorer, https://
rapid.sap.com/bp/ . Companies can efficiently extend solutions through SAP Cloud Platform,
which maintains integration and interfaces as a service, unlike costly to maintain
© Copyright. All rights reserved.
10
Lesson: Explaining the Purpose and Functions of SAP HANA and SAP S/4HANA
customizations in the on-premise past; or through a hybrid deployment with SAP S/4HANA
or SAP S/4HANA Cloud, single-tenant edition, based on a company's business or regulatory
requirements. In any scenario, you benefit from a complete, consistent choice.
LESSON SUMMARY
You should now be able to:
Explain the purpose and functions of SAP HANA and SAP S/4HANA
© Copyright. All rights reserved.
11
Unit 1
Lesson 2
Describing the New Architecture of Accounting
LESSON OBJECTIVES
After completing this lesson, you will be able to:
Explain the idea and concept of the universal journal
Explain how SAP safeguards customer investments
Outline the architectural changes in SAP S/4HANA
Universal Journal
Scenario
You want to understand the underlying architectural changes to the SAP ERP application after
the installation of SAP S/4HANA Finance. You want to understand the potential benefits
these changes bring and also make sure that your custom developments are not disrupted
because of the migration.
SAP Accounting Architecture Rational
The architecture for SAP S/4HANA has the following features:
There is a true single source of truth for all accounting components.
Reconciliation is a topic of the past that brings large cost and time savings.
It provides a simple but holistic data model.
SAP S/4HANA can provide 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.
There is non-disruptive innovation and simplification.
SAP strives to provide a true next generation application with the least possible disruption,
safeguarding customer investments and processes.
© Copyright. All rights reserved.
12
Lesson: Describing the New Architecture of Accounting
Figure 11: Challenges of the Architecture Before SAP S/4HANA Finance
Multiple sources of truth result in the following challenges:
The combined content of several tables represents the truth. Reconciliation efforts are
needed by architecture.
Different levels of detail are stored in the respective components or tables.
Components are structured differently. For example, fields and entities differ.
Users must move data to the appropriate table for reporting (for example, settlement).
There are different capabilities in the components (customer fields, currencies, multiGAAP, and so on).
Multiple business intelligence (BI) extractors are required to cover the complete truth in
BI.
Figure 12: New Architecture - Universal Journal as the Single Source
© Copyright. All rights reserved.
13
Unit 1: Overview of Financials for SAP S/4HANA
The universal journal is now the single source of truth. Each posting creates line items in the
universal journal table that combines all data entered in the different financial components
into one single structure.
The new architecture includes the following benefits:
There is one line item table with full detail for all components. Data is stored only once, so
no reconciliation is needed by the architecture.
Fast multidimensional reporting on the universal journal is possible without replicating
data to BI. If BI is in place, one single BI extractor is needed.
The memory footprint is reduced through elimination of redundancy.
Technical preparation enhances important structural capabilities of the financials solution
(for example, multi-GAAP and additional currencies).
Safeguards for Customer Investments
Figure 13: Non-disruptiveness
The main focus of SAP S/4HANA development is to provide a product that does not disrupt
the processes and daily life of a business. A great effort has been made to safeguard the
customer investments that were made in custom code. Existing programs and interfaces can
still be used through generated compatibility views, as follows:
Read access from custom ABAP programs or reports to prior tables function as
previously.
Read access is automatically redirected to the universal journal as the new single source of
truth.
Some programs have write access to tables that were deleted and replaced by CDS views.
These programs will cause problems and can no longer be used without adaptation. To adapt
them, simply remove all write accesses for the tables that have been replaced by views. You
can use the code inspector to find all affected sections of the code (see SAP Note 1976487).
© Copyright. All rights reserved.
14
Lesson: Describing the New Architecture of Accounting
Figure 14: List of Tables Replaced by Compatibility Views
The figure, List of Tables Replaced by Compatibility Views, shows a list of tables that have
been replaced by compatibility views in the new system. All the classic index tables, like BSIS
and BSAS, and all the aggregate tables or totals tables, like FAGLFLEXA and GLT0, have been
replaced by compatibility views. The compatibility views use data direct from the universal
journal and that were generated on the fly.
Architectural Changes in Financials with SAP S/4HANA
Figure 15: Universal Journal Extensibility
The universal journal can be extended with customer fields. Extensibility is available for all
components that use the universal journal (G/L, CO, AA, and ML).
Profit and loss (P&L) line extension using CO-PA capabilities is provided, both for field
definition (characteristics) and the rich derivation tools from CO-PA.
The standard general ledger coding block extensibility can also be used. It affects the
universal journal.
The new SAP HANA-based reporting of all components (G/L, AA, ML, and CO) can access the
customer fields.
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 (for example, carry forward, corrections in migration). These entries do not represent
standard business processes.
© Copyright. All rights reserved.
15
Unit 1: Overview of Financials for SAP S/4HANA
The corresponding line items have artificial document numbers beginning with letters, for
example, “A” .
The ACDOCA table contains all fields needed for G/L, CO, AA, ML, and PA.
All cost elements, including secondary cost elements, are G/L accounts.
Multi-GAAP capability is available through the Ledger (RLDNR) dimension.
There is six digit field for line item numbering and 23 digits for currency fields.
Figure 16: External Postings with SAP S/4HANA
Data for COEP, FAGLFLEXA, ANEP, MLIT, and so on, is stored directly in ACDOCA.
BSEG is maintained, and is unaffected by the new architecture. BSEG is still limited to 999
lines per document, but you can summarize those lines and have up to 999,999 analytically at
the highest granularity directly in ACDOCA.
Profit center accounting, special purpose ledgers, and consolidations remain technically
untouched and they continue to work.
Components that have been built with special purpose ledger functionality, such as joint
venture accounting and public sector management, continue to work as before. Additionally,
costing-based CO-PA also works exactly as before with the enhancements that come with
SAP HANA systems and CO-PA.
LESSON SUMMARY
You should now be able to:
Explain the idea and concept of the universal journal
Explain how SAP safeguards customer investments
Outline the architectural changes in SAP S/4HANA
© Copyright. All rights reserved.
16
Unit 1
Lesson 3
Explaining the Purpose and Functions of SAP
Fiori
LESSON OBJECTIVES
After completing this lesson, you will be able to:
Explain SAP Fiori applications and tools
SAP Fiori Application and Tools
Scenario
You want to ensure that your users have the best possible experience when interacting with
SAP Business Suite. You want to ensure that users can access critical business applications
on any device without compromises. Finally, you want to ensure that the solution integrates
with your existing IT system landscape and can expand to cover your specific needs. You
want to make sure that SAP Fiori meets these requirements.
SAP Fiori User Experience Paradigm
Figure 17: SAP Fiori User Experience Paradigm
The SAP Fiori user experience paradigm consists of the following pillars:
Role-based: Users have access to the applications where they perform their tasks, and the
applications are specific to completing this task.
Responsive: The application interface is responsive; it adapts to the size and device used
by the users to access it.
Simple: The scope of the application is simple. There is one user, one use case, and up to
three screens for each application.
Coherent: The applications are developed with a coherent structure. The apps all speak
the same language, and can be implemented in multiple landscapes and environments.
© Copyright. All rights reserved.
17
Unit 1: Overview of Financials for SAP S/4HANA
Instant value: A low adoption barrier provides instant value, both on the IT-system side and
on the user-adoption side.
What is SAP Fiori?
Figure 18: What is SAP Fiori?
Transaction apps offer task-based access to tasks like change, create, display (documents,
master records), or entire processes with guided navigation.
Analytical apps provide insight to action. They give you a visual overview of complex topics for
monitoring or tracking purposes.
Fact sheets allow you to search and explore your data. They provide a 360 degree view on
essential information about an object and contextual navigation between related objects.
© Copyright. All rights reserved.
18
Lesson: Explaining the Purpose and Functions of SAP Fiori
SAP Fiori Launchpad - One Entry Point for the User
Figure 19: SAP Fiori Launchpad - One Entry Point for the User
The SAP Fiori launchpad is the single entry point where the user can interact with the system.
It is role-based and person-centric. The users access those applications that are specific to
their role within the company. They can then perform the specific tasks as per their
requirement. There is embedded search, collaboration, and feed functionality.
The SAP Fiori launchpad offers themes and can be personalized to meet branding
requirements.
It offers a stable URL for bookmarking and sharing. It is browser based and therefore works
with multiple devices and browsers.
The launchpad also offers active tiles through which the user can receive updated information
directly from the front page without opening the application.
© Copyright. All rights reserved.
19
Unit 1: Overview of Financials for SAP S/4HANA
SAP Fiori Launchpad User Personalization
Figure 20: SAP Fiori Launchpad User Personalization
The following personalization options are available to users in SAP Fiori launchpad:
Adding applications from the catalog assigned to them
Removing applications that they do not want to use
Modifying and adding applications for filtered report results
For example, if the user is a group cash manager who is interested in the German market, the
user can create an application to take them directly to the cash position of the German
market. They can arrive at the cash position directly with one click from the SAP Fiori
launchpad home page.
SAP Fiori Launchpad Designer
Figure 21: SAP Fiori Launchpad Designer
© Copyright. All rights reserved.
20
Lesson: Explaining the Purpose and Functions of SAP Fiori
In SAP Fiori launchpad designer, you can perform the following tasks:
Configure tiles for static app launchers, dynamic app launchers, and configure the target
mapping
Create preconfigured groups and catalogs for the launchpad home page and for assigning
to users
Transport configurations, correction request packages, or the customizing workbench
Note:
For more information on the SAP Fiori launchpad designer, see the help document
at the following URL: https://go.sap.corp/fldhelp .
SAP Fiori Theme Designer
Figure 22: SAP Fiori Theme Designer
In the SAP Fiori theme designer, you can design custom themes for the launchpad. For
example, you can perform the following tasks:
Change font color
Change background color
Add images
Assign a new theme to users
Related SAP Links
For more information, see the following links, see the SAP Fiori Apps Library,
fioriappslibrary.hana.ondemand.com/sap/fix/externalViewer/
.
https://
LESSON SUMMARY
You should now be able to:
Explain SAP Fiori applications and tools
© Copyright. All rights reserved.
21
Unit 1
Lesson 4
Outlining the Migration of Financials to SAP S/
4HANA
LESSON OBJECTIVES
After completing this lesson, you will be able to:
Describe the migration process
SAP S/4HANA Adoption Scenarios
Figure 23: Transition to SAP S/4HANA
You have several options to migrate to SAP S/4HANA:
Complete conversion of an existing SAP Business Suite system to S/4HANA.
New or existing SAP customer implementing a new SAP S/4HANA system.
Selective Conversion: Consolidation of current regional SAP Business Suite landscape into
one global SAP S/4HANA system.
The advantages of this approach are that only topics are rebuilt that no longer meet the
requirements (e.g. account approach or an other aspect of reorganization) or that only
certain data are to be transferred to S/4HANA (e.g. certain fiscal years or company
codes).
© Copyright. All rights reserved.
22
Lesson: Outlining the Migration of Financials to SAP S/4HANA
Figure 24: Migration to SAP S/4HANA
Greenfield
New SAP customers starting with SAP S/4HANA can use classic migration tools or the S/
4HANA Migration Cockpit (on-premise) to take over their legacy data.
Conversion
The SAP S/4HANA migration tools work only for existing customers and systems. Depending
on the active applications in the source system, different preparation steps are required. The
description can be found in the SAP online help. The duration and effort is relatively small. The
migration can be executed at any period end and is supported by a migration guide and
monitor. The first test migration gives an indication of the duration, and highlights any
potential setbacks during the migration project.
Migration to Accounting on SAP HANA from a classic G/L setup does not support the
following scenarios:
Implementation of Document Splitting
Balance Sheets at the Profit Center Level
Migration from Special Purpose Ledger to New General Ledger Accounting
New Implementation of Parallel Accounting
New Implementation of Segment Reporting
Implementation of the Ledger Approach for Parallel Accounting
Change in Chart of Accounts and Conversion of Chart of Accounts
Inclusion of Customer Fields
Transfer of Quantities to New General Ledger Accounting
© Copyright. All rights reserved.
23
Unit 1: Overview of Financials for SAP S/4HANA
Figure 25: Sequence in Test and Productive Environment
Required pre-checks
Before you convert your SAP ERP system to SAP S/4HANA or upgrade your SAP S/4HANA it
applies SAP BW/4HANA as well, you may want to analyze the impact on your system based
on simplification items. With the Readiness Check (SAP Note 2758146), it is checked whether
the system is S/4HANA-capable, e.g. which add-ons are used. With the Simplification ItemCheck (SAP Note 2399707) provides capabilities in your managed system. There are two
types of check integrated into the program:
Relevance check which tells you whether an item is relevant to the system or not. The
relevance is calculated based on rules maintained in the simplification item catalog
Consistency check which checks whether the system is in a consistent state to ensure that
the conversion can happen with Software Upgrade Manager (SUM). Only the items which
are relevant to the system will be included in a consistency check. All remaining
inconsistencies need to be solved before SUM enters downtime. The check also warns you
about critical changes during conversion for example data loss. To continue, you must
confirm that you have understood the warning. The consistency check is performed by
individual check classes provided by each application area. The check classes are
delivered through SAP Note 2502552. Note: How to eliminate issues found is described in
the notes reported in error messages as part of the check result.
When running the simplification item check (/SDF/RC_START_CHECK) to prepare for a
conversion from SAP ERP to SAP S/4HANA or to do an upgrade to a higher SAP S/4HANA
version, it is important to follow below guides. Otherwise the technical conversion/upgrade
might be blocked and you may have to repeat the SUM procedure by resetting the SUM,
updating this SAP Note (2399707) and SAP Note 2502552, potentially resolve new issues
found by the check and the restart the SUM procedure.
Implement and run the check and solve any errors found by the included consistency check.
This is mandatory for any conversion or upgrade to SAP S/4HANA 1709 or higher.
To identify and fix possible issues in time, you need to implement and run the check well in
advance, before starting the technical conversion/upgrade. The check is run the last time by
the SUM tool shortly before the technical downtime of the conversion/upgrade of a system.
© Copyright. All rights reserved.
24
Lesson: Outlining the Migration of Financials to SAP S/4HANA
However, do not wait to implement the check until shortly before starting SUM. If there are
any issues found, fixing them might take some time.
Depending on the target stack of your system conversion or release upgrade, you need to
have certain minimum versions of this SAP Note (2399707) and SAP Note 2502552 installed.
Otherwise, the check cannot be successfully completed.
Figure 26: SAP Readiness Check for SAP S/4HANA
Note:
For more information, see SAP Note 2399707 - Simplification Item Check.
For more information, see SAP Note 2758146 - SAP Readiness Check 2.0 & Next
Generation SAP Business Scenario Recommendations or SAP Innovation and
Optimization Pathfinder.
LESSON SUMMARY
You should now be able to:
Describe the migration process
© Copyright. All rights reserved.
25
Unit 1
Learning Assessment
1. SAP HANA is designed for supporting both Online transactional processing and Online
analytic processing.
Determine whether this statement is true or false.
X
True
X
False
2. SAP S/4HANA can run on non-HANA databases but it is slower.
Determine whether this statement is true or false.
X
True
X
False
3. The on-premise edition of SAP S/4HANA can interface with SAP Cloud Platform even
though it is a cloud only.
Determine whether this statement is true or false.
X
True
X
False
4. Improvements to finance with SAP S/4HANA concern core accounting functions alone
currently.
Determine whether this statement is true or false.
X
True
X
False
© Copyright. All rights reserved.
26
Unit 1: Learning Assessment
5. What are the business benefits of SAP S/4HANA Finance?
Choose the correct answers.
X
A Reduced system complexity
X
B Single source of truth on the line item level
X
C Automatic update of custom applications to SAP HANA standards
X
D Overall reporting across financial applications
6. What is the character length of the field for line item numbering in the universal journal
table ACDOCA?
Choose the correct answer.
X
A 3
X
B 6
X
C 10
7. Which tables are replaced by compatibility views?
Choose the correct answers.
X
A BSIS: Index for GL Account
X
B FAGLFLEXT: New GL Account totals
X
C BSEG: Line Item
X
D ANLC: Fixed Assets totals
8. Which of the following are the pillars of SAP Fiori user experience paradigm?
Choose the correct answers.
X
A Role-based
X
B Responsive
X
C Simple
X
D Coherent
X
E Instant value
© Copyright. All rights reserved.
27
Unit 1: Learning Assessment
9. SAP S/4HANA can run on an SAP HANA database only.
Determine whether this statement is true or false.
X
True
X
False
10. Which of the following is a prerequisite for conversion to SAP S/4HANA?
Choose the correct answer.
X
A Custom code has to be checked for compatibility.
X
B New G/L Accounting must be active.
X
C New Asset Accounting must be active.
X
D The SAP migration service must be used.
11. An existing SAP ERP customer can upgrade their existing system to SAP S/4HANA only if
they have already implemented new G/L accounting.
Determine whether this statement is true or false.
X
True
X
False
© Copyright. All rights reserved.
28
Unit 1
Learning Assessment - Answers
1. SAP HANA is designed for supporting both Online transactional processing and Online
analytic processing.
Determine whether this statement is true or false.
X
True
X
False
Correct. SAP HANA is designed to support both Online transactional processing and
Online analytic processing.
2. SAP S/4HANA can run on non-HANA databases but it is slower.
Determine whether this statement is true or false.
X
True
X
False
Correct. SAP S/4HANA is built natively and optimally to run only on the SAP HANA
platform.
3. The on-premise edition of SAP S/4HANA can interface with SAP Cloud Platform even
though it is a cloud only.
Determine whether this statement is true or false.
X
True
X
False
Correct. The on-premise edition of SAP S/4HANA can interface with SAP Cloud Platform,
even though it is cloud only.
4. Improvements to finance with SAP S/4HANA concern core accounting functions alone
currently.
Determine whether this statement is true or false.
X
True
X
False
Correct. Improvements to finance with SAP S/4HANA does not only concern core
accounting functions.
© Copyright. All rights reserved.
29
Unit 1: Learning Assessment - Answers
5. What are the business benefits of SAP S/4HANA Finance?
Choose the correct answers.
X
A Reduced system complexity
X
B Single source of truth on the line item level
X
C Automatic update of custom applications to SAP HANA standards
X
D Overall reporting across financial applications
Correct. Although custom code will generally work on an SAP S/4HANA system, it is not
upgraded automatically to take advantage of SAP HANA.
6. What is the character length of the field for line item numbering in the universal journal
table ACDOCA?
Choose the correct answer.
X
A 3
X
B 6
X
C 10
Correct. The universal journal has a 6–digit number range for the line items.
7. Which tables are replaced by compatibility views?
Choose the correct answers.
X
A BSIS: Index for GL Account
X
B FAGLFLEXT: New GL Account totals
X
C BSEG: Line Item
X
D ANLC: Fixed Assets totals
Correct. BSEG remains as a transparent table.
© Copyright. All rights reserved.
30
Unit 1: Learning Assessment - Answers
8. Which of the following are the pillars of SAP Fiori user experience paradigm?
Choose the correct answers.
X
A Role-based
X
B Responsive
X
C Simple
X
D Coherent
X
E Instant value
Correct. All the listed options are correct.
9. SAP S/4HANA can run on an SAP HANA database only.
Determine whether this statement is true or false.
X
True
X
False
Correct. SAP S/4HANA requires the SAP HANA database to work.
10. Which of the following is a prerequisite for conversion to SAP S/4HANA?
Choose the correct answer.
X
A Custom code has to be checked for compatibility.
X
B New G/L Accounting must be active.
X
C New Asset Accounting must be active.
X
D The SAP migration service must be used.
Correct. The only requirement is to check the system code for compatibility.
11. An existing SAP ERP customer can upgrade their existing system to SAP S/4HANA only if
they have already implemented new G/L accounting.
Determine whether this statement is true or false.
X
True
X
False
Correct. An existing SAP ERP customer can upgrade their existing system to SAP S/
4HANA without implementing new G/L accounting.
© Copyright. All rights reserved.
31
UNIT 2
General Ledger
Accounting
Lesson 1
Managing GL Accounts and Cost Elements in SAP S/4HANA
33
Lesson 2
Managing Ledgers in SAP S/4 HANA
42
UNIT OBJECTIVES
Explain the new master data maintenance model
Understand the impact on authorizations and the posting period lock
Use the universal journal to enhance ledgers
Configure ledgers in SAP S/4HANA
© Copyright. All rights reserved.
32
Unit 2
Lesson 1
Managing GL Accounts and Cost Elements in
SAP S/4HANA
LESSON OBJECTIVES
After completing this lesson, you will be able to:
Explain the new master data maintenance model
Understand the impact on authorizations and the posting period lock
Master Data Maintenance Model
Scenario
Until now, you have kept G/L accounts separate to your cost elements. With the move to SAP
S/4HANA, you now only maintain G/L accounts. You want to understand how this change
works at the system architecture level and also how this impacts processes for master data
maintenance and other transactions.
Figure 27: New Data Model for Both Master Data in SAP S/4HANA
In the classical data model, an account consists of charts of accounts data (SKA1), company
code specific data (SKB1), and an account description (SKAT).
If an account is relevant for controlling, a cost element (primary cost element) is generated.
During the creation of the cost element, the CSKA, CSKB, and CSKU tables are updated.
© Copyright. All rights reserved.
33
Unit 2: General Ledger Accounting
Secondary cost elements exist for cost elements only; therefore only the CSK* tables are
updated.
In the new data model, the account is the master record and nothing else is required.
In this model, you can move between the following G/L account types (GLACCOUNT_TYPE):
nonoperating expense or income, primary costs or revenue, secondary costs, and balance
sheet account. The tables SKA1, SKB1, and SKAT are always filled. The CSK* tables are also
updated for the following G/L types: primary costs or revenue, and secondary costs.
Figure 28: Cost Element Categories for G/L Accounts from Type Primary Costs or Revenue or Secondary Costs
When the G/L type primary costs or revenue is chosen, you can update account settings for
the controlling area.
The cost element category specifies the business transactions that can be used with each
cost element. The following business transactions can be selected:
01 Primary costs/cost-reducing revenues
03 Accrual/deferral per surcharge
04 Accrual/deferral per debit = actual
11 Revenues
12 Sales deduction
22 External settlement
Secondary costs accounts types can be used for internal CO allocations only. The following
business transactions can be selected:
21 Internal settlement
31 Order/project results analysis
41 Overhead rates
42 Assessment
© Copyright. All rights reserved.
34
Lesson: Managing GL Accounts and Cost Elements in SAP S/4HANA
43 Internal activity allocation
50 Project-related incoming orders: sales revenue
51 Project-related incoming orders: other revenues
52 Project-related incoming orders: costs
61 Earned value
In SAP S/4HANA, a default account assignment can be defined using transaction OKB9or
through substitution rules. The default account assignments that are maintained in former
cost element master data are migrated to transaction OKB9as part of the migration process.
Figure 29: Cost Element Category 90 for Balance Sheet Accounts in Financial Accounting
Capital investments that do not have an asset under construction phase are usually
capitalized directly in asset accounting. However, you can view that information in
management accounting at the same time. For instance, you might want to perform plan or
actual comparisons and manage plan values, budgets, and commitments. You can post and
track these transactions on statistical internal orders or work breakdown structure (WBS)
elements.
The following conditions are necessary for the statistical updating of orders or WBS elements:
The CO object (investment order or WBS element) is entered in the asset master record as
an investment account assignment (in the time-origin).
The indicator for statistical updating of the order or WBS element is set in the definition of
the transaction types used for asset transactions (indicator: relevant to budget).
Note:
This indicator is already set in the standard transaction types.
© Copyright. All rights reserved.
35
Unit 2: General Ledger Accounting
The balance sheet account for asset APC values must be created in CO as cost elements.
Select the Apply Acct Assignments Statistically in Fixed Asset Acct / Material Acct
checkbox. You can select the checkbox under the following conditions:
-
When you create a balance sheet G/L account.
-
When the account is a reconciliation account for assets.
-
When you add the account in the asset account assignment in the Bal. sheet account:
Acquisition and production costs field.
In the field status variant of the corresponding fixed asset balance sheet account, the
CO/PP Order field or the WBS Element field must be set as an optional entry: see the
Additional Account Assignment group. The same applies for the Investment Account
Assignments field group in the screen layout rule of the asset class.
The investment order and the investment project account assignment objects must be
activated. Then you can specify the account assignment types for activated account
assignment objects.
Note:
The G/L account type Cash Account is the Master data setting for the Bank
Reconciliation Accounts approach.
Please refer to unit Basic Cash Management for further information.
Figure 30: Impact on Authorizations
The merging of cost elements and G/L accounts requires the following adjustments to
authorizations for creating cost elements:
If you want to maintain primary costs or revenue accounts, you require authorization to
create or change cost element master data.
© Copyright. All rights reserved.
36
Lesson: Managing GL Accounts and Cost Elements in SAP S/4HANA
If you want to maintain secondary costs accounts, you require authorization to create or
change G/L accounts.
To check or change the authorizations, use transaction
role is FUCN_GL_ACCOUNTANT(G/L Accountant).
PFCG. The standard delivered SAP
Business Partner
Figure 31: Business Partner
There are redundant object models in the traditional SAP ERP system. In SAP ERP, the vendor
master and customer master is used. In SAP S/4HANA, the (mandatory) target approach is
the business partner approach. Business partner is now capable of centrally managing
master data for business partners, customers, and vendors. With current development,
business partner is the single point of entry to create, edit, and display master data for
business partners, customers, and vendors.
The introduction of the customer and vendor integration will be checked in the prechecks and
the technical transition procedure of SAP S/4HANA. For a system where the customer and
vendor integration is not in place, the transaction is declined. The business partner approach
is not mandatory for the SAP S/4HANA Finance, 1503 and 1605.
The user interface for SAP S/4HANA Cloud and on-premise is transaction BP. There is no
specific user interface for customer or vendor in SAP Business Suite (transactions
XD01,
XD02, XD03 or VD01, VD02, VD03 or XK01, XK02, XK03 or MK01, MK02, MK03, and so on, are not
available). Calls to these transactions are redirected to transaction BP. For clients who
implemented financial supply chain management (FSCM), the business partner functionality
is not something new that previously managed credit management, collections, and so on.
© Copyright. All rights reserved.
37
Unit 2: General Ledger Accounting
Figure 32: Business Partner - Customer /Vendor Integration Process
You can assign only one customer/vendor to a business partner and vice versa (1:1
assignment). You can assign one customer and one vendor to a business partner
simultaneously in a corresponding business partner role.
Customer/Vendor Integration takes place in the background whilst the system processes
master data. When you create the business partner the system posts all required fields in the
customer/vendor in accordance with the information in the business partner. Technically
speaking when you update the business partner, the system updates the corresponding
customer/vendor at the same time.
The customer/vendor master record is linked to the business partner in accordance with the
settings made for synchronization control and Customer/Vendor Integration in Customizing.
You can generate a customer/vendor during business partner processing only if you have
selected a customer business partner role category for which this is possible.
When processing the business partner you have also updated the relevant data for the
customer/vendor master record.
© Copyright. All rights reserved.
38
Lesson: Managing GL Accounts and Cost Elements in SAP S/4HANA
Figure 33: BP Customer Integration - Number Ranges and Grouping
Figure 34: BP Customer/Vendor Integration
In customizing, you assign account groups for the customer and vendor master records to
the business partner groupings to ensure that the system updates the customer and vendor
at the same time as you process Business Partners.
The Flag Same Number determines that when you create a customer master record/ vendor
master record as part of Customer/Vendor Integration you use the same number as the
business partner number that is currently being processed. Prerequisites therefore are:
Number ranges for the customer/vendor and business partner have the same areas
External number assignment is set in Financial Accounting (FI)
© Copyright. All rights reserved.
39
Unit 2: General Ledger Accounting
Posting Period Lock
Figure 35: Effect on Period Lock
In SAP S/4HANA, CO relevant postings do not check the CO period lock (OKP1) as previously.
Instead, you must also check the G/L period opening/closing (OB52). Therefore, you have to
allow postings to accounts from the secondary costs account type in the G/L period opening/
closing.
In the CO period lock, you need to specify the transactions that you want to lock and the
periods that you want to lock them for.
In SAP S/4HANA, you must also open accounts from the secondary costs account type for FI
postings.
Figure 36: Period Intervals
In transaction OB52, you can specify which posting periods are open for posting for each
variant. You can choose period intervals between 1 and 3.
© Copyright. All rights reserved.
40
Lesson: Managing GL Accounts and Cost Elements in SAP S/4HANA
You can use period intervals 1 and 2 for all normal posting processes in regular and special
periods.
For period interval 1, you can enter a group of authorized users. This means that for monthend or year-end closing, for example, you can open posting periods for specific users only.
Make the necessary authorization settings in the optional authorization object accounting
document: authorizations for posting periods (F_BKPF_BUP). Use period interval 1 for special
periods because only authorizations can be managed here.
Period interval 3 is used for postings from controlling (CO) to financial accounting (FI). If you
do not make an entry for period interval 3, the check on these postings is made against period
intervals 1 and 2. If you make an entry for period interval 3, the check on these postings is only
made against period interval 3. For each interval, specify the lower and upper limits of the
posting period as well as the fiscal year.
You can also use the report RFOB5200 (transaction OB52B).
Which accounting period version is checked? The leading ledger works with the accounting
period that is assigned to the accounting area. Nonleading ledgers can be assigned different
posting period variants.
Check the version of the nonleading ledger at ledger group specific bookings, and also for
bookings with ledger group blank. Determine this by selecting the Manage Posting Period field
in the global parameters of the company code.
Alternatively you can use the app Manage Posting Periods . With the Manage Posting Periods
app, you can open and close posting periods to make sure that postings to the accounts
happen in proper posting periods. You can also choose to schedule the opening to run once or
multiple times according to your business requirements. For this app, the business function
FINS_PERIOD_CTRL_BY_BTTYPE is available. When activated, the following Cost Accounting
features are available in the separate Manage Posting Periods – Cost Accounting app:
Access the CO period status by selecting CO Period Status in the footer bar, which will
navigate you to the Manage Posting Periods - Cost Accounting app
Display Business Transaction Type related periods
LESSON SUMMARY
You should now be able to:
Explain the new master data maintenance model
Understand the impact on authorizations and the posting period lock
© Copyright. All rights reserved.
41
Unit 2
Lesson 2
Managing Ledgers in SAP S/4 HANA
LESSON OBJECTIVES
After completing this lesson, you will be able to:
Use the universal journal to enhance ledgers
Configure ledgers in SAP S/4HANA
Ledger Enhancement Using the Universal Journal
Scenario
You manage multiple parallel accounting principles in your system and need to be able to
report on each one separately. You are concerned that with the universal journal, the
previously independent components will lose their flexibility because of the legal restrictions
of financial accounting. You want to understand the ledger capabilities with SAP S/4HANA
Finance so that you can configure ledgers to your requirements.
Figure 37: The Universal Journal Enforces Discipline
In the general ledger, everything is entered according to accounting rules. The posting periods
are locked after the month-end closing. The accounting rules cannot be changed.
© Copyright. All rights reserved.
42
Lesson: Managing Ledgers in SAP S/4 HANA
Figure 38: Standard Ledger and Extension Ledger - Use Cases
In the new general ledger accounting, different accounting principles are mapped using the
accounts approach. In addition to accounts, the new G/L also lets you use different ledgers to
save the different valuation approaches. This is called the ledger approach.
In an account approach, there is only one ledger: the leading ledger 0L. In a ledger approach,
next to the leading ledger, there are other nonleading ledgers. These ledgers are all called
standard ledgers. A standard ledger contains a full set of journal entries for all business
transactions.
In addition, you can add other extension ledgers. Extension ledgers are based on an
underlying ledger.
An extension ledger is assigned to a standard ledger and inherits all the journal entries of the
standard ledger for reporting. Postings made explicitly to an extension ledger are visible in
that extension ledger, but not in the underlying standard ledger.
It is possible to define an extension ledger based on another extension ledger.
An extension ledger stores delta values and points to another ledger. Thus, it provides a
flexible mechanism for adjustments and reporting. An important use case is for management
views on top of legal data (IFRS or locale GAAP). Besides creating a master record, extension
ledgers do not need additional configuration. Reporting on the extension ledger always
includes the data of the underlying ledger. Multiple extension ledgers can point to the same
underlying ledger. The benefits of a reduced data footprint and zero reconciliation effort mean
that only delta values are kept.
Extension ledgers are stored in the universal journal, as are standard ledgers. Extension
ledgers can be assigned your own booking period variants. This means that the standard
ledger can be closed and the assigned extension ledger can be open.
© Copyright. All rights reserved.
43
Unit 2: General Ledger Accounting
Figure 39: Extension Ledger - Basic Idea
Each specific ledger is self-contained, has a special purpose, and provides a specific view on
financial data. A ledger stores a lot of redundant data in other ledgers.
With extension ledgers you can staple ledgers on top of each other, thus providing the
different views that you need. This structure minimizes the data footprint and provides
greater flexibility for creating additional views.
Extension ledger can have different ledger types:
Standard journal entries ( ): Extension used to store additional data.
Line items with technical numbers (S): Simulation used in for foreign currency valuation.
Line items with technical numbers (P):Prediction and Commitments used to store
commitments in table ACDOCA and store the values of incoming sales orders and of
statistical conditions for account-based CO-PA .
© Copyright. All rights reserved.
44
Lesson: Managing Ledgers in SAP S/4 HANA
Figure 40: Postings into the Extension Ledger
Only manual postings are allowed to the extension ledger. Use the transaction that enables
you to add the ledger group to the expending ledgers, for example, KB11N, KB41N, FB50L, and
FB01L.
You can use a simulation extensions ledger for the daily valuation of foreign currency
valuation (transaction FAGL_FCV).
ACDOCA stores the data for all extension ledgers.
BSEG does not store any extension ledger data. You can only book ledger specific onto the
extension ledger the table BSEG_ADD is filled.
Implementing the BADI BADI_FINS_APPL_RELEVANCE allows you to feed components like
PCA, FI-SL, and EC-CS with the data posted to extension ledgers. Take precautions with this
functionality. The BADI implementation must clearly separate extension ledger data from the
other data.
© Copyright. All rights reserved.
45
Unit 2: General Ledger Accounting
Figure 41: Document Summarization
BSEG summarization can be used as usual (see SAP Note 2179270). BSEG is used for storing
open items and clearing details, so you can be aggressive with the summarization.
ACDOCA stores the full detail that is needed for all components on ACDOCA (G/L, AA, ML,
CO, and PA).
Summarize the BSEG table as much as possible. Conversely, summarize the ACDOCA table
as little as possible so that reporting that is differentiated in the ACDOCA table.
The summarization in the ACDOCA table can be as large as that of the BSEG table. Line items
in the ACDOCA table cannot be summarized further than the corresponding line items in the
BSEG table.
You can find these, along with additional documentation, in customizing by choosing
Financial
Accounting
Financial Accounting Global Settings
Document
Summarization . From
here, you can also access the summarization of the BSEG table described in SAP Note 36353.
The account-based CO-PA line items, including the profitability segment number and the
resolved characteristic vector, are stored in the table ACDOCA. Therefore, the same
summarization settings are used for CO-PA profitability segment determination also. Access
these settings, along with documentation and the existing summarization for costing-based
CO-PA line items, by choosing Controlling
Profitability Analysis
Flows of Actual Values
Initial Steps
Summarization .
© Copyright. All rights reserved.
46
Lesson: Managing Ledgers in SAP S/4 HANA
Ledger Configuration in SAP S/4HANA
Figure 42: Master Data Maintenance for Ledgers
In Customizing, choose Financial Accounting
Financial Accounting Global Settings
Ledgers
Ledger
Define Settings for Ledgers and Currency Types. The following
options are available:
Transaction: FINSC_LEDGER
First level:
-
Master data of ledger
-
Define the leading ledger
-
Define additional ledgers: standard or extension
-
Set a ledger as underlying ledger only for the extension ledgers
Second level:
-
Company code assignment to ledger
-
For the leading ledger: 0L
-
All companies are assigned to the leading ledger.
© Copyright. All rights reserved.
47
Unit 2: General Ledger Accounting
Multiple Currency Groups
Figure 43: Currency Flexibility for the Universal Journal
Other currencies can be defined and translated according to the role they have in Accounting.
In contrast to reporting, in which the displayed amounts are translated into the desired
currency, currencies managed in parallel in the Universal Journal are translated during
posting. Translation when posting ensures the zero balance setting for each document,
clearing, and reversal. These currencies managed in parallel in the Universal Journal are
configured as currency types in the system.
In addition to managing the ledgers in the company code currency and global company
currency, there is the option to manage up to eight other currency types, for example, in hard
currency, index-based currency, or global company currency, or in currencies that you
configure yourself (in namespaces Y* to Z*).
The following is a list of the currency fields of ACDOCA:
Local currency: currency type 10, ACDOCA field name HSL
Global currency: currency type 30 ACDOCA field name KSL
Freely defined currencies 1 - 8: You can configure your own currency type, and there is no
dependency on currency types of the leading ledger. ACDOCA field names: OSL, VSL, BSL,
CSL, DSL, ESL, FSL, and GSL.
Note:
The currency type of the controlling area is preset as the global currency for all
ledgers and company codes, provided that the company code has an assignment
to a controlling area. You can maintain this currency type by using the Maintain
Controlling Area activity (transaction OKKP). SAP recommend that you set
currency type 30 (group currency) in the controlling area to have a consistent
currency for the consolidated financial statement that is also supported by all FI
processes (not the case for 20).
The group currency is the currency used for the consolidated financial statement.
The group currency (currency key 30) is defined on Client.
Caution:
If you activate parallel valuations with transfer prices, then additional rules and
constraints apply.
© Copyright. All rights reserved.
48
Lesson: Managing Ledgers in SAP S/4 HANA
Figure 44: Currency Conversion Settings
For each currency type you add, decide whether you want the corresponding currency
conversion settings to be valid globally for all company codes or you want to define the
currency conversion settings on company code-level.
You cannot make any changes to the SAP default currency type company code currency (10).
For the other standard currency types, you can define whether the corresponding currency
conversion settings are valid globally or on company code-level.
For your currency types, make the following currency translation settings either for all
company codes (that is, globally) or separately for individual company codes (that is,
company-code-specifically):
For your own currency types, enter the currency into which the currency translation is to be
made ( Currency field), and the currency from which the currency translation is to be made
(Source Currency field). In addition, enter the exchange rate type and the date on which the
translation is to be carried out (document date, posting date, or translation date). You can
also decide whether the currency translation is to be done in real time. Unless you select the
Real-Time checkbox, you can do this at period-end closing using the foreign currency
translation run.
Figure 45: Currency Type Integration into FI&CO Applications
© Copyright. All rights reserved.
49
Unit 2: General Ledger Accounting
For each ledger, you can display a detail screen by double-clicking the relevant row in the
ledger.
If you expand the details, you can see whether the general ledger has calculated a currency
that is not kept in a particular subledger as an approximation. If slight deviations, for example,
rounding differences, are possible for a particular application component for which there is no
historical data, this is indicated by the Deviation in Application Component checkbox.
With Manage Currencies, you can introduce new currencies for company codes and ledgers
that are already used in your production system. Afterward, the newly introduced currencies
are available in the Universal Journal (ACDOCA table) and can be used in both accountingspecific processes and reporting. When you introduce a new currency, both the new currency
and its calculated value are added to all journal entries, which are available in the system.
However, archived data cannot be enriched with the new currency.
In Customizing, choose Financial Accounting
Financial Accounting Global Settings
Tools
Manage Currencies
Information: Manage Currencies .
Note:
For more information, see SAP Notes 2344012 and 2334583.
Additional Company Code Settings for Ledgers
Figure 46: Additional Company Code Settings for Ledgers
The following are some additional company code settings for ledgers:
Fiscal Year Variant
If the leading ledger is inherited from the controlling area setting, non-leading ledgers can
have fiscal year variants that deviate.
Posting Period Variant
This defines open posting periods. It is the basis for a check of the leading ledger and the
representative ledger in ledger group.
© Copyright. All rights reserved.
50
Lesson: Managing Ledgers in SAP S/4 HANA
Parallel Accounting using G/L Accounts
In an account approach, this spot has to be marked.
Third Level
Entries are only necessary for parallel financial reporting with an accounting principle.
Look at, for example, Fi-AA.
Figure 47: General Ledger Technical Changes Compared to New G/L
Data previously stored in FAGLFLEXA and 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 the ACDOCA table.
Data of customer-created new G/L tables ZZ<CUST>T, ZZ<CUST>A is now stored in the
ACDOCA table.
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.
Document Splitting
Figure 48: Universal Journal
© Copyright. All rights reserved.
51
Unit 2: General Ledger Accounting
In the FAGLFTEXT totals table in the new general ledger, the updated profit center, segment,
business, area, and cost-of-sales accounting fields are also updated in SAP S/4HANA
accounting in the universal ledger.
All known scenarios from the new general ledger are turned on in SAP S/4HANA.
Customers who wish to draw up financial statements by business areas, profit centers, or
segments have to activate document splitting.
Document splitting is only for customers who have to or want to enter a further characteristic.
For example, a customer might want to enter a segment on the balance sheet in addition to
the company code.
Figure 49: Analyzing Document Splitting
A financial accounting document always has two views in SAP S/4HANA: The data entry and
the general ledger view.
Besides the leading ledger, you can also view the document in another, non-leading ledger or
extension ledger in the general ledger view.
You can display the profit and loss statement using the following objects:
Profit center
Business area
Segment
Line items are not displayed split in the entry view.
When using document splitting, the line items are displayed split in the general ledger view.
For the entities defined as splitting, characteristics are inherited in posting lines where the
characteristics were not specified. In the figure, the balance of the profit center and segment
characteristics is zero.
The figure also shows the vendor and tax lines in the general ledger view. The vendor and tax
lines (items 1 and 4) are split in accordance with the expense lines.
Document splitting, also known as an online split, enables companies to create complete
balance sheets for objects.
© Copyright. All rights reserved.
52
Lesson: Managing Ledgers in SAP S/4 HANA
If you do not activate document splitting, then there is no difference between the entry view
and the general ledger view.
Figure 50: Subsequent Implementation of Document Splitting — Project Phases
The feature Subsequent Implementation of Document Splitting allows SAP S/4HANA 1709
customers, with production systems, to implement document splitting. In the SAP
Implementation Guide, you can sequentially work through the Customizing activities
provided. You can then ensure that the necessary enrichment of relevant posting data is
supported.
The architecture of the accounting module in SAP S/4HANA is based on the concept of the
former new GL. The concept of the Subsequent Implementation of Document Splitting in SAP
S/4HANA differs from the migration scenario 6 of the new GL. In SAP S/4HANA, the
activation of document splitting is time-dependent. You can, therefore, implement it without
system downtime.
The new solution is offered as standard tool and does not require a service fee.
The Subsequent Implementation of Document Splitting requires a separate project. The
Subsequent Implementation of Document Splitting includes the preparatory phase, the
execution phase, and the post processing phase. In the preparatory phase, you can prepare
the customizing for document splitting. In the execution phase, you can start the data
enrichment. In the post processing phase, you can manually adjust the opening balances
based on the document splitting characteristics.
In customizing, choose Financial Ledger
Accounting Business Transactions
Splitting
Subsequent Implementation of Document Splitting .
Document
It is not in scope of this course to go into the solution implementation detail. You can find
more information in the relevant Early Knowledge Transfer learning maps available on the
SAP Learning Hub.
© Copyright. All rights reserved.
53
Unit 2: General Ledger Accounting
Accounting Principle Expansion
Figure 51: Implementation of a Further Accounting Principle
For existing customers, the universal journal runs with different features that activate after
the implementation of SAP S/4HANA. The type of features that become available depend on
the general ledger application that is used before migration.
For example, the SAP S/4HANA features for a classic GL migration path are limited to the
following:
The leading ledger keeps all accounting data
GL and CO automatically sync without real-time integration or reconciliation ledger
New asset accounting
All dimensions available for reporting: no decision is needed for reporting dimensions
(such as scenarios in new GL)
SAP now offers the option of implementing an additional accounting principle through the
addition of a ledger.
Basic use cases for this function include the following:
Introduction of a new accounting principle, for example, IFRS or group-based GAAP
Assignment of one or many productive company codes to an existing representative
ledger
Note:
This solution replaces the new GL migration scenario 7 “Subsequent
implementation of a ledger” in SAP S/4HANA 1610 and SAP S/4HANA Finance
1605 SP5.
© Copyright. All rights reserved.
54
Lesson: Managing Ledgers in SAP S/4 HANA
The new solution is offered as standard tool and does not require a service fee.
The following are not in scope for SAP S/4HANA 1610:
Replacement of parallel accounts by ledger
Data transfer from special ledger into new ledger
Definition of more than one ledger in one project
Definition of a nonrepresentative ledger
Figure 52: Availability of General Ledger Features in SAP S/4HANA
The solution Subsequent Implementation of a Further Accounting Principle offers the
following features:
Guided implementation of a new accounting principle using an additional ledger and
relevant depreciation areas
Flexible data transfer from a source ledger into a new ledger
Reconciliation steps to ensure correct and consistent accounting data
Automatic enhancement of asset master data with new depreciation areas
Easy handling using an implementation cockpit in customizing
© Copyright. All rights reserved.
55
Unit 2: General Ledger Accounting
Figure 53: Project Phases in SAP Implementation Guide
The implementation of an additional general ledger requires a separate project. The basic
phases are shown in the figure, Project Phases in SAP Implementation Guide. There is a
separate branch in the customizing SAP Implementation Guide to help implement the
required changes in the system.
In Customizing, choose Financial Accounting
Financial Accounting Global Settings
Subsequent Implementation of a Further Accounting Principle .
Tools
It is not in scope of this course to examine the solution implementation detail. However, you
can find more information in the relevant Early Knowledge Transfer learning maps on the SAP
Learning Hub.
LESSON SUMMARY
You should now be able to:
Use the universal journal to enhance ledgers
Configure ledgers in SAP S/4HANA
© Copyright. All rights reserved.
56
Unit 2
Learning Assessment
1. The cost element category specifies the business transactions that can be used with each
cost element.
Determine whether this statement is true or false.
X
True
X
False
2. Which level does the cost element category get assigned on?
Choose the correct answer.
X
A Chart of account
X
B Controlling area
X
C Company code
3. Which G/L account types are relevant for CO?
Choose the correct answers.
X
A Non-operating expense or income
X
B Primary costs or revenue
X
C Secondary costs
X
D Bank and Cash Accounts
4. The manage posting periods app shows three period intervals. Which interval checks
exclusively the posting from Controlling (CO) to Financial Accounting (FI)?
Choose the correct answer.
X
A 1
X
B 2
X
C 3
© Copyright. All rights reserved.
57
Unit 2: Learning Assessment
5. Which statements are true for an extension ledger?
Choose the correct answers.
X
A Contains a full set of journal entries for all business transactions.
X
B Stores only delta values.
X
C Reporting on the extension ledger always includes the data of the underlying
ledger.
X
D Multiple extension ledgers can point to the same underlying ledger.
6. How can you represent different accounting principles in SAP S/4HANA Finance?
Choose the correct answers.
X
A Ledger approach
X
B Accounts approach
X
C Valuation approach
7. When document splitting is active, in which table is the splitting information stored?
Choose the correct answer.
X
A ACDOCA
X
B FAGLFLEXA
X
C BSEG
X
D ACDOCP
© Copyright. All rights reserved.
58
Unit 2
Learning Assessment - Answers
1. The cost element category specifies the business transactions that can be used with each
cost element.
Determine whether this statement is true or false.
X
True
X
False
Correct. The cost element category specifies the business transactions that can be used
with each cost element.
2. Which level does the cost element category get assigned on?
Choose the correct answer.
X
A Chart of account
X
B Controlling area
X
C Company code
Correct. The controlling area is the level on which the cost element category for secondary
cost accounts is assigned.
3. Which G/L account types are relevant for CO?
Choose the correct answers.
X
A Non-operating expense or income
X
B Primary costs or revenue
X
C Secondary costs
X
D Bank and Cash Accounts
Correct. Primary costs or revenue and secondary costs are tracked in CO.
© Copyright. All rights reserved.
59
Unit 2: Learning Assessment - Answers
4. The manage posting periods app shows three period intervals. Which interval checks
exclusively the posting from Controlling (CO) to Financial Accounting (FI)?
Choose the correct answer.
X
A 1
X
B 2
X
C 3
Correct. The Period interval 3 is used for postings from controlling (CO) to financial
accounting (FI).
5. Which statements are true for an extension ledger?
Choose the correct answers.
X
A Contains a full set of journal entries for all business transactions.
X
B Stores only delta values.
X
C Reporting on the extension ledger always includes the data of the underlying
ledger.
X
D Multiple extension ledgers can point to the same underlying ledger.
Correct. The following statements that are true for an extension ledger are: stores only
delta values, reporting on the extension ledger always includes the data of the underlying
ledger, and multiple extension ledgers can point to the same underlying ledger.
6. How can you represent different accounting principles in SAP S/4HANA Finance?
Choose the correct answers.
X
A Ledger approach
X
B Accounts approach
X
C Valuation approach
Correct. Both the ledger approach and accounts approach are valid, but the ledger
approach is proposed for new installations.
© Copyright. All rights reserved.
60
Unit 2: Learning Assessment - Answers
7. When document splitting is active, in which table is the splitting information stored?
Choose the correct answer.
X
A ACDOCA
X
B FAGLFLEXA
X
C BSEG
X
D ACDOCP
Correct. The universal journal, ACDOCA is the single point of truth for all financial line
items.
© Copyright. All rights reserved.
61
UNIT 3
Asset Accounting
Lesson 1
Analyzing the Posting Logic of New Asset Accounting
63
Lesson 2
Legacy Data Transfer Asset Accounting SAP S/4HANA
72
UNIT OBJECTIVES
Understand the architecture of asset accounting in SAP S/4HANA
Explain the posting logic in asset accounting
Legacy Data Transfer Asset Accounting SAP S/4HANA
© Copyright. All rights reserved.
62
Unit 3
Lesson 1
Analyzing the Posting Logic of New Asset
Accounting
LESSON OBJECTIVES
After completing this lesson, you will be able to:
Understand the architecture of asset accounting in SAP S/4HANA
Explain the posting logic in asset accounting
The Architecture of Asset Accounting in SAP S/4HANA
Scenario
You want to understand and use the posting logic in asset accounting. You also want to know
what benefits your end-users will gain from asset accounting.
Figure 54: Technical Changes to Tables
New asset accounting is the only asset accounting solution in SAP S/4HANA. Classic asset
accounting is no longer available. The configuration and activation is on the client level. Both
multiple valuation approaches are possible: ledger approach and account approach. Use of
the new depreciation calculation engine is mandatory (based on extension EA-FIN SAP Note:
1498047).
The actual items are as follows:
Actual data of ANEP, ANEA, ANLP, and ANLC is now stored in the ACDOCA table. ANEK
data is stored in BKPF.
© Copyright. All rights reserved.
63
Unit 3: Asset Accounting
Compatibility views FAAV_<TABLENAME> (that is, FAAV_ANEK) are provided to enable
nondisruptive reporting on old tables.
After migration, you can still access the content of old tables via views
FAAV_<tablename>_ORI.
The nonactual items are as follows:
Statistical line item in asset accounting (for example, calculation for tax purposes) items
are now stored in table FAAT_DOC_IT.
Planned depreciations and revaluations (previously ANLP and ANLC) are now stored in
FAAT_PLAN_VALUES.
Year-dependent attributes for depreciation are now stored in FAAT_YDDA.
The universal journal integration provides the following benefits:
No redundancy in data storage
Reconciliation between G/L and AA is ensured by design
Reconciliation step in financial close is not required
All nonstatistical items are updated as universal journal entries
Reporting for previous fiscal years is possible because compatibility views are available
even after migration
Transparent assignment of depreciation area to accounting principle
Depreciation posted with all details: accumulated depreciation and depreciation cost by
asset
Figure 55: Integrated Asset Acquisition
The simplification of posting logic provides the following benefits:
© Copyright. All rights reserved.
64
Lesson: Analyzing the Posting Logic of New Asset Accounting
Auditability and simplicity:
It provides independent and complete depreciation areas of equal power.
Simplified chart of depreciation:
Only one depreciation area per valuation is necessary. Additional depreciation areas (delta
areas) not required to portray a parallel valuation.
New document display:
It explains the detailed impact of any transaction to the books.
New transactions for ledger group (depreciation area) specific documents
Flexible account determination
Simple close, fast close, and soft close
Transparency throughout the period
Asset balances in real time: APC posting run is no longer required
Plan values in real time: updated with every master data change and every asset
transaction
Elimination of reconciliation steps
Fast depreciation posting run due to simple processing logic, new data structures, and
parallel processing
Navigation and drilldown per accounting principle
Posting to different periods is possible:
However, the restriction is that the beginning and end of FY must be equal.
Explain the Posting Logic in Asset Accounting
Figure 56: Example: Integrated Acquisition with Different Amounts per Accounting Principle
For an integrated asset acquisition posting, the system divides the business transaction into
an operational part and a valuating part. For the operational part (vendor invoice), the system
© Copyright. All rights reserved.
65
Unit 3: Asset Accounting
makes a posting to all ledger groups against the technical clearing account for integrated
asset acquisitions. For the valuating part (asset posting with asset capitalization), the system
generates ledger group-specific documents that it also posts against the technical clearing
account for integrated asset acquisitions.
For each ledger group that is assigned in your chart of depreciation, the system creates a
corresponding ledger group-specific document. In this way, the system ensures that the
technical clearing account for integrated asset acquisitions has a balance of zero (for each
ledger and account assignment object) for every ledger group assigned in the chart of
depreciation. So that the system can ensure the zero balance, manual postings cannot be
made to the account. The account does not appear in the balance sheet, but in the notes to
the financial statement (because it has a zero balance).
Automatic postings are made to the technical clearing account for integrated asset
acquisitions for the following transactions: asset acquisition and investment support
measures.
Figure 57: Sample Posting - Ledger Approach Transaction Vendor Invoice
The ledger approach results in the following documents:
Technical clearing account acquisition (TCA) to vendor (the
Principle fields are blank)
Ledger Grp and Account.
Asset to TCA ( Ledger Grp: 0L and Account. Principle : IFRS)
Asset to TCA ( Ledger Grp: N1 and Account. Principle : LOCA)
© Copyright. All rights reserved.
66
Lesson: Analyzing the Posting Logic of New Asset Accounting
Figure 58: Sample Posting - Ledger Approach Transaction Correction Advertising and Sales Costs
To post transactions such as corrections, you no longer need a transaction type limited to
specific depreciation areas.
You can choose the accounting principle or depreciation area (transaction
the transaction view.
AB01L) directly in
Figure 59: Sample Posting - Account Approach
For secondary depreciation areas in the accounts approach, the account is posted to contra
account: acquisition value posting. This account is assigned in the account determination
instead of the technical clearing account. This approach results in n+1 documents, where n is
the number of separate accounting principles you update in parallel.
The previous figure is an example of a company with two accounting principles. In this
example, the following documents are available:
Technical clearing account acquisition (TCA) to vendor (the
Principle fields are blank)
Ledger Grp and Account.
Asset to TCA ( Ledger Grp: 0L and Account. Principle : INT)
Asset to contra account ( Ledger Grp: LO and Account. Principle : LOC)
With an account approach, there is only one ledger 0L. The ledger groups 0L and LO both
post to the leading ledger 0L.
© Copyright. All rights reserved.
67
Unit 3: Asset Accounting
Figure 60: Assets Activated for Specific Accounting Principles
Only relevant accounting principles are represented on the asset (or on the asset class) by
their corresponding depreciation areas.
All postings issued within FIAA affect those accounting principles that are relevant for the
involved assets only.
P&L postings for all other accounting principles can be handled manually by the end user.
If a certain accounting principle is not represented on the asset by an area, which posts APC
online to general ledger, the posting is redirected to account for nonoperating expense (field
T095-KTNAIB).
If no accounting principle is represented on the asset by an area, which posts APC online to
G/L, the system issues an error. This error notification can be changed into a warning, in
which case the statistical areas in FI-AA are updated.
Figure 61: New Settlement for Assets Under Construction
You can assign the settlement rule for each line per depreciation area posting to the general
ledger (transaction AIAB ).
Accounting principle specific postings are also generated from
© Copyright. All rights reserved.
Controlling .
68
Lesson: Analyzing the Posting Logic of New Asset Accounting
Figure 62: New and Obsolete Programs for FI-AA (New)
For year-end closing, there is no separate balance carryforward needed in asset accounting.
The general balance carryforward transaction of FI transfers asset accounting balances by
default.
The current planned depreciation values are calculated automatically for the new year after
performing the balance carryforward.
Figure 63: SAP Fiori App: Display Asset Worklist
The Display Asset Worklist app provides an overview of the fixed asset masters that you are
responsible for. Your area of responsibility can be defined by a flexible set of filter values for
company code, asset class, and other asset attributes.
From any single asset, you can perform the following tasks:
Navigate to other actions from any assets to other actions such as the Change Asset
Master or Display Asset Master.
Display the Asset Master Record Segment and the time-dependent asset master
assignments in a personalized set of asset masters.
© Copyright. All rights reserved.
69
Unit 3: Asset Accounting
Focus on incomplete, in process, capitalized, or retired assets if needed. Display the
number of incomplete assets depending on the configured default filter already on the
launchpad.
Download selected assets to Microsoft Excel, e-mail a link to the personalized list, or share
it by mail.
Save a personalized and filtered list as a tile to your home page.
SAP Fiori App: Manage Fixed Asset
With the Manage Fixed Asset app, all the data for an asset is in one place. A graphical
representation of the asset's life cycle provides an overview of the asset’s status and allows
you to adjust the valuation. Key figures, such as acquisition and production cost (APC),
accumulated depreciation, and netbook value, help you to understand the asset valuation in
detail. The key figures also help you to determine why unexpected value changes have
occurred, for example when special depreciation has been posted accidentally for the fixed
accident.
To access the Manage Fixed Asset app, open the Display Asset Master Worklist app. Select a
fixed asset master data and navigate to Manage Fixed Assets using the link list or the
navigation arrow. You can also navigate to this app from the following reporting apps:
Asset History Sheet
Asset Balances
Depreciation Lists
Asset Transactions
Manage Fixed Assets Functions
The Manage Fixed Assets app provides functions that enable you to complete the following
tasks:
View key characteristics of selected assets, such as the asset number, asset class, short
description, and net book value.
Get an overview of all parallel depreciation areas and their parameters in one place, and
deep dive into the details for each depreciation area.
View key figures by area and view the depreciation due to different value corrections, such
as ordinary or special depreciation.
View the life cycle chart and determine how the values for your fixed asset are evolving.
Compare values for a range of fiscal years and several depreciation areas in parallel.
View master data of fixed assets with all their time-dependent and time-independent
assignments, such as cost center or supplier.
Add attachments.
Create notes.
Edit the asset.
© Copyright. All rights reserved.
70
Lesson: Analyzing the Posting Logic of New Asset Accounting
Figure 64: New Depreciation Run
The determination of the depreciation values of an asset and the posting of depreciation
expense takes place in the system asynchronously. It occurs as follows:
1. Calculate depreciation:
The planned depreciation is determined with each master record change and with each
posting on the asset. It is updated in the database directly.
2. Post depreciation:
The depreciation run adopts the planned asset values and posts them in financial
accounting.
Planned depreciation is determined and updated with each asset master record change and
each posting to the asset. The depreciation run posts the precalculated planned values.
The journal entry is updated in financials on the asset level.
You can perform period-end closing even if there are errors on individual assets.
You can also perform a test run, but still with the restriction for 1000 assets.
The Selection view is simplified as the Reasons for posting run (planned depreciation run,
repeat, restart, and unplanned posting run) are no longer relevant.
LESSON SUMMARY
You should now be able to:
Understand the architecture of asset accounting in SAP S/4HANA
Explain the posting logic in asset accounting
© Copyright. All rights reserved.
71
Unit 3
Lesson 2
Legacy Data Transfer Asset Accounting SAP
S/4HANA
LESSON OBJECTIVES
After completing this lesson, you will be able to:
Legacy Data Transfer Asset Accounting SAP S/4HANA
Legacy Data Transfer Asset Accounting SAP S/4HANA
Figure 65: Legacy Data Transfer Asset Accounting S/4HANA
In a new production system, after configuration and asset classification is complete, you can
then transfer data from a legacy system. You can transfer asset data automatically from the
legacy system. Alternatively, if there is only a small amount of asset data in the legacy
system, you can enter the asset master data manually using the transaction AS91. However,
the takeover values are posted separately in the posting transaction ABLDT. When you do this,
a posting is made to the transfer clearing account immediately. That is, the manual step for
the summary write-off is no longer required.
Transaction ABLDTuses an input-enabled ALV grid control. According to SAP Note 311440, it
does not support batch input. Therefore, it is not possible to create a legacy system migration
workbench (LSMW) recording for transaction ABLDT. For more information, see SAP Note
554635.
© Copyright. All rights reserved.
72
Lesson: Legacy Data Transfer Asset Accounting SAP S/4HANA
The following programs are used to transfer legacy data automatically:
For large quantities of legacy data, use the business application programming interface
(BAPI) BAPI_FIXEDASSET_OVRTAKE_CREATE. The BAPI also supports the creation and
transfer of legacy asset values in a single step. The transfer of values to existing legacy
assets is not supported. If you change existing migration values, you must first reverse the
transfer transactions before you can use BAPI_FIXEDASSET_OVRTAKE_POST to post new
values. To cancel transfer transactions, use BAPI_ASSET_REVERSAL_POST. For more
information, see SAP Note 2481644.
For several hundred assets, use Microsoft Excel (transaction AS100). Transaction AS100
can process a maximum of 5,000 assets in one file upload. However, you can split the file,
if required.
Note:
The BAPI supports only new assets for legacy assets and the optional transfer of
values. It does not support the transfer of values to an existing legacy asset or the
correction of values transferred previously.
For greater transparency, and because transfer documents are posted in the new
solution, the only way to change takeover values is to reverse the posted transfer
document and then repost it. To reverse a transfer document, a fixed asset must
not have any subsequent transactions; the legacy data transfer provides the value
foundation for this fixed asset. If follow-on transactions have already been posted
to the fixed asset, you must first reverse all transactions (preferably in reverse
sequence). You can then reverse the transfer transaction, and finally post the new
takeover values. You can then create the follow-on transactions again individually.
In the case of assets under construction (AuC), you cannot transfer cumulative APC or
accumulated depreciations. The transfer must take place by the transfer of transactions, as
follows:
In the manual case, use transaction AB01, not transaction ABLDT. Alternatively, since SAP
Note 2294012, use the new transaction ABLDT_OI.
In the case of a transfer using BAPI_FIXEDASSET_OVRTAKE_CREATE
, do not enter the
values into the CUMULATEDVALUES table; instead enter them into the TRANSACTIONS
table.
Note:
For more information, see SAP Note 2208321.
To start the legacy data transfer, in Customizing for Financial Accounting , choose Asset
Accounting
Asset Data Transfer
Set Company Code Status. Set the status of the
company code to Asset data transfer not yet completed .
You can transfer legacy data in FI-AA with the Asset data transfer not yet completed status,
but you cannot post normal transactions.
© Copyright. All rights reserved.
73
Unit 3: Asset Accounting
LESSON SUMMARY
You should now be able to:
Legacy Data Transfer Asset Accounting SAP S/4HANA
© Copyright. All rights reserved.
74
Unit 3
Learning Assessment
1. New asset accounting is the only asset accounting solution in SAP S/4HANA.
Determine whether this statement is true or false.
X
True
X
False
2. For an integrated asset acquisition posting, the system divides the business transaction
into an operational part and a valuating part. Which part posts to all accounting principles?
Choose the correct answer.
X
A Operational part (technical clearing account against supplier invoice)
X
B Valuating part (asset against technical clearing account)
3. Which of the following statements about the integration of asset accounting tables in the
universal journal are true?
Choose the correct answers.
X
A No redundancy in data storage.
X
B Reconciliation between G/L and AA is necessary.
X
C No reconciliation-step in financial close.
X
D Statistical items are updated as Universal Journal Entries.
X
E After conversion, reporting for previous fiscal years is not possible.
X
F Planned depreciations and revaluations are now stored in ACDOCA.
© Copyright. All rights reserved.
75
Unit 3: Learning Assessment
4. Which of the following reports are obsolete and deleted?
Choose the correct answers.
X
A Periodic APC postings: RAPERBxxxx
X
B Post depreciation: FAA_DEPRECIATION_POST
X
C Reconciliation postings: RAABSTxxxx
X
D Fiscal Year Change: RAJAWE00
X
E Post depreciation: RAPOSTxxxx
5. During legacy data migration,you can transfer cumulative APC or accumulated
depreciation values for assets under construction.
Determine whether this statement is true or false.
X
True
X
False
© Copyright. All rights reserved.
76
Unit 3
Learning Assessment - Answers
1. New asset accounting is the only asset accounting solution in SAP S/4HANA.
Determine whether this statement is true or false.
X
True
X
False
Correct. New asset accounting is the only asset accounting solution in SAP S/4HANA.
2. For an integrated asset acquisition posting, the system divides the business transaction
into an operational part and a valuating part. Which part posts to all accounting principles?
Choose the correct answer.
X
A Operational part (technical clearing account against supplier invoice)
X
B Valuating part (asset against technical clearing account)
Correct. The operational part (crediting the supplier) is always posted to all accounting
principles.
3. Which of the following statements about the integration of asset accounting tables in the
universal journal are true?
Choose the correct answers.
X
A No redundancy in data storage.
X
B Reconciliation between G/L and AA is necessary.
X
C No reconciliation-step in financial close.
X
D Statistical items are updated as Universal Journal Entries.
X
E After conversion, reporting for previous fiscal years is not possible.
X
F Planned depreciations and revaluations are now stored in ACDOCA.
Correct. There is no longer any redundancy in data storage (all actual items are stored in
the universal ledger) and there are no reconciliation steps with the G/L.
© Copyright. All rights reserved.
77
Unit 3: Learning Assessment - Answers
4. Which of the following reports are obsolete and deleted?
Choose the correct answers.
X
A Periodic APC postings: RAPERBxxxx
X
B Post depreciation: FAA_DEPRECIATION_POST
X
C Reconciliation postings: RAABSTxxxx
X
D Fiscal Year Change: RAJAWE00
X
E Post depreciation: RAPOSTxxxx
Correct. Only the periodic depreciation posting remains.
5. During legacy data migration,you can transfer cumulative APC or accumulated
depreciation values for assets under construction.
Determine whether this statement is true or false.
X
True
X
False
Correct! The transfer must take place by the transfer of transactions.
© Copyright. All rights reserved.
78
UNIT 4
Reporting Options
Lesson 1
Providing an Overview of Reporting Options
80
Lesson 2
Manage Global Hierarchies
87
UNIT OBJECTIVES
Understand the analytics architecture in SAP S/4HANA
Explain the different data consumption tools
Manage Global Hierarchies
© Copyright. All rights reserved.
79
Unit 4
Lesson 1
Providing an Overview of Reporting Options
LESSON OBJECTIVES
After completing this lesson, you will be able to:
Understand the analytics architecture in SAP S/4HANA
Explain the different data consumption tools
Virtual Data Model (VDM) and its Implementation with SAP S/4HANA
Scenario
You want to understand the reporting options for SAP S/4HANA Finance. You want to know
how you can leverage your existing infrastructure and see what other options are available.
You want to make the best choice for both your backend and frontend reporting and for your
analytics tools so that you can report effectively on the data posted to the system.
In the past, we periodically moved transaction data from the transactional systems (OLTP) to
dedicated, analytical (OLAP) systems, through a series of steps known as Extraction,
Transformation, and Loading (ETL). This was done because transactional systems are not
built to handle sophisticated analysis. Their focus is on optimal transaction processing. The
transaction data is physically moved to a system where the focus is on optimized analysis.
This movement creates delays is making operational data available for analysis, and there are
many points of failure along the journey, so it comes with risk. This data transfer activity
encourages the inefficient behavior of transact then analyze. Whereas we really need to be
able to analyze at the very same time that we transact for optimal decision making.
Figure 66: No More Moving Data to Begin Analysis
Additionally, the landscape is complex and expensive, and special skills are needed to
implement and run the various components in the ETL flow. One of the side-effects of the ETL
© Copyright. All rights reserved.
80
Lesson: Providing an Overview of Reporting Options
approach is that a huge amount of duplication is generated, due to the constant copying of
data from one system to the next.
With SAP S/4HANA, OLTP and OLAP are combined on a single, in-memory platform. This
means that there is no more moving data, generating multiple copies, and causing delays in
the viewing of the business performance information. We also have a much simpler IT
landscape with only the SAP HANA platform needed.
With embedded analytics in SAP S/4HANA, everything is on the same technical stack and
uses the same user interface. This structure improves the time to customer (TCO) and helps
the user to be more efficient. The embedded analytics are available inside the business
processes, making the processing more efficient. The simplified data model reduces the
redundancy of data so that more space is available to keep a longer data history. The
simplified data model reduces the number of tables, making it easier to create virtual data
models.
SAP S/4HANA blends transactions and analytics allowing operational reporting on live
transactional data.
With SAP S/4HANA, this concept is supported by core data services (CDS views) for realtime operational reporting. The content is represented as a virtual data model (VDM), which is
based on the transactional and master data tables of SAP S/4HANA. CDS views are
developed, maintained, and extended in the ABAP layer of the SAP S/4HANA system. The
system generates SQL runtime views in SAP HANA to execute the data read and
transformation inside the SAP HANA database layer.
Figure 67: CDS-Based VDM for SAP S/4HANA Embedded Analytics
The SAP S/4HANA VDM is built with ABAP-managed CDS views. ABAP-managed CDS views
are developed, maintained, and extended in the ABAP layer of the SAP S/4HANA system.
They are ABAP artifacts, and are physically stored in the ABAP repository, where the ABAP
programs reside. They do not reside in SAP HANA.
© Copyright. All rights reserved.
81
Unit 4: Reporting Options
It is advisable to refer to them carefully as ABAP-managed CDS views because there is
another type of CDS view that is managed and stored in the SAP HANA platform. These are
called SAP HANA native CDS views. These CDS views are not relevant to SAP S/4HANA
embedded analytics.
Many SAP S/4HANA embedded analytics tools directly consume the CDS views, but CDS
views also generate transient SAP BW InfoProviders. Think of these as dynamic SAP BW
InfoCubes that are created at runtime and disappear when the session ends.
This is good news, because it means you can build SAP BW BEx queries using CDS views as
the data source. It also means you can build reports with any SAP BI (BusinessObjects) tools,
making use of the CDS views, with or without a BEx query.
A key concept behind CDS views is that they are the foundation for all consumption for SAP
S/4HANA analytics and remove the need to develop the consumption layer in the database.
Figure 68: SAP S/4HANA VDM Architecture
CDS views are built in layers. The idea is to provide a set of base layer views (called private
views) to offer a high degree of re-usability of common views. Then you combine these private
views to make them more useful at the next layer (interface views).
Finally, you add more business semantics (such as filters and aggregation behavior) to
provide a view that is optimal for consumption by the application code or analytic engine
(consumption view).
At all layers, extensions can be added. Customers can also add their own views at any layer
and combine them with SAP-delivered views.
This layering model is strictly enforced by SAP to provide governance and promote controlled
extensibility.
© Copyright. All rights reserved.
82
Lesson: Providing an Overview of Reporting Options
Different Data Consumption Tools
Figure 69: Embedded Analytics Map
Analytic tools can be broken down according to the type of user, as follows:
End User
-
Multidimensional Reporting: ABAP Web Dynpro-based standard delivered reports with
flexible slice-and-dice navigation features presented through SAP Fiori.
-
SAP Smart Business Cockpits: SAP Fiori-based cockpits built using the KPI modeling
apps toolkit to create and group related KPIs and drill downs.
-
View Browser: SAP Fiori portal presenting standard and custom-created CDS views,
with ability to launch a CDS query view into a SAP Lumira, designer edition template for
basic slice and dice.
-
Embedded analytics in SAP Fiori Apps: Any SAP Fiori application that presents
concentrated analytics either standalone or part of a transaction.
Key User
-
Query Designer: An SAP Fiori app to develop custom query views on top of CDS views.
-
KPI Modeling tools: Toolkit to build KPIs, associate them with drilldowns, and assign
them to tiles.
-
Custom CDS View: Create custom CDS views using easy tool, where standard SAP
supplied views are not suitable. This tool is shared between IT and key users.
IT user
© Copyright. All rights reserved.
83
Unit 4: Reporting Options
-
Core Data Service maintenance using Eclipse: CDS is the foundation for all analytics,
provided by SAP and extendable by customers. IT users perform the maintenance
using scripts in the Eclipse editor.
The other tools listed in figure, Embedded Analytics Map, are recommended by SAP for
each user type, but are not part of the supplied embedded analytics and require separate
licenses.
Custom CDS View: Create custom CDS views using an easy tool, where standard SAP
supplied views are not suitable. This tool is shared between IT and key users.
Figure 70: SAP S/4HANA Strategic Analytics
SAP S/4HANA strategic analytics is the name given to the tools that are recommended by
SAP for each user type, but are not part of the core SAP S/4HANA license.
These tools leverage the same foundation used by embedded analytics, which are CDS views.
They are used by dedicated BI users, who need to go beyond the capabilities of embedded
analytics.
Strategic analytics focus less on the operational analytics and more on a long-term,
aggregated view of business performance.
Strategic analytics include the following areas:
SAP BW
Enterprise data warehouse used to consolidate multiple data sources, including SAP and
non-SAP, with advanced data staging, and ETL flows with strong data flow management.
Also capable of handling huge stores of data, with data lifecycle strategies.
SAP Lumira
Powerful data-mashup and visualization tool, used to create story boards that can provide
insight where data is complex.
SAP Lumira, designer edition
© Copyright. All rights reserved.
84
Lesson: Providing an Overview of Reporting Options
A developers' tool used to create advanced analytical applications and dashboards that
can be presented on any device.
SAP Analysis for Microsoft Office
Microsoft Excel-based advanced, multidimensional OLAP tool used for unrestricted, deep
exploration of data.
Other SAP BusinessObjects Tools
These tools include SAP Predictive Analytics, SAP BusinessObjects Web Intelligence, and
SAP Crystal Reports.
CDS views can be a data source to be consumed directly by the reporting tools. They can
also be used as a data source (extractor) to load BW DataStore objects.
These can then be the data source for all reporting tools shown in the figure, What is SAP
S/4HANA Strategic Analytics?
Links to Videos about Analytics Tools
Table 1: Links to Videos about Analytics Tools
Use the following YouTube links to examine the look and feel of the different reporting tools:
What
Link
Tutorials for SAP Lumira, designer edition
https://www.youtube.com/playlist?
list=PLs5htBIwERYWFt-ixnVgxsUGvQpR9E8hI
SAP BusinessObjects Dashboards 4.x Tutorials
https://www.youtube.com/playlist?
list=PLs5htBIwERYUA748i26Z9Y0Z2dXw3s29E
SAP Analysis 1.x, edition for Microsoft Office
Tutorials
https://www.youtube.com/playlist?
list=PLs5htBIwERYXTVP--IvbjaTJF0enYv6kK
SAP BusinessObjects Explorer 4.x Tutorials
https://www.youtube.com/playlist?
list=PLs5htBIwERYW9NthcmsyCMSMNwJhF6QP5
SAP BusinessObjects Web Intelligence 4.x
Tutorials
https://www.youtube.com/playlist?
list=PLs5htBIwERYUjNLyWJR2g2U2aSWPzJBou
SAP Lumira 1.17 - 1.23 Tutorials
https://www.youtube.com/playlist?
list=PLs5htBIwERYWqmHlnbAB6gSQ3b39JzWLa
SAP Crystal Reports 2011 / 2013 Tutorials
https://www.youtube.com/playlist?
list=PLs5htBIwERYULWPdq3xdVb6R68Up_kCFu
© Copyright. All rights reserved.
85
Unit 4: Reporting Options
Figure 71: SAP S/4HANA Analytics and SAP Business Warehouse
SAP S/4HANA analytics together with SAP Business Warehouse (SAP BW), provides a suite
of analytical services.
SAP BW covers the following requirement examples:
Consolidated reporting on data collected from several SAP and non-SAP applications, and
for data governance
Aggregated reporting on historical data that might not be online in the underlying SAP
business system
For a case study with implementation scenarios of SAP BW together with SAP S/4HANA
analytics, see the following URL: http://scn.sap.com/docs/DOC-55312
.
LESSON SUMMARY
You should now be able to:
Understand the analytics architecture in SAP S/4HANA
Explain the different data consumption tools
© Copyright. All rights reserved.
86
Unit 4
Lesson 2
Manage Global Hierarchies
LESSON OBJECTIVES
After completing this lesson, you will be able to:
Manage Global Hierarchies
Manage Global Hierarchies
Global Hierarchy Maintenance
Figure 72: Global Hierarchy Maintenance
Today, basically each separate master data record type has an own logic and app for group or
hierarchy maintenance. The app Manage Global Hierarchies is a single point of entry for the
maintenance of different accounting hierarchies in SAP S/4HANA.
The Manage Global Hierarchies app has the following key features:
Modern, consistent UI and persistency in one Hierarchy - SET group
Create and edit of multiple accounting hierarchies, for example, cost center, profit center,
functional area and financial statement versions
Different timeframes under specific hierarchy IDs,
Status control (draft vs. active)
Export of hierarchies to spreadsheets / Import hierarchies from spreadsheets
© Copyright. All rights reserved.
87
Unit 4: Reporting Options
Supports the maintenance of node texts in different languages
Assign semantic tags to hierarchy nodes and G/L accounts
Add Aging attributes for hierarchy nodes for reporting based reclassification
Support custom extensibility - custom hierarchy, custom field and custom logic
Compatible with existing hierarchies
LESSON SUMMARY
You should now be able to:
Manage Global Hierarchies
© Copyright. All rights reserved.
88
Unit 4
Learning Assessment
1. You want to provide your analysts with a tool for powerful visualizations and exploration.
Which of the following would you recommend?
Choose the correct answer.
X
A SAP BusinessObjects Web Intelligence
X
B SAP Lumira
X
C SAP Crystal Reports Enterprise
2. Can the Manage Global Hierarchies app be set as time-dependent?
Determine whether this statement is true or false.
X
True
X
False
© Copyright. All rights reserved.
89
Unit 4
Learning Assessment - Answers
1. You want to provide your analysts with a tool for powerful visualizations and exploration.
Which of the following would you recommend?
Choose the correct answer.
X
A SAP BusinessObjects Web Intelligence
X
B SAP Lumira
X
C SAP Crystal Reports Enterprise
Correct. SAP Lumira is the correct analytics tool for creating visualizations and data
exploration.
2. Can the Manage Global Hierarchies app be set as time-dependent?
Determine whether this statement is true or false.
X
True
X
False
Correct. The Manage Global Hierarchiesapp can be set as time-dependent.
© Copyright. All rights reserved.
90
UNIT 5
Basic Cash
Management Capability
Lesson 1
The Basic Cash Management Capability
92
Lesson 2
Bank Account Processing with Bank Reconciliation Accounts
95
UNIT OBJECTIVES
Understand the Basic Cash Management Capability
Understand Bank Reconciliation Accounts
© Copyright. All rights reserved.
91
Unit 5
Lesson 1
The Basic Cash Management Capability
LESSON OBJECTIVES
After completing this lesson, you will be able to:
Understand the Basic Cash Management Capability
The Basic Cash Management Capability
Customers who do not have the license for SAP Cash Management can run the basic cash
management version. It offers only basic functions on managing bank account master data,
and any customer who uses the SAP S/4HANA Finance can use this functionality. Previously
this was known as the Bank Account Management light. Starting from SAP S/4HANA Finance
1503, transaction code FI12 is disabled and customers must use Bank Account Management
to maintain house bank accounts. Transaction FI12 is active with release 1809. Note that with
this transaction, it is only possible to create House Banks like before. To create the House
Bank Accounts you still have to access either the NWBCaApp or the Fiori App Manage Bank
Accounts . This transaction has a button to launch the NWBC App for Create/Change based
on the action you execute. (SAP Note 2646577)
Figure 73: SAP S/4HANA Basic Cash Management
The basic cash management capability can integrate with the following data sources:
Memo Records
Financial Operations
Treasury and Risk Management
© Copyright. All rights reserved.
92
Lesson: The Basic Cash Management Capability
Consumer and Mortgage Loans
Contract Accounts Receivable and Payable
Sales and Distribution
Materials Management
With the basic cash management capability, cash managers can centralize the management
of bank accounts and perform the following tasks:
Manage banks and house banks (only a subset of fields that are needed for enabling the
payment process).
Define bank accounts and house bank accounts (only common attributes are supported).
Displaying bank accounts in a list view.
Import and export bank accounts.
Replicate house banks, house bank accounts, and bank accounts by using IDoc
(Intermediate Document).
Monitor cash positions and liquidity forecasts.
Manage memo records using the app or transactions FF63 and FF65.
Alongside the functionality for bank accounts, the SAP S/4HANA Basic Cash Management
has five SAP Fiori theme apps that provides the following processes:
Display Cash Position (FF7AN)
-
With this app, you can gain an overview over short-term liquidity trends. This app
provides you with information on the current financial situation in your bank accounts
and bank clearing accounts.
-
The cash position is based on memo records and One Exposure from Operations.
Display Liquidity Forecast (FF7BN)
-
With this app, you can gain an overview of medium-term liquidity trends. This app
shows changes in liquidity in the liquidity items and planning groups.
-
The liquidity forecast is based on memo records and One Exposure from Operations.
Edit Memo Records (FF63)
-
With this app, you can create memo records manually of incoming and outgoing
payments that are not transferred to the SAP Cash Management system via actual
postings.
-
You can gain relevant information on the expected payment flows. The data is
consumed by the cash position and liquidity forecast.
-
You differentiate between the payment advice relevant for the cash position and the
planned items relevant for the liquidity forecast.
Payment advice:
© Copyright. All rights reserved.
93
Unit 5: Basic Cash Management Capability
-
You can enter notified incoming payments, noted items, provisional bank statement
postings, fixed-term deposits, loans revenue, all bank fields, and so on, as Memo
Records Payment Advice in the system.
Planned items:
-
You can enter all subledger fields, noted items, general planning, and so on, as Memo
Records Planned Items in the system.
Display Memo Records (FF65)
-
With this app, you display memo records in a list. You can select memo records to
transfer them afterwards into an archive.
-
After they are archived, the records are no longer relevant to the cash position and
liquidity forecast, but are still available for evaluations (for example, for calculating the
average interest on fixed-term deposits from last year).
Cash Concentration via Payment Advice (FF73)
LESSON SUMMARY
You should now be able to:
Understand the Basic Cash Management Capability
© Copyright. All rights reserved.
94
Unit 5
Lesson 2
Bank Account Processing with Bank
Reconciliation Accounts
LESSON OBJECTIVES
After completing this lesson, you will be able to:
Understand Bank Reconciliation Accounts
Bank Account Processing with Bank Reconciliation Accounts
Figure 74: House Bank Account - G/L Account Type: Cash Account (Bank Reconciliation Account)
Up to now, each time you created a new house bank account, you also had to create a new
G/L account to enable payment processes for the new house bank account. Depending on the
number of house bank accounts that you needed to create. Overtime this could lead to a high
number of G/L accounts.
With the new procedure, you can create bank reconciliation accounts that can be assigned to
multiple house bank accounts. For this bank reconciliation account, you can create and assign
bank clearing accounts for each of your payment methods. When this set of G/L accounts is
© Copyright. All rights reserved.
95
Unit 5: Basic Cash Management Capability
set up according to your requirements, you can assign this to all relevant new house bank
accounts that you create.
Example: If your company makes payments using multiple national and international banks,
you can just define two sets of G/L accounts. For the national banks, you assign all your local
house bank accounts to one bank reconciliation account with one bank sub-account (that is,
clearing account) per payment method. For international banks, you assign all your foreign
house bank accounts to one bank reconciliation account with one bank sub-account (that is,
clearing account) per payment method.
The Bank G/L account is assigned to the G/L account type Cash Account in the master
record. You use the G/L account subtype B to define the use of the G/L account as a Bank
Reconciliation Account .
Create a bank clearing account in General Ledger Accounting for each required payment
method. These accounts are also assigned to the G/L account type Cash Account. The G/L
account subtype S - Bank Sub Account is used to define the use as a bank clearing account.
The bank reconciliation account is then assigned directly to the Bank Sub Accounts in the G/L
account master record.
This means that there is an n:1 relationship between house bank accounts in Bank
Relationship Management and the G/L account in General Ledger Accounting.
Possible advantages:
Reduced reconciliation effort between the Cash Management and General Ledger
Accounting departments when creating new bank accounts in the system.
Reduced number of bank and bank clearing accounts in General Ledger Accounting over
the time.
Note:
There is no need to migrate or move from the known Balance Sheet Approach to
the Bank Reconciliation Account Approach. Since you control the method through
master data settings in the House Bank Account an individual approach for each
House Bank Account is possible. Thereby a side-by-side approach is feasible. This
also implies that no big-bang solution must be implemented as customer have to
option to gradually move to the Bank Account Reconciliation, if desired.
© Copyright. All rights reserved.
96
Lesson: Bank Account Processing with Bank Reconciliation Accounts
Figure 75: Account Determination for Self Initiated Payments (SIP) – Bank Reconciliation Account Approach
When working with the Bank Reconciliation Account Approach and self initiated payments the
bank sub-account determination is slightly different to the current setup for Balance Sheet
Accounts.
The bank sub-account for payments in this case is not determined anymore through the
Ranking Order assignment in the IMG under Financial Accounting
Accounts Receivable and
Accounts Payable
Business Transactions
Outgoing Payments
Automatic Outgoing
Payments
Payment Method/Bank Selection for Payment Program
Set Up Bank
Determination for Payment Transactions.
The account determination is defined the following way:
1) Set the account symbols relevant for self initiated payments in Customizing under Financial
Accounting
Bank Accounting
Business Transactions
Payment
Transactions
Electronic Bank Statement
Make Global Settings for Electronic Bank
Statement.
2) Define the country, payment method and the linked account symbol in Customizing under
Financial Accounting
Accounts Receivable and Accounts Payable
Business
Transactions
Outgoing Payments
Automatic Outgoing Payments
Payment Method/
Bank Selection for Payment Program
Assign Account Symbol to Payment Methods.
3) Through the customizing path Financial Accounting
Bank Accounting
Business
Transactions
Payment Transactions
Electronic Bank Statement
Make Global Settings
for Electronic Bank Statement. and the assignment of accounts to account symbols, the
system is able to determine the G/L Clearing Account in a combination of the
4) Setting of the G/L Account in the House Bank Account Data and the
5) G/L Clearing Account as masked entry -> here 11000000 plus the +++++++020 =
11000020.
LESSON SUMMARY
You should now be able to:
Understand Bank Reconciliation Accounts
© Copyright. All rights reserved.
97
Unit 5
Learning Assessment
1. The Basic Cash Management offers workflow capabilities for managing maintenance of
bank accounts.
Determine whether this statement is true or false.
X
True
X
False
2. Which of the following statements about the Bank Account Processing with Bank
Reconciliation Accounts are true?
Choose the correct answers.
X
A When you create a new house bank account, you can decide whether you use the
new procedure with the bank reconciliation account approach or whether you use the
known procedure of creating a new G/L account as a balance sheet account.
X
B When you create a new house bank account, you can only use the new procedure
with the bank reconciliation account approach.
X
C Before you can create a new house bank account with the bank reconciliation
procedure, you need to make sure that the bank reconciliation G/L account exists.
This G/L account must be created with Cash Account as its G/L account type and
with Bank Reconciliation Account as its G/L account subtype.
© Copyright. All rights reserved.
98
Unit 5
Learning Assessment - Answers
1. The Basic Cash Management offers workflow capabilities for managing maintenance of
bank accounts.
Determine whether this statement is true or false.
X
True
X
False
Correct. Bank Account Management offers workflow capabilities for managing
maintenance of bank accounts.
2. Which of the following statements about the Bank Account Processing with Bank
Reconciliation Accounts are true?
Choose the correct answers.
X
A When you create a new house bank account, you can decide whether you use the
new procedure with the bank reconciliation account approach or whether you use the
known procedure of creating a new G/L account as a balance sheet account.
X
B When you create a new house bank account, you can only use the new procedure
with the bank reconciliation account approach.
X
C Before you can create a new house bank account with the bank reconciliation
procedure, you need to make sure that the bank reconciliation G/L account exists.
This G/L account must be created with Cash Account as its G/L account type and
with Bank Reconciliation Account as its G/L account subtype.
© Copyright. All rights reserved.
99