SFin - Record To Report Financial Accounting

Global Business Services
SAP SIMPLE FINANCE

GL, AP & AR
Shivesh Sharma
Basvi Ayuluri
Ambuj Garg August 14, 2015
1 IBM Confidential © 2015 IBM Corporation

Welcome

Training Details:
Training purpose:
To gain SAP Simple Finance overview, lessons learned, and key points for new SAP
S/4 HANA Simple Finance implementations.
Target Attendants :
•FI-CO Consultants
•Team leads
•Project managers
•FI-CO Business users
The Curriculum:
This training covers the following 5 courses.
1. Simple Finance overview In addition following 4 Exercises
are also included:
2. Finance (GL, AP, AR) – This Course 1. Exercises: Finance
3. Acquire to Retire 2. Exercises: Acquire to Retire
4. Treasury and Banking 3. Exercises: Treasury and Banking
5. Controlling 4. Exercises: Controlling

Agenda
Unit Description
1 Welcome
2 Simple Finance Architecture
3 Functionality Impact
a. Functionality Change
b. Summary of Changes in Transactions (T-codes)
c. Summary of Table Changes
d. Configuration Changes
4 WRICEF Impact
5 User Interface Apps (FIORI)
6 Closing process impact
7 Bolt-Ons Impact
8 Key Limitations/Restrictions
9 Security/Authorizations
10 HANA views/reporting available in Simple Finance 2.
11 Lessons Learnt and Pain Points
12 Appendix A – HANA Live Views for Finance

Pop Quiz: Ice Breaker
 How many SAP FICO consultants currently work for IBM R2R practice in the United
States?
A. 391
B. 242
C. 182
D. 121

Simple Finance
Architecture

Architecture: Traditional SAP Finance
Traditionally, SAP has stored GL, Customer, and Vendor balances and open item statuses in
a number of extra database tables in order to support reporting
Customer Vendor General Ledger Controlling
COSS
KNA1 LFA1 SKA1 COBK COEP
COSP
KNC1 LFC1 GLT0
Finance
Index Tables (i.e. Open Item Tracking)
BKPF BSEG BSIS BSID BSET BSIK BSAK BSAS BSAD
Legend:
Update
Insert
A vendor invoice with 3 accounting line items would update at least 10 tables at least 15 times!

Architecture: New SAP Simple Finance

All the fields from sub modules like Management Accounting, Asset Accounting, Material
Ledger, Profitability Analysis are available in ACDOCA Table

Architecture: Simple Finance 1.0
 Simple Finance 1.0 (powered by HANA) can achieve the same reporting directly off of the line
item tables without the need to store balances or open item statuses separately
Customer Vendor
Vendor General Ledger Controlling
KNA1 LFA1
LFA1 SKA1 COBK COEP
Finance
BKPF BSEG
Legend:
Update
Insert
The same vendor invoice in Simple Finance would update at least 4 tables 7 times

Architecture: Simple Finance 2.0
 Simple Finance 2.0 (powered by HANA) can achieve the same reporting directly from table
ACDOCA without the need to store balances or open item statuses separately
Customer Vendor
Vendor General Ledger Controlling
KNA1 LFA1 SKA1 COBK COEP
Finance
BKPF ACDOCA BSEG
Legend:
Update
Insert
The same vendor invoice in Simple Finance 2.0 would update at least 4 tables 5 times

Pop Quiz
How does Simple Finance differ from Traditional Finance?
A) BSIS
B) BSIK
B) BSIK
Q: Which of the following

tables are eliminated in C) BSID
simple finance:
D) FAGLFLEXT
E) All of the Above

Process and Functionality

Impact

Master Data impact

GL Accounts & Cost Elements – Transition to Simple Finance 2.0
Traditional SAP As of sFIN 2.0

Maintain Single Transaction
GL Account in FI Maintenance
Balance Sheet Balance Sheet

Accounts Accounts
Profit & Loss Non Operating

Accounts Maintain Expenses/Revenues
Cost Element in CO
Primary Cost Primary Cost

Elements Elements
Secondary Cost Secondary Cost

Elements Elements

Master Data in Traditional Finance

GL Accounts and Cost Elements are created separately
 In Traditional Finance the GL accounts and Cost Elements were separately maintained

Master Data impact in Simple Finance

Merge of GL accounts and Secondary Cost Elements
 As of version 2.0, logic for the maintenance and use of General Ledger accounts and Secondary
Cost elements have merged.
A new account type value has been added for The field Cost Element Category has been added to the
“secondary costs” Control Data Tab
Master Data impact in Simple Finance

Merge of GL accounts and Secondary Cost Elements
Unified Master Data Maintenance Effects on Reporting

• Chart of Accounts covers balance sheet and all P&L • Secondary cost elements appear in
accounts GL reporting.
• Cost elements move into GL account logic that • Postings on secondary cost elements
means always balanced to zero
− No time dependency for cost elements any longer • The real time integration mapped
− No default account assignments in cost secondary to primary accounts.
element master • In the past postings on secondary
• P&L accounts can be classified as cost cost elements appeared in GL
elements that means cost elements reporting on primary accounts.
became GL accounts with a specific • With SAP Accounting postings on
semantic secondary cost elements appear directly on
• Cost element type remains ensuring the secondary cost element in GL reporting.
secondary cost elements cannot be • The P&L version have to be updated accordingly
posted to directly - only via CO allocations
• Default account assignments maintained
in cost element master are migrated to OKB9
In the past postings on secondary cost elements effecting GL

reporting entities (e.g. profit center, functional area) created real
16 time integration postings.
IBM Confidential © 2015 IBM Corporation
Functionality Change
Ledger – Standard & Appendix
• Leading ledger concept remain the same , it will contain full set of line items in ACDOCA & will be basis for
actual CO data (assigned to actual VERSN 0)
• Non-leading Standard Ledgers, as in earlier version can still be assigned to selected company codes, it will
contain full set of line items in ACDOCA, Inherits currency configuration of leading ledger and can have
different fiscal year variant / open period variant possible.
• Appendix ledger contains only adjustment postings. In reporting appendix ledger inherits postings of base
ledger.
• It defined on the top of base ledger, allows only manual postings, inherits currency settings and fiscal year
variant of base ledger but can have separate open period variant and company code assignment
• It can report on all transaction data of base ledger so it allow to create views without affecting base ledger

Universal Journal Ledger- Organization
Business Data of Universal Journal Entry is organized in Ledgers
What is a Ledger in sFIN? Characteristics

A ledger / company represents an accounting principle All line items in the Universal Journal are contained in
(except account ACDCOA table.
solution)
Benefits
Universal Reporting on the
Journal Ledger appendix ledger includes
Types the data of the base ledger.
Standard Appendix ledgers can point to
another appendix ledger instead of a
The Standard ledger is base ledger - creating a hierarchy of ledgers.
modeled after the existing
New GL ledger and contains 1 leading leader and 1 or Benefit of reduced data footprint and
more non-leading ledgers reduced reconciliation as only (manual) delta
postings are maintained in the appendix ledger. It defined on
Appendix (2.0 only) the top of base ledger, allows only manual postings, inherits
This ledger is intended as a management reporting tool currency settings and fiscal year variant of base ledger but
and only contains adjustment postings. In reporting can have separate open period variant & company code
appendix ledger inherits postings of base ledger. assignment

Ledger – Leading & Appendix
Standard Ledger Appendix Ledger
Leading Ledger Appendix Ledger
• There must be exactly one leading • Is defined on top of a the base or standard ledger and only accepts ledger
ledger and is assigned to all company specific manual adjustment postings, but reporting for the ledger will also
codes. Ledger 0L is delivered as contain transactions data of underlying base ledger
leading ledger • Inherits currency settings and fiscal year variant
• Defines document number (BELNR) • Separate company code assignment and
for all ledgers. • Allows for control by its own Open Period Variant
• Basis for actual CO data (assigned to • Can be used e.g. to create a management views without influencing the
VERSN 0). data in the base ledger.
• Contains full set of line items in • Several appendix ledgers can be defined onto the same base ledgers, but
ACDOCA. not on top of an existing appendix ledger (no stapling)
Additional Non-leading Standard
Ledgers
• Can be assigned to some company Universal
codes. Appendix Ledger A
Journal Appendix Ledger B
• Contains full set of line items in “Post into closed periods
for restatement purposes” Appendix Ledger C “Distribute revenues
ACDOCA. differently than in legal
“Adjustments for
• Inherit currency configuration of consolidation view”
leading ledger (in SFIN 2.0 SP0). purposes”
• Deviating fiscal year variant / open
period variant possible.
Base Ledger 0L - US-GAAP

Summary of Changed Transactions
OLD Transaction Use NEW Transaction
Foreign Currency
FAGL_FC_VAL FAGL_FCV
Valuation
GL Master Data
FS01/FS02/FS03 This can be achieved by FS00
maintenance

Summary of Table Changes
Area Obselete Tables Details of Tables used Tables in use Details of Table
Document header
Document Header for Accounting for Accounting
Header Document BKPF documents
BSIS GL Open Item Table
BSAS GL Cleared Item Table
GL GLT0, GLT1, GLT3 GL Totals Table

BSID Customer Open Item Table
ACDOCA Universal Journal

BSAD Customer Cleared Item Table
AR KNC1, KNC3 Customer Totals Table
BSIK Vendor Open Item Table
BSAK Vendor Cleared Item Table
AP LFC1, LFC3 Vendor Total Tables
New GL FAGLFLEXA New GL index teable
New GL FAGLFLETXT New GL totals Table

Summary of Table Changes

Comparison of BSEG and ACDOCA
 Dimensions
• ACDOCA has fields from CO, ML, AA that are not in BSEG
• BSEG has dedicated fields for open item management/payment that are not in ACDOCA
 Content
• Due to 999 document lines limitation, BSEG is usually aggregated. This limitation does not exist
in ACDOCA
• ACDOCA stores the full detail needed for CO, ML, AA
• ACDOCA stores all CO internal postings. These are not posted to BSEG
• ACDOCA stores carry forward and correction lines from migration. These lines are not stored in
BSEG.
 Definition of BSEG > did not foresee the requirement to store
• To store different GAAPS in parallel (key like ledger is missing)
• To store “split” document lines (receivables/payables)
 BSEG was designed to handle open item management and payment efficiently
• Open items must not be split and must not be doubled or tripled according to GAAP

Pop Quiz
Table Changes
A) FAGLFLEXA
B) BSEG
Q: Which table is
being replaced by
ACDOCA
C) SKB1
D) None of the Above

Pop Quiz
Changed Transaction
A) FS00
Q: What transaction B) FSP0

would you use in
sFIN to create a GL
account in a
Company Code
Segment C) FS00

Pop Quiz
Changed Transaction
A) FS01
B) FS02
Q: Which of the
transactions are not
in use
C) All of the above

Configuration Changes
Sequence of Configuration for New Implementations

1. Company Codes
– Create Company Codes
– Maintain Global Data
2. Controlling Area
• Create and configure controlling area
• Assign Company Codes
3. Ledger
• Assign Company Codes
• Configure Currencies / Accounting Principle
4. CO Integration
• Configure CO Integration
5. Run consistency check by calling transaction FINS_CUST_CONS_CHK and clean up inconsistencies

 The functionality for copying company codes has been expanded and now includes the
controlling area assignment which ensures that the currency settings are consistent.
Transaction: EC01 Copy Company Codes
 Note: If the controlling area is not included when copying a company code the currency
setting have to be checked after the company code is assigned to a controlling area

Configuration Changes- Ledgers

Traditional Finance Simple Finance
Define Ledgers for

General Ledger V_FAGL_T881
Accounting
Define Settings for
Journal Entry Ledger
Define Currencies
TC = OB22
of Leading Ledger
FINSVC_LEDGER
Define & Activate

V_FAGL_T882G
Non-Leading Ledgers

Ledger – Standard & Appendix
• Define Leading Ledger

• Make the ledger a Standard or Appendix Ledger
• Set the standard ledger as a base for the appendix ledger

Appendix Ledger
• Is defined on top of a base ledger, which is a standard ledger.

• Inherits in reporting all transaction data of underlying base ledger.
• Contains physically only line items posted to appendix ledger only.
• Inherits currency settings and fiscal year variant of base ledger.
• Separate company code assignment (subset of base ledger) Separate Open Period Variant

