S4 HANA INTERVIEW PREPARATION

Total Time Expected : 45 Minutes

Areas of Expectation

AREAS EXPECTATION
Time
Tell about you and your profile Your position, Your education, Your current 03
company, your experience, your certification

Tell about the recent Project (S4 About the Client : 03

HANA FINANCE) About the Project :
Current Status of the Project :

About SFIN Project Migration Project

Pre-Requisites What are the pre-requisites before migration?
What are the new functionalities introduced in
S4 HANA?
What are all the impact areas in Simple
Finance?
What methodology you applied in your project
for Migration? Tell about the various Phases in
its implementation?
What are the benefits in S/4 HANA finance than
R3?
What are the Functional changes with S/4
HANA finance?
What do you mean by custom code in R3 to Sfin
Migration?
What are all the phases in migration and
objectives, key activities and deliverables?

1.1 Check Functional Scope and Restrictions

1.2 Feasibility Checklist
1.2.1 System Landscape
1.2.2 SAP ERP Users and Maturity
1.2.3 Data Size and Growth
1.2.4 General/Business Drivers
1.2.5 SAP ERP-Specific Questions
1.2.6 SAP S/4HANA Finance Questions
1.3 The Maintenance Planner and Pre-checks
1.4 Check Custom Coding
1.4.1 Check Custom Code and Modifications
1.4.2 Handling Custom-Defined Fields and Interfaces
1.5 Check Sizing
1.6 Precheck for Migration to New Asset Accounting
1.7 Activate Business Functions
1.7.1 Activate Business Functions for Asset Accounting, Parallel Valuation
FI N_AA_PARALLEL_VAL
 Main Differences over R3 and SFIN

Business Processes Module Old T New T

code Code Observations in SFIN 2.0
General Cost Center Planning
General Cost Center Cost center KP06 Via Planning should be done via webdynpro
Planning accounting Webdynpro FCOM_IP_CC_COSTELEM01

Manufacturing Cost Cost center KP06 Via Planning should be done via webdynpro
Center Planning accounting Webdynpro FCOM_IP_CC_COSTELEM01

Cost Center -Activity Cost center KB21N For Sfin 2.0, SAP recommends to plan cost center
Planning and revaluation Accounting via Integrated business planning. BW has
(175-176)BP separate info provider to store planning data
from IBP. From ERP activity calculation and
revaluation process wise nothing changes

Project Systems
Project with Fixed Price Project system CJ40 Via CJ40 transaction has been replaced by web
and T&M Billing Webdynpro dynpro FCOM_IP_PROJ_OVERALL01
Internal Projects

Internal Product Project system KKE1 & CKCU KKE1 and KKE2 transaction has been replaced by
Development KKE2 transaction code CKCU

Segment Reporting
Segment report Reporting should be done via webdynpro
FCOM_FIS_AR_OVP and FCOM_FIS_AP_OVP

Internal Order Accounting

Internal Order accounting Internal Order KO12 Via Planning should be done via webdynpro
BB_766 accounting Webdynpro FCOM_IP_ORD_COSTELEM01

Research and Internal Order KO12 Via Planning should be done via webdynpro
development Internal accounting Webdynpro FCOM_IP_ORD_COSTELEM01
Orders BB_767
Cash Management
Bank & Bank Account New Cash Bank Account Management (BAM)
Management • Bank hierarchy based on bank business partners
• Free-style bank account groups allow ad-hoc
watch for several bank accounts.
• Fuzzy search for bank accounts
• Attachments
• Replaces transaction on FI12 for Accounting
customers
Define house banks: Use the new transaction
FI12_HBANK or Fiori app Manage HouseBanks
Define house bank accounts: You can do so by
editing the bank account master data, on the
Connectivity Path tab .

• SAP Fiori App Manage House Banks and

transaction FI12_HBANK can both be used to
define house banks

The following transactions are still necessary:

• Create Bank: FI01
• Change Bank: FI02
• Display Bank: FI03
• Business Partner (Role TR0703): BP

Bank Account Management Lite (BAM Lite)*

A basic version of Bank Account Management is

provided for customers without the license of SAP
Cash Management powered by SAP HANA.
It provices:

• Attributes include account holder, internal

contact persons, and house bank account related
settings on bank accounts.
• No workflow-based bank account processes.
• Replace transaction FI12 for Accounting
customers:
• Define house bank: use the new transaction
• FI12_HBANK
• Define house bank accounts: you can do so by
editing the bank account master data, on the
Connectivity Path tab.
• For information on the differences between
BAM and BAM Lite, see SAP note 2165520.

Cash Position / Liquidity New Cash Significant change in the process has been notice,
Forecast Management Cash Concentration can work based on the new
Bank Account Management (BAM) accounts in
Webdynpro
application or Fiori app Manage Bank
Accounts.User experience is greatly enhanced for
both defining cash pools and executing cash
concentration. Cash pools can be defined by crea
ng bank account groups in
BAM applications directly.
Bank Statement New Cash SAP Fiori Significant change in the process has been notice,
Management Tile Retrieve remote Liquidity Planner actual data into
the Exposure Hub.

Manual Payment New Cash SAP Fiori

Management Tile

Liquidity Planner New Cash

Management

Cash Concentration New Cash Via Significant change in the process has been notice,
Management WebDynpro Cash Concentration can work based on the new
& Bank Account Management (BAM) accounts in
Fiori Tile Webdynpro
application or Fiori app Manage Bank
Accounts.User experience is greatly enhanced for
both defining cash pools and executing cash
concentration. Cash pools can be defined by crea
ng bank account groups in
BAM applications directly.

