Financials S4 AC110-EN-S4HANA.pdf

AC110Collection: 03 Material Number: 50129799 SAP Accounting powered by SAP HANA © 2015 SAP SE or an SAP affiliate company. All rights reserved. Abstract Target Group Application Consultant General Description The course provides an overview of the functionality of SAP Accounting powered by SAP HANA within SAP Simple Finance. Learning Objectives - Explain the scope and impact of the SAP Simple Finance On-Premise Edition 1503 - Explain the architecture of the SAP Simple Finance add-on - Explain the Central Finance deployment option of SAP Simple Finance - Configure and use new functionalities in SAP Accounting powered by SAP HANA - Use the standard SAP Fiori applications designed for Simple Finance Duration 2 days (classroom) © 2015 SAP SE or an SAP affiliate company. All rights reserved AC110 Unit Overview SAP Accounting powered by SAP HANA Unit 1: Overview of the SAP 120 minutes 180 minutes Unit 4: Management Simple Finance On-Premise Accounting Edition 1503 180 minutes 180 minutes Unit 2: General Ledger Unit 5: Further Simple Accounting Finance Integration 180 minutes Unit 3: Asset Accounting © 2015 SAP SE or an SAP affiliate company. All rights reserved  Unit 1: Overview of the SAP Simple Finance On-Premise Edition 1503 © 2015 SAP SE or an SAP affiliate company. All rights reserved. Unit 1 – Agenda Introducing SAP HANA and Providing an overview of SAP S/4HANA Reporting Options Describing the Architecture of Introducing SAP Fiori SAP Simple Finance Overview of Migration to the Analyzing the Universal Journal Simple Finance On-Premise Edition1503 Analyzing the Central Finance Option © 2015 SAP SE or an SAP affiliate company. All rights reserved  Lesson 1: Introducing SAP HANA and SAP S/4HANA © 2015 SAP SE or an SAP affiliate company. All rights reserved. Learning Objective After completing this lesson, you will be able to:  Give an overview of SAP HANA, SAP S/4HANA, and SAP Simple Finance © 2015 SAP SE or an SAP affiliate company. All rights reserved Scenario Your business has to process an ever increasing flood of data. You are looking for ways to extract meaningful information from this data and to be able to report on it efficiently. You are interested in understanding how SAP HANA can help you with your data storage and analysis needs today. You also want to make sure SAP HANA is the right core to future proof your organization in preparation for the information explosion coming with the expansion of the Internet of Things. You are interested in upgrading your current system landscape to a next generation solution. You are particularly interested in the new S/4HANA suite and want to understand the scope of the solution offering and available deployment option. © 2015 SAP SE or an SAP affiliate company. All rights reserved Tradeoff - Broad & Deep or Speedy & Simple With existing technologies, optimizing across all five dimensions in the spider diagram is not possible. DEEP OR DEEP HIGH SPEED HIGH SPEED BROAD REAL -TIME SIMPLE SIMPLE In both scenarios, real time updates are not possible per design; in a data warehouse environment they occur overnight via nightly batch jobs. © 2015 SAP SE or an SAP affiliate company. All rights reserved The Vision of SAP HANA A Common Database Approach for online transaction processing (OLTP) and online analytical processing (OLAP) Using an In-Memory Column Database Hasso Plattner - Co-founder and Chairman of the Supervisory Board of SAP Transactions + Analysis + Acceleration One individual copy of data for processes separated Transactions + Analysis, all in Memory SAP HANA ETL (DRAM) ETL Cache VS Transact Analyze Accelerate  3 copies of data in different data  Eliminate unnecessary complexity & models latency  Inherent data latency  Less hardware to manage  Poor innovation leading to wastage  Accelerate through innovation, simplification + in-memory © 2015 SAP SE or an SAP affiliate company. All rights reserved Paradigm Shift for Developers Calculation Application Layer Database Layer Calculation In traditional applications (especially from SAP), the database is largely used as a data store mechanism only. Massive queries bring large amounts of data back to the application server for processing. Lots of application execution time is spent in the application server looping over records and performing exclusions, calculations, etc. With HANA, the key to the best application performance is pushing as much of the logic execution into the database as possible. We now “trust” the database. Keep all the data intensive logic down in the database as SQL, SQLScript, and HANA Views. © 2015 SAP SE or an SAP affiliate company. All rights reserved SAP S/4HANA, Next Generation Business Software SAP SAP SAP Business Business Simple Warehouse Suite Finance SAP HANA powered powered powered by SAP by SAP by SAP HANA HANA HANA  In-memory  Real-time analysis  Real-time business  Instant financial platform  Real-time reporting  OLAP and OLTP insight together  No aggregates  Simplified data model  SAP HANA Enterprise  Single source of  New user experience Cloud for SAP truth Business Suite on  Advanced processing SAP HANA  Choice of deployment  Multitenancy 2011 2012 2013 2014 2015 • S/4HANA is natively built on SAP HANA for massive simplifications (simplified data model: no indices, no aggregates, no redundancies) • S/4HANA is natively designed with SAP Fiori offering an integrated user experience with modern usability (role-based, 3 steps max to get the job done, mobile-first, consistent experience across LoBs) • S/4HANA is natively built for advanced innovations (e.g. new applications predicting, recommending, simulating / processing of text, geo data, graphs, genomes. • S/4HANA is natively engineered for providing choice of deployment (on-premise, cloud, hybrid) • S/4HANA fully leverages the new multi-tenancy functionality enabled by SAP HANA © 2015 SAP SE or an SAP affiliate company. All rights reserved SAP S/4HANA, the next generation business suite Internet People of Things SAP Fiori UX role-based user experience for all devices SAP S/4HANA applications and extensions instant insight-driven applications for all lines of business and industries Business networks Devices SAP HANA platform in-memory platform for all data On-premise Cloud Social edition edition Big Data networks Native integration for hybrid scenarios Ariba Concur Fieldglass hybris Software SuccessFactors © 2015 SAP SE or an SAP affiliate company. All rights reserved Technical & Business Values Reduced Data Footprint Higher Throughput Full Flexibility S4HANA ERP on anyDB (estimate) ERP on HANA S4HANA ERP on anyDB (estimate) No Indices No Aggregates No Redundancy 7.1 TB 1.8 TB 0.8 TB 0.5 TB ACTUALS 1 3-7x Enterprise Software for Big Data and Agility © 2015 SAP SE or an SAP affiliate company. All rights reserved  Customer journey to SAP S/4HANA – 3 situations, 3 deployment options Choice of deployment Starting point A New customer On Premise Cloud Hybrid deploy new installation up and running with best practices in two days Starting point B SAP Business Suite on anyDB On Premise Cloud Hybrid customer upgrade to latest EHP, migrate database transfer data to the cloud to SAP HANA, deploy exchange no migration Supported by predefined innovation migration, system conversion in the cloud and deployment Starting point C packages from partners and SAP SAP Business Suite powered by SAP HANA On Premise Cloud Hybrid deploy exchange innovation transfer data to the cloud customer no migration Innovation without disruption © 2015 SAP SE or an SAP affiliate company. All rights reserved SAP Simple Finance Instant Insight Intuitive User Experience Flexible and Non-disruptive in memory-enabled all devices cloud or on premise Financial Planning Accounting and Treasury and Finance Enterprise Risk and Analysis Financial Close Financial Risk Operations and Compliance © 2015 SAP SE or an SAP affiliate company. All rights reserved Impact of SAP HANA on Finance: Simpler and Faster “Personalized information for end users with granular drill down“ Business Intelligence Renewed Managerial Roles Renewed Transactional Roles Web Financial Chief Financial Officer General ledger accountant Statement Financial close Accounts receivable Web Journal Entry manager accountant Analyzer Cash manager Accounts payable SAP Analysis for Office Receivables manager accountant SAP Lumira Payables manager Collections specialist SAP Business Explorer Finance for managers Dispute specialist SAP Design Studio © 2015 SAP SE or an SAP affiliate company. All rights reserved Impact of SAP HANA on Financials: Simpler and Faster Chief SAP Simple Finance - delivers functional completeness across all financial roles Financial Officer VP of Finance Head of Corporate Corporate Head of Finance Chief Compliance Reporting Treasurer Operations Officer Treasury & Collaborative Enterprise Risk & Financial Planning Accounting & Financial Risk Finance Compliance & Analysis Financial Close Management Operations Management Develop and Payments and Bank Receivables Enterprise, Risk Accounting Translate Strategy Communications Management Management Controls and Planning, Budgeting Cash and Liquidity Collaborative Entity Close Invoice to Pay Compliance and Forecasting Management Management Debt and Profitability and Cost Corporate Close Investment Travel Management Access Governance Management Management Monitoring and Reporting and Financial Risk Financial Shared International Trade Reporting Disclosure Management Services Management Financial Close Commodity Risk Real Estate Governance Fraud Management Management Management Audit Management © 2015 SAP SE or an SAP affiliate company. All rights reserved Key Innovations within SAP Simple Finance SAP Accounting SAP Cash Management SAP Integrated Business powered by SAP HANA powered by SAP HANA Planning for Finance Alternative in-memory New product for New capabilities and enhanced functionality for ERP customers Group Cash Management integration for ERP and BPC Business Suite on HANA SAP HANA Platform Aligned Agile Predictive Single Source of Truth Real time processes Dynamic Planning and Analysis © 2015 SAP SE or an SAP affiliate company. All rights reserved Adoption Scenarios for Simple Finance Option 1: Upgrade and Migrate Option 2: Upgrade, Migrate and Consolidate (all instances) (reduce number of instances) Simple Simple SAP ERP SAP ERP Migrate Finance Finance or or Migrate SAP R/3 SAP ERP 6.0 SAP ERP 6.0 SAP R/3 EhP7 on HANA EhP7 on HANA Option 3: Replicate into a Central Finance (and optionally reduce number of instances over the time) Replicate Simple SAP ERP Finance or SAP ERP 6.0 SAP R/3 EhP7 on HANA source system(s): Real-time Central Finance  SAP (any release) Reconciled instance  non-SAP systems © 2015 SAP SE or an SAP affiliate company. All rights reserved Related SAP Links Where What Link SAP.COM SAP HANA http://hana.sap.com/ Help Portal SAP HANA Innovations for SAP http://help.sap.com/hibs Business Suite SAP.com Discover SAP S/4HANA http://discover.sap.com/S4HANA SAP Service Hybrid Scenarios http://service.sap.com/public/hybrid Marketplace SAP.COM Help Page for SAP Simple Finance http://www.sap.com/solution/lob/fin ance/software/cloud-erp-finance- management/index.html © 2015 SAP SE or an SAP affiliate company. All rights reserved Learning Summary You should now be able to:  Give an overview of SAP HANA, SAP S/4HANA, and SAP Simple Finance © 2015 SAP SE or an SAP affiliate company. All rights reserved Unit 1 – Agenda Introducing SAP HANA and Providing an overview of SAP S/4HANA Reporting Options Describing the Architecture of Introducing SAP Fiori SAP Simple Finance Overview of Migration to the Analyzing the Universal Journal Simple Finance On-Premise Edition1503 Analyzing the Central Finance Option © 2015 SAP SE or an SAP affiliate company. All rights reserved  Describing the Architecture of SAP Simple Finance © 2015 SAP SE or an SAP affiliate company. All rights reserved. Learning Objective After completing this lesson, you will be able to:  Explain the idea and concept of the Universal Journal  Explain how SAP safeguards the customer investments  Outline the most important architectural changes in Simple Finance  Understand the Universal Journal entry  Outline the Appendix Ledger functionality © 2015 SAP SE or an SAP affiliate company. All rights reserved Scenario You want to understand in detail the underlying architecture changes to the SAP ERP application from the installation of the Simple Finance On-Premise Edition 1503. You want to understand the potential benefits these changes bring and also make sure your custom developments won’t be disrupted with the migration. © 2015 SAP SE or an SAP affiliate company. All rights reserved SAP Accounting Architecture Rational A true single source of truth for all accounting components.  Reconciliation is a topic of the past bringing large cost and time savings. A simple but holistic data model.  HANA can be leveraged in the best possible manner bringing unprecedented insight (in both speed and content!). The universal journal combines and harmonizes the good qualities of all accounting components.  The simplification of the application is a required step and a great foundation for further enhancements. Non-disruptive innovation and simplification.  SAP strives to provide a true next generation application with the least possible disruption, safeguarding customer investments and processes. © 2015 SAP SE or an SAP affiliate company. All rights reserved Multiple sources of truth (1/2) No profit center & Different level of detail due to no G/L account in the ‘999’ document lines limit Asset Accounting Totals e.g. 1:n documents FI/CO Material Ledger does G/L and Profitability updated not store G/L account at different business events and Profit Center on different entities (e.g. account) Separate components due to technical restrictions in the past (without HANA) © 2015 SAP SE or an SAP affiliate company. All rights reserved Multiple sources of truth (2/2) Challenges of the architecture before Simple Finance Challenges:  The combined content of several tables represents “the truth”. Reconciliation efforts are needed by architecture.  Different level of detail stored in the respective components/tables  Components are structured differently (e.g. fields/entities differ)  Need “to move” data to the appropriate table for reporting (e.g. “settlement”)  Different capabilities in the components (customer fields, currencies, multi-GAAP etc.)  Multiple BI extractors needed to cover the complete truth in BI. © 2015 SAP SE or an SAP affiliate company. All rights reserved New Architecture – Universal Journal as the Single Source  One line item table with full detail for all components. Data stored only once, so no reconciliation needed by architecture.  Fast multi-dimensional reporting on the Universal Journal possible without replicating data to BI. If BI is in place, one single BI extractor is needed.  Reduction of memory footprint through elimination of redundancy.  Technical preparation done to enhance important structural capabilities of the Financials solution (e.g. multi-GAAP, additional currencies) © 2015 SAP SE or an SAP affiliate company. All rights reserved Non-disruptiveness Existing programs and interfaces can still be used access via compatibility views:  Read access from custom ABAP programs or reports to prior tables will work as before  Read access is automatically re-directed to the universal journal as the new single source of truth  All programs with write access to those deleted tables replaced by CDS views will make trouble and can´t be used anymore without adaption. Remove all write accesses in by views replaced tables. Use the code inspector to find all affected parts of the code (see note 1976487). © 2015 SAP SE or an SAP affiliate company. All rights reserved List of Tables Replaced by Compatibility Views © 2015 SAP SE or an SAP affiliate company. All rights reserved Universal Journal extensibility Universal Journal Standar Standard zzcust0 wwprof0 … zzcust01 … wwprof02 … d Field x Field x+1 2 1 Coding Block extensibility CO-PA extensibility  The Universal Journal can be easily extended with customer fields. Extensibility is available for all components that use the Universal Journal (G/L, CO, AA, ML).  P&L line extension using “CO-PA capabilities” is provided, both for field definition (characteristics) and the rich derivation tools from CO-PA.  The standard General Ledger coding block extensibility can be used and affects the Universal Journal  The new HANA based reporting of all components (G/L, AA, ML, CO) can access the customer fields. © 2015 SAP SE or an SAP affiliate company. All rights reserved Demos & Exercises Activity Name Page DEMO 1 HOW TO EXTEND THE GENERAL LEDGER EX-3 CODING BLOCK EXERCISE 1 DISPLAY FINANCIALS TABLES IN SIMPLE EX-12 FINANCE © 2015 SAP SE or an SAP affiliate company. All rights reserved Summary You should now able to:  Explain the idea and concept of the Universal Journal  Explain how SAP safeguards the customer investments  Outline the most important architectural changes in Simple Finance © 2015 SAP SE or an SAP affiliate company. All rights reserved Unit 1 – Agenda Introducing SAP HANA and Providing an overview of SAP S/4HANA Reporting Options Describing the Architecture of Introducing SAP Fiori SAP Simple Finance Overview of Migration to the Analyzing the Universal Journal Simple Finance On-Premise Edition1503 Analyzing the Central Finance Option © 2015 SAP SE or an SAP affiliate company. All rights reserved  Analyzing the Universal Journal © 2015 SAP SE or an SAP affiliate company. All rights reserved. Learning Objective After completing this lesson, you will be able to:  Understand the Universal Journal entry  Outline the Appendix Ledger functionality © 2015 SAP SE or an SAP affiliate company. All rights reserved Scenario You want to understand the new posting logic within the accounting component. You are interested in understanding how the journal postings are handled from the various components and whether the unification into a central finance limits the flexibility you have associated with your management accounting processes. © 2015 SAP SE or an SAP affiliate company. All rights reserved Universal Journal Entry  The new journal entry consists of a header (table BKPF) and the respective items (table ACDOCA) – There are rare cases, where entries in ACDOCA are written without a respective document header (e.g. carry forward, corrections in migration). These entries do not represent standard business processes. – The corresponding line items have ‘artificial document numbers’ beginning with letters (e.g. ‘A’).  ACDOCA table contains all fields needed for G/L, CO, AA, ML, PA  All cost elements, including secondary cost elements are G/L accounts  Multi-GAAP capability through “RLDNR” dimension  6 digit field for line item numbering  23 digits for currency fields © 2015 SAP SE or an SAP affiliate company. All rights reserved Document Numbers in Simple Finance  Since the system now writes only one journal entry for all of the components G/L, CO, AA, ML, one document number is sufficient from a business point of view. The journal entry consists of a header (BKFP) and items (ACDOCA). The respective document number (BKPF-BELNR/ACDOCA-BELNR) must obey the legal rules of Financial Accounting. As a consequence, the document number is dependent on the fiscal year and the company code.  CO document numbers have not been year ACDOCA dependent. Material ledger document numbers have not been dependent from the DOCLN CO_BELNR CO_BUZEI organizational unit (e.g. company code). 000001 A00X345100 001 Both numbers did not have a legal 000002 relevance. Moreover, ACDOCA has a 6 digit … field for the document line, whereas COEP has only a 3 digit field. This is still used in 001082 A00X345100 999 many user interfaces and reports. For 001083 A00X345101 001 compatibility reasons, SAP offers a new .. transaction number for every 999 document 001130 A00X345101 086 lines. © 2015 SAP SE or an SAP affiliate company. All rights reserved Prima Nota in Simple Finance  The Prima Nota is the source document that triggers the creation of Journal Entries. The Prima Nota is the single anchor that allows e.g. to reverse the complete process triggered by the Prima Nota.  The Prima Nota keeps the information that has been entered to the system, before derivations, enrichments, splits etc. take place in Accounting in order to create Journal Entries.  In many cases the Prima Nota is a document outside Financials. Examples are Expense Reports, Invoices, Payroll documents.  For posting within the Financials world a Prima Nota is needed as well. © 2015 SAP SE or an SAP affiliate company. All rights reserved Prima Nota per Financial Component  For classical FI postings (FB01, FB50, FB60, FB70 etc.) the Prima Nota is still stored in table BSEG and the corresponding Journal Entries (can be several due to the multi GAAP capability) are written to table ACDOCA.  For classic (manual) CO postings the Prima Nota is still written to table COEP. The corresponding journal entries are written to table ACDOCA. A Prima Nota is written as well in cases, where “CO” is triggered via BAPI interfaces (AWTYP <> AFRU, CATS)  For allocation postings (assessment, settlement etc.) no Prima Nota is required and data is written to table ACDOCA only. The allocation process has its own history management (for example canceling an allocation journal entry)  Material price changes (MR21) or Material Debit/Credit (MR22) create a Prima Nota in the material ledger (tables MLHD, MLIT etc. ). The respective journal entries are posted to ACDOCA. © 2015 SAP SE or an SAP affiliate company. All rights reserved External Postings with Simple Finance  Former COEP, FAGLFLEXA, MM ANEP, MLIT etc. data are ACDOCA stored in ACDOCA  BSEG as before Simple SD Finance. Can still be BSEG summarized.  Profit Center Accounting (EC- HR PCA), Special Purpose Ledgers PCA (FI-SL) and, Consolidation (EC- Accounting CS) remain technically Interface AA untouched and work as before. FI-SL  Components that have been built with FI-SL technology like ML Joint Venture Accounting, EC-CS Public Sector etc. are untouched and work as before. Other Cost Based  Cost based CO-PA works as CO-PA before © 2015 SAP SE or an SAP affiliate company. All rights reserved Demos & Exercises Activity Name Page EXERCISE 2 POST AND REVERSE A SIMPLE FI DOCUMENT EX-20 EXERCISE 3 POST A CO TRANSFER POSTING AND VIEW THE EX-30 RESULT © 2015 SAP SE or an SAP affiliate company. All rights reserved Summary You should now able to:  Understand the Universal Journal entry  Outline the Appendix Ledger functionality © 2015 SAP SE or an SAP affiliate company. All rights reserved Unit 1 – Agenda Introducing SAP HANA and Providing an overview of SAP S/4HANA Reporting Options Describing the Architecture of Introducing SAP Fiori SAP Simple Finance Overview of Migration to the Analyzing the Universal Journal Simple Finance On-Premise Edition1503 Analyzing the Central Finance Option © 2015 SAP SE or an SAP affiliate company. All rights reserved  Analyzing the Central Finance Option © 2015 SAP SE or an SAP affiliate company. All rights reserved. Learning Objective After completing this lesson, you will be able to:  Understand the motivation for the Central Finance solution  Get an overview of the Central Finance solution  Explain implementation options and requirements © 2015 SAP SE or an SAP affiliate company. All rights reserved Scenario You are managing a complex and varied ERP system landscape. You want to find a solution to improve financial reporting and processes, both in speed and accuracy. A large transformation and migration project to completely new systems is out of the question due to time, cost, complexity and business continuity requirements. You want to understand if and how the SAP Central Finance solution can help transform and modernize your Finance reporting and operations. © 2015 SAP SE or an SAP affiliate company. All rights reserved Business Challenges  Consolidated entity reporting latent, high-level, aggregated management information  Central process execution missing economies of scale, no shared services  Business model pressure organic and non-organic growth mandate  Heterogeneous IT landscapes unyielding to modernization or transformation  SAP and non-SAP ERP systems high consolidation, harmonization, reconciliation effort  Relational database designs data duplication, data redundancies  Productivity & Effectiveness people can’t get the data they need to make a decision © 2015 SAP SE or an SAP affiliate company. All rights reserved The Central Finance Solution Central Finance helps companies report on financial figures sourced from different systems. These systems might be running Classic G/L, new G/L, or might not be SAP at all. They probably have different customizing settings and un-harmonized master data: With the Central Finance solution , there are three interfaces that feed data from the source systems into the target system’s Accounting Interface.  An interface for reposting FI/CO postings: Financial documents that are posted in the source system get reposted as new FI documents in the central finance system. If these postings are relevant to CO (expenses on cost elements), CO will be updated, too  An interface for reposting CO postings: This interface reposts CO postings where the CO document is the loading document. In contrast to the interface for FI/CO postings, these are postings that are not necessarily reflected in Financials in the source system (sometimes only for reconciliation purposes). For example, postings on secondary cost elements.  An interface for replicating certain cost objects (such as production orders, internal orders, QM orders etc.). The posted documents are stored in the universal journal of the SAP Simple Finance system. It is possible to take advantage of new G/L features within SAP Simple Finance as well as the ability of flexible reporting based on line-items instead of pre-aggregated totals. Furthermore beautiful Fiori User Interfaces and reporting tools can be used in the Central Finance. Reporting with the speed of HANA is available on line- item levels. © 2015 SAP SE or an SAP affiliate company. All rights reserved System Landscape A dedicated Simple Finance system (Suite on HANA, Simple Finance at its core) and SAP planning, consolidation and reporting capabilities (optional) connected to one or more ERP systems on-premise plan, consolidate, report Simple Real-time Finance Reconciled Harmonized Suite on OR HANA ERP cloud SAP HANA ERP(s) (platform) source system(s): central finance instance  SAP (any release)  non-SAP systems  old, out-of-maintenance  over-customized © 2015 SAP SE or an SAP affiliate company. All rights reserved Key installation components Required:  SAP HANA hardware (on-premise, cloud, private cloud) and software (database / appliance)  SAP Landscape Transformation (LT) Replication Server (plus partner products like Datalytics for non-SAP ERP systems)  SAP S/4HANA (ERP with SAP Simple Finance)  SAP HANA Live/Fiori and Smart Business Cockpits etc.  SAP Business Intelligence tools like Analysis for Office  Additional Simple Finance products like Integrated Business Planning, Cash Management, or Fraud Management etc. (optional) © 2015 SAP SE or an SAP affiliate company. All rights reserved Deployment  A Central Finance can be established on-premise or in the cloud. DEPLOYMENTS  In a cloud deployment scenario data is replicated using the same mechanisms used in on-premise installations (SLT). The respective SLT portions will have to be available on both, the sending (on-premise) and receiving system (cloud).  Non-SAP reporting and analytics (as well as additional SAP On Premise Simple Finance or partner products) need to be connected to the cloud instance or be made available within the cloud installation as required.  Special considerations in the cloud scenario include but are not limited to wide area network (WAN) throughput and Hybrid firewall/security requirements. Cloud © 2015 SAP SE or an SAP affiliate company. All rights reserved Inbound posting interfaces (Finance, Controlling) Central Finance FI/CO Postings FI Universal Document CO Central Journal Entry Document Finance CO Postings Suite on HANA Accounting CO Interface Document Cost Object Mapping Reposting harmonizes data but retains line item-based detail SAP HANA Central Finance instance © 2015 SAP SE or an SAP affiliate company. All rights reserved Sender data fields for document drill back New “Sender” data fields that explicitly track source Double-click to navigate back to FI document in source system Central Finance system Sender system © 2015 SAP SE or an SAP affiliate company. All rights reserved Master data creation for CO cost objects Cost Object Mapping Framework manages short-lived cost objects Central Finance Long-Life Master Data Central Cost Production Object Stable, only need to be Order1 harmonized once Expense1 Reporting Production Examples: Company Code, Cost Object Mapping Order2 Central Product Cost Collector Plant, Material, Cost Center Expense2 Production Managed by SAP Master Order3 Data Governance Primary and Secondary Expense3 Cost Postings Expense1 Short-Life Cost Object Expense2 Source System Similar to transactional data, generated frequently Expense3 Examples: Production Order, SAP HANA Internal Order, Service Order… Managed by Cost Object Central Finance instance Mapping Framework A cost object in the source system is mapped to an automatically generated cost object in Central Finance © 2015 SAP SE or an SAP affiliate company. All rights reserved Implementation Realization  Implementing the Central Finance is not a “ERP-from-scratch” effort; and could be as low 10 - 15% of a traditional ERP implementation effort and duration  Most if not all business processes most likely already exist in one of the existing SAP systems and can be re-used / re-applied. Lessons learned from previous implementations can be incorporated.  The actual roll-out effort varies based on data harmonization applied, business transformation desired, and the number of systems and processes touched Roll-out  Incremental - based on processes, business areas and source systems selected  Not a typical ERP implementation - No Big Bang !!! Timeline  Phased in quarterly (milestone-based) increments; first roll-out possible in as little as 3 months Skills / Resources  Basis/Admin (system setup, security setup)  Technical (HANA / HANA Live / SLT replication, ABAP)  Functional (configuration, processes, master data, data harmonization) © 2015 SAP SE or an SAP affiliate company. All rights reserved Restrictions  Centrally executed processes must not result in back-postings to the source systems in order to maintain the integrity (completeness etc.) and legacy system status of those systems.  The amount of configuration, customizing, and master data synchronization required in the central instance depends on the type of process desired. Many scenarios, especially core GL scenarios, are achievable with limited effort. More complex scenarios, or scenarios beyond (core GL) Finance might be challenging or in selected cases not feasible. © 2015 SAP SE or an SAP affiliate company. All rights reserved Summary You should now able to:  Understand the motivation for the Central Finance solution  Get an overview of the Central Finance solution  Explain implementation options and requirements © 2015 SAP SE or an SAP affiliate company. All rights reserved Unit 1 – Agenda Introducing SAP HANA and Providing an overview of SAP S/4HANA Reporting Options Describing the Architecture of Introducing SAP Fiori SAP Simple Finance Overview of Migration to the Analyzing the Universal Journal Simple Finance On-Premise Edition1503 Analyzing the Central Finance Option © 2015 SAP SE or an SAP affiliate company. All rights reserved  Providing an overview of Reporting Options © 2015 SAP SE or an SAP affiliate company. All rights reserved. Learning Objective After completing this lesson, you will be able to:  Explain the different options that are offered for analytics in Simple Finance  Explain which option to use for a given use case © 2015 SAP SE or an SAP affiliate company. All rights reserved Scenario You want to make sure you have a good overview of the reporting options for Simple Finance. You want to see how you can leverage your existing infrastructure but also understand what other options are available. You want to make an optimal choice for both your backend and frontend reporting and analytics tools so that you effectively report on the data posted to the system. © 2015 SAP SE or an SAP affiliate company. All rights reserved SAP HANA Live With SAP HANA Live, you have Real- Reporting options Time operational reporting directly on + All SAP Smart Business Apps your S/4HANA system without any + Open architecture redundancy or latency. + 3rd party / customer UIs + Data sources from logistics etc.  No hierarchy support  User management in HANA Smart AO Lumira SQL Business Performance considerations + Very lean stack + No overhead  No load balancing  Pure SQL statements Criteria to choose SAP HANA Live Views  Smart Business  SAP UI 5 / HTML 5 Apps  Cross area reporting  3rd party interface © 2015 SAP SE or an SAP affiliate company. All rights reserved Embedded BW Embedded BW directly supports: Reporting options  business processes in the SAP Business + Hierarchy support Suite like integrated business planning + User management in NW for Finance, + Flexible report design in BW Query  analytics in the SAP Business Suite for + Real-time data typical SAP BW OLAP scenarios + Transient (on the fly) BW objects  BW technology stack Design Crystal Performance considerations AO Lumira Studio Report + ABAP code injection possible + HANA optimization used BW Query + Load balancing on App Server + BW caches Transient ODP / Virtual Provider  BW technology overhead Criteria to choose SAP HANA Live Views  Operational FIN reporting  Lists, drilldown, dashboards,… Plan  Plan / actual reporting for planning scenarios on new embedded planning architecture © 2015 SAP SE or an SAP affiliate company. All rights reserved SAP BW on HANA With SAP BW you can integrate, Reporting options transform, and consolidate relevant + Warehousing capabilities business information from productive SAP  Not real time (best near real time) applications and external data sources.  BW Content management  BW system TCO Performance considerations + Separation of OLAP / OLTP load AO Lumira Design Crystal  Replication overhead & load Studio Report  Split of OLAP & OLTP processes BW Query Criteria to choose  Data consolidation and cleansing  Data enrichment Virtual Provider SAP HANA Live Views SLT ETL © 2015 SAP SE or an SAP affiliate company. All rights reserved Backend Reporting Tool Decision matrix SAP ODP Virtual BW on HANA based Provider HANA Live reporting Usage of hierarchies (for display, selection, authorization) ++ ++ ++ Plan data integration (New sFIN integrated planning O ++ O scenarios) Cross system reporting including data harmonization -- ++ No End User access to DB server ++ ++ ++ Real Time reporting ++ ++ ++ You are already using BW for Financials reporting O + ++ ++ You do not yet use BW for Financials reporting ++ ++ - -- You are already using Smart Business + O O O Report to report navigation -- ++ ++ O Access by non SAP tools ++ O O O Report / selection variants -- + + + TCO/TCI + + O - Extensibility and adaptability O - - O © 2015 SAP SE or an SAP affiliate company. All rights reserved Data Consumption Tools Discovery and analysis Dashboards and apps Reporting Discover. Predict. Create. Build engaging experiences Share information  Discover areas to optimize  Securely distribute information  Deliver engaging information to Purpose your business users where they need it across your organization  Adapt data to business needs  Track key performance indicators  Give users the ability to ask and and summary data answer their own questions  Tell your story with beautiful visualizations  Build custom experiences so  Build printable reports for users get what they need quickly operational efficiency SAP Solution  Design Studio Analysis Pattern  Web Intelligence  Design Studio  Lumira  Dashboards (a.k.a., Xcelsius®)  Crystal Reports  Explorer  Smart Business  Fiori Analytical Applications  Analysis for Office © 2015 SAP SE or an SAP affiliate company. All rights reserved Frontend Reporting Tool Decision matrix There are several distinct types of reporting, specific requirements need specific frontends. Use Case Recommended Customizable Characteristics Frontend Alternatives Interactive Drill Design Studio3 AO1,2, BO Explorer2, Flexible analysis on any level of detail combined with easy Down BeX1,2, FPM Grid adaptability to the customer setup Plan data entry Design Studio3 AO1,2, FPM Grid Integrated plan and actuals, flexible planning levels and forms (Work)lists Design Studio3 or Predefined lists with focus on insight to action Fiori KPI Reporting Smart Business, Excelsius1,2, Design High level graphical visualization of KPIs with basic drill executive edition Studio2 down capabilities, primarily for management Explorative Ad Lumira2 BO Explorer2, APF Easy to build and share graphical visualization of Hoc Reporting4 individual reports Legal Reports4 Globalization Creation and management of legal reports like Securities Services Legal and Exchange Commission (SEC) filings reporting tool Formatted Crystal reports1,2 or Web Intelligence2 Reports with high requirements on exact formatting, reporting4 Adobe anything requiring something beyond normal output management 1 not cloud ready 2 separate license required 3 limited runtime license included in Simple Finance license 4 no content shipped © 2015 SAP SE or an SAP affiliate company. All rights reserved Reporting Outlook for Simple Finance Simple Finance S/4HANA Target for Simple Finance in S/4HANA Analysis Office Lumira Crystal reports 3rd party Enterprise APF Dashboard Smart Smart Design Studio Fiori Apps Design Studio Fiori Apps Business Business oDATA BW Query oDATA CDS View Query CDS View ExtView ODP / Virtual Provider SAP HANA Live Views CDS VDM Views © 2015 SAP SE or an SAP affiliate company. All rights reserved Links to videos for analytics tools What Link SAP BusinessObjects Design Studio https://www.youtube.com/playlist?list=PLs5htBIw Tutorials ERYWFt-ixnVgxsUGvQpR9E8hI SAP BusinessObjects Dashboards 4.x https://www.youtube.com/playlist?list=PLs5htBIw Tutorials ERYUA748i26Z9Y0Z2dXw3s29E SAP BusinessObjects Analysis 1.x, https://www.youtube.com/playlist?list=PLs5htBIw edition for MS Office Tutorials ERYXTVP--IvbjaTJF0enYv6kK SAP BusinessObjects Explorer 4.x https://www.youtube.com/playlist?list=PLs5htBIw Tutorials ERYW9NthcmsyCMSMNwJhF6QP5 SAP BusinessObjects Web Intelligence https://www.youtube.com/playlist?list=PLs5htBIw 4.x Tutorials ERYUjNLyWJR2g2U2aSWPzJBou SAP Lumira 1.17 - 1.23 Tutorials https://www.youtube.com/playlist?list=PLs5htBIw ERYWqmHlnbAB6gSQ3b39JzWLa SAP Crystal Reports 2011 / 2013 https://www.youtube.com/playlist?list=PLs5htBIw Tutorials ERYULWPdq3xdVb6R68Up_kCFu SAP Smart Business Example https://www.youtube.com/watch?v=sRjrhralEHE © 2015 SAP SE or an SAP affiliate company. All rights reserved Summary You should now able to:  Explain the different options that are offered for analytics in Simple Finance  Explain which option to use for a given use case © 2015 SAP SE or an SAP affiliate company. All rights reserved Unit 1 – Agenda Introducing SAP HANA and Providing an overview of SAP S/4HANA Reporting Options Describing the Architecture of Introducing SAP Fiori SAP Simple Finance Overview of Migration to the Analyzing the Universal Journal Simple Finance On-Premise Edition1503 Analyzing the Central Finance Option © 2015 SAP SE or an SAP affiliate company. All rights reserved  Introducing SAP Fiori © 2015 SAP SE or an SAP affiliate company. All rights reserved. Learning Objective After completing this lesson, you will be able to:  Understand the importance of the user interface (UI) design  Present the technical component landscape  Explain the basic Fiori application tools © 2015 SAP SE or an SAP affiliate company. All rights reserved Scenario You want to make sure your users have the best possible experience when interacting with the Business Suite. You want to ensure users can access business critical applications on any device without compromises. Finally, you want to assure the solution will integrate into your existing IT system landscape and can expand to cover your specific needs. You want to make sure SAP Fiori covers these requirements. © 2015 SAP SE or an SAP affiliate company. All rights reserved Why focus on User Experience? Great User Experience Gain productivity $ Increase user adoption Decrease user errors Save training costs © 2015 SAP SE or an SAP affiliate company. All rights reserved SAP Fiori User Experience Paradigm Instant Role-based Responsive Simple Coherent Value Decomposition All sizes, 1-1-3 (1 user, Apps that speak Low barrier into task-based devices, 1 use case, the same to adoption experience versions, 3 screens) language channels © 2015 SAP SE or an SAP affiliate company. All rights reserved Key benefits of SAP Fiori - Improving customer’s user experience Increase productivity Improve time to value Lower risk Reduce TCO  Employees are able to get  Faster implementation  Implementation aligned  Reduce customization the job done anytime, to business value and and integration  Predictable anywhere feasibility complexity via SAP Fiori implementation timeline toolkit and rapid-  Managers can streamline  Supportability by SAP  Better quality deployment offerings processes, impact assurance/reliability  SAP validated and tested business results  Lower maintenance costs  Standards-based, flexible  Future-proof investment  Apps coherent and easy  Reuse of skill sets software framework to use  Continuous innovation  Intuitive usage  Instant roll out  Additional features significantly reduces capabilities to different (example: mass learning effort and cost devices approvals) to accelerate handling  IT helps improve employees satisfaction by addressing their business needs in a timely manner © 2015 SAP SE or an SAP affiliate company. All rights reserved Technical Architecture of Smart Business and Fiori © 2015 SAP SE or an SAP affiliate company. All rights reserved Fiori Launchpad – One Entry Point for the User Role based & Theming and personal centric branding Personalization Stable URLs for bookmarking and Search, sharing collaboration and feeds Multiple Platforms Multiple Devices SAP Fiori Active Tiles, Provides the most impactful real-time information and KPIs at a glance © 2015 SAP SE or an SAP affiliate company. All rights reserved Fiori Launchpad User Personalization End users can personalize the tiles in their Fiori Launchpad environment. Add new tile to Enter the Title of the new Search the new tile in the catalog and add to catalog tile and threshold Launchpad  For example: The group cash manager would like to create a new Cash Position app which monitors the cash position for the German subsidiary only as that is a market of interest for him. © 2015 SAP SE or an SAP affiliate company. All rights reserved SAP Fiori Launchpad Designer The Fiori Launchpad designer is the standard tool for:  Configuring the tiles for static app launchers, dynamic app launchers, and target mapping.  Creating pre-configured groups and catalogs for the Launchpad home page.  Transporting the configurations via correction requests / packages or customizing workbench. Fiori Launchpad Designer help doc (https://go.sap.corp/fldhelp) © 2015 SAP SE or an SAP affiliate company. All rights reserved SAP Fiori Theme Designer An administrator uses the tool to design custom themes for the Launchpad. © 2015 SAP SE or an SAP affiliate company. All rights reserved Related SAP Links Where What Link SAP Service Note 2117719 https://css.wdf.sap.corp/sap/suppo Marketplace Release Information Note: SAP Fiori for the rt/notes/2117719 SAP Simple Finance On-Premise Edition 1503 © 2015 SAP SE or an SAP affiliate company. All rights reserved Demos & Exercises Activity Name Page EXERCISE 4 CUSTOMIZE YOUR LAUNCHPAD AND MANAGE EX-35 CUSTOMER ITEMS © 2015 SAP SE or an SAP affiliate company. All rights reserved Summary You should now be able to:  Understand the importance of the user interface (UI) design  Present the technical component landscape  Explain the basic Fiori application tools © 2015 SAP SE or an SAP affiliate company. All rights reserved Unit 1 – Agenda Introducing SAP HANA and Providing an overview of SAP S/4HANA Reporting Options Describing the Architecture of Introducing SAP Fiori SAP Simple Finance Overview of Migration to the Analyzing the Universal Journal Simple Finance On-Premise Edition1503 Analyzing the Central Finance Option © 2015 SAP SE or an SAP affiliate company. All rights reserved  Overview of Migration to the Simple Finance On-Premise Edition1503 © 2015 SAP SE or an SAP affiliate company. All rights reserved. Learning Objective After completing this lesson, you will be able to: • Understand the possible starting points for migration • Give a brief overview of the migration process © 2015 SAP SE or an SAP affiliate company. All rights reserved Scenario You are currently running a system on classic G/L, new G/L, or Simple Finance 1.0 and want to upgrade to use the functionalities of the latest version of the Simple Finance add-on. You want to know if your current system configuration meets the prerequisites and what kind of changes will you need to prepare for. © 2015 SAP SE or an SAP affiliate company. All rights reserved From where can I migrate to Simple Finance? Classic GL, New GL, New GL, Simple Finance old Asset old Asset new Asset 1.0 Accounting Accounting Accounting (New GL, new Asset Accounting) SFIN Migration SFIN Migration SFIN Migration SFIN Migration Installation & Installation & Installation & Installation & New SAP customer – Accounting in Non- SAP System Data Takeover SAP Accounting in Simple Finance On-Premise Edition 1503 New SAP customers starting with SAP S/4HANA will take over their legacy data using classic migration tools. The SAP Simple Finance migration tools work only for existing customers/system. Depending on the active applications in the source system, different preparation steps are relevant. The description can be found in the SAP online help. © 2015 SAP SE or an SAP affiliate company. All rights reserved Migration to the Simple Finance Add-On is Fast and Easy  The duration and effort is relatively small. It can be executed at any period end.  It is supported by a migration guide and monitor.  No New G/L (or other) Migration Service is needed to migrate to SAP Accounting powered by SAP HANA  Migration scope is comparable to migration to new G/L scenario 1 (Merge of the FI ledger)  Changes to coding blocks, external interfaces, security, reporting etc. are optional © 2015 SAP SE or an SAP affiliate company. All rights reserved Classic General Ledger Migration Constraints Migration to Accounting on 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 Note: If you have started or are in the planning phase to start a migration to new GL using the SAP General Ledger Migration Service, SAP recommends that you complete the new GL migration project before installing the Simple Finance Add-On. © 2015 SAP SE or an SAP affiliate company. All rights reserved Length of the Migration Project It is not possible to make an exact statement here. Factors that could influence the duration: • Support from the customer themselves (how many people, how quickly can you set up a test system etc.) • Experiences of project members and consultants • Quality of data, size of the system etc.(Migration of a system with goLive 2013 might obviously be easier than a system with goLive 1996.) • A delta migration scenario is planned to optimize (minimize) downtime. The first test migration will give a good first impression for the duration and potential setbacks during the migration project © 2015 SAP SE or an SAP affiliate company. All rights reserved Sequence in Test and Productive Environment DOWNTIME Productive System Completeness Preparation Installation Migration Uptime Imports Check C o p Import y Test/Development System System Installation of Customizing Data Post- Data Checks Preparation SAP Simple for Migration Migration Migration and Process Phase Finance Add-on Activities Tests Checks: Installation of: Customizing for: • Cost Elements • Cold Store • Data comparison • Pre-checks • SAP Simple • General Ledger • Enrich items/ • Add further • Reporting checks • Consistency & Finance Add- • Asset documents information to • Process tests Data Clean-up On Accounting documents • Line Items • Custom Code • HANA Live • Controlling • Balances • Closing: • Fiori • Activities • Reporting © 2015 SAP SE or an SAP affiliate company. All rights reserved Summary You should now be able to: • Understand the possible starting points for migration • Give a brief overview of the migration process © 2015 SAP SE or an SAP affiliate company. All rights reserved  Unit 3: General Ledger Accounting © 2015 SAP SE or an SAP affiliate company. All rights reserved. Unit 3 – Agenda GL Accounts and Cost Elements in SAP Accounting powered by HANA Managing Ledgers in SAP Accounting powered by HANA © 2015 SAP SE or an SAP affiliate company. All rights reserved  GL Accounts & Cost Elements in SAP Accounting powered by HANA © 2015 SAP SE or an SAP affiliate company. All rights reserved. Learning Objective After completing this lesson, you will be able to:  Understand the new master data maintenance model  Explain the handling for Asset and Material accounts  Understand the impact on authorizations and the posting period lock © 2015 SAP SE or an SAP affiliate company. All rights reserved Scenario You have traditionally kept G/L Accounts separate to your Cost Elements. With the move to Simple Finance you will now only maintain G/L accounts, you want to understand how this works on the system architecture level and also how this might impact your processes for master data maintenance and other transactions. © 2015 SAP SE or an SAP affiliate company. All rights reserved Classic Data Model for the Master Data G/L Account and Cost Element Management Accounting Cost Elements Cost Elements Cost Elements (Chart of Account) (Controlling Area) (Description) CSKA CSKB CSKU MANDT MANDT MANDT KTOPL KOKRS SPRAS KSTAR KSTAR, DATBI KTOPL, KSTAR Financial G/L Account Master G/L Account Master G/L Account Master Accounting (Chart of Account) (Company Code) (Description) SKA1 SKB1 SKAT MANDT MANDT MANDT KTOPL BUKRS SPRAS, KTOPL SAKNR SAKNR SAKNR Creation of cost elements updates the tables CSK*. Creation of G/L accounts updates the tables SK*. For CO relevant external postings you need both master data records. © 2015 SAP SE or an SAP affiliate company. All rights reserved New Data Model for both Master Data in SAP Accounting SAP Accounting Cost Elements Cost Elements Cost Elements (Chart of Account) (Controlling Area) (Description) CSKA CSKB CSKU Fields: Fields: Fields: MANDT MANDT MANDT KTOPL KOKRS SPRAS KSTAR KSTAR, DATBI KTOPL, KSTAR G/L Account Master G/L Account Master G/L Account Master (Chart of Account) (Company Code) (Description) SKA1 SKB1 SKAT Fields: Fields: Fields: MANDT MANDT MANDT KTOPL, SAKNR BUKRS SPRAS, KTOPL NEW FIELD GLACCOUNT_TYPE SAKNR SAKNR Only one master data record is required: the G/L account. G/L accounts from type ‘Secondary Costs or Revenues’ update all CSK* and SK* tables! © 2015 SAP SE or an SAP affiliate company. All rights reserved Cost Element Categories for G/L Accounts from Type ‘Primary Costs or Revenue’ The cost element category specifies which transactions can use this cost element. © 2015 SAP SE or an SAP affiliate company. All rights reserved Cost Element Categories for G/L Accounts from Type ‘Secondary Costs’ Accounts of type ‘Secondary Costs’ can be used only for internal CO allocations. © 2015 SAP SE or an SAP affiliate company. All rights reserved Cost Element Category 90 for Balance Sheet Accounts in Financial Accounting “Statistical” cost elements of category 90 are created automatically when: 1) You create a Balance Sheet G/L Account. 2) The Account Group is one used for fixed asset or material accounts. 3) The account is a reconciliation account for assets or material. 4) The accounts have been setup in the Asset or Material management account assignment. 5) You select the checkbox “Apply Acct Assignments Statistically in Fixed Asset Acct / Material Acct”. © 2015 SAP SE or an SAP affiliate company. All rights reserved Account Determination for Asset and Material Accounts  You add the account in the Asset account assignment in the field “Bal. sheet account: Acquisition and production costs” (T095-KTANSW).  For a material account you can check, if this account is defined as a material account in Customizing under Configure Automatic Postings. Choose Goto  Account Assignment. Here you choose the line ‘Inventory posting’. On the next screen there should be an entry for your account for the relevant valuation modifier and valuation class. © 2015 SAP SE or an SAP affiliate company. All rights reserved Impact on Default Account Assignment In SAP Accounting a default account assignment can be defined only using transaction OKB9 or through substitution rules. Default account assignments maintained in former cost element master data are migrated to transaction OKB9 as part of the migration process. © 2015 SAP SE or an SAP affiliate company. All rights reserved Impact on Authorizations The merge of cost elements and G/L accounts requires adjustments to authorizations for creating cost elements:  If you want to maintain accounts of the account type Primary Costs or Revenue, you need to have authorization to create or change cost element master data.  If you want to maintain accounts of the account type Secondary Costs, you need to have authorization to create or change G/L accounts. To check or change the authorizations, use transaction PFCG. The standard delivered SAP Role is: FUCN_GL_ACCOUNTANT (G/L Accountant) The relevant authorizations are:  Controlling, CO-CCA: Cost Element Master (K_CSKB)  Financial Accounting, G/L Account: Change Authorization for Certain Fields (F_SKA1_AEN)  Financial Accounting, G/L Account: Account Authorization (F_SKA1_BES)  Financial Accounting, G/L Account: Authorization for Company Codes (F_SKA1_BUK)  Financial Accounting, G/L Account: Authorization for Charts of Accounts (F_SKA1_KTP) © 2015 SAP SE or an SAP affiliate company. All rights reserved Effect on Period Lock In SAP Accounting CO relevant postings do not check only the CO Period Lock as in the past but as well the GL period opening/closing. Therefore you have to allow postings to accounts from account type ‘Secondary Costs‘ in the GL period opening/closing. Period Lock FI Period Lock CO in SAP Menu Financial Accounting in SAP Menu Controlling © 2015 SAP SE or an SAP affiliate company. All rights reserved Period Lock in CO In CO you need to specify which transactions you want to lock, and for which periods. Example: you lock periods 1 and 2 against actual overhead assessment postings. All other postings in this periods are allowed! © 2015 SAP SE or an SAP affiliate company. All rights reserved Period Lock in FI In FI you need to specify which accounts for a specified account type you want to allow for postings, and for which periods and fiscal years. Example: you allow postings for all G/L accounts (account type S) for a specified timeframe. All other postings (other accounts or periods) are not allowed! In SAP Accounting it is also necessary to open accounts from account type Secondary Costs for FI postings. © 2015 SAP SE or an SAP affiliate company. All rights reserved Fiori Application for Period Lock In the Fiori application you can in addition lock the period per ledger, especially useful for working with appendix ledgers. A single unified maintenance should be available in the future. © 2015 SAP SE or an SAP affiliate company. All rights reserved Demos & Exercises Activity Name Page DEMO 2 HOW TO CREATE A PRIMARY COST ACCOUNT EX-55 EXERCISE 5 CREATE A SECONDARY COST ACCOUNT EX-63 DEMO 3 HOW TO CREATE AN ASSET ACCOUNT AS A EX-69 STATISTICAL COST ELEMENT EXERCISE 6 CREATE A DEFAULT ACCOUNT ASSIGNMENT EX-75 DEMO 4 HOW TO USE THE PERIOD LOCK EX-81 TRANSACTIONS © 2015 SAP SE or an SAP affiliate company. All rights reserved Summary You should now able to:  Understand the new master data maintenance model  Explain the handling for Asset and Material accounts  Understand the impact on the posting period lock © 2015 SAP SE or an SAP affiliate company. All rights reserved Unit 3 – Agenda GL Accounts and Cost Elements in SAP Accounting powered by HANA Managing Ledgers in SAP Accounting powered by HANA © 2015 SAP SE or an SAP affiliate company. All rights reserved  Managing Ledgers in SAP Accounting powered by HANA © 2015 SAP SE or an SAP affiliate company. All rights reserved. Learning Objective After completing this lesson, you will be able to:  Understand the enhancement to Ledgers with the Universal Journal  Configure Ledgers in SAP Simple Finance © 2015 SAP SE or an SAP affiliate company. All rights reserved Scenario You manage multiple parallel accounting principles in your system and need to be able to report on each separately. You also are afraid that with the universal journal, the previously independent components lose some of their flexibility being bound by the legal restrictions of financial accounting. You want to understand the Ledger capabilities with SAP Simple Finance and be able to configure ledgers to meet your needs. © 2015 SAP SE or an SAP affiliate company. All rights reserved The Universal Journal enforces discipline G/L “Periods cannot be open and closed at the same time” How can we offer “I have to close the fiscal period” flexibility in our solution Universal Journal without reintroducing a reconciliation issue? CO “I have to close the fiscal period” “I want to post despite closed periods in G/L” © 2015 SAP SE or an SAP affiliate company. All rights reserved Requirement: Unified and flexible solution  “On top” - usually manual postings. Extension e.g. for specific  Report on extension always includes the management adjustments embedded “Standard” to provide the full or realignments picture  Less strict rules (e.g. different period lock) “Appendix”  Use of standard FI/CO UI’s and reports.  “Appendix” authorization needed . Unified FI and CO  “Regular” universal journal entries (e.g. according to serving FI, CO, AA, ML, with e.g. IFRS IFRS) valuation.  Posting of consistent standard “Standard” (”Base”) processes.  Strict standard rules (e.g. standard period lock) have to be obeyed Several extensions possible to one “base”: More flexibility than previously through FI and CO separation © 2015 SAP SE or an SAP affiliate company. All rights reserved Appendix Ledger – Basic Idea Each specific ledger is self contained, has a special purpose and provides a specific view on financial data. A ledger usually stores a lot of redundant data to other ledgers. With Appendix Ledgers you can “staple” ledgers on top of each other, providing the different views you need. This minimizes the data footprint and provides new flexibility for easily creating additional views. © 2015 SAP SE or an SAP affiliate company. All rights reserved Appendix Ledger – Use Cases Universal Journal  An appendix ledger stores delta values and points to another ledger – thus providing a flexible mechanism for adjustments and reporting. Appendix Ledger A Appendix Ledger B  An important use case is for management views “Post into closed periods “Distribute revenues on top of legal data. differently on org units for restatement purposes” than in legal view”  Besides creating a master record, appendix ledgers Appendix Ledger need no additional configuration. C  Reporting on the appendix ledger always includes the “Adjustments for consolidation data of the base ledger (in the figure: IFRS ledger). purposes”  Multiple appendix ledgers can point to the same base ledger.  Benefit of reduced data footprint and zero reconciliation effort as only delta values are kept.  Appendix ledgers are stored in the universal journal – Ledger IFRS same as “normal” ledgers. Ledger Local GAAP © 2015 SAP SE or an SAP affiliate company. All rights reserved Technical implementation of the read access Persistence View for Data Selection The transaction data is “mapped” to the corresponding Ledger © 2015 SAP SE or an SAP affiliate company. All rights reserved Postings into the Appendix Ledger  ACDOCA stores the data for all ACDOCA appendix ledgers.  BSEG does not store any appendix ledger data. CO:  Implementing the BADI KB11N BADI_FINS_APPL_RELEVANCE allows to feed components like PCA PCA, FI-SL, EC-CS with the data posted to appendix ledgers. This RWIN functionality should be handled with care. It is up to the implementation FI: in the BADI to clearly separate FB01L appendix ledger data from the other data. FI-SL © 2015 SAP SE or an SAP affiliate company. All rights reserved The new and the old Ledger master  The Universal Journal ledgers have own master records  The new master record key FINSC_LEDGER-RLDNR is technically compatible with the FI-SL/New G/L ledger key (T881-RLDNR)  The FI-SL technology is used in a lot of components (FI-SL, EC-PCA, New G/L, Public Sector etc.).  Parts of this technology has been enabled for the Universal Journal ledgers. Both “worlds” can be mapped e.g. via the function modules G_GET_LEDGER_INFO and G_GET_ORGANIZATIONAL_DATA. The modules have a compatibility mode that might help customers to leverage their own code for Universal Journal ledgers. © 2015 SAP SE or an SAP affiliate company. All rights reserved Document Summarization  BSEG summarization works and BSEG can be used as usual. BSEG is MM used for storing open item and Document clearing details, thus you can be Summarization quite aggressive with the summarization.  ACDOCA stores the full detail that SD is needed for all components that Accounting base on ACDOCA (G/L, AA, ML, Interface CO, PA).  Summarizing BSEG “aggressively” will bring relief with respect to the HR 999 line item limitation (BSEG- BELNR has only 3 digits). This can be done, since ACDOCA stores the full detail and ACDOCA has a 6 digit ACDOCA field for line item numbering. … © 2015 SAP SE or an SAP affiliate company. All rights reserved Master Data Maintenance for Ledgers Transaction: FINSC_LEDGER First Level: Master Data of Ledger  Define the Leading Ledger  Define additional Ledgers, Standard or Appendix  Set a Ledger as Base Ledger only for the Appendix Ledgers © 2015 SAP SE or an SAP affiliate company. All rights reserved Company Code Assignment to Ledgers Second Level  Company Code Assignment to Ledger  For the Leading Ledger: – All Company Codes are assigned. – Company Code Assignments for Leading Ledgers are defaulted in the view maintenance. Do not forget to save the defaulted entries. © 2015 SAP SE or an SAP affiliate company. All rights reserved Company Code Settings for Ledgers Second Level – Detail Screen – Currency Settings  Local Currency – ACDOCA-Field HSL – All settings are fix  Global Currency for GL & CO – ACDOCA Field KSL – Curr. type of controlling area – Special case: only rel. In CO Curr. type not used in FI  1st additional Currency – ACDOCA Field OSL – Leading Ledger defines settings – Non-Leading Ledgers inherit settings  2nd additional Currency – ACDOCA Field VSL – Only available in the special case you saved the object currency in CO. © 2015 SAP SE or an SAP affiliate company. All rights reserved Additional Company Code Settings for Ledgers Second Level – Detail Screen – Other Company Code Settings  Fiscal Year Variant – In the leading ledger is inherited from the controlling area setting – Non leading ledgers may have deviating fiscal year variants  Posting Period Variant – Defines open periods – Basis for check of leading ledger / representative ledger in ledger group  Parallel Accounting using G/L Accounts – Flag switches off the check, that Ledger / Company is assigned to max. one Accounting Principle © 2015 SAP SE or an SAP affiliate company. All rights reserved Assignment of Accounting Principle to Ledgers per Company Code Third Level  Assignment of Accounting Principle to Ledger / Company Code  By default you assign one Accounting Principle per Ledger / Company, unless you use Parallel Accounting with the GL Account Approach. © 2015 SAP SE or an SAP affiliate company. All rights reserved General Ledger Technical Changes compared to new GL  Data previously stored in FAGLFLEXA, FAGLFLEXT FAGLFLEXA (carry forward) is now stored in table ACDOCA.  Data of New G/L industry tables for Public Sector and Joint Venture Accounting ( FMGLFLEXA/T, FAGLFLEXT PSGLFLEXA/T, JVGLFLEXA/T) is now stored in table ACDOCA.  Data of customer created New G/L tables ZZ<CUST>T, ZZ<CUST>T ZZ<CUST>A is now stored in table ACDOCA.  A compatibility view is provided for table FAGLFLEXA: ACDOCA FGLV_FAGLFLEXA. This compatibility view redirects ZZ<CUST>A select statements to FAGLFLEXA to ACDOCA.  Compatibility views for the New G/L industry tables are provided: V_<Industry>A, V_<Industry>T <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 <Industry>A items), where x is a number. © 2015 SAP SE or an SAP affiliate company. All rights reserved Demos & Exercises Activity Name Page DEMO 2 POST SECONDARY COST TO FINANCIAL EX-91 ACCOUNTING EXERCISE 5 CREATE AN APPENDIX LEDGER AND POST A EX-105 DOCUMENT TO IT © 2015 SAP SE or an SAP affiliate company. All rights reserved Summary You should now able to:  Understand the enhancement to Ledgers with the Universal Journal  Configure Ledgers in SAP Simple Finance © 2015 SAP SE or an SAP affiliate company. All rights reserved  Unit 4: Asset Accounting © 2015 SAP SE or an SAP affiliate company. All rights reserved. Unit 4 – Agenda Providing an Overview of new Asset Accounting Functions Analyzing the Posting Logic of new Asset Accounting Configuring new Asset Accounting © 2015 SAP SE or an SAP affiliate company. All rights reserved  Providing an Overview of new Asset Accounting Functions © 2015 SAP SE or an SAP affiliate company. All rights reserved. Learning Objective After completing this lesson, you will be able to:  Outline the features of new Asset Accounting in SAP Accounting powered by SAP HANA © 2015 SAP SE or an SAP affiliate company. All rights reserved Scenario You want to find out more about new asset accounting to understand if there are benefits beyond the fact that it is a requirement for the SAP Simple Finance On- Premise Edition. © 2015 SAP SE or an SAP affiliate company. All rights reserved New Asset Accounting and SAP Accounting on HANA  New Asset Accounting is the only Asset Accounting solution in SAP Accounting on HANA, classic Asset Accounting is not available any more  Configuration and activation is on the client level.  Both multiple valuation approaches are possible: Ledger Approach and Account Approach  Usage of the new Depreciation Calculation Engine is mandatory (based of extension EA- FIN) © 2015 SAP SE or an SAP affiliate company. All rights reserved Technical Changes to the Tables Actual items  Actual data of ANEK, ANEP, ANEA, ANEK ANLP, ANLC is now stored in table ACDOCA. ANEK data is stored in BKPF.  Compatibility views ANEP FAAV_<TABLENAME> (e.g. BKPF FAAV_ANEK) are provided to enable non-disruptive reporting on old tables ANEA  After migration: access to content of old ACDOCA tables is still possible via views FAAV_<tablename>_ORI. ANLP Non actual items:  Statistical data (for example calculation for tax purposes) are now stored in table ANLC FAAT_DOC_IT FAAT_DOC_IT.  Plan data (previously ANLP and ANLC) FAAT_PLAN_VALUES are now stored in FAAT_PLAN_VALUES  Year-dependent attributes of Fixed FAAT_YDDA Assets are now stored in FAAT_YDDA. © 2015 SAP SE or an SAP affiliate company. All rights reserved Benefits from the Universal Journal integration Fixed Asset Accounting based on Universal Journal:  No redundancy in data storage  Reconciliation between G/L and AA is ensured by design – No reconciliation-step in financial close needed anymore. – All non-statistical items are updated as Universal Journal Entries.  Even after migration, reporting for previous fiscal years is possible due to compatibility views.  Transparent assignment of depreciation area to accounting principle  Depreciation posted with all details: Accumulated depreciation and depreciation cost by asset © 2015 SAP SE or an SAP affiliate company. All rights reserved Benefits from Posting Logic Simplification Auditability and simplicity:  Independent and complete depreciation areas of equal power – Simplified Chart of Deprecation: Only one depreciation area per valuation necessary – no further depreciation areas (Delta areas) necessary to portray a parallel valuation  New document display: explain the detailed impact of any transaction to the books  New transactions for ledger group (depreciation area) specific documents  Flexible account determination © 2015 SAP SE or an SAP affiliate company. All rights reserved Benefits from Changed Closing Processes Simple close, fast close, soft close: Transparency throughout the period  Asset balances in real time - APC posting run not needed anymore  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 possible (restriction: beginning/end of FY needs to be equal) © 2015 SAP SE or an SAP affiliate company. All rights reserved Out of Scope for new Asset Accounting The new architecture prerequisites are  Usage of the New Depreciation Calculation Engine is mandatory The new architecture does not support the following feature (and vice-versa)  Joint Venture Accounting (JVA) (officially released for ledger-solution via Business Function as of EhP6) (1)  Lease Accounting Engine (LAE)  Real Estate Classic (RE Classic)  Public Sector Management – Funds Management (PSM-FM) using requests (2)  Application Link Enabling (ALE): transfer of assets  Transaction “Post transfer between depreciation areas” (ABUB) (1) Will be investigated to be supported in a future support package (2) A check is necessary to see if new Asset Accounting can be used with installed industry components © 2015 SAP SE or an SAP affiliate company. All rights reserved Demos & Exercises Activity Name Page EXERCISE 9 CREATE ASSETS EX-112 © 2015 SAP SE or an SAP affiliate company. All rights reserved Summary You should now be able to:  Outline the features of new Asset Accounting in SAP Accounting powered by SAP HANA © 2015 SAP SE or an SAP affiliate company. All rights reserved Unit 4 – Agenda Providing an Overview of new Asset Accounting Functions Analyzing the Posting Logic of new Asset Accounting Configuring new Asset Accounting © 2015 SAP SE or an SAP affiliate company. All rights reserved  Analyzing the Posting Logic of new Asset Accounting © 2015 SAP SE or an SAP affiliate company. All rights reserved. Learning Objective After completing this lesson, you will be able to:  Understand the posting logic in new Asset Accounting © 2015 SAP SE or an SAP affiliate company. All rights reserved Scenario You want to understand the changes implementing new Asset Accounting brings for your end-users. You want to understand the posting logic with new Asset Accounting to be able to explain and use it. © 2015 SAP SE or an SAP affiliate company. All rights reserved Posting Logic in new Asset Accounting Universal Journal The system generates several documents:  The Operational Entry Document posts to a technical clearing account. The Operational Entry Document does not update the asset values, the asset data is only used to perform checks.  Accounting principle specific documents (1 to n). The accounting principle specific documents post to: – the technical clearing account in each view (balancing to zero) – the asset reconciliation account (and update the asset line items) © 2015 SAP SE or an SAP affiliate company. All rights reserved Sample Posting – Ledger Approach Both depreciation areas 01 and 30 will be posted to in real-time * * Screenshot is a combination of two simulated entries Result: 3 documents (Technical Clearing Account Acquisition = TCA)  TCA to Vendor (Ledger group blank and Account. principle blank)  Asset to TCA (Ledger group 0L and Account. principle IFRS)  Asset to TCA (Ledger group N1 and Account. principle LOCA) © 2015 SAP SE or an SAP affiliate company. All rights reserved Sample Posting – Account Approach Both depreciation areas 01 and 30 will be posted to in real-time * * Screenshot is a combination of two simulated entries Result: 3 documents (Technical Clearing Account Acquisition = TCA)  TCA to Vendor (Ledger group blank and Account. principle blank)  Asset to TCA (Ledger group 0L and Account. principle INT)  Asset to TCA (Ledger group LO and Account. principle LOC) © 2015 SAP SE or an SAP affiliate company. All rights reserved Example: Integrated Acquisition with different amounts per Accounting Principle Asset Reconcilation. IFRS AP Reconcilation Tech.Clear.Acc.Acqu. Freight expenses 1) 10.200 1) 10.200 2a) 10.200 2a) 10.200 Asset Reconcilation LGAAP 1) 10.200 1) 10.200 2b) 10.200 2b) 10.200 3) 200 3) 200 Transaction vendor invoice 1) “Technical Clearing Account Acquisition to Vendor” ledger group and accounting principles Blank 2a)“Asset to Technical Clearing Account Acquisition” ledger group and accounting principle IFRS 2b)“Asset to Technical Clearing Account Acquisition” ledger group and accounting principles LGAAP Transaction correction freight cost 3) “Freight expenses to Asset” ledger group LGAAP © 2015 SAP SE or an SAP affiliate company. All rights reserved Additional Information on Integrated Posting  The technical account always balances to zero.  The operational entry document will be posted by the entered document type, the rest can be posted under a different document type (for example AA)  Accounting Principle specific documents will always be created  Using different reconciliation account per accounting principle is possible  Technical clearing account will be always posted, even if a certain accounting principle is not represented on the asset*. * There is a small difference between ledger and account solution. The account “Contra account: Acquisition value posting” assigned in the account determination will be posted to instead of the Technical Clearing Account for secondary depreciation areas in the accounts approach. © 2015 SAP SE or an SAP affiliate company. All rights reserved Assets activated for specific accounting principles Behavior during integrated asset acquisitions after deactivation of non-required depreciation areas: The screenshot is a combination of two simulated entries © 2015 SAP SE or an SAP affiliate company. All rights reserved Assets activated in only some accounting principles e.g. in-house developed software  Only relevant accounting principles need to be represented on the asset (or on the asset class) by their corresponding depreciation areas  All postings issued within FIAA will only affect those accounting principles which are relevant for the involved asset(s).  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 will be re-directed to “Account for non-operating expense“ (field T095-KTNAIB)  If no accounting principle is represented on the asset by an area which posts APC online to GL, the system issues an error. This error message can be changed into a warning, in which case the statistical areas in FI-AA are updated. © 2015 SAP SE or an SAP affiliate company. All rights reserved New Settlement for Assets under Construction  It is possible to assign the settlement rule for each line per depreciation area posting to the general ledger (transaction AIAB).  Accounting principle specific postings are generated from Controlling as well. © 2015 SAP SE or an SAP affiliate company. All rights reserved New and obsolete programs for FI-AA Changes after installation of SAP Simple Finance On-Premise Edition 1503:  Periodic APC postings: – RAPERBxxxx – obsolete and deleted  Reconciliation postings: – RAABSTxxxx – obsolete and deleted  Post depreciation – RAPOSTxxxx is replaced by program FAA_DEPRECIATION_POST © 2015 SAP SE or an SAP affiliate company. All rights reserved Calculating and Posting Depreciations The determination of the depreciation values of an asset and the posting of depreciation expense takes place in the system asynchronously: 1. Calculate depreciation:  The planned depreciation is determined with each master record change and with each posting on the asset and updated in the database directly. 2. Post depreciation:  The depreciation run adopts the planned asset values and posts them in Financial Accounting. © 2015 SAP SE or an SAP affiliate company. All rights reserved New Depreciation Run How does the depreciation run work?  Planned depreciation is determined and updated with each asset master record change and each posting to the asset. No longer  The depreciation run posts the pre-calculated planned relevant values.  The journal entry is updated in financials on the asset level.  Period end closing can be performed even if there are errors on individual assets.  A test run can be performed but still with the restriction for 1000 assets.  The Selection screen is simplified as the “reasons for posting run” (planned depreciation run, repeat, restart, unplanned posting run) are no longer relevant. Simplified Selections  . © 2015 SAP SE or an SAP affiliate company. All rights reserved Further Topics Year end closing:  There is no separate balance carry forward needed in asset accounting, the general balance carry forward transaction of FI transfers asset accounting balances by default.  The most current planned depreciation values will be calculated automatically for the new year after performing the balance carry forward. Resetting data (test data):  Resetting data in asset accounting should only be performed in case all Accounting data will also be reset. © 2015 SAP SE or an SAP affiliate company. All rights reserved Demos & Exercises Activity Name Page EXERCISE 9 CREATE ASSETS EX-112 EXERCISE 10 POST INTEGRATED ASSET ACQUISITIONS 118 EXERCISE 11 POST A PARTIAL SCRAPPING TO AN ASSET 133 DEMO 5 EXECUTE A DEPRECIATION POSTING RUN AND 139 ANALYZE THE LOG EXERCISE 12 MANAGE DEPRECIATION RUNS 147 © 2015 SAP SE or an SAP affiliate company. All rights reserved Summary You should now be able to:  Understand the posting logic in new Asset Accounting  Explain Period-End process © 2015 SAP SE or an SAP affiliate company. All rights reserved Unit 4 – Agenda Providing an Overview of new Asset Accounting Functions Analyzing the Posting Logic of new Asset Accounting Configuring new Asset Accounting © 2015 SAP SE or an SAP affiliate company. All rights reserved  Configuring new Asset Accounting © 2015 SAP SE or an SAP affiliate company. All rights reserved. Learning Objective After completing this lesson, you will be able to:  Understand the customizing of New Asset Accounting  Perform the customizing for New Asset Accounting © 2015 SAP SE or an SAP affiliate company. All rights reserved Scenario Asset Accounting (new) has to be configured in your system with Simple Finance On-Premise Edition 1503. You need to be able to understand and execute the additional and changed customizing steps in new Asset Accounting. © 2015 SAP SE or an SAP affiliate company. All rights reserved Required Customizing for New Asset Accounting The following customizing steps and checks are required:  Check and create accounting principles and ledger groups.  Assign accounting principles to ledger groups for both approaches: – Ledger Approach – Account Approach  For every additional currency type defined on the company code a corresponding depreciation area needs to be set up.  Account approach: Define Asset Balance Sheet Accounts of Parallel Valuation as Reconciliation Accounts.  Define account “technical clearing account” for integrated asset acquisition. © 2015 SAP SE or an SAP affiliate company. All rights reserved Optional Customizing for New Asset Accounting The following customizing steps and checks are required:  Quantity update: define depreciation area.  Integrated transactions: specify alternative document type for ledger postings.  Choose between revenue distribution for retirement by APC or net book value.  Post net book value instead of Gain/Loss during retirement.  Make any Transaction Types that post to specific depreciation areas obsolete. © 2015 SAP SE or an SAP affiliate company. All rights reserved New Asset Accounting in Preparation Status for New Asset Accounting has to be “In Preparation” IMG: Asset Accounting (New) -> Migration Asset Accounting (New) -> Activate Asset Accounting (New) © 2015 SAP SE or an SAP affiliate company. All rights reserved Chart of Depreciation All depreciation areas representing the same accounting principle will be assigned to the same accounting principle (and ledger group): © 2015 SAP SE or an SAP affiliate company. All rights reserved Explanation of the Parallel Valuation Approaches Companies often reports the following accounting regulations:  International GAAP  Local GAAP  Tax GAAP There are different objects to indicate these requirements:  Valuation areas (FI) are used for: – Closing activities like Foreign Currency Valuation, Sorting/Reclassification (New) or Further Valuations  Accounting Principles are used for: – The New Asset Accounting to combine different depreciation areas to a accounting principle – Accrual Engine  Ledger Groups are used for: – Manual postings in FI (e.g. FB50L Enter G/L Account Document for Ledger Group) – Manual postings in CO (e.g. KB11N Manual Reposting of Costs) © 2015 SAP SE or an SAP affiliate company. All rights reserved Explanation per Approach to Parallel Valuation  Account Approach:  Ledger Approach:  All objects are linked via customizing. Combinations of n ledgers to one ledger group is possible, e.g. to post IFRS and US-GAAP together © 2015 SAP SE or an SAP affiliate company. All rights reserved Depreciation area assigned settings  You have to assign an accounting principle to each depreciation area, even to non-posting depreciation areas or to delta depreciation areas that are only for reporting. (The accounting principle is not allowed to be initial (blank).)  You can assign the same accounting principle to several depreciation areas, as long as the areas represent the same valuation.  For every additional currency type defined on the company code level, a corresponding depreciation area needs to be configured. © 2015 SAP SE or an SAP affiliate company. All rights reserved GL Update Settings for Depreciation Areas With Asset Accounting (New), the Posting Indicator supports five (4) different values. For the depreciation areas the Posting Indicator need to be adjusted.  The leading area of the leading valuation always contains the Area Posts in Realtime option.  The following applies to the ledger approach: The leading area of the parallel valuation also contains the Area Posts in Realtime option.  The following applies for the accounts approach: The leading area of the parallel valuation receives the option Area Posts APC Immediately, Depreciation Periodically (or Area Posts APC and Depreciation Periodically). © 2015 SAP SE or an SAP affiliate company. All rights reserved Adapt value take over and parameter take over Value take over can only be done within a set of depreciation areas which are assigned to the same accounting principle. Leading areas need to be set to 00. © 2015 SAP SE or an SAP affiliate company. All rights reserved Reconciliation Accounts (only for Account Approach) There is a program to automatically switch all accounts of parallel valuations to reconciliation accounts: © 2015 SAP SE or an SAP affiliate company. All rights reserved New account technical clearing account for integrated asset acquisition Characteristics of the new account “technical clearing account for integrated asset acquisition” as balance sheet account: Balance behavior:  Ledger Approach: Always balances to zero per ledger group and account assignment.  Account Approach: Always balances to zero together with the account “Contra account: Acquisition value posting” in your financial statement. Is defined as a reconciliation account, but not managed on line items. Different “technical clearing account for asset acquisition” for specific account determination are possible, e.g. to set different field status like for the text field. © 2015 SAP SE or an SAP affiliate company. All rights reserved Quantity Update Define depreciation area for quantity update:  In the asset master data the quantity will only be updated in case a posting is performed to the depreciation area  In case this IMG activity is not manually maintained, the system will by default update the quantity when a posting is made to depreciation area “01” © 2015 SAP SE or an SAP affiliate company. All rights reserved Document types for integrated transactions It is possible to indicate a different document type to be used by the system for the automatically generated accounting principle specific documents in asset accounting on the client level (use of document split can be a reason or external number ranges for FI-documents used by logistics invoice verification. or on the company code level: © 2015 SAP SE or an SAP affiliate company. All rights reserved Revenue distribution for retirement by APC or net book value for mass retirement  In this step, you specify at company code level how the system is to distribute revenues arising from asset retirements: either based on the net book value or on APC. In the standard system, the distribution is based on the net book value.  Check the distribution of revenue for your company codes, and adjust the distribution to meet your requirements.  Customizing Menu Path: IMG: Asset Accounting (New) -> Transactions -> Retirements -> Gain/Loss Posting -> Define Revenue Distribution for Fixed Asset Retirement © 2015 SAP SE or an SAP affiliate company. All rights reserved Post net book value instead of Gain/Loss  In this step you specify that you want the system to post the net book value of an asset being retired to the account "Clearing of revenue from sale of assets" and "Clearing or revenue from internal sale". No profit/loss (from sale) or loss from asset retirement (after scrapping) is then posted.  Post Net book value (e.g. legal requirement in France – French Retirement): IMG: Asset Accounting (New) -> Transactions -> Retirements -> Gain/Loss Posting -> Post Net Book Value Instead of Gain/Loss  The restriction of the posting logic to certain depreciation areas was done in classic Asset Accounting using area types. © 2015 SAP SE or an SAP affiliate company. All rights reserved Check Transaction Types  In new Asset Accounting, it is not possible and also not necessary to restrict transaction types to depreciation areas. You restrict posting to a depreciation area or accounting principle directly in the posting transaction.  If you were using transaction types that were restricted to certain depreciation areas, then you can no longer use these transaction types. Check whether your existing transaction types that are not restricted to depreciation areas are sufficient. Investment support and also revaluation and new valuation are an exception. Exceptions:  The transaction types for investment support and revaluation are automatically generated by the system when you create a corresponding measure, and therefore are restricted to the depreciation area to be posted to.  The transaction types for revaluation and new valuation that relate to transaction type group 81/82/89 can continue to be restricted to depreciation areas. © 2015 SAP SE or an SAP affiliate company. All rights reserved Marking Transaction Types as Obsolete  A task only required when migrating an existing system.  All transaction types, restricted to depreciation areas, should be set to obsolete.  Do not delete it. © 2015 SAP SE or an SAP affiliate company. All rights reserved Summary You should now able to:  Understand the customizing of New Asset Accounting  Perform the customizing for New Asset Accounting © 2015 SAP SE or an SAP affiliate company. All rights reserved  Unit 5: Management Accounting © 2015 SAP SE or an SAP affiliate company. All rights reserved. Unit 5 – Agenda Understanding the new Architecture of Management Accounting Understanding the Material Ledger and Cost of Goods Sold handling in SAP Simple Finance Explaining Profitability Analysis in SAP Simple Finance Outlining new Period Closing Programs for Management Accounting © 2015 SAP SE or an SAP affiliate company. All rights reserved  Understanding the new Architecture of Management Accounting © 2015 SAP SE or an SAP affiliate company. All rights reserved. Learning Objective After completing this lesson, you will be able to:  Understand the Architecture for Management Accounting  Perform customizing for Management Accounting © 2015 SAP SE or an SAP affiliate company. All rights reserved Scenario You want to understand how the Financial and Management Accounting harmonization works in SAP Simple Finance. You also need to understand what new customizing activities are required for the new architecture to work. © 2015 SAP SE or an SAP affiliate company. All rights reserved Controlling – Technical Changes with SAP Simple Finance Actual Items  Actual data of COEP (Value Types ‘04’ Actual and COBK ‘11’ statistical actual) is stored in ACDOCA  Required actual data for long running orders/projects from COSP_BAK, COSS_BAK is BKPF stored in table ACDOCA. COEP  Currently, the header table COBK is written as before. The target is to replace COBK through ACDOCA BKPF.  Compatibility views V_<TABLENAME> (e.g. COSP_BAK V_COEP) are provided in order to reproduce the old structures.  Access to data in the old tables is still possible via the views V_<TABLENAME>_ORI (e.g. COSS_BAK V_COEP_ORI) Non-actual items  Value types other than ‘04’ and ‘11’ are still stored in COEP, COSP_BAK, COSS_BAK © 2015 SAP SE or an SAP affiliate company. All rights reserved CO Compatibility Views Provide Non-Disruptiveness  In the figure, an example access to table COEP is redirected via the view V_COEP to the new Universal Journal Entry.  Any custom ABAP programs that read table COEP directly via select statements continue to run as before . © 2015 SAP SE or an SAP affiliate company. All rights reserved CO Postings without specifying ledger groups  ACDOCA is posted via the Accounting Interface similarly to FAGLFLEXA (New G/L) in the past. “ACDOCA” ACDOCA stores full detail.  Former COEP, FAGLFLEXA, ANEP, MLIT etc. data are stored in ACDOCA. “BSEG”  BSEG is only written in case open item managed accounts are affected (e.g. usually for cross company postings).  PCA, FI-SL work as before. Where the FI-SL PCA was posted via activity “COFI” (real time Accounting CO integration CO-FI), now secondary cost (G/L Interface accounts) are posted directly and there is no mapping to a primary cost element. FI-SL  EC-CS as before with New G/L real time integration, but now including secondary cost (G/L accounts). The system works directly with EC-CS the original CO activities like RKU1 instead of using the activity “COFI”.  Cost based CO-PA works as before (with the SAP HANA accelerators of course). Cost Based CO- PA © 2015 SAP SE or an SAP affiliate company. All rights reserved Document type and Ledger Groups in Controlling  With Simple Finance CO processes are enabled to post into ledger groups and you can also specify the document type.  On the UI this is enabled for KB11N, KB41N and KB15N. Other processes can be configured in the IMG to post with ledger groups. © 2015 SAP SE or an SAP affiliate company. All rights reserved CO Postings when specifying ledger groups  ACDOCA is posted in any case taking the respective ledgers into account. “ACDOCA”  BSEG is only written in case open item managed accounts are affected (e.g. for Filter: ledger group contains “leading ledger” cross company postings) and the ledger “BSEG” group contains the leading ledger.  Other components (PCA, FI-SL, Cost Based CO-PA, industry solutions like public sector and joint venture accounting PCA etc.) are only posted, if the ledger group Accounting CO contains the leading ledger. The BADI Interface BADI_FINS_APPL_RELEVANCE allows customers to overrule this behavior. FI-SL EC-CS Cost Based CO-PA © 2015 SAP SE or an SAP affiliate company. All rights reserved General Management Accounting Customizing  Align Fiscal Year Variants between controlling areas and the assigned company codes.  Define the document type for CO postings.  Define one or more Document Type Mapping Variants (pre-delivered: 000001) and assign these to the company codes.  Specify default ledger group – Ledger group is only for manual re-postings on the UI (KB11, KB41) – If no ledger group is entered in CO transactions the default ledger group is taken. – If no default ledger group is configured all ledgers are updated  Define Intercompany Clearing Accounts for CO cross company postings © 2015 SAP SE or an SAP affiliate company. All rights reserved Check and Adopt Fiscal Year Variants  The Fiscal Year Variants of all productive controlling areas and their assigned company have to be the same.  Example 1 FI: K4 Cal. Year, 4 Spec. Periods / CO: K1 Cal. Year, 1 Spec. Period  Example 2 FI and CO: both Cal. Year, 4 Special Periods, but different keys © 2015 SAP SE or an SAP affiliate company. All rights reserved Define Document Types for Postings in Controlling  This activity is the same one used in Financial Accounting to create document types. Controlling now uses document types when posting to FI as well. It is recommended to have a separate document type for Controlling postings with only the indicator “G/L account” set in the account type.  With the Simple Finance On-Premise Edition 1503 all Controlling business transactions use document types. © 2015 SAP SE or an SAP affiliate company. All rights reserved Define Document Type Mapping Variants for CO Business Transactions Assign the document type for postings in Controlling to a document type mapping variant. You should copy the provided sample to a customer specific entry. The entry will be created automatically in case you already use real-time integration in new G/L The document types can be specified on the following levels:  Company code via different document type mapping variants  Controlling business transactions (for example KAZI – “Actual cost center accrual” can have a separate document type  Normal postings and cross-company postings can have separate types per business transaction as well. © 2015 SAP SE or an SAP affiliate company. All rights reserved Ledger and CO – SAP Simple Finance Parallel actual versions are currently not supported:  Version 0 must be assigned to the leading ledger in all company codes assigned to the controlling area. Therefore CO reads from the leading ledger (reporting and allocations).  CO writes to the manually specified ledger group. In case no ledger group is entered and no default ledger group is set in customizing it is posted to all ledgers. Usually CO should write into Leading Ledger (because this is the source for reading). © 2015 SAP SE or an SAP affiliate company. All rights reserved Check and Define Default Values for Postings in Controlling  Default settings are necessary for postings where there is no possibility to manually define the document type and leger group in the Controlling business transaction.  The major question here is “which ledger should Controlling update” © 2015 SAP SE or an SAP affiliate company. All rights reserved Define Intercompany Clearing Accounts  Posting transfers between cost objects belonging to different company codes now update the Universal Journal and so you need to assign Clearing G/L accounts for the transaction and for each combination of Company Codes such postings occur. © 2015 SAP SE or an SAP affiliate company. All rights reserved Demos & Exercises Activity Name Page DEMO 6 HOW TO CHECK THE CONFIGURATION OF THE EX-150 INTEGRATION OF CO WITH FI © 2015 SAP SE or an SAP affiliate company. All rights reserved Summary You should now able to:  Understand the Architecture for Management Accounting  Perform customizing for Management Accounting © 2015 SAP SE or an SAP affiliate company. All rights reserved Unit 5 – Agenda Understanding the new Architecture of Management Accounting Understanding the Material Ledger and Cost of Goods Sold handling in SAP Simple Finance Explaining Profitability Analysis in SAP Simple Finance Outlining new Period Closing Programs for Management Accounting © 2015 SAP SE or an SAP affiliate company. All rights reserved  Understanding the Material Ledger and Cost of Goods Sold handling in SAP Simple Finance © 2015 SAP SE or an SAP affiliate company. All rights reserved. Learning Objective After completing this lesson, you will be able to:  Understand the scope and enhancements to the Material Ledger © 2015 SAP SE or an SAP affiliate company. All rights reserved Scenario You need to closely control your inventory balances in multiple currencies. You want to understand the Material Ledger solution integration and scope in SAP Simple Finance. © 2015 SAP SE or an SAP affiliate company. All rights reserved Inventory Accounting and the Universal Journal Actual Costing Material Ledger optional Revaluation of stock value Material Inventory with actual price (with real cost of goods receipt or cost of goods manufactured) Parallel Currencies Parallel Valuation Valuate with Transfer Prices historical exchange rates Company Legal ProfitCenter for multiple currencies  Classic Material Valuation provides balances per inventory account in company code currency – these values are now included in the universal journal.  The Material Ledger provides balances per inventory account in multiple currencies – these values are now included in the universal journal  Material Ledger also provides options to perform multilevel actual costing. This will be performed using a costing run as before (not in scope for the Universal Journal). © 2015 SAP SE or an SAP affiliate company. All rights reserved Technical Changes to the ML with SAP Simple Finance Usage of Material Ledger for parallel MLHD currencies and parallel valuation purpose MLIT  Contents of tables MLIT, MLPP, MLPPF, MLCR, MLCRF, MLCD, CKMI1, BSIM is now stored in ACDOCA. MLHD data is stored in BKPF MLPP  Compatibility views V_<TABLENAME> (e.g. V_MLIT) BKPF are provided in order to reproduce the old structures MLPPF  Access to old data in tables still possible via the views V_<TABLENAME>_ORI (e.g. V_MLIT_ORI) MLCR ACDOCA  MLHD, MLIT, MLPP, MLCR still keep prima nota MLCRF information, in case of manual price changes or material debit/credit. MLCD Usage of Material Ledger for Actual Costing purpose CKMI1  MLIT, MLIT, MLPP, MLPPF, MLCR, MLCRF, MLCD are used as before Simple Finance BSIM © 2015 SAP SE or an SAP affiliate company. All rights reserved Price Determinations in Material Ledger Multiple Valuations – Price Determination 2  Prices and Values shown in the Material Master are taken directly from the Universal Journal Multilevel Actual Costing – Price Determination 3  No Change – Costing Run Needed to Update Inventory Values at Period Close © 2015 SAP SE or an SAP affiliate company. All rights reserved Material Price Analysis Material Price Analysis (CKM3) is widely used to analyze all factors contributing to the cost of a material.  Material Price Analysis initially displays data from aggregated data sets (MLCD) and then drills down to the document level (MLIT, MLPP)  You can switch between valuations and currencies and navigate between periods in this view. In SAP Simple Finance this data is read directly from the universal journal. © 2015 SAP SE or an SAP affiliate company. All rights reserved Cost of Goods Sold Postings in SAP Accounting To provide more details in the income statement, a refinement of the posting mechanism for COGS is required to reflect the standard cost component split on the G/L account and to distinguish fixed and variable values: Income Statement Details - Costing Sales 2.400.000 Labor 150 COGS - Labor 800.000 External Labor 650 COGS - Material 700.000 Material fix 400 COGS - Overhead 300.000 Material variable 300 COGS overall 1.800.000 1000EA Overhead 200 Net Income Administration 100 … Total 1.800 © 2015 SAP SE or an SAP affiliate company. All rights reserved Prerequisites • Create GL accounts for COGS and detailed COGS (e.g. COGS material COGS labor etc.). • Set up account determination for material movements by specifying transaction keys BSX (to determine the inventory account) and GBB (to determine the COGS/inventory change account). • Set up customizing for the refinement of COGS. • Ensure that the costing run is executed and prices in the material master are up to date. © 2015 SAP SE or an SAP affiliate company. All rights reserved Refinement of COGS in SAP Accounting powered by SAP HANA – Customizing Steps • Create new G/L accounts on which you want to reflect the single cost components of the COGS posting. • Select your chart of accounts and enter every COGS account that should be refined. • Select the cost component structure and the cost component and assign it to a refinement GL account. One or more cost components can be assigned to one refinement account. • Tag one refinement account as the default account (flag ‚Default‘). Unassigned cost components are automatically posted to that default account. • Assign your splitting scheme to the relevant company code with a valid from date. © 2015 SAP SE or an SAP affiliate company. All rights reserved Account Determination Cost of Goods Sold (COGS) for I/S by Function and I/S by Nature Income Statement by Function Income Statement by Nature 894010 Changes in Inventory 893010 Cost of Goods Sold Depending on the income statement method used, the account for the debit line represents: • Changes in Inventory of Finished Goods for Income Statement by Nature • Costs of Goods Sold for Income Statement by Function © 2015 SAP SE or an SAP affiliate company. All rights reserved Refinement of COGS in SAP Accounting powered by SAP HANA SAP Accounting powered by SAP HANA provides an optional customizing activity to refine the COGS posting in GL and account-based CO-PA. The COGS amount is refined according to the cost component split. The fixed value of the COGS amount is stored in the corresponding value field in the CO line item table. The assignment of the customizing is time dependent. © 2015 SAP SE or an SAP affiliate company. All rights reserved Demos & Exercises Activity Name Page EXERCISE 13 PROCESS PURCHASE TO INVOICE (MATERIAL EX-156 LEDGER UPDATE) DEMO 7 HOW TO CHECK THE CUSTOMIZING FOR THE EX-178 COST OF GOODS SOLD SPLIT EXERCISE 14 POST AND ANALYZE THE COST OF GOODS EX-180 SOLD © 2015 SAP SE or an SAP affiliate company. All rights reserved Summary You should now able to:  Understand the scope and enhancements to the Material Ledger © 2015 SAP SE or an SAP affiliate company. All rights reserved Unit 5 – Agenda Understanding the new Architecture of Management Accounting Understanding the Material Ledger and Cost of Goods Sold handling in SAP Simple Finance Explaining Profitability Analysis in SAP Simple Finance Outlining new Period Closing Programs for Management Accounting © 2015 SAP SE or an SAP affiliate company. All rights reserved  Explaining Profitability Analysis in SAP Simple Finance © 2015 SAP SE or an SAP affiliate company. All rights reserved. Learning Objective After completing this lesson, you will be able to:  Understand the improvements to Profitability Analysis with SAP HANA  Understand the specific innovations for Account based Profitability Analysis with SAP Simple Finance © 2015 SAP SE or an SAP affiliate company. All rights reserved Scenario You need analysis of profitability on the market segment level and flexibility to define your own reporting characteristics. You are interested in understanding the scope of the Profitability Analysis component in SAP Simple Finance and what options you have for implementing it. © 2015 SAP SE or an SAP affiliate company. All rights reserved The Purpose of Profitability Analysis The business purpose of Profitability Analysis (CO-PA) is to provide the company with profitability-oriented information on the performance of its market segments or sales channels. This information is used to support corporate planning and decision-making, especially in the areas of sales and marketing. CO-PA allows you to define market segments and performance figures, with maximum flexibility in market evaluation.  The definition of a market is configured in the system by selecting the characteristics that are the subjects of analyses.  Performance figures may be based either on profit and loss accounts (Account Based CO-PA) or freely-defined value fields (Cost Based CO-PA). © 2015 SAP SE or an SAP affiliate company. All rights reserved Profitability Analysis with Simple Finance  Account-based CO-PA is the recommended approach.  Cost-based is fully supported but is not integrated in the Universal Journal.  You can use both approached in parallel, for ne customers you have to evaluate if there is a need for cost-based CO-PA.  For derivation of customer specific profitability attributes CO-PA offers advanced derivation functionality, this can be used for both types of CO-PA. For example: – Posting on cost center -> derives the product group through the CO-PA derivation tool. – Posting on Sales order item -> all Market segment information is already provided automatically. © 2015 SAP SE or an SAP affiliate company. All rights reserved HANA Acceleration of CO-PA – Report Execution In both types of CO-PA, you will see a great speed improvement in processing when comparing to a non-HANA DB system. CO-PA data quantity structure: Analyzed CO-PA drilldown reports:  85 Million line items  Sales margin analysis  33,000 customers  Cost allocation analysis  27,000 articles ERP without ERP with Acceleration SAP HANA SAP HANA factor (1) (2) (1)/(2) Sales margin analysis 280 sec 7 sec 40 – initial report (DB 2.8 sec) Sales margin analysis 620 sec 5 sec 124 – drilldown by cost center (DB 2.9 sec) Cost allocation analysis 45 sec 5 sec 9 – initial report (DB 3.4 sec) Cost allocation analysis 260 sec 7 sec 37 – drilldown by cost center (DB 3.3 sec) © 2015 SAP SE or an SAP affiliate company. All rights reserved HANA Acceleration of CO-PA – Process Execution The below example shows the processing time for an assessment run: Runtime with HANA Runtime without HANA © 2015 SAP SE or an SAP affiliate company. All rights reserved Real-time Account Based Profitability in Simple Finance  The Universal Journal as a single source of truth in Financials provides profitability attributes for every P&L line item.  The Operating Concern generation appends the CO-PA characteristics to the Universal Journal.  Profitability attributes are derived online  Profitability attributes can be enriched by further processes such as settlement or allocations Reconciled Profitability Reporting at any Time © 2015 SAP SE or an SAP affiliate company. All rights reserved Example – P&L for Legal and Management Reporting Legal Reporting Profitability Reporting on GL account or by Market Segment functional area © 2015 SAP SE or an SAP affiliate company. All rights reserved Refinement of COGS in SAP Accounting powered by SAP HANA – CO-PA Line Item The cost component structure of Cost of Goods Sold (COGS) will be posted in the Account Based Profitability Analysis and Financial Accounting as well. The values are stored on line item level in the universal journal table (ACDOCA) and the accounts are updated on the basis of total costs. The COGS with fixed and variable cost will continue to be posted in the Costing Based COPA on different value fields. The contribution margin can be calculated in the Costing Based COPA. © 2015 SAP SE or an SAP affiliate company. All rights reserved Demos & Exercises Activity Name Page DEMO 8 HOW TO CHECK THE CONFIGURATION OF THE EX-191 OPERATING CONCERN © 2015 SAP SE or an SAP affiliate company. All rights reserved Summary You should now able to:  Understand the improvements to Profitability Analysis with SAP HANA  Understand the specific innovations for Account based Profitability Analysis with SAP Simple Finance © 2015 SAP SE or an SAP affiliate company. All rights reserved Unit 5 – Agenda Understanding the new Architecture of Management Accounting Understanding the Material Ledger and Cost of Goods Sold handling in SAP Simple Finance Outlining new Period Closing Programs for Management Accounting Outlining new Period Closing Programs for Management Accounting © 2015 SAP SE or an SAP affiliate company. All rights reserved  Outlining new Period Closing Programs for Management Accounting © 2015 SAP SE or an SAP affiliate company. All rights reserved. Learning Objective After completing this lesson, you will be able to:  Understand the new Architecture of the Period Close Programs  Use the Period Close transactions © 2015 SAP SE or an SAP affiliate company. All rights reserved Scenario You currently have very long processing times for your Management Accounting period close activities, you want to understand if and how processing speed is improved with Simple Finance. © 2015 SAP SE or an SAP affiliate company. All rights reserved HANA Coding Options HANA views are used to select the relevant costs from the line item table HANA procedures are used to handle the calculation logic in the close transactions. HANA Views are used to ABAP application select costs ABAP application (calculation logic) from the line item tables rather than the totals tables HANA Procedure HANA Views HANA (Calculation logic) Procedures are used to handle complicated calculation logic Totals Line Item Line Item © 2015 SAP SE or an SAP affiliate company. All rights reserved Period Close Transactions Traditional approach 2. Selection of costs, 1. Selection of 3. Update results per status, configuration,… objects object sequentially per object Transactions: Settlement (CO88, VA88, KO8G, CJ8G), WIP at actual costs (KKAO), results analysis on sales orders (KKAK), variances with full settlement (KKS1), cost center variances (KSS1) HANA-optimized approach 1. Selection of objects, costs, status, and 2. Update results per configuration directly from database object New Transactions: Settlement (CO88H, VA88H, KO8GH, CJ8GH), WIP at actual costs (KKAOH), results analysis on sales orders (KKAKH), production variances (KKS1H), cost center variances (KSS1H) Results in performance Improvements between 10% and 60% (depending on volumes & configuration) © 2015 SAP SE or an SAP affiliate company. All rights reserved New Period Close Transactions in SAP Simple Finance  Results Analysis KKAK KKAKH  WIP Calculation at Actual Costs KKAO KKAOH  Variance Calculation (Production) KKS1 KKS1H  Variance Calculation (Cost Centers) KSS1 KSS1H  Settlement (plant selection) CO88 CO88H  Settlement (make-to-order sales orders) VA88 VA88H  Settlement (internal orders) KO8G KO8GH  Settlement (projects) CJ8G CJ8GH  Generate settlement rules (projects) CJB1 CJB1H © 2015 SAP SE or an SAP affiliate company. All rights reserved Results Analysis for Sales Orders (Transaction: KKAKH) As a cost accountant dealing with the need to account for long-term contracts in the balance sheet, you need to run results analysis to prepare the appropriate postings for each accounting period. Depending on local legislation and sometimes corporate guidelines, the degree of progress towards completion is measured based either on the revenue or the incurred costs. Severe performance issues can occur due to the volume of sales order items to be handled in each period.  In the first release, KKAKH supports two commonly used methods 01 revenue-based RA and 03 cost-based RA (out of 17 methods). Not supported:  Some expert methods  Customer enhancements;  Other 15 methods (Besides 01 and 03 methods);  Multiple result analysis versions  See SAP Note 1939621 for further details © 2015 SAP SE or an SAP affiliate company. All rights reserved WIP Calculation (Transaction: KKAOH) At period-end close, the production controller calculates the value of the work in process for the unfinished products. The number of production orders to be processed can result in long-running jobs.  KKAOH values production orders only, at actual cost for the selected plant with defined legal valuation for a single result analysis version. Not yet supported:  Customer enhancements;  WIP calculation for product cost collectors;  WIP calculation for process orders;  Multiple result analysis versions  See SAP Note 1939621 for further details © 2015 SAP SE or an SAP affiliate company. All rights reserved WIP Calculation: UI Differences between KKAO and KKAOH  The buttons “With Product Cost Collectors” “With Process Orders” and “All RA Versions” are suppressed.  Collective Processing is only valuated at actual cost with Production Order for selected plant by single version.  You can only choose “With Production Orders” and a single version in the screen. © 2015 SAP SE or an SAP affiliate company. All rights reserved Business Scope: Variance Calculation for Production Orders (Transaction: KKS1H) Cumulative variance calculation compares the target costs with the cumulative control costs.  The target costs are calculated by adjusting the standard costs for the actual quantity delivered.  The control costs are calculated by subtracting the work in process and the scrap variances from the actual costs. Currently product cost collectors, production orders and process orders are supported but only target version 0 is supported Refer to SAP Note 2027639 for details of further limitations © 2015 SAP SE or an SAP affiliate company. All rights reserved Business Scope: Variance Calculation for Cost Centers (Transaction KSS1H) Variance calculation for Cost Centers provides you with detailed cost information at the activity level. The variance calculation function does the following:  Shows the variance between target costs and control costs (the control costs can be the net actual costs, for example)  Determines the difference between the actual costs debited to the object and the credit from other controlling objects(total variance)  Show how the cost is split at the activity level  Categorize the variance into the different variance category The system updates the variances by object for each cost element, or for each cost element and origin. © 2015 SAP SE or an SAP affiliate company. All rights reserved Settlement Transactions Costs that arise from processing an order, or project (for example, costs for material, personnel or external services) are transferred to the settlement receiver specified in the settlement rule in the master record of the object. Both the selection statements for order and project settlement and for the generation of project settlement rules have been reworked to improve performance. With SAP Simple Finance, a mass settlement run can be executed in the foreground, where you used to only be able to perform background processing. Note that to use the new transactions (CO88H, VA88H, KO8GH, CJ8GH) you will need to create new selection variants that offer less selection options than the original selection variants. If the new variants do not meet your requirements, then you can of course continue to use the existing non-optimized transaction. © 2015 SAP SE or an SAP affiliate company. All rights reserved Demos & Exercises Activity Name Page DEMO 9 HOW TO CHECK THE CONFIGURATION FOR EX-196 SPLITTING PRICE DIFFERENCES EXERCISE 15 POST PRICE DIFFERENCE – VARIANCE EX-198 CATEGORIES OF PRODUCTION ORDER © 2015 SAP SE or an SAP affiliate company. All rights reserved Summary You should now able to:  Understand the new Architecture of the Period Close Programs  Use the Period Close transactions © 2015 SAP SE or an SAP affiliate company. All rights reserved  Unit 6: Further Simple Finance Integration © 2015 SAP SE or an SAP affiliate company. All rights reserved. Unit 6 – Agenda Outlining the Functions of SAP Cash Management powered by SAP HANA Outlining the Functions of Integrated Business Planning for Finance (IBPF) © 2015 SAP SE or an SAP affiliate company. All rights reserved  Outlining the Functions of SAP Cash Management powered by SAP HANA © 2015 SAP SE or an SAP affiliate company. All rights reserved. Learning Objective After completing this lesson, you will be able to:  Understand the position of SAP Cash Management powered by SAP HANA in the overall Treasury solution map of SAP  Understand the main functions and business values of this product  Understand the main features of Cash Operations  Understand the main features of Bank Account Management  Understand the main features of Liquidity Management © 2015 SAP SE or an SAP affiliate company. All rights reserved Scenario You are interested in the solution of SAP Cash Management powered by SAP HANA, you want to get an overview of the functions and features that can help the company run better in the Cash Management area. You are particularly interested in understanding what benefits you can gain from implementing the SAP Cash Management powered by SAP HANA in your SAP ERP system. © 2015 SAP SE or an SAP affiliate company. All rights reserved End-to-End Treasury and Risk Management Treasury Solution Map Payments and Bank Workflow and Monitoring and Status Bank and SWIFT Payment Operations Payment Factory Communications Signatures Tracking Connectivity Cash and Liquidity Electronic Bank Statements Cash Operations Liquidity Management Bank Account Management Management Debt and Investment Front Office Mid Office Back Office Accounting Management Deal capture Risk Controlling Correspondence & Settlement Financial Risk Risk Identification Risk Quantification Risk Management Risk Analysis Management Type and Origin of Risk Exposure Mgmt Hedge with Financial Instruments Working Capital Governance Risk and Suite Capabilities Shared Service Center Commodity Risk Management Management Compliance Rapid Deployment Foundation Cloud HANA Platform Analytics Mobile Solutions (RDS) SAP Cash Management powered by SAP HANA Treasury Solution Map, Edition 2014 © 2015 SAP SE or an SAP affiliate company. All rights reserved Integrated Treasury and Cash Platform SAP Treasury and Cash Solution  FX Management  Limit Management Market  Debt Management  Exposure Management Banks Places  Investment Management  Hedge Management  Correspondence Framework  Risk Management  Payments Liquidity Management  In House Bank  Bank Statements Market Data Cash Operations  Monitoring  Status Management SAP Bank Account Management  Signatory FSN One Exposure SAP HANA Platform + SAP Simple Finance Add On AP/AR SAP Others … © 2015 SAP SE or an SAP affiliate company. All rights reserved SAP Cash Management powered by SAP HANA Instant Insight SAP Cash Management powered by SAP HANA on SAP HANA Centralized Daily Cash Rolling Bank Operations Liquidity Cash Flow Liquidity Account and Cash Forecast Analysis Planning Management Position Intuitive User Experience SAP Accounting powered Integrated Business all devices by SAP HANA Planning SAP Simple Finance On-Premise Edition 1503 Flexible and Non-disruptive Business Suite on HANA cloud or on premise © 2015 SAP SE or an SAP affiliate company. All rights reserved SAP Cash Management powered by SAP HANA: Benefits  Bank Account Management – Centralized Bank Account Management SAP Cash Management powered by SAP HANA – Better Lifecycle Management for Bank Accounts – Master Data Fully Charged by Business Users  Cash Operations – Short Term Cash Positions Analysis – Make and Track Bank Transfers  Liquidity Management – Mid and Long Term Liquidity Forecast – Actual Cash Flow Analysis – Embedded Rolling Liquidity Planning and Variance Analysis  New Fiori (HTML5) user interface, and KPI cockpit – SAP Smart Business for Cash Management.  Integrated with FI, TRM, BCM (Bank Communication Management) and IHC (In- House Cash). © 2015 SAP SE or an SAP affiliate company. All rights reserved Function Overview of Bank Account Management Centralized Bank Account 2. Fuzzy Search Management 1. Bank and 3. Bank Bank Account Account Group  Plenty of attributes reflecting controls on Hierarchy （free style) both bank and company sides 5. Overdraft Limits  Bank Account standard hierarchy and 4. New free style group 6. Payment Bank Account Signatures Master Data Bank  Signatory integrated with BCM Payment Account Approval Management 9. Workflow for  Approval process for Bank Accounts 7. Attachments Bank Account Opening, Changing and Closing activities 8. Change History  Bank Accounts Review process 12. Upload and 10. Review  Upload and Download Bank Accounts Download Process  Bank Account Management Lite 11. Cash Pooling © 2015 SAP SE or an SAP affiliate company. All rights reserved Function Overview of Cash Operations Cash Operations  Cash Operations for the day to day management of the corporates working capital  Monitoring status of incoming bank statements  Preparing a daily forecast of cash receipts, disbursements and expected closing balances  Overseeing bank risk  Initiating bank transfers and payments  Approving and monitoring payments © 2015 SAP SE or an SAP affiliate company. All rights reserved Function Overview of Liquidity Management Liquidity Management  Complete lifecycle management of Rolling Liquidity Planning  System provides reference data to help Cash Manager to plan the liquidity precisely and easily  Functionality to plan hedging of operating activities for foreign currencies  Plan/Plan, Plan/Forecast and Plan/Actual comparisons  Overview suspicious plans  Liquidity Forecast  Cash Flow Analysis © 2015 SAP SE or an SAP affiliate company. All rights reserved List of Transactional and Analytical Fiori apps and Others Bank Account Management: Cash Operations:  Manage Bank Accounts (Webdynpro)  Bank Statement Monitor (Analytical)  My Sent Requests (Webdynpro)  Cash Position (Analytical)  My Bank Account Worklist  Cash Position Details (Transactional) (Webdynpro)  Analyze Payment Details (Transactional)  Maintain Signatory (Webdynpro)  Make Bank Transfer (Transactional)  Initiate Review Process (Webdynpro)  Track Bank Transfers (Transactional)  Monitor Review Status (Webdynpro)  Approve Bank Payments (Transactional)  Create Bank (HTMLGUI)  Bank Risk (Analytical)  Change Bank (HTMLGUI)  Payment Statistics (Analytical)  Manage House Banks (Transactional)  Bank (Factsheet) Liquidity Management:  House Bank (Factsheet)  Develop Liquidity Plans (Transactional)  House Bank Account (Factsheet)  Liquidity Plans (Analytical)  Liquidity Forecast (Analytical)  Cash Flow (Analytical) You can find detailed information of Fiori and Smart Business apps in following URL: https://go.sap.corp/kya © 2015 SAP SE or an SAP affiliate company. All rights reserved Deployment Options for SAP Cash Management powered by SAP HANA Client Client Client Client Client SAP ERP SAP ERP Business Suite on HANA Fin Acc SAP Cash Fin Acc SD SAP Cash BCM BCM Management SAP Cash BCM Mgmt Acc powered by Mgmt Acc Management Mgmt powered MM IHC IHC SAP HANA powered by IHC by SAP HANA Payment Payment SAP HANA SD SAP Accounting TRM SD TRM TRM SD powered by Simple Finance Simple Finance MM SAP HANA MM Add-on MM Add-on SAP Any Any DB SAP HANA DB SAP HANA DB HANA DB DB Side-by-side Scenarios Integrated Scenario Accelerated Analysis and Extended Functionality through Full Integration of Business Detailed Insights Integration of Single Processes Suite on SAP HANA © 2015 SAP SE or an SAP affiliate company. All rights reserved Related SAP Links Where What Link SAP Service Configuration Guide for SAP Cash http://service.sap.com/erp-inst -> SAP ERP Add-Ons -> SAP Simple Finance Add-On for Marketplace Management SAP Business Suite powered by SAP HANA -> SAP Simple Finance Add-On 2.0 SAP Service Data Setup Guide for SAP Cash Management Same as above Marketplace powered by SAP HANA SAP Service Note 2149337 https://css.wdf.sap.corp/sap/suppo Marketplace Release Scope Information - SAP Cash rt/notes/2149337 Management powered by SAP HANA © 2015 SAP SE or an SAP affiliate company. All rights reserved Demos & Exercises Activity Name Page OPTIONAL MANAGE HOUSE BANK ACCOUNTS EX-212 EXERCISE 16 © 2015 SAP SE or an SAP affiliate company. All rights reserved Summary You should now able to:  Understand the position of SAP Cash Management powered by SAP HANA in the overall Treasury solution map of SAP  Understand the main functions and business values of this product  Understand the main features of Cash Operations  Understand the main features of Bank Account Management  Understand the main features of Liquidity Management © 2015 SAP SE or an SAP affiliate company. All rights reserved Unit 6 – Agenda Outlining the Functions of SAP Cash Management powered by SAP HANA Outlining the Functions of Integrated Business Planning for Finance (IBPF) © 2015 SAP SE or an SAP affiliate company. All rights reserved  Outlining the Functions of Integrated Business Planning for Finance (IBPF) © 2015 SAP SE or an SAP affiliate company. All rights reserved. Learning Objective After completing this lesson, you will be able to:  Understand the Functions of Integrated Business Planning for Finance (IBPF)  Explain the Benefits of Integrated Business Planning for Finance (IBPF) © 2015 SAP SE or an SAP affiliate company. All rights reserved Scenario In your current system environment all planning processes are performed in the ERP environment. It is hard to maintain and execute a logical planning workflow and to achieve consistent planning on the various planned attributes. You want to understand how Integrated Business Planning for Finance can help you streamline and simplify the planning process. © 2015 SAP SE or an SAP affiliate company. All rights reserved What problems does IBPF address? Problem: Can’t plan across the organization in time, don’t have the right information, and can’t test assumptions Finance: “How’s Sales Mgmt: our overall margin “Can we impacted by our growth in BRIC?” support this Consequences new account?” Finance Sales  Miss the quarter  Lose a high-profile ERP customer GM/CXO:  Lose market share “How do we make sure we don’t miss Operations  Errors And the quarter?” Omissions CRM Marketing Marketing: “How SCM will a pricing change Supply Chain: impact demand of my highest volume “Where/when am I product family?” going to source this new product?” © 2015 SAP SE or an SAP affiliate company. All rights reserved What Does Integrated Business Planning for Finance (IBPF) Do?  Enables the financial planning capabilities provided by SAP Business Planning and Consolidation to be seamlessly integrated in SAP ERP user interfaces and workflows, effectively replacing the current planning capabilities in SAP ERP.  Overcomes limitations when planning in ERP through the SAP GUI  Eliminates Data replication.  Retracts Plan data developed in SAP Business Planning and Consolidation to SAP ERP for variance analysis and SAP Business Planning and Consolidation will be able to access real time master data and actuals maintained in SAP ERP.  Provides end-to-end simulation capabilities. © 2015 SAP SE or an SAP affiliate company. All rights reserved Why Use IBPF?  Integrated Business Planning for finance comes embedded with the SAP Business Suite on SAP HANA where SAP Simple Finance is being utilized.  Provides significant functional off the shelf content including templates and calculations covering multiple planning scenarios  Allows Companies using traditional financial planning within ERP to rapidly implement while protecting their existing investment. (Minimizes cost and time to implement)  Takes advantage of HANA views that support direct real time access to ERP Master data and the FI-CO document tables.  Optimal for organizations who have a significant portion of the data upon which they perform planning within the SAP ERP on HANA system and are planning against “traditional” FI and CO data structures yet at the same time provides for truly integrated planning across finance. © 2015 SAP SE or an SAP affiliate company. All rights reserved Functional Advantages of IBPF SAP Hana Driven Line Items  Fast plan data reporting and plan/actual comparisons  Fast plan data processing through planning functions of PAK (Planning Application Kit) Integrated FI and CO  Unbeatable bottom-up and top-down planning capabilities integrating data from high level expense group level down to most detailed market segmentations  Plan data are available at any level without the need of replication between applications Seamless upgrade possible:  CO Historic Plan Data can be migrated to the new solution (currently not GL).  Existing Plan Data processes remain unchanged (Tariff Calc., Allocations & Distributions, …) Enhanced Reconciliation Capabilities  Same granularity as in General Ledger: Every plan data record (even if it has been recorded at a higher level) is stored on company & account level.  No distinction between G/L Accounts and Cost Elements: Reconciled by Design © 2015 SAP SE or an SAP affiliate company. All rights reserved Conceptual Overview (Traditional Architecture) BPC* BW-IP** ERP Traditional Pain Points  Separate Systems for ERP-based planning and standalone planning EHP6 Architecture tools  Planning silos with separate data stores BW- XLS BPC* OLTP  Peer-to-peer transfer programs and IP** files ELT between different planning applications any any any  Long running batch jobs / DB DB DB Simulation impossible  Many manual steps / Long planning cycles * SAP Business Planning and Consolidation ** SAP Business Warehouse Integrated Planning © 2015 SAP SE or an SAP affiliate company. All rights reserved Simplified Planning Integration Today in ECC Integrated Business Planning  Planning silos with separate data stores  Common Financial Planning model  Long running batch jobs  Leverage In-Memory-planning capabilities  Peer-to-peer transfer programs  Faster planning cycles  Cumbersome process  Better decisions through end-to-end simulation  Many manual steps – fault prone capabilities  Simulation impossible Expense Profitability P&L Expense Profitability P&L Planning Planning Planning Planning Planning Planning HANA Views Common Planning Model © 2015 SAP SE or an SAP affiliate company. All rights reserved Comparison: Data Sources Where do my planned data “typically” come from ? P&L Planning + Profit Center Planning + Integrated Project Planning Business Planning for + Finance Cube Cost Center Planning + Internal Order Planning © 2015 SAP SE or an SAP affiliate company. All rights reserved Content delivered with IBPF Integrated Business Planning for finance includes templates that provide support for:  Cost Center Planning  Internal Order Planning  Project Planning  Profit Center Planning  Cost of Sales Planning  P&L Planning  Market Segment Planning  Liquidity Planning Integrated Business Planning for finance also includes:  Queries  Planning Functions  Sequences  Info-Objects  Info-Providers © 2015 SAP SE or an SAP affiliate company. All rights reserved What are the pre-requisites for Integrated Business Planning for Finance? Licensing Installation  SAP ERP Foundation starter plus  SAP HANA 1.0 Platform appropriate named user licensing  SAP NetWeaver 7.40  SAP Accounting Powered by SAP HANA  SAP ECC Release 6.0EhP7 license  SAP Simple Finance 1503  SAP Cash Management for Finance (Liquidity planning is a part of Cash Management )  SAP HANA Limited Runtime edition for Applications or other appropriate HANA licensing  SAP Business Planning & Consolidation, version for SAP NetWeaver license  SAP BusinessObjects Analysis Edition for Office (soon to be included in the above) © 2015 SAP SE or an SAP affiliate company. All rights reserved Limitations and Outlook Current solution limitations:  Enterprise Performance Management (EPM) Add-In client not available yet  Finance driven master data administration/management not available where master data not maintained directly in ERP  Currently no equivalent to IBPF for Consolidation (you need to use standalone BPC for this functionality). High level development roadmap direction:  Legal & Managerial Consolidation  Investment Planning  Improved Simulation  Improved Process Administration © 2015 SAP SE or an SAP affiliate company. All rights reserved Related SAP Links Where What Link SAP Service Consolidated SAP information note for https://css.wdf.sap.corp/sap/support/notes Marketplace IBPF: 2081400 /2081400 Youtube IBPF Demo https://go.sap.corp/IBPFDEMO © 2015 SAP SE or an SAP affiliate company. All rights reserved Demos & Exercises Activity Name Page OPTIONAL PLAN COSTS USING IBPF EX-223 EXERCISE 17 © 2015 SAP SE or an SAP affiliate company. All rights reserved Summary You should now able to:  Understand the Functions of Integrated Business Planning for Finance (IBPF)  Explain the Benefits of Integrated Business Planning for Finance (IBPF) © 2015 SAP SE or an SAP affiliate company. All rights reserved © 2015 SAP SE oder ein SAP-Konzernunternehmen. Alle Rechte vorbehalten. Weitergabe und Vervielfältigung dieser Publikation oder von Teilen daraus sind, zu welchem Zweck und in welcher Form auch immer, ohne die ausdrückliche schriftliche Genehmigung durch SAP SE oder ein SAP-Konzernunternehmen nicht gestattet. SAP und andere in diesem Dokument erwähnte Produkte und Dienstleistungen von SAP sowie die dazugehörigen Logos sind Marken oder eingetragene Marken der SAP SE (oder von einem SAP-Konzernunternehmen) in Deutschland und verschiedenen anderen Ländern weltweit. Weitere Hinweise und Informationen zum Markenrecht finden Sie unter http://global.sap.com/corporate-de/legal/copyright/index.epx. Die von SAP SE oder deren Vertriebsfirmen angebotenen Softwareprodukte können Softwarekomponenten auch anderer Softwarehersteller enthalten. Produkte können länderspezifische Unterschiede aufweisen. Die vorliegenden Unterlagen werden von der SAP SE oder einem SAP-Konzernunternehmen bereitgestellt und dienen ausschließlich zu Informations- zwecken. Die SAP SE oder ihre Konzernunternehmen übernehmen keinerlei Haftung oder Gewährleistung für Fehler oder Unvollständigkeiten in dieser Publikation. Die SAP SE oder ein SAP-Konzernunternehmen steht lediglich für Produkte und Dienstleistungen nach der Maßgabe ein, die in der Vereinbarung über die jeweiligen Produkte und Dienstleistungen ausdrücklich geregelt ist. Keine der hierin enthaltenen Informationen ist als zusätzliche Garantie zu interpretieren. Insbesondere sind die SAP SE oder ihre Konzernunternehmen in keiner Weise verpflichtet, in dieser Publikation oder einer zugehörigen Präsentation dargestellte Geschäftsabläufe zu verfolgen oder hierin wiedergegebene Funktionen zu entwickeln oder zu veröffentlichen. Diese Publikation oder eine zugehörige Präsentation, die Strategie und etwaige künftige Entwicklungen, Produkte und/oder Plattformen der SAP SE oder ihrer Konzern- unternehmen können von der SAP SE oder ihren Konzernunternehmen jederzeit und ohne Angabe von Gründen unangekündigt geändert werden. Die in dieser Publikation enthaltenen Informationen stellen keine Zusage, kein Versprechen und keine rechtliche Verpflichtung zur Lieferung von Material, Code oder Funktionen dar. Sämtliche vorausschauenden Aussagen unterliegen unterschiedlichen Risiken und Unsicherheiten, durch die die tatsächlichen Ergebnisse von den Erwartungen abweichen können. Die vorausschauenden Aussagen geben die Sicht zu dem Zeitpunkt wieder, zu dem sie getätigt wurden. Dem Leser wird empfohlen, diesen Aussagen kein übertriebenes Vertrauen zu schenken und sich bei Kaufentscheidungen nicht auf sie zu stützen. © 2015 SAP SE or an SAP affiliate company. All rights reserved © 2015 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 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. © 2015 SAP SE or an SAP affiliate company. All rights reserved