Level 1 - Define Ledgers for Unified Journal Entries
Ledger (Standard or Appendix) have to be defined

Level 2 - Company Code Assignment to Ledger-
Level 2: Company Code Assignment
• All Company Codes have to be assigned to the Leading Ledger.
• Company Code Assignments for Leading Ledgers will default in the view maintenance

Level 2 - Ledger specific Company Code Settings
• The below screen shot is the detailed view of the Company Code settings
• Please note that these settings have the Co Code settings for the ledger
1. Local Currency settings- Which are defaulted from the Co Code
settings
2. Global Currency for Controlling. This currency is not used for GL
3. Additional currencies can also be defined.

Fiscal Year Variant

• Must match controlling area setting for leading ledger
• Non leading ledger may have deviation fiscal year variants
Posting Period Variant

• Defines open periods
• Check for leading ledger / representative ledger in ledger group
Parallel Accounting using G/L Accounts

• Flag switches off the check, that Ledger / Company is assigned to one Accounting Principle

Each Ledger (Standard or Appendix) is assigned to a Accounting Principle

Configuration Changes- Document Types and Numbering

Document Types and Numbering
Going forward accounting entries in SAP will have a common Document Number
• The existing use of Document Type / Number combination in the General Ledger
View per Ledger is obsolete
• The standard Document Type and number of entry view will be used for all ledgers
except in the case it is required otherwise

Configuration Changes- Document Types and Numbering

The Financial document for P/L accounts still generates Controlling documents
• The Controlling document so generated from the FI document is a Internal cryptic

document number into field CO_BELNR
• It is needed for CO compatibility views & groups universal journal entries from CO
perspective
• The controlling number ranges are still needed as before for Internal CO postings
Configuration Changes- CO Integration

CO Integration
As of Simple Finance 2.0, the existing CO Real time integration into New GL is obsolete.
• Secondary cost elements will no longer be mapped to GL accounts
• Only account determination for intercompany accounts will remain

Configuration Changes- CO Integration

CO Integration
As of Simple Finance 2.0, the concept of reconciliation ledger has been completely
eliminated.
The need does not arises as CO & FI have been integrated by architectural changes in GL and
Cost element master

Pop Quiz
Configuration
A) True
When you copy a company code in
Simple Finance, the controlling
area are included and the currency
settings are inherently in sync.
B) False

WRICEF’s Impact

WRICEF’s Impact
Secondary Cost Elements in FSV

In earlier version of SAP, The Secondary Cost elements could not be displayed in the Financial
statement. In Simple Finance, the secondary Cost elements are created as GL accounts. This gives an
option of Secondary Cost elements being viewed in Financial Statement Version

User Interface Apps

(FIORI)

FIORI- Implementation steps for FIORI App
ECC Configuration
• Create System Alias
• Connection Settings to SAP Gateway
• Activate App-Specific Gateway Services Gateway
• Activate UI5 Application
LaunchPad Configuration
• Maintaining SAP Gateway OData Services
• Configuring ICF Nodes for Local Gateway Deployment SICF Services
• Configuring ICF Nodes for Remote Gateway System
Security
• Role Creation in ECC and Gateway

FIORI- Transactional Apps

Below is a list of FIORI applications. The details can be found in the reporting and appendix segment
AppId AppName Description
You can use this app to check G/L account line items. You can switch between the general
ledger view and entry view. In both views you can use filter criteria to choose whether
the app should display open and cleared items for OI-managed accounts, or all of the
Display G/L Account Line items for an account. You can select the line items based on a key date or after the
F0706
Items clearing date in connection with a key date. In the entry view, you can also choose
whether the app should display normal, noted, or parked items only, or all items. You can
group, sort and filter the results list using various characteristics. You can show numerous
additional characteristics, and also swap the order of the columns in the list.
With this transactional app, you can check and compare the balances, and the credit and
debit amounts of a ledger in a company code for each period of a fiscal year. You can
F0707 Display G/L Account restrict the data to a single general ledger account, or other selection criteria (for
F0708 Balances example, profit center). In a further view, you can compare the balances relating to
several fiscal years with each other. To make an additional detailed check of the data,
you can call the related line items in the Display G/L Account Line Items app
With the transactional app G/L Documents you can analyze your accounting documents
and create reversals in order to make adjustments. Filtering and selection criteria enable
you to quickly find documents, for example based on the document type or the user. The
information provided includes the G/L accounts posted, other account assignment
F0717 Manage G/L Documents objects, and any sales or purchase taxes. You can create new G/L documents based on
other G/L documents. Display variants allow you to add or remove fields. You can enter
notes or add attachments to explain the posting. Information is shown on any related
documents, such as purchase orders or incoming invoices. Amounts can be displayed in
different currencies, such as local currency or transaction currency


FIORI App – F0706 Display GL line Items
The view can be switched between general ledger view and entry view. In both views can be filtered. There is a criteria to
choose whether the app should display open and cleared items for OI-managed accounts


FIORI App – F0717 Manage GL documents
Accounting documents can be analyzed to create reversals in order to make adjustments. Filtering and selection criteria enable
a fast find for documents, New GL documents can also be created based on reference documents


With the transactional app Post G/L Document you enter manual postings to G/L
accounts. For example you can make adjusting entries during period-end closing, or
record business transactions that have no source document (such as expenses paid with
petty cash). Applicable taxes can optionally be calculated automatically as you enter the
F0718 Post G/L Document
items. You can specify additional account assignment objects such as cost centers, orders,
or materials. You can enter notes or add attachments to explain the reason for a posting.
Postings can be made in all relevant ledgers for the accounts for which you are
responsible
With the transactional app Manage G/L Account Master Data, you can search, create,
Manage G/L Account
F0731 display, and edit the master data of G/L accounts. You can also easily add new G/L
Master Data
accounts from scratch or based on existing accounts.
With the transactional app Display Chart of Accounts, you can display G/L accounts
according to where they are assigned in the financial statement version you selected.
F0763 Display Chart of Accounts You can also display accounts that are as yet not assigned anywhere in the financial
statement version. From an individual account number, you can also access an app where
you can edit that account.
With the transactional app Open Posting Periods you can define the open and close
F0806 Open Posting Periods
posting periods
With the transactional app, you can make important decisions via mobile or desktop
F0862 My Inbox devices anywhere and anytime. Using this app, you can process your standard and
custom workflow tasks based on the decision options defined in the back-end system


FIORI App – F0806 Open & Close Posting Period
Financial Periods can be opened and closed using FIORI apps

FIORI- Analytical Apps

The analytical app displays the Key Performance Indicator (KPI);Financial Close
Financial Close Delayed Tasks. You can display the delayed tasks in a closing cycle. You can also find
F0519
Delayed Tasks out about the reasons for the errors and follow up through SAP Jam or emails so that
the responsible agent can speed up
This analytical app displays the Key Performance Indicator (KPI);Financial Close
History. You can track the historical close information to find out whether the financial
Financial Close close in the previous posting periods was on track. By analyzing the root causes for
F0695
History errors or delays in the previous posting periods, you can improve the financial close
cycle so that the closing tasks can be completed on time or with reduced delays and
errors in the future
This analytical app displays the Key Performance Indicator (KPI) &;Financial Close
Financial Close Overall;. You can find out about the overall delay in hours of a closing cycle. You can
F0522
Overall Delay also find out about the reasons for the overall delay and follow up through SAP Jam or
emails so that the responsible agent can speed up.
This analytical app displays the Key Performance Indicator (KPI) Financial Close
Progress;. You can get an overview of the completion status of the tasks in a closing
Financial Close cycle. This KPI tile shows you the number of tasks that are open, in progress, with
F0521
Progress errors, and completed, respectively. You can choose to display such data by different
views, such as region and company. This allows you to find out, for example, how
many tasks have run into errors in a specific region or company


This analytical app displays the Key Performance Indicator (KPI) Financial Close
Progress (Due Today) You can get an overview of the completion status of the tasks
Financial Close that are due today. This KPI tile shows you the number of such tasks that are open, in
F0520 Progress (Due progress, with errors, and completed, respectively. You can choose to display such data
Today) by different views, such as region and company. This allows you to find out, for
example, how many tasks that are due today have run into errors in a specific region or
company
This analytical app displays the Key Performance Indicator (KPI) ;Financial Close Tasks
Financial Close
with Errors. You can display the tasks with errors in a closing cycle. You can also find out
F0518 Tasks with
about the reasons for the errors and follow up through SAP Jam or emails so that the
Errors
responsible agent can speed up


FIORI App – F0518 Financial Close Tasks with errors
This App displays the errors encountered in the Financial close process. It also tells the responsible person executing the tasks
and the errors

FIORI- FACT Sheet (Master Data) Apps

This fact sheet displays contextual information about the Cost Element.
F0125 Cost Element You can navigate to its related business objects and you can access
related transactions in operational systems.
This fact sheet displays contextual information about the Cost Element
Cost Element
F0126 Group. You can navigate to its related business objects and you can access
Group
This fact sheet displays contextual information about the G/L Account.
F0129 G/L Account You can navigate to its related business objects and you can access
This fact sheet displays contextual information about the G/L Accounting
G/L Accounting
F0130 Document. You can navigate to its related business objects and you can
Document
access related transactions in operational systems.
This fact sheet displays contextual information about the Functional Area
Functional Area
F0727 Group business object. You can navigate to its related business objects,
Group
and you can access related transactions in operational systems.</p>
This fact sheet displays contextual information about the Functional Area
F0728 Functional Area Group business object. You can navigate to its related business objects,
and you can access related transactions in operational systems.

FIORI- My Inbox App

FIORI App – My Inbox
This App displays customized display for the items we care about for example “Approval of Appropriation request”
Through this App the user can Approve, Reject, Forward or postpone a Appropriation request
There is no need for him to go in Business workplace and approve.

FIORI- My Inbox App

FIORI App – My Inbox
The below screen shot shows that the same request was created in SAP went to a particular approver.

Closing Process Impact

Closing Process Impact
• Closing process will be faster as processing steps like FI-CO recon is eliminated
• Elimination of period-end closing tasks for deriving market segment information
• No more settlement of sales order items
• No cost center allocations to profitability
• The bottlenecks for intercompany reconciliation are removed since ICR can be run any time.
• The closing Cockpit also integrates with FIORI and facilitates user running / Scheduling tasks from
the apps itself

SFIN – Closing Cockpit

 Feature Closing Cockpit  Add on 2.0 Feature Closing Cockpit
 Activities recur periodically.  Event-driven organization of closing activities

 Multiple responsible agents are involved.  The bottlenecks for intercompany reconciliation are
 The activities are performed within a process removed since ICR can be run any time
that has a fixed chronological sequence or is  Elimination of period-end closing tasks for deriving
determined by dependencies. market segment information
• No more settlement of sales order items
 The activities need to be supported by a shared,
• No cost center allocations to profitability
uniform interface for everyone involved.
 The status of all periodic activities needs to be  Process overview and monitoring options
documented and made transparent and  The closing Cockpit also integrates with FIORI and
available for everyone involved. facilitates user running / Scheduling tasks from the
apps itself
 Analysis tools

Financial Close FIORI apps

SAP Financial Closing Cockpit functionality will be used. This tool allows to schedule closing steps from the Time
table, plan jobs, execute tasks, monitor closing activities, analyze and follow-up the progress of the period-end
close Time Table.
Financial Close History

The analytical app displays the Key Performance Indicator (KPI) Financial Close History. You can track the historical
close information to find out whether the financial close in the previous posting periods was on track. By analyzing
the root causes for errors or delays in the previous posting periods, you can improve the financial close cycle so that
the closing tasks can be completed on time or with reduced delays and errors in the future

Financial Close FIORI apps

Financial Close Progress
The analytical app displays the Key Performance Indicator (KPI) Financial Close Progress. You can get an overview of
the completion status of the tasks in a closing cycle. This KPI tile shows you the number of tasks that are open, in
progress, with errors, and completed, respectively. You can choose to display such data by different views, such as
region and company. This allows you to find out, for example, how many tasks have run into errors in a specific region
or company.

Closing Process Dash Board