Distributed Cash New Cash Significant change in the process has been notice,
Management Retrieve remote Liquidity Planner actual data into
the Exposure Hub.

Asset Accounting
Architecture changes Asset Accounting All actual asset accounting line item postings will
be stored in ACDOCA. Header info will be stored
in Table BKPF.

Creation of Asset Master Asset Accounting No Change AS01

Creation of Legacy Asset Asset Accounting AS91 Only Master Data can be created
Master
Entering Values in Legacy Asset Accounting Refer to SAP Note 2014219 Transaction Values to
Asset Master be posted with Transaction ALBDT

Asset Depreciation Asset Accounting Screen has been enhanced. Accounting Principle
can be selcted as well
The radio buttons for " Reason of Posting runs
have been eliminated

Asset Depreciation Asset Accounting Depreciation Posting document is posted on the

Asset level.. Earlier it was on the GL accounts
level

Asset Depreciation Asset Accounting Error handling in depreciation has changed.

Depreciation document without errors are
posted. The error log has to be corrected. When
the dpereciation is run again only the delta
(incorrect Assets) are posted.

Periodic Asset Posting Asset Accounting This has been eliminated as Asset posts in Real
Time

Configuration Change Asset Accounting For Parallel valuations (Leading and Non Leadng
ledgers) the Delta depreciation area has been
eliminated as all ledgers post in real time
 Asset Accounting Real time integration of Asset with GL,
Elimination of reconciliation steps

Balance Carry forward Asset Accounting No separate program to be executed for balance
carry forward in asset accounting

General Ledger
Accounting
New Architecture General Ledger The following Index Tables have been deleted
GL-BSIS, BSAS
The Below Totals Tables have been deleted
GL- GLT0, GLT1, GLT3
New Table ACDOCA has been included

Unification of Master General Ledger KA01/KA06 FS00 GL master has been changed to incorporate the
Data Maintenance for GL cost elements (Primary & Secondry)
Account and Cost
Element
CO-FI Reconcilation General Ledger CO-FI reconciliation has been eliminated

Ledgers General Ledger Transactions post into multiple ledgers creating

universal journal entries with the same document
number in all ledgers

Ledgers General Ledger There is a separate document type assignment

for postings made without the leading ledger.
this ensures no gaps in document number of the
leading ledger

Cut Over Data load General Ledger Migration and Balance Carried Forward
transactions generate document numbers with a
letter as a prefix

Foreign Currency Period end close New Transaction code for Foreign Currency
Valuation Valuation FAGL_FCV

Period End Closing

_Controlling
Variance Calculation Period End Close KKS1 KKS1H Production variance split is available in GL
New T Codes with a suffix 'H' (i.e. KKS1H)
In classic FI man and machine hours are not
visible in GL until process order settlement. Now,
man and machine hours are posted to GL, both
primary and secondary costs are available in
Financial accounting and Management
accounting

WIP Period End Close KKHO KKAOH New T. Code KKAOH has been introduced for
calculation of WIP
In KKAOH, WIP can only be calculated on
production orders, not on product cost collectors
or process orders
WIP calculation in only one version is supported

CO Settlement Period End Close CO88 CO88H Actual settlement has changed to CO88H
 CO-PA Account based – Period End Close Classic FI does not split cost components of
Reconciling Cost COGM and COGS in GL. This is only possible in
Component Split costing based CO-PA assigning value fields from
each and every cost component of the standard
cost price provided by product costing. But in
Simple Finance does split cost components of
COGM and COGS in GL
Thus, Simple Finance eliminates reconciliation
issues between FI and CO

CO-PA Costing based – Period End Close Best practice SAP is to post Goods Issue to SCOGS
Goods Issued Not account causing reconciliation issue between FI
Invoiced and costing based CO-PA especially when GI and
Customer billing document are accounted for in
difference periods

COGS Postings SD integration Cost component split is available in GL

COGS can be split between multiple GL accounts
to mirror the Cost Components

YEC: Balance Carry Period end close New functionality

forward Reset Balance Carryforward and Perform Again
If you set this checkbox, the program first deletes
all line items that have already been created in
the specified fiscal year. It then performs the
balance carryforward again as an initial run.

Resetting the balance carryforward line items is

useful if a) you have made a large amount of
postings to the previous year after performing
balance carryforward and b) you would like to
prevent a large number of line items from being
created as a result of automatic corrections to
balances that have already been carried forward.

In S/4 HANA, we will have 4 different account type options to select while defining GL master
data.

• Balance Sheet Account - financial statement which summarizes a company’s assets,

liabilities and equity for the specific period of time.

• Non-Operating Expenses or Incomes - gains or losses from sources not related to the
typical activities of the business or organization

• Primary Cost or Revenue - It is a financial statement which summarizes costs, expenses and
revenues incurred for the specific period of time.

• Secondary Cost – allocated cost created for a purpose of assessment.

Why do we need G/L Master Data Maintenance Process in S/4 HANA?

In S/4 HANA, Cost Element is now part of GL master data so, Cost Element creation is no more
associated with costing team.

This change is adopted in GL master creation due to Cost Element creation is integrated with GL
master creation & also only one accounting document will have all the dimensions of accounting.

This will solve the problem for Reconciliation (as in case of CO to FI) is no longer needed.
Period end closing also will be faster.

In GL master data (company code segment) Under Control Data tab, the cost element category can
be identified as follow: