You are on page 1of 19


SAP S4 Hana represents the next generation & latest evolution of SAP’s core
application platforms with redesign & reengineering to exploit the in-memory
capabilities of the SAP Hana Data base. SAP Hana database with in-memory
computing power to process huge amount of data for analysis in a very short
period. SAP database supports columnar database tables and can move the logic
to the database layer through stored procedures.

S/4 HANA is natively built on SAP HANA with simplified data model, without
indices, aggregates and no redundancies. It leverages the multi tenancy
functionality of SAP HANA. It can be deployed on premise, cloud or
mixed/hybrid. It is natively designed with SAP Fiori offering an integrated user

The Design of SAP HANA allows it to drastically boost speed for both Online
Transaction Processing (OLTP) and Online Analytical Processing (OLAP). HANA,
on the other hand, is column-oriented and combines OLAP and OLTP into a
single structure, cutting memory usage by a factor of 10 or more and improving
S/4HANA is designed to use Fiori UX. Customers can still use the old user
interface during the transition, however they’ll be able to take advantage of the
power and flexibility offered in HANA S/4 with Fiori. For some organizations, the
current S/4 features may not outweigh the added complexity of moving past
ECC. As time passes and new SAP S/4HANA functions are added, the benefits of
moving away from Business Suite on HANA to S/4 will increase for a greater
range of organizations.
Enhanced functionality of SAP S/4HANA
The greatest benefits of SAP S/4HANA over Business Suite on HANA lie in
financial management and accounting. SAP S/4HANA Finance is designed to
cover the full range of finance tasks, including planning, analysis, accounting,
compliance and risk management. According to SAP chairman Hasso Plattner,
the HANA S/4 finance app can shrink data more than 10 fold, from 593 GB to 42
GB, “with only 8.4 GB being dynamic, current-year data requiring high
availability and backups.”

SAP S4 Hana builds on the well proven functional base of SAP Business Suite
and can be introduced in an evolutionary, gradual and selective way into an
existing SAP environment.
Key benefits of S4 Hana:
 Providing real time reporting & single version of truth via SAP Hana live,
SAP Fiori applications & Universal Journal.
 Bringing many data sources from inside & outside the business into SAP
Hana platform for real insight.
 Building business rules in the platform, including embedded analytics, to
create new optimized & innovative business process.
 Optimizing & simplifying the business model that is embedded SAP BPC
for S4 Hana Finance, including removal of unnecessary steps & batch
 Using simplified user interface (UI)

Universal journal
Universal journal is the single source of truth for the accounting in SAP S/4 HANA
Finance (Simple finance). It combines documents journals from Financial Accounting
(FI) and Controlling (CO), removing the necessity of reconciliation between these
Following components are using the Universal Journal:

 General ledger
 Asset Accounting
 Controlling
 Profitability analysis (account based)
 Material ledger

Single journal entry with all required information is created for the relevant components
(figure 2).
From the technical perspective the universal journal entry consists of the header (table
BKPF) and related items (table ACDOCA, figure 1). The items table is ledger dependent,
which enables a multi GAAP capability. No totals tables are used as aggregated
information can be calculated on the fly due to SAP HANA superior performance
capabilities. This allows to have a very detailed level of information for reporting and
analysis purposes.
Figure 1: ACDOCA table combines data fields from various components.
Figure 2: Depreciation posting example in ACDOCA table (fields related to GL, AA, CO).
The creation of an entry in the Universal journal is based on the source document. The
source document stores the initial information entered into the system before any
derivations, enrichments or splitting take place in Accounting for the purpose of the journal
entry creation. Below are the examples of the source documents and their respective
tables in FI/CO:

 For the FI postings source document is stored in BSEG table. The BSEG table has
been converted to a transparent table.
 For the manual CO postings source document is stored in COEP table. Entries can
be viewed via the V_COEP_ORI view.
 For the Material price change transaction source document is stored in material
ledger tables (MLHD, MLIT, MLCR, …). BSEG document is also created.

For all these documents corresponding entries are created in the Universal journal.
Old FI/CO totals and index tables were removed to avoid data redundancy. But in order to
maintain compatibility with the traditional programs, corresponding compatibility views were

Business Benefits:
The role of the CFO today is broader & more complex than ever before. The CFO
is not restricted to optimizing operations such as paying bills, closing the books
& producing financial results. Today CFOs are expected to develop new
approaches to manage their organisation, produce business insights on a daily
basis, spot market opportunities, predicting changes in business environment &
driving business to growth. With a view to addressing the information
requirements due to this shift, SAP has introduced S4 Hana finance its first
module for transactional simplicity & advanced analytics in the new SAP S4 Hana
offering. Although covering key functionalities such Universal Journal, Appendix
ledger, the new asset accounting, accelerated close, SAP S4 Hana finance is all
about creating a simplified UX.

Overall Business & Functional benefits:

 SAP S4 Hana finance redefines data aggregation using the in-memory
capabilities of the SAP Hana database. This allows for reduction of your
data foot print because calculations for financial transaction are
performed on the database layer instead of traditional application layer
on an adhoc basis.
 Universal journal is the single source of truth for financial information. It
has new data model that combines Controlling (CO), SAP ERP financials
(FI), Asset Accounting (AA), Material Ledger (ML), Profitability Analysis
(CO-PA) & other financial data into one Universal Journal entry, all
represented in table ACDOCA, with full details of components. Because all
data are provided in real time from this single journal, the period end
reconciliations & financial reporting preparation efforts are reduced
 The New Universal Journal allows ad hoc, on-the-fly computations for
converting periodic transactions from batch to real time without needing
data to be replicated first to other systems such as SAP business objects
business intelligence (SAP Business objects BI).
 It facilitates accelerated month-end & year-end close. The ability to move
away from batch-based to event-based processing enables period end
processes to be run on daily or weekly basis. This allows organisations a
real time view of their profit & loss, providing the business early visibility
of emerging trends.
 SAP BPC is a real-time integrated business planning in S4 Hana. This is a
new planning functionality introduced where the planning data can be
uploaded using Microsoft excel.
 New FI-AA in SAP S4 Hana finance replaces the classic FI-AA functionality.
The simplified posting logic allows seamless integration with the Universal
Journal. Due to real-time postings, there is no need to wait for the month
end depreciation run.
 Cash management powered by Hana is optional replacement. SAP cash
management provides on-the-fly reporting capabilities about cash
position & liquidity forecasts.
 SAP credit management is now completely covered under collaborative
finance operations & receivables management.
 The reconciliation between FI & CO are removed by design as cost
elements are created as GL accounts, and all the data from CO & FI are
held in a common data base structure.
 New on-the-fly & real time reporting capabilities are available with the
elimination of batch jobs during period end finance processes such GR/IR
clearing, cost allocations & FI-CO reconciliations. The speed and online
availability are achieved using the in-memory functionality within SAP
Hana & the reduction of aggregate tables.
 Classic GL functionality has been completely replaced by the New GL.
Classic GL is only supported before the Introduction of Hana.
 Data aging replaces SAP data archiving. The new method builds data aging
objects, create partitions & execute data aging runs. Thus, reducing the
SAP Hana memory foot print.

System Architecture of SAP S4 Hana Finance.

S4 Hana’s Universal Journal architecture is comprised of a single source of
truth for all accounting components which makes a reconciliation a topic
of the past.
The new architecture consists of following elements:
 One single source for data in FI is provided in the form of Line Item table
ACDOCA with all details for components. Following are some of the
features of Universal Journal Features:
 Link on line item level (1:1) between FI & CO.
 Link from Co line items to a dimension table in CO-PA.
 Enhancements of Accounts based CO-PA (detailed posting of COGS
& Variances)
 Logical document SAP Hana view for analysing the converged data.
 Universal journal entry is the reporting data base keeping all
previously used tables in Hana compatibility views.
 All fields in Universal journal Entry such as asset data, CO-PA
attributes & so on, can be reported from this single table.
 Accounts & Cost elements are harmonised. Secondary Cost elements are
created & depicted as GL accounts.
 Primary & Secondary Cost elements are to be maintained at Co-Code
 Simplification of reporting based on one single source of truth allows fast
multidimensional reporting on the universal journal which is possible
without replicating data to a separate system. It replaces SAP Business
Objects BI reporting.
 If SAP Business Objects BI is in place, only a single business objects BI
extractor is needed instead of many extractors as used in traditional ERP.
 The memory of foot print is reduced by eliminating redundancy.
 Technical preparations enhance important structural capabilities of the
financial solution (Multi GAAP & additional currencies)

When SAP S4 Hana Finance is activated, the following aggregate tables of

classic FI &AA are replaced with SAP Hana views with the same name:
 SAP GL accounting’s totals tables & secondary index tables such as
 The totals tables & application tables of AR & AP such as KNC1, KNC3,
 The Totals table of CO such as table COSP & COSS.


1. SAP ERP 6.0 or lower to SAP Business suite on SAP Hana & then to S4
Hana. This is known as two steps approach.
 Step-1, To migrate to Business Suite Hana (with or without S4
Hana), existing SAP ERP ecc. or lower, SAP ECC6.0 is upgraded to
EHP 7 or higher & Upgrade Data base to Hana .
 Step2, then migrate to S4 Hana
 Before S4 Hana migration, three activities are to be completed.
1. New GL implementation
2. New FI-AA implementation
3. Assessment of Custom code.
For Exp, if an SAP ERP Ecc 6.0 is using Classical GL functionality, you need to
undertake a new GL migration project ideally before the start of S4 Hana Project.
Additionally, during the upgrade, the FI-AA needs to be enabled with relevant
enhancement package. New SAP cash management, although optional, can be
enabled during the upgrade or later.
You also can perform New GL migration together with S4 Hana Finance
migration. New Gl migration takes 6-18 months depend on volume of
transactions to be migrated. New GL migration must be completed before
cutover of S4 Hana finance migration. Cutover from Classic GL to New GL must
happen at the start of new financial year.
There are two approaches for S4 Hana migration from SAP running Non-Hana
data base or any RDBMS
1) Two Step approach (EHP 7 or above upgrade followed by SAP S4 Hana
migration) which has been explained above.
This option is less risk but creates a longer overall project & higher costs.
2) One Step approach (EHP 7 or above upgrade & SAP S4 Hana migration
This option is faster, more cost-effective migration including synergies of
testing, but it is admittedly a more complex project. It require more
downtime for both migration which affect production server.

Greenfield Implementation: Fresh SAP S4 Hana

Besides DMO, there is a Green Field implementation for SAP S4 Hana
Finance. When SAP Hana migration project is more complex & costs more
in migration, because of the many factors like not using New GL which
needs migration before SAP S4 Hana migration, it makes projects longer
& more cost, in that case Green Field is preferred. Non-SAP Client is also
deciding for SAP S4 Hana finance because of business benefits or

SAP S4 Hana Finance Project Phases:

4.Data migration
5.Post migration activities.

Impact of S4 Hana Migration:

 Impact on General Ledger Accounting:
Traditionally SAP stored SAP GL, AR & AP balances & open items in various
database tables to support reporting. With introduction of S4 Hana
Finance, the same report can be achieved directly from table ACDOCA
without storing separately. All the fields from Sub-Modules such as
Controlling (CO), Asset Accounting (FI-AA), SAP Material Ledger (
ML),Profitability Analysis ( CO-PA) are available in table ACDOCA. In earlier
versions of SAP ERP FI, the secondary cost elements could not be
displayed in Financial statement. In SAP S4 Hana Finance, secondary cost
elements are created as GL accounts which allows secondary cost
elements to be included & viewed in financial statement version.
 Impact on FI Architecture
 With SAP S4 Hana finance, when you post a journal entry, the
header record is posted in table BKPF & Line item record is posted
in table ACDOCA.
 The corresponding line items have artificial document numbers
beginning with a letter.
 Table ACDOCA contains all fields (350+) required for GL, CO, FI-AA,
 Tables ACDOCA & BSEG don’t store completely identical
 Table ACDOCA has fields for CO, FI-AA, ML, that are not in table
BSEG. Similarly table BSEG has dedicated fields for Open item
management/ payment that are not in table ACDOCA.
 Due to the 999document line item posting limitation, table BSEG is
usually aggregated. This limitation does not exist in table ACDOCA.
 Table ACDOCA stores all CO internal postings, these are not posted
to table BSEG.
 Fast multidimensional reporting is possible from Table ACDOCA
without replicating data to SAP BW.
 The Universal Journal can easily be extended with custom fields
such as the derivation tools from CO-PA & standard coding block
extensibility. The respective custom fields as required are added to
the Universal Journal table.
 The table ACDOCA stores the data previously stored in table
 Table ACDOCA stores the data of NEW GL public sector industry
tables & Joint venture accounting.
 Compatibility view exists for table FAGLFLEXA & table FAGLFLEXT.
 Customers can access old data in customer defined New GL tables
that are created as views in the data dictionary (DDIC).
 Unification of master data maintenance for GL accounts & cost
elements with the introduction of account type & cost element
attributes in transaction FS00.
 Leading Ledger concept remains same. Appendix ledger only
inherits adjustment postings additionally. Leading Ledger is full set
of Line items. The appendix ledger is assigned to the base ledger.
 S4 Hana finance has two major functionality impacts on SAP
General Ledger Accounting. Open Item reports have been removed
from S4 Hana due to introduction of Universal Journal.
 FI postings with SAP S4 Hana finance is similar with Traditional FI.
Table ACDOCA posted is similar to table FAGLFLEXA in the past.
 Entries previously stored in table COEP is now in ACDOCA.
 With Universal Journal, a single legal document number is
generated & populated in tables BKPF & ACDOCA in field BELNR for
 The system generates a transaction number for CO. This number is
captured in CO_BELNR field for CO. And it generates a new number
for every 999line items. In short, In One FI document can have
many corresponding document nos in CO, but they are all linked.
 Central Finance is one of the deployment methods to migrate to
SAP S4 Hana. It breaks out FI/CO applications from other
applications by using ALE.
Impact on Customer & Vendor Master data
Customer & Vendor master data change into business partner data.
FD01,FD02,FK01,FK02,FK08,XD01,XD02,XK01,XK02,etc are no more .You must
clean up customer & vendor data before it can be converted into S4 Hana
business partner. SAP note 2211312,2210486 conversion prechecks.

Credit Management Impact

SAP S4 Hana Finance does not support SAP ERP financials Accounts Receivable
Credit Management. The corresponding function in SAP S4 Hana Finance is SAP
credit management.
You need to perform the migration from old credit management (FI-AR-CR) to
the New SAP credit management which is comprised of the following elements
1.Master data
2.Configuration data
3.Credit exposure data
4.Credit decision data
Transaction F.28,F.32,F.34 ,FD32,FCV3,VKM3,VKM5,S_ALR_87012215, etc are
not available in S4 Hana finance.

Impact on Leading & Nonleading Ledger:

In Traditional FI, Leading Ledger posts transaction in real time & Non-Leading
ledger posts periodically. In SAP S4 Hana Finance, both ledgers are created as
standard ledger. The newly Introduced appendix ledger can report on all
transaction data of the base ledger & it allows you to create views without
affecting the base ledger.

Integration of SAP ERP Financials & Controlling:

In SAP S4 Hana Finance, CO is integrated in real time into the New GL. Both Primary &
secondary cost elements are created as GL accounts are now part of Chart of Accounts. With
introduction of S4 Hana Finance, the concept of reconciliation ledger has been eliminated.
Because CO & FI have been integrated by architectural changes in the GL & cost element
master data. Similarly, transaction for posting CO documents to FI is no longer available in
SAP S4 Hana Finance. Due to the real time integration of FI & CO, the data gets populated to
CO at the same time it is posted FI.

Impact on New Asset Accounting:

With introduction of SAP S4 Hana Finance, Classic FI-AA is no longer available.
The usage of new depreciation engine is mandatory and comes with activation
of the business function EA-FIN.
 Architectural impact: Header data is in table BKPF. All line item is in table
 Posting Logic in new FI-AA is changed. Operational entry debits Technical
Clearing account & credit vendor. Accounting Principle specific
documents are posted with debit to the Asset reconciliation account and
Credit Technical Clearing a/c. This document updates the line item.
Separate docs are also posted to each of these ledgers within the ledger
group that are assigned to the accounting principle associated with
depreciation area.
 Technical Clearing account generates entries for asset acquisition from a
Vendor by using transaction F-90. All links between sample chart of
depreciation & Co codes must be deleted because they trigger an error
during NEW FI-AA activation.
 In SAP S4 Hana, It is a three step process.
1.Master data is loaded through transaction AS91.
2.Asset historical values, accumulated depreciation, and depreciation for
the year are loaded through transaction ABLDT.
3.The Current Year Acquisitions are managed through transaction AB01.
 Depreciation run screen is now simplified in S4 Hana. You can now run
depreciation for a particular accounting principle. Server group needs to
be entered.
 Tables ANEP,ANEA,ANLP, & ANLC were replaced by table ACDOCA but are
still supported by means of compatibility views. Table ANEK data are
stored in BKPF.
 Statistical data stored previously in tables ANEP,ANEA,ANLP, & ANLC are
now stored in in table FAAT_DOC_IT
 Planned data stored previously in tables ANLP & ANLC are now stored in
 No depreciation areas post periodically. All areas post immediately to GL
 Activation of New Asset accounting is must.

The Closing process is impacted by New FI-AA in SAP S4 Hana

1. Realtime integration of AA with GL occurs, eliminates reconciliation
2. APC posting run is not required.
3. The planned depreciation Value of the Asset is reflected in real time &
is updated with every master data change & every asset transaction
4. No separate programme is executed for balance carry forward for FI-
AA. The general balance carry-forward of FI transfers AA balances by
5. Planned depreciation is automatically calculated for the New Year
after the Balance carry-forward (Year -end Close) is performed.
6. Depreciation posting run is executed faster due to simple processing
logic, new data structures & parallel processing.

Impact on Controlling:
Controlling contains internal accounting data & the account assignment objects
needed to produce management-oriented reports & analysis.
 In S4 Hana, Accounting docs are posted using common doc number. The
FI document for P&L account still generates CO documents. To maintain
CO consistency & Compatibility views, the document type & document
number customizing settings are maintained for internal CO postings & to
assign actual version of CO to the Ledger. With the integration of FI & CO,
there is no requirement for reconciliation ledger going forward.
 With the S4 Hana Finance, Totals table (COSP & COSS) are no longer
required. Only Line Item Table COEP to store actual data. Two new tables
COSP_BAK & COSS_BAK have been created to store planned data related
to primary & secondary costs, respectively.
 Cost elements are no longer required in SAP S4 Hana, because they are
created as GL accounts using transaction FS00 & are part of chart of
accounts. A new field for the cost element category has been introduced
in the GL master record. The default account assignment is maintained
using transaction OKB9.
 With the introduction of UNIVERSAL JOURNAL in SAP S4 Hana Finance, all
the CO postings are posted directly to the Universal Journal entries.
Secondary Cost elements are now part of GL accounts in FI & do not
require separate assignment in CO. So there is only One Allocation.
 T codes like KA01, KA03, KA06, KKC1, etc. are no longer required.
 In SAP S4 Hana, you need to define a ledger that represents CO that by
assigning version 0 to a ledger. This is done at co-code level but needs to
be same for all co-codes.
 In SAP S4 Hana, Leading ledger is assigned to version 0 for all Co-Codes
which are assigned to a controlling area.
 General Ledger Planning & Cost element planning are now part of SAP
business Client.

Impact on Cost Centre Accounting & Profit Centre Accounting:

Cost Centre Accounting is used for controlling purposes to analyse costs for
management decisions within your organisation. The costs incurred by the
organization are captured using cost centres as Cost Objects. An ideal scenario,
all costs should be allocated to the source where it was incurred, but the
challenge lies in allocating overhead costs.
Profit Centre accounting is used to determine profit & loss for specific profit
centres using period accounting or the cost of sales approach. Profit centres are
the organisational units within a controlling area that area of responsibility
within an organisation for which a separate operating statement can be
 Actual data of table COEP are now stored in table ACDOCA.
 Actual data for orders that are continuing for long periods of time &
stored in COSP_BAK & COSS _ BAK are now stored in table ACDOCA
 Table COBK is used as before.
Impact on Profitability of Analysis
In SAP S4 Finance, it is recommended to use Accounts based CO-PA.
 Split the COGS posting on multiple accounts.
 Split the production variance posting on multiple accounts.
 Accounts based CO-PA is more powerful than Costing based CO-PA in
SAP S4 Hana environment.
 Unlimited value fields are in accounts based CO-PA, whereas Costing
based CO-PA has only 250 value fields.
 Profitability Characteristics are derived immediately when the primary
docs get posted.
 All the fields that used to store in table CE4* become part of Universal

Hana Migration Steps to SAP S4 Hana Finance.

Preparatory phase of Migration:

1. Data Consistency Check before activation of S4 Finance
2. Custom code Check
3. Check Customization settings prior to S4 Hana Migration
4. Activation of business functions sequence wise
5. Run reconciliation for GL with Asset accounting
6. Reconciliation of FI with MM
7. Reconciliation of FI with SD
8. Reconciliation of FI with AR & AP.
9. Period end Closing activities before Migration

Installation & Upgradation

 The System automatically Creating back up tables for total & index tables
& creating SAP Hana views for the same in the same name while installing
S4 Hana.
 After S4 Hana Fin installation, no postings can be made until the end of
 SAP note 2157996 includes a checklist for installation & upgrade to S4
 An Organisation that has complex & large distributed system landscapes
involving multiple SAP ERP & non-SAP ERP systems can also benefit from
the functionality of SAP S4 Hana finance without migrating the entire
system landscape to SAP S4 Hana Finance. In this case, Central Finance is
one of the deployment scenarios for installing SAP S4 Hana Finance in
which various source systems are connected.
 Customers already using Hana should update their SAP Hana data base to
Ecc 6.0 EHP 7 or higher to allow for migration to SAP S4 Hana Fin.
 If a Customer Ecc 6.0 EHP 7 and data base Oracle or SQL must upgrade to
SAP Business Suite Hana & then S4 Hana. Before S4 Hana migration, New
GL is a must be in SAP Business suite Hana.
 Software Update Manager (SUM) helps you to perform release upgrades,
install enhancement package, apply service packs & update single
components on SAP Net weaver. The SUM is the main tool used to convert
your system into SAP S4 Hana Finance. If your source system is not yet
running on SAP Hana Database, use the Data base Migration option (DMC)
of the SUM to migrate your database to SAP Hana during the conversion.
 With the SUM & DMO, you can run the upgrade to SAP ERP6.0 EHP7 or
above, the data base migration to SAP Hana & the installation of SAP S4
Hana fin in a single step.
 If Cash Management is to be used, you need to switch to New SAP Cash
Management powered by Hana, a separate license is required for
installing this component.
 Hanatization checks are done with the migration to SAP Hana database.

Customizing for The SAP General Ledger

 Activate ref IMG for SAP FI.
 Migrate GL settings
 Activate business functions
 Define settings for Journal Entry Ledger
 Define Ledger Groups
 Assign Accounting Principles to Ledger Group
 Execute Consistency check for GL settings
 Define source Ledger for migration of Balances

Customizing for New Asset Accounting:

 Migrate Charts of depreciation.
 Customization prior to activation
 Check prerequisites for activating New Asset accounting.
 Define active chart of depreciation
 Change definition of dep. Area.
 Activate New Asset Accounting.
Customization for Controlling:
 Execute SAP BW delta extraction for account based Profitability.
 Maintain Operating Concern.
 Activate Accounts based profitability
Data Migration
 Partitioning of the Universal Journal Entry table
 Regenerating core data services views & field mapping.
 Migration of Cost Elements
1. Check Consistency of SAP GL accounts & Cost Elements
2. Migrate Secondary Cost Elements to COA.
 Migration of Line Items to New Data structure.
 Migration of Balances
 Calculation of Depreciation & Total values
 Migration of House banks
 Reconcile & compare migrated data
 Set migration to completed.
 Migration with zero downtime.

Post migration activities:

 Run reconciliation reports to check data consistency
 Validate business process
 Transfer of application indexes
 Display of status application index transfer
 Fill the due dates in SAP ERP Financial Documents.
 Fill the offsetting account in SAP ERP Financial docs.

Post-migration Testing:
 Test SAP Hana optimized transactions
 Test Multi-dimensional Reporting Capability
 Test data base Foot print reduction.
 Test Inter-Co reconciliation.
 Test Closing environment
 Test Universal Journal
 Execute Change Management

New functionality of SAP S4 Hana:

 Validate SAP cash Management
 Set up Bank account Master data
 Define payment approval process
 Enable SAP business workflow for bank account management
 Create Cash pools as Source of Application
 Manage cash operations
 Integrate with One Source from various operations
 Set Cash Management transaction data.
 Activate individual source application.
 Activate multiple source applications.
 Rebuild planning levels, groups & dates in accounting documents
 Rebuild the Flow types in accounting documents
 Load transaction data into One exposure from Operation Hub.
 Set Up SAP Liquidity Management
 Install & Configure SAP Business objects & Business Intelligence.
 Activate SAP business objects & Business Intelligence Contents
 Install template for Cash flow analysis
 Generate a Planning view
 Activate SAP BPC content
 Install SAP BPC Content
 Set up Liquidity Planning
SAP BPC for S4 Hana Finance
 Activate business functions for Planning.
 Activate embedded business warehouse.
 Activate SAP business Objects
 Test the SAP BI
 Activate services for Planning Applications