Closing Process Impact – Capacity to respond
S4 – Simple
Finance
S4 Simple Finance
provides much faster
reporting time and
granularity to
management.

Bolt on Impact
Bolt on’s are not certified and it took considerable efforts to convince client for installing them without certified
As such they do not have any visible impact on the FI business process

Key Limitations and

Restrictions

Not Applicable

Security Authorizations

Security Impact
General Ledger
SAP delivers new end user roles to be templates for creation of company specific roles.
For GL, the role name is as follows:
• SAP_SFIN_ACC_ACTUALPOSTING
• SAP_SFIN_ACC_CLOSING
• SAP_SFIN_ACC_MASTERDATA
• SAP_SFIN_ACC_REPORTING

Security Impact
Accounts Payable & Accounts Receivable
SAP delivers new end user roles to be templates for creation of company specific roles.
For AP & AR, the role names are as follows:
• SAP_SFIN_AP
• SAP_SFIN_AR

Pop Quiz
Security
A) None
B) 11
Q: How many new Simple roles has SAP

delivered for AR, AP and GL?
C) 6
D) 9

HANA views
Reporting in sFIN2

HANA Views
• HANA views are helpful in case there is a need to build up a custom report.
• The details of the HANA views would be helpful in understanding of the Tables
and Joints & would help developing reports quickly
• Complete list of HANA views have been added in the Appendix
• In this course the relevant HANA views have been listed

HANA Views
Accounting Document GL view
The HANA view for the Accounting document GL view is attached below
This view provides the prerequisites for analyzing accounting documents that are relevant for General Ledger
accounting, as well as the accounts that the line items are posted against.
All of this information is presented in General Ledger View format.

Calculation Views
Accounting Document GL view – Table Joints
 Calculation View: sap.hba.sfin700.P_ACDOCA_COM  Calculation View: sap.hba.ecc.Country
– Table: SAP_ECC.FINSC_LEDGER_REP – Table: SAP_ECC.T005T
– Table: SAP_ECC.ACDOCA – Table: SAP_ECC.T005
– Table: SAP_ECC.TKA02
 Calculation View: sap.hba.ecc.SpecialGLCode – Table: SAP_ECC.T001
– Table: SAP_ECC.T074U – Table: SAP_ECC.SKB1
– Table: SAP_ECC.T074T
 Calculation View:
 Calculation View: sap.hba.ecc.ProfitCenter sap.hba.ecc.GLAccountInChartOfAccounts
– Table: SAP_ECC.CEPCT
– Table: SAP_ECC.CEPC  Calculation View: sap.hba.ecc.ChartOfAccounts
 Calculation View: sap.hba.ecc.GLAccount – Table: SAP_ECC.T004
 Calculation View: – Table: SAP_ECC.SKAT
sap.hba.ecc.GLAccountInCompanyCode – Table: SAP_ECC.SKA1
 Calculation View: sap.hba.ecc.CompanyCode  Calculation View: sap.hba.ecc.FinancialAccountType
– Table: SAP_ECC.DD07T
 Calculation View: sap.hba.ecc.Currency – Table: SAP_ECC.DD07L
– Table: SAP_ECC.TCURX
– Table: SAP_ECC.TCURT  Calculation View: sap.hba.ecc.Company
– Table: SAP_ECC.TCURC – Table: SAP_ECC.T880
sap.hba.ecc.AccountingDocumentType
75 IBM Confidential – Table: SAP_ECC.T003 © 2015 IBM Corporation
HANA Views
Accounting Document Journal
– Tablelinks
Calculation View:
sap.hba.sfin700.P_ACDOCA_COM
Table: SAP_ECC.FINSC_LEDGER_REP
Table: SAP_ECC.ACDOCA
Table: SAP_ECC.SKAT

HANA Views – Accounts Payable

sap.hba.sfin700.AccountsPayable
 Tablelinks

Calculation Views
sap.hba.sfin700.AccountsPayable - Tables used:
 Calculation View: sap.hba.sfin700.P_BSEG_COM  Calculation View: sap.hba.ecc.Currency

– Table: SAP_ECC.BSEG – Table: SAP_ECC.TCURX
– Table: SAP_ECC.TCURT
 Calculation View: sap.hba.ecc.VendorFinancialData
– Table: SAP_ECC.TCURC
 Calculation View: sap.hba.ecc.Vendor
 Calculation View: sap.hba.ecc.Country
– Table: SAP_ECC.TSAD3T
– Table: SAP_ECC.T005K
– Table: SAP_ECC.T005
– Table: SAP_ECC.LFA1
– Table: SAP_ECC.ADRC
– Table: SAP_ECC.ADR6
 Calculation View: – Table: SAP_ECC.LFB1
sap.hba.ecc.PaymentBlockingReason
 Calculation View: sap.hba.ecc.Region
– Table: SAP_ECC.T005U
– Table: SAP_ECC.T005S
 Calculation View: sap.hba.ecc.CompanyCode

HANA Views – Accounts Receivable

sap.hba.sfin700.AccountsReceivable
 Tables/VDMs used are:

Calculation Views
sap.hba.sfin700.AccountsReceivable SAP Tables used:
 Calculation View:  Calculation View:
sap.hba.sfin700.P_BSEG_COM sap.hba.ecc.KNA1_COM
– Table: SAP_ECC.BSEG – Table: SAP_ECC.TSAD3T
– Table: SAP_ECC.KNA1
 Calculation View: sap.hba.ecc.Region
– Table: SAP_ECC.ADRC-
– Table: SAP_ECC.T005U
– Table: SAP_ECC.T005S  Calculation View:
sap.hba.ecc.CompanyCode
sap.hba.ecc.CustomerFinancialsData  Calculation View: sap.hba.ecc.Currency
– Table: SAP_ECC.T001S – Table: SAP_ECC.TCURX
– Table: SAP_ECC.KNB1 – Table: SAP_ECC.TCURT
sap.hba.ecc.CustomerBasicData  Calculation View: sap.hba.ecc.Country
Reporting
Account Receivable Dashboard in Fiori Aps

Reporting
Account Payable Dashboard in Fiori Aps

Reporting-Intuitive User Experience

Financial Statements
Financial Statement App
 Simple search for accounts and hierarchy
nodes
 App navigation to show G/L balances
 App navigation to show G/L line items

Reporting - Intuitive User Experience

Financial Statements drill down to any Journal Dimension

General Ledger Reporting

Overview through Net weaver business client

General Ledger Reporting

Financial Statements
Eliminate manual report compilation and static, offline reporting; gain real-time financial statement reporting with
flexibility to add dimensions for analysis on the fly and to drill down to account level detail
Run live financial statement reports that

can expand down to GL account detail
Drill down to GL account balances
Drill down to GL account line items

Lessons Learnt

Lessons Learnt
1. The Financial document for P/L accounts still generates Controlling documents
• The Controlling document so generated from the FI document is a Internal cryptic

document number into field CO_BELNR
• It is needed for CO compatibility views & groups universal journal entries from CO
perspective
• The controlling number ranges are still needed as before for Internal CO postings
Lessons Learnt
2. GL/ Cost Element Planning for Simple Finance
• The GL/ Cost Element Planning does not work in Simple Finance as a stand alone function
• Integrated Business planning (IBP) needs to be activated for planning to work
3. Errors in Activation of Coding Block
• There are errors in activation of Coding Block. Adding of a custom field lead to
inconsistencies in activation.
• SAP recommended implementing Notes 2192536 , 2135878 & 2129804 in sequence

Lessons Learnt
4. Statistical Account assignment object for Fixed Assets and Material Account
• This setting is done for statistical account assignment objects to flow in Accounting documents
• It is used for Budgeting/ Commitment management on Asset Accounting
• It eliminates the feature of traditional finance to create Cost Element Cat 90 for Fixed Assets accounts

Lessons Learnt
5. Appendix Ledger
• In traditional finance, The leading ledger posted in “Real Time” and the non leading ledger posted
“Periodically”
• In Simple Finance, this has changed. Both Leading and Non leading ledgers are created as “Standard
Ledger”
• Most Business scenarios would be covered with the “Standard Ledger” functionality
• SAP has introduced an additional functionality of “Appendix Ledger” to make sure that if there is a
business requirement to
A. To Post in Closed period for reinstatement purpose
B. Adjustment for Consolidations
C. Report & distribute revenues
differently
Universal
Appendix Ledger A
“Post into closed
Journal Appendix Ledger B
periods Appendix Ledger C “Distribute
for restatement revenues differently
purposes”
“Adjustments for
than in legal view”
consolidation purposes”
Base Ledger 0L - US-GAAP

Lessons Learnt
6. Usage of Central Finance (previously known as Central Journal)
• Central Finance is not a product but rather a deployment model for SAP Simple Finance.
• The key notion behind the Central Finance function is that it breaks out the Finance and Controlling
(FI/CO) applications from the rest of SAP ERP via Application Link Enabling.
• By using Application Link Enabling, customers are provided with a technical foundation for integrating
business processes in a dispersed environment.
• This deployment fits the scenario where there are multi-ERP (SAP & Non SAP) system Landscape and
already highly customized SAP legacy system.
• This deployment model would need separate license for Central Finance and installation of SAP LT
Replication Server.

Questions

Appendix

HANA Views
HANA views/reporting available in Simple Finance 2.0
 AccountingDocumentGLView
 AccountingDocumentJournal
 BSEG_PROJECTION
 P_ACDOCA_AS_COEP
 P_ACDOCA_COM
 P_ACDOCA_COM_PARA
 P_ACDOCA_CUBE
 P_BKPF_COM
 P_BSEG
 P_BSEG_COM
 P_COPA_DOC
 P_FINSC_LD_CMP
 P_GLACCT_LINE_ITEM
 P_JOURNAL_ENTRY
 P_JournalEntryCube
 P_TRIAL_BALANCE

Calculation View: sap.hba.sfin700.BSEG_PROJECTION

Tables Used:
 SAP_ECC.BSEG

Calculation View: sap.hba.sfin700.FAGLFLEXT:
sap.hba.sfin700.P_ACDOCA_COM
– Table: SAP_ECC.FINSC_LEDGER_REP
– Table: SAP_ECC.ACDOCA

Calculation View: sap.hba.sfin700.GLAccountLineItem

Tables used:
 Calculation View:  Calculation View: sap.hba.ecc.GLAccount
sap.hba.sfin700.P_GLACCT_LINE_ITEM  Calculation View:
sap.hba.ecc.GLAccountInCompanyCode
sap.hba.sfin700.P_ACDOCA_COM  Calculation View: sap.hba.ecc.CompanyCode
– Table: SAP_ECC.FINSC_LEDGER_REP  Calculation View: sap.hba.ecc.Currency
– Table: SAP_ECC.ACDOCA – Table: SAP_ECC.TCURX
 Calculation View: sap.hba.sfin700.Ledger – Table: SAP_ECC.TCURC
– Table: SAP_ECC.FINSC_LEDGER_T
– Table: SAP_ECC.FINSC_LEDGER – Table: SAP_ECC.T005T
 Calculation View: sap.hba.ecc.Segment – Table: SAP_ECC.TKA02
– Table: SAP_ECC.FAGL_SEGMT – Table: SAP_ECC.T001
– Table: SAP_ECC.FAGL_SEGM – Table: SAP_ECC.SKB1
 Calculation View: sap.hba.ecc.ProfitCenter  Calculation View:

– Table: SAP_ECC.CEPCT sap.hba.ecc.GLAccountInChartOfAccounts
– Table: SAP_ECC.CEPC  Calculation View: sap.hba.ecc.ChartOfAccounts
 Calculation View: sap.hba.ecc.Plant – Table: SAP_ECC.T004
– Table: SAP_ECC.T001W – Table: SAP_ECC.SKAT
– Table: SAP_ECC.SKA1
 Calculation View: sap.hba.ecc.Material
– Table: SAP_ECC.MARA
– Table: SAP_ECC.MAKT

Calculation View: sap.hba.sfin700.GLAccountLineItem

Tables used:
 Calculation View: sap.hba.ecc.FunctionalArea  Calculation View: sap.hba.ecc.BusinessArea
– Table: SAP_ECC.TFKBT – Table: SAP_ECC.TGSBT
– Table: SAP_ECC.TFKB – Table: SAP_ECC.TGSB

sap.hba.ecc.FinancialAccountType sap.hba.ecc.AccountingDocumentType
– Table: SAP_ECC.DD07T – Table: SAP_ECC.T003T
– Table: SAP_ECC.DD07L
 Calculation View: sap.hba.ecc.DebitCreditCode

 Calculation View: sap.hba.ecc.CostCenter

– Table: SAP_ECC.CSKT
– Table: SAP_ECC.CSKS
 Calculation View: sap.hba.ecc.ControllingArea


Calculation View: sap.hba.sfin700.GLAccountListInChartOfAccounts

Tables used:
 Calculation View: sap.hba.ecc.ChartOfAccounts  Calculation View: sap.hba.ecc.Company
– Table: SAP_ECC.T004T – Table: SAP_ECC.T880
– Table: SAP_ECC.SKAT
– Table: SAP_ECC.T077Z
 Calculation View: sap.hba.ecc.FunctionalArea

– Table: SAP_ECC.TFKBT
– Table: SAP_ECC.TFKB

 Calculation View: sap.hba.ecc.Currency


Calculation View: sap.hba.sfin700.JournalEntryHeader

Tables used:
sap.hba.sfin700.P_BKPF_COM sap.hba.ecc.AccountingDocumentType
– Table: SAP_ECC.BKPF – Table: SAP_ECC.T003T


Calculation View: sap.hba.sfin700.JournalEntryItem

Tables used:
 Calculation View: sap.hba.sfin700.P_JOURNAL_ENTRY  Calculation View: sap.hba.ecc.GLAccount
 Calculation View: sap.hba.sfin700.P_ACDOCA_CUBE  Calculation View: sap.hba.ecc.GLAccountInCompanyCode
 Calculation View: sap.hba.sfin700.P_ACDOCA_COM  Calculation View: sap.hba.ecc.CompanyCode

– Table: SAP_ECC.FINSC_LEDGER_REP  Calculation View: sap.hba.ecc.Currency
– Table: SAP_ECC.ACDOCA – Table: SAP_ECC.TCURX
 Calculation View: sap.hba.sfin700.Ledger – Table: SAP_ECC.TCURC
– Table: SAP_ECC.FINSC_LEDGER  Calculation View: sap.hba.ecc.Country
 Calculation View: sap.hba.ecc.Segment – Table: SAP_ECC.T005
– Table: SAP_ECC.FAGL_SEGMT – Table: SAP_ECC.TKA02
– Table: SAP_ECC.FAGL_SEGM – Table: SAP_ECC.T001
– Table: SAP_ECC.SKB1
 Calculation View: sap.hba.ecc.ProfitCenter
– Table: SAP_ECC.CEPCT  Calculation View: sap.hba.ecc.GLAccountInChartOfAccounts
– Table: SAP_ECC.CEPC
 Calculation View: sap.hba.ecc.ChartOfAccounts
 Calculation View: sap.hba.ecc.Plant – Table: SAP_ECC.T004T
– Table: SAP_ECC.T001W – Table: SAP_ECC.T004
– Table: SAP_ECC.SKAT
 Calculation View: sap.hba.ecc.Material
– Table: SAP_ECC.MARA

Calculation View: sap.hba.sfin700.JournalEntryItem

Tables used:
– Table: SAP_ECC.SKA1  Calculation View: sap.hba.ecc.BusinessArea
– Table: SAP_ECC.TGSBT
– Table: SAP_ECC.TFKBT – Table: SAP_ECC.TGSB
– Table: SAP_ECC.TFKB
 Calculation View: sap.hba.ecc.AccountingDocumentType
sap.hba.ecc.FinancialAccountType – Table: SAP_ECC.T003T
– Table: SAP_ECC.DD07T – Table: SAP_ECC.T003


– Table: SAP_ECC.CSKT
 Calculation View: sap.hba.ecc.ControllingArea


Calculation View: sap.hba.sfin700.JournalEntryOperationalView

Tables used:
 Calculation View: sap.hba.sfin700.OperationalAcctgDocItem  Calculation View: sap.hba.ecc.Country
 Calculation View: sap.hba.sfin700.P_BSEG_COM  Table: SAP_ECC.T005T
– Table: SAP_ECC.BSEG – Table: SAP_ECC.T005
 Calculation View: sap.hba.ecc.Segment – Table: SAP_ECC.T001
– Table: SAP_ECC.FAGL_SEGMT – Table: SAP_ECC.SKB1
– Table: SAP_ECC.FAGL_SEGM
 Calculation View: sap.hba.ecc.GLAccountInChartOfAccounts
 Calculation View: sap.hba.ecc.ProfitCenter
– Table: SAP_ECC.CEPCT  Calculation View: sap.hba.ecc.ChartOfAccounts
– Table: SAP_ECC.CEPC – Table: SAP_ECC.T004T
 Calculation View: sap.hba.ecc.Plant – Table: SAP_ECC.SKAT
 Table: SAP_ECC.T001W
 Calculation View: sap.hba.ecc.Material – Table: SAP_ECC.TFKBT
– Table: SAP_ECC.MARA – Table: SAP_ECC.TFKB
 Calculation View: sap.hba.ecc.FinancialAccountType
 Calculation View: sap.hba.ecc.GLAccount – Table: SAP_ECC.DD07T
 Calculation View: sap.hba.ecc.GLAccountInCompanyCode
 Calculation View: sap.hba.ecc.CompanyCode – Table: SAP_ECC.CSKT
– Table: SAP_ECC.TCURX  Calculation View: sap.hba.ecc.ControllingArea
– Table: SAP_ECC.TCURT – Table: SAP_ECC.TKA01
– Table: SAP_ECC.TCURC – Table: SAP_ECC.T000

Calculation View: sap.hba.sfin700.JournalEntryOperationalView

Tables used:
 Calculation View: sap.hba.ecc.BusinessArea
– Table: SAP_ECC.TGSBT
– Table: SAP_ECC.TGSB
 Calculation View: sap.hba.ecc.AccountingDocumentType

 Calculation View: sap.hba.sfin700.JournalEntryCube

 Calculation View: sap.hba.sfin700.JournalEntryItem
 Calculation View: sap.hba.sfin700.P_JOURNAL_ENTRY
 Calculation View: sap.hba.sfin700.P_ACDOCA_CUBE
 Calculation View: sap.hba.sfin700.P_ACDOCA_COM
– Table: SAP_ECC.ACDOCA
 Calculation View: sap.hba.sfin700.Ledger

– Table: SAP_ECC.FINSC_LEDGER

 Calculation View: sap.hba.sfin700.JournalEntryHeader

 Calculation View: sap.hba.sfin700.P_BKPF_COM
– Table: SAP_ECC.BKPF

Calculation View: sap.hba.sfin700.Ledger

Tables used:
 Table: SAP_ECC.FINSC_LEDGER_T
 Table: SAP_ECC.FINSC_LEDGER

Calculation View: sap.hba.sfin700.NewGLFinancialStatementTotals

Tables used:
 Calculation View: sap.hba.sfin700.NewGLTotals  Calculation View: sap.hba.ecc.Company
 Calculation View: sap.hba.sfin700.FAGLFLEXT  Table: SAP_ECC.T880
 Calculation View: sap.hba.sfin700.P_ACDOCA_COM  Table: SAP_ECC.T005
– Table: SAP_ECC.ACDOCA  Table: SAP_ECC.T001A
 Calculation View: sap.hba.ecc.LedgerCurrencyInformation  Table: SAP_ECC.T000
 Calculation View: sap.hba.ecc.Ledger  Calculation View: sap.hba.ecc.FinancialStatementStructure
– Table: SAP_ECC.T881  - Calculation View: sap.hba.ecc.FinancialStatementItem
 Calculation View:  - Table: SAP_ECC.FAGL_011ZC

sap.hba.ecc.CompanyCodeCurrencyInformation  - Table: SAP_ECC.FAGL_011VC
 Calculation View: sap.hba.ecc.CompanyCode  - Table: SAP_ECC.FAGL_011SC
 Calculation View: sap.hba.ecc.Currency  - Table: SAP_ECC.FAGL_011PC
– Table: SAP_ECC.TCURT  - Table: SAP_ECC.FAGL_011FC
 - Table: SAP_ECC.TFKB
– Table: SAP_ECC.T005T  - Table: SAP_ECC.T011
– Table: SAP_ECC.TKA02  - Table: SAP_ECC.T001
– Table: SAP_ECC.T882G
 - Table: SAP_ECC.SKB1
 - Table: SAP_ECC.SKA1
 - Table: SAP_ECC.FAGL_011PC
 - Table: SAP_ECC.T001

Calculation View: sap.hba.sfin700.NewGLTotals

Tables used:
 Calculation View: sap.hba.sfin700.FAGLFLEXT  Calculation View: sap.hba.ecc.Company
 Calculation View: sap.hba.sfin700.P_ACDOCA_COM
– Table: SAP_ECC.ACDOCA – Table: SAP_ECC.T001A
– Table: SAP_ECC.T000 - Calculation View:
sap.hba.ecc.LedgerCurrencyInformation
 Calculation View: sap.hba.ecc.Ledger
sap.hba.ecc.CompanyCodeCurrencyInformation


FIORI Apps source

https://fioriappslibrary.hana.ondemand.com/sap/fix/externalViewer/#/detail/Apps%28%27F0520%27%29

SFin - Record To Report Financial Accounting

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

SFin - Record To Report Financial Accounting

Uploaded by

Copyright:

Available Formats

Global Business Services

SAP SIMPLE FINANCE

1 IBM Confidential © 2015 IBM Corporation

2 IBM Confidential © 2015 IBM Corporation

3 IBM Confidential © 2015 IBM Corporation

4 IBM Confidential © 2015 IBM Corporation

Pop Quiz: Ice Breaker

5 IBM Confidential © 2015 IBM Corporation

6 IBM Confidential © 2015 IBM Corporation

Architecture: Traditional SAP Finance

Customer Vendor General Ledger Controlling

KNC1 LFC1 GLT0

BKPF BSEG BSIS BSID BSET BSIK BSAK BSAS BSAD

7 IBM Confidential © 2015 IBM Corporation

Architecture: New SAP Simple Finance

8 IBM Confidential © 2015 IBM Corporation

Architecture: Simple Finance 1.0

9 IBM Confidential © 2015 IBM Corporation

Architecture: Simple Finance 2.0

KNA1 LFA1 SKA1 COBK COEP

BKPF ACDOCA BSEG

10 IBM Confidential © 2015 IBM Corporation

Q: Which of the following

E) All of the Above

11 IBM Confidential © 2015 IBM Corporation

Process and Functionality

12 IBM Confidential © 2015 IBM Corporation

Master Data impact

Traditional SAP As of sFIN 2.0

Balance Sheet Balance Sheet

Profit & Loss Non Operating

Primary Cost Primary Cost

Secondary Cost Secondary Cost

13 IBM Confidential © 2015 IBM Corporation

Master Data in Traditional Finance

14 IBM Confidential © 2015 IBM Corporation

Master Data impact in Simple Finance

Master Data impact in Simple Finance

Unified Master Data Maintenance Effects on Reporting

In the past postings on secondary cost elements effecting GL

17 IBM Confidential © 2015 IBM Corporation

Business Data of Universal Journal Entry is organized in Ledgers

What is a Ledger in sFIN? Characteristics

18 IBM Confidential © 2015 IBM Corporation

19 IBM Confidential © 2015 IBM Corporation

Summary of Changed Transactions

OLD Transaction Use NEW Transaction

20 IBM Confidential © 2015 IBM Corporation

Summary of Table Changes

GL GLT0, GLT1, GLT3 GL Totals Table

ACDOCA Universal Journal

21 IBM Confidential © 2015 IBM Corporation

Summary of Table Changes

22 IBM Confidential © 2015 IBM Corporation

D) None of the Above

23 IBM Confidential © 2015 IBM Corporation

Q: What transaction B) FSP0

D) None of the Above

24 IBM Confidential © 2015 IBM Corporation

D) None of the Above

25 IBM Confidential © 2015 IBM Corporation

Sequence of Configuration for New Implementations

5. Run consistency check by calling transaction FINS_CUST_CONS_CHK and clean up inconsistencies