Central Finance-2016.pdf

Full text

(1)What’s in Central Finance? May 2016 Product Version / LoB: SAP S/4HANA Finance, on-premise edition 1605. E2E Solution/Solution Capability: Central Finance.

(2) Objectives Slide. At the end of this lesson, you will be able to: • Outline how customers can connect their distributed system landscape (which can be made up of a combination of SAP systems of different releases and non-SAP system) to a centralized SAP S/4HANA Finance system. • Describe how customers can establish a Central Reporting Platform for FI/CO with the option to create a common reporting structure. • Explain how acquired companies can be integrated more easily • Explain how a foundation can be established today for further centralizing financial processes in future • Explain how reposted Financial Accounting (FI) and Management Accounting (CO) documents look in Central Finance and how they reconcile back to the source systems • Explain how the Central Finance integration works (including mapping and error handling) © 2015 SAP SE or an SAP affiliate company. All rights reserved.. Early Knowledge Transfer. Customer. 2.

(3) Table of Contents. Motivation and General Overview Posting of FI Documents Reporting: Once the documents are in – there are new possibilities in reporting Mapping and Error Handling Posting of CO Documents Initial Load Integrated Planning in Central Finance with SAP BPC for S/4HANA Finance. Summary: New compared with the first release Future scenarios. © 2015 SAP SE or an SAP affiliate company. All rights reserved.. Early Knowledge Transfer. Customer. 3.

(4) Motivation and General Overview.

(5) Situations we find at many customers: Finance is complex … and not (digitally) connected. Consolidate. Plan. ERP / CPM. programs / user interfaces. BW. programs / user interfaces data data. programs / user interfaces. Signs of complexity. line item. data .... open items. .... open items. • Extractions and transformations. balances. line item balances. line item balances. ERP. .... open items Application. • Mappings and harmonization. Production programs / user interfaces programs / user interfaces data. • Delays, anomalies, inconsistency's. BI. data. line item balances. programs / user interfaces. line item balances. • Data reconciliation, data validation. .... open items. data. .... open items. line item balances. • Report provision (data-to-people). open items. Finance. .... programs / user interfaces. Procurement data. Business issue(s). .... programs / user interfaces line item balances. programs / user interfaces. data. • Limited transparency. open items. .... data. line item balances. line item. • Throttled productivity. open items. balances. .... open items. .... • Pro-longed process execution • Service level challenges. © 2015 SAP SE or an SAP affiliate company. All rights reserved.. Early Knowledge Transfer. Customer. 5.

(6) Trusted Insights.

(7) Typical Challenges Address challenges in Reporting Instant insight across the entire company • What do I spend in my entire company on external consultants? • How well do I benefit from cash discounts across my entire company? • How does the aging of my payables overall look like? • What vendor groups are most overdue? • What customers are most overdue? • Why do customers not pay on time? • … Challenges that customers have today • No single source of truth • or very aggregated view only and without drill-down capabilities to operational lineitems • Lack of real-time view • Unharmonized master data (vendors, customers, accounts, payment terms, cost centers, profit centers…). Centralize Processes (planned functionality) • • • •. Streamline processes – do it the same way in the entire company Improve efficiency in Shared Service Centers (fewer systems to connect to) Reduce training efforts for different releases and vendors Simplify interfacing with external partners (e.g. banks, rating agencies…). © 2015 SAP SE or an SAP affiliate company. All rights reserved.. Early Knowledge Transfer. Customer. 7.

(8) IT Strategy and Vision. Cross-system SAP capabilities like credit, intercompany, treasury, shared services on can be consolidated on one Central Finance instance Instance consolidation. Finance Hub for group-wide analytics and central processes Permanent Side-Car. Platform to onboard smaller entities or subsidiaries. Subsidiary onboarding. Platform for accelerated onboarding with early insights. Migrate and decommission selected existing SAP and non-SAP ERP systems System consolidation**. Mergers & Acquisitions. Consolidated reporting, central processes (shared services), business transformation. SAP and 3rd Party*. Harmonize and centralize finance information across nonSAP ERP or mixed landscapes. new. Move to the cloud. Transition to the Cloud. * Integration infrastructure (mapping content for specific Non-SAP systems not predelivered) –refer to note 2184567, question #5) ** preparation for later system consolidation (start with FI and move logistics later). © 2015 SAP SE or an SAP affiliate company. All rights reserved.. Early Knowledge Transfer. Customer. 8.

(9) THE non-disruptive step towards system consolidation Real-Time repost financial transactions into Central Finance instance. . Transaction-level data replicated into instance with latest SAP innovations, HANA optimizations and cutting edge UI.  . Existing systems remain untouched (notes need to be applied but no process changes) Benefit from harmonized master data for processing, planning, consolidating, and reporting. ERP. Real-time replication. source system(s):  SAP (any release*)  non-SAP systems*  over-customized. plan, consolidate, report *. SAP S/4HANA Finance – Central Finance. SAP HANA. Simplified single system landscape * requires respective SAP products and licenses (e.g. SAP Accounting powered by SAP HANA, SAP Business Planning and Consolidation, BOBJ BI) etc.. * Some releases supported out-of-the-box – others require additional effort –refer to note 2184567, question #5). © 2015 SAP SE or an SAP affiliate company. All rights reserved.. Early Knowledge Transfer. Customer. 9.

(10) Functionalities supporting Central Finance. SAP MDG Existing Master Data Governance Tool. SAP S/4HANA Finance – Central Finance. Central Finance Accounting Interface ERP. Business Mapping. Error correction handling. Real-time replication with. SAP Landscape Transformation Replication Server . Transaction-level. . Reconciled. . Harmonized. SAP ERP. SAP HANA. Universal Journal Entry. Some releases supported out-of-the-box – others require additional effort –refer to note 2184567, question #5. © 2015 SAP SE or an SAP affiliate company. All rights reserved.. Early Knowledge Transfer. Customer. 10.

(11) Functionalities supporting Central Finance HANA Enterprise Cloud HANA Enterprise Cloud SAP MDG Existing Master Data Governance Tool. SAP S/4HANA Finance – Central Finance. Central Finance Accounting Interface ERP. Business Mapping. Error correction handling. Real-time replication with. SAP Landscape Transformation Replication Server. SAP ERP. SAP HANA. Universal Journal Entry. Some releases supported out-of-the-box – others require additional effort –refer to note 2184567, question #5. © 2015 SAP SE or an SAP affiliate company. All rights reserved.. Early Knowledge Transfer. Customer. 11.

(12) Central Finance Accounting Interface Reposting harmonizes data but retains line item-based detail. Central Finance. FI/CO Postings FI CO Document Document. CO Postings. CO Document. Universal Central Journal Entry Finance Suite on HANA Accounting Interface. Cost Object Mapping. SAP HANA. Central Finance instance. Further information on the functional scope of the interfaces can be found in notes 2184567, 2103482, 2180924 and 2184567. © 2015 SAP SE or an SAP affiliate company. All rights reserved.. Early Knowledge Transfer. Customer. 12.

(13) Posting of FI Documents.

(14) Document Display in Fiori. © 2015 SAP SE or an SAP affiliate company. All rights reserved.. Early Knowledge Transfer. Customer. 14.

(15) From Central Finance, reference back to FI document in source ERP system. Reference key to identify document in source system. Journal Entry view in Central Finance system. © 2015 SAP SE or an SAP affiliate company. All rights reserved.. Early Knowledge Transfer. Customer. 15.

(16) Reporting Once the documents are in – there are new possibilities in reporting.

(17) © 2015 SAP SE or an SAP affiliate company. All rights reserved.. 22.

(18) © 2015 SAP SE or an SAP affiliate company. All rights reserved.. Early Knowledge Transfer. Customer. 23.

(19) Trial Balance – Flexible Drill-down to Any Dimension. 2016. © 2015 SAP SE or an SAP affiliate company. All rights reserved.. Early Knowledge Transfer. Customer. 24.

(20) Analysis for Office. © 2015 SAP SE or an SAP affiliate company. All rights reserved.. 25.

(21) Apps working on Receivables and Payables Information. © 2015 SAP SE or an SAP affiliate company. All rights reserved.. Early Knowledge Transfer. Customer. 26.

(22) KPI Tiles: no more looking for work. 2016. © 2015 SAP SE or an SAP affiliate company. All rights reserved.. Early Knowledge Transfer. Customer. 27.

(23) Mapping and Error Handling.

(24) Functionalities supporting Central Finance. SAP MDG Existing Master Data Governance Tool. SAP S/4HANA Finance – Central Finance. Central Finance Accounting Interface ERP. Business Mapping. Error correction handling. Real-time replication with. SAP Landscape Transformation Replication Server . Transaction-level. . Reconciled. . Harmonized. SAP ERP. SAP HANA. © 2015 SAP SE or an SAP affiliate company. All rights reserved.. Early Knowledge Transfer. Universal Journal Entry. Customer. 29.

(25) Typical candiates for mapping •. Company Code (BUKRS). •. Material (MATNR). •. GL Account (HKONT, SAKNR). •. Plant (WERKS). •. Cost elements (KSTAR) •. Purchasing Organization (EKORG). •. Cost Centers (KOSTL). •. Sales Organization (VKORG). •. Profit Center (PRCTR). •. Sales Group (VKGRP). •. Business Area (GSBER). •. Sales Office (VKBUR). •. Functional Area (FKBER) •. TaxCode (MWSKZ). •. Company (VBUND). •. Customer (KUNNR). •. Supplier (LIFNR). © 2015 SAP SE or an SAP affiliate company. All rights reserved.. Early Knowledge Transfer. Customer. 30.

(26) Typical candiates for mapping - continued. •. Payment Methods. •. Dunning Area. •. Cash Discount Terms. •. Distribution channel,. •. Division code. •. Valuation type. •. Measure units,. •. Tax jurisdiction code. •. Country codes. •. Region codes. •. Industry Key. © 2015 SAP SE or an SAP affiliate company. All rights reserved.. Early Knowledge Transfer. Customer. 31.

(27) Key Mapping and Value Mapping Key-Mappings: Usually distributable by MDG new ones created frequently • Customer • Vendor • Material • Accounts • …. Value Mappings: typically customizing values rather stable typically an attribute for master data: • Payment terms • Dunning area • Payment methods • …. © 2015 SAP SE or an SAP affiliate company. All rights reserved.. Early Knowledge Transfer. Customer. 32.

(28) Example – Replicated FI Document with Mapping. Central Finance. Source System. © 2015 SAP SE or an SAP affiliate company. All rights reserved.. Early Knowledge Transfer. Customer. 33.

(29) Master data can be mapped, harmonized and distributed with SAP Master Data Governance. Create customer CUST_CENT. 1. Central Finance Customer Mapping Table. SAP Master Data Governance. Customer “100000” created. System A. CUST_CENT. 100000. Central Finance Accounting Interface. 2. Un-harmonized Master Data. Central Finance Accounting Interface.  Chart of Accounts  Material Numbers / Product Hierarchies. Central Finance.  …. Business Mapping / MDG Business Mapping / MDG. Error correction handling. SAP ERP.  Customer / Vendor Numbers  Cost Centers / Cost Center Hierarchies. 3. Universal Journal Entry Receivable customer 100000: 10.00 Revenue. 10.00. 4. Receivable Receivable customer VEND_CENT: CUST_CENT: 10.00 10.00 customer Revenue 10.00 Revenue 10.00. SAP ERP Central Finance instance. SAP HANA. Universal Journal Entry. Central Finance instance. © 2015 SAP SE or an SAP affiliate company. All rights reserved.. Early Knowledge Transfer. Customer. 34.

(30) Mapping – Manual Maintenance of Mappings If SAP MDG is not Used •. Key mapping. • Value mapping. (Webdynpro: MDG_BS_WD_ID_MATCH_SERVICE). (MDG Customizing). performed via IMG. © 2015 SAP SE or an SAP affiliate company. All rights reserved.. Early Knowledge Transfer. Customer. 35.

(31) Places Where Mapping and Derivations are Performed. S/4HANA – Central Finance. SAP Landscape Transformation Replication Server. Central Finance Accounting Interface. 2. 1 Business Mapping. BAdI. AIF Error Correction Tool. Internal Accounting Interface. 1. Exits, BAdIs, BTEs. 3. Standard Derivations and Substitutions. 4. Preferred place Standard derivations and substitutions based on master data and configuration of the target system can overwrite mappings to ensure consistency. (e.g. for postings into the P&L, the profit center is derived from the cost center). © 2015 SAP SE or an SAP affiliate company. All rights reserved.. Early Knowledge Transfer. Customer. 36.

(32) Mapping – Store Original Values for Reconciliation. By default: •. GL Account. •. „Real“ cost object (that carries the cost). User can add additional fields into universal journal entry if he wishes to store original values of more fields © 2015 SAP SE or an SAP affiliate company. All rights reserved.. Early Knowledge Transfer. Customer. 37.

(33) Error Handling Tool (AIF) for Central Finance Scenarios. Calendar based view User has mouse-over feature to see how many messages and how many errors there are on a certain date Color of calendar day changes based on message status User can click in calendar (click on month, week, day) to show only selected time frame or a time range can be entered. © 2015 SAP SE or an SAP affiliate company. All rights reserved.. Early Knowledge Transfer. Customer. 38.

(34) Error Handling Tool (AIF) for Central Finance Scenarios. AIF shows multiple errors, not just the main message. Field names can be shown with own texts. Messages can be rephrased if a message text is not meaningful. Messages can be assigned to SAP-transaction codes (e.g. IMG activities) which allows users to navigate the place where the error can be solved. Emergency correction mode (requires special authorization) allows changing any posting data field by entering the correct value. © 2015 SAP SE or an SAP affiliate company. All rights reserved.. Early Knowledge Transfer. Customer. 39.

(35) Posting of CO documents.

(36) Cost Object Mapping Framework. Master Data Harmonize. SAP S/4HANA Finance – Central Finance. ERP. Long Living Master Data. Short Living Cost Object. Stable, only need to be harmonized once. More like transactional data, generated frequently. Company Code, Plant, Material, Cost Center…. Production Order, Internal Order, Service Order…. Details on scope see SAP note 2180924 .. © 2015 SAP SE or an SAP affiliate company. All rights reserved.. Early Knowledge Transfer. Customer. 41.

(37) Cost Object Mapping Framework. Currently supported cost objects and mapping scenarios. See more information in note 2180924.. Cost Object in Source System Production Order Product Cost Collector Internal Order Service Order(PM Order) QM Order Production Order Service Order(PM Order) QM Order. Cost Object in Central system Product Cost Collector Product Cost Collector Internal Order Service Order(PM Order) QM Order Internal Order Internal Order Internal Order. © 2015 SAP SE or an SAP affiliate company. All rights reserved.. Early Knowledge Transfer. Changes of cost objects now replicated see note 2308365. Customer. 42.

(38) Cost Object Mapping Framework- Customizing Path in Customizing. Step 1: Define scenarios for cost object mapping. Step 2: Define mapping rule for selected scenario. © 2015 SAP SE or an SAP affiliate company. All rights reserved.. Early Knowledge Transfer. Customer. 43.

(39) Example – Reposting CO Document with Master Data Mapping SAP MDG Mapping Source Cost Center. Central Cost Center. ZZZ01. ZZZC1. Cost Object Mapping Source Internal Order. Central Internal Order. 102680. 100621. Details on scope see SAP note 2103482.. © 2015 SAP SE or an SAP affiliate company. All rights reserved.. Early Knowledge Transfer. Customer. 44.

(40) Example – Drill Back – Document Relationship Browser. N a v i g a t e. © 2015 SAP SE or an SAP affiliate company. All rights reserved.. Early Knowledge Transfer. All business documents related to the transaction are available in browser, provided source system is SAP. Customer. 45.

(41) CO Secondary Posting and Universal Journal Entry. Source System. Central System Central System. © 2015 SAP SE or an SAP affiliate company. All rights reserved.. Early Knowledge Transfer. Customer. 46.

(42) While MDG keeps long-life data harmonized, Cost Object Mapping Framework manages very short-lived cost objects. Long-Life Master Data. Stable, only need to be harmonized once Examples: Company Code, Plant, Material, Cost Center Managed by SAP Master Data Governance. Central Finance Production Order1. Expense1. Cost Object Mapping Expense2. Expense3. Production Order2. Central Cost Object Reporting. Central Product Cost Collector. Production Order3. Primary and Secondary Cost Postings. Expense1. Expense2. Short-Life Cost Object. Source System Expense3. Similar to transactional data, generated frequently Examples: Production Order, Internal Order, Service Order… Managed by Cost Object Mapping Framework. SAP HANA. 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.. Early Knowledge Transfer. Customer. 47.

(43) Revolutionize group cost reporting Centrally allocate costs originating from different source systems. Central Finance. Expense. Expense. Transformative insight into crosssystem costs. Primary and Secondary Cost Postings. Activities. Allocations. System A. Expense. Expense. Improve transparency. Primary and Secondary Cost Postings. System B. © 2015 SAP SE or an SAP affiliate company. All rights reserved.. Better distribute resources based on more accurate cost allocations. SAP HANA. Early Knowledge Transfer. Drive cost accountability. Customer. 48.

(44) Initial Load.

(45) Overview. Initial Load is used to transfer a starting balance and FI and CO documents from previous periods. The recommendation is to keep the number of periods small.. There are different types of Initial Loads (see next slides) More important information can be found in the EKT material for the application consultant. © 2015 SAP SE or an SAP affiliate company. All rights reserved.. Early Knowledge Transfer. Customer. 50.

(46) General Information – Sequence of the different Initial Loads. There are different kinds of initial loads – recommendation is to perform them in the following sequence:. 1. Initial Load of cost objects  Performed via SLT  Cost objects might be needed by the other initial loads  Requires configuration of cost object mapping framework in the Central Finance System  Basis for replication: table AUFK and related tables.  Work with filters in SLT (controlling area, order types, creation dates etc.) 2. Initial Load of FI postings  Performed via IMG of the Central Finance System  Basis for replication: GLT0/FAGLFLEXT/BKPF/BSEG/COEP/CE4xxx  More information see below 3. Initial Load of CO-internal postings  Performed via SLT  Basis for replication: COBK/COEP  Work with filters (controlling area, company codes…). © 2015 SAP SE or an SAP affiliate company. All rights reserved.. Early Knowledge Transfer. Customer. 51.

(47) Initial Load of Balances  Reposting each and every single FI document causes effort (master data, runtime, data quality…) for older data it makes sense to only take over the balances instead of individual Replication Start documents Balances & Open Items. Documents Online Transfer….  The timespan for the take over of individual documents shall be kept as short as possible. t.  The phases are configured via customizing in the source system Customizing View: VCFIN_SOURCE_SET.  Tip: add default account assignment for offsetting account in OKB9 to avoid errors © 2015 SAP SE or an SAP affiliate company. All rights reserved.. Early Knowledge Transfer. Customer. 52.

(48) Initial Load for Financial Accounting Preparation Balances & Open Items. Documents Online Transfer…. t. Like in a migration scenario it makes sense to •. Apply account maintenance in the source system upfront in order to keep the number of open items to be loaded small. •. Keep the time horizon for the Initial Load of Documents at a minimum: • •. Cover only documents which will most likely be required for follow up processes Don‘t load more documents than you would also cover in a migration project. © 2015 SAP SE or an SAP affiliate company. All rights reserved.. Early Knowledge Transfer. Customer. 53.

(49) Integrated Planning in Central Finance with SAP BPC for S/4HANA Finance..

(50) Integrated Planning in Central Finance. SAP ERP Planning. • •. •. SAP GUI Sequential Planning Process  Cost Center Plan  Project Plan…  No direct share of values Fixed data model. © 2015 SAP SE or an SAP affiliate company. All rights reserved.. SAP BPC for S/4HANA Finance.. • • • • • •. Early Knowledge Transfer. HTML5 UI, Analysis for Office Parallel Planning Process HANA Optimized performance Workflow/Workstatus support Real time Actuals Activity Log. Customer. 55.

(51) Use centralized harmonized data as platform for integrated business planning to replace “SETL” approaches. Scheduled extraction, transformation, loading. Central Finance. SAP BW Info Objects (Master data). InfoCubes (Plan Data). Central Financial Planning. InfoCubes (Actual Data). Expense Planning. Profitability Planning. P&L Planning. Common Planning Model SAP ERP Expense Planning. Profitability Planning. P&L Planning. Corporate alignment difficult  Process time lags due to data loading. Master Data & Actual Data. Plan Data. ERP. InfoCube. Improved planning cycles  No replication into BW required  Faster cycle times  Integrate and automate planning and transaction processing for speed and efficiency. SAP HANA.  Data harmonization difficult in multi-system setup. Corporate alignment.  Updates in one plan not immediately reflected in other related plans.  Harmonized data and common planning model improve transparency and accountability  Dynamically adapt to changing business environments  Simulation capabilities for better decision making. © 2015 SAP SE or an SAP affiliate company. All rights reserved.. Early Knowledge Transfer. Customer. 56.

(52) New compared with the first release.

(53) Overview. Replication of clearings Replication of document changes Replication of changes to cost objects Error Handling (AIF) Performance Improvements (bulk mode) Tools supporting the Initial Load. © 2015 SAP SE or an SAP affiliate company. All rights reserved.. Early Knowledge Transfer. Customer. 58.

(54) Open Item Management in Central Finance. Open items are replicated into Central Finance. To avoid duplication of effort to pay/clear, there are the following options: Local Open item. Central Finance SLT. Open item. Clearing. Tech Cleared. Local. Central Finance SLT. Open item. Open item SLT. Clearing. Clearing. Local Open item Tech Cleared. Central Finance SLT. Open item. Replicate open item and automatically/technically clear in Central Finance •. Available as of 1503. •. Continued open item management in source system. Not suitable for central reporting or central processing (since clearing status not correct). Replicate open item and clearing status in Central Finance. Centralization of finance operations reporting and central process orchestration. •. Continued open item management in source system. •. A/R and A/P reporting (cross-system view of customer or vendor account). •. For restrictions and further information, please see note 2292043. •. Central Disputes, Collections, Invoice Mgmt, Credit, Shared Services. •. Local clearing processes optimized based on central clearing advices**. Replicate open item and automatically/technically clear in Central Finance •. **Not yet available. •. Centralized open item management in Central Finance system. Clearing •. No posting back to the source systems. © 2015 SAP SE or an SAP affiliate company. All rights reserved.. Early Knowledge Transfer. Similar to existing ALE scenarios, this is a customerspecific process where consistency in certain local logistics processes has to be determined in a case-bycase analysis *ALE, RFC, other **roadmap item, not committed. Customer. 59.

(55) Centralization of finance operations reporting and central process orchestration Central Finance. Cross-system view of customer or vendor account / real-time operational reporting with Fiori user experience. A/R reporting: Credit Customer Management Analysis. Dispute Lists. Collections Worklists. SLT. Open Item. Key processes managed centrally, executed centrally whenever possible Postings are seamlessly triggered in local FI systems Centralize process know-how in shared service center. Harmonized, mapped master data. © 2015 SAP SE or an SAP affiliate company. All rights reserved.. Open Item ERP. ALE / Web Scenarios. Source logistics processes access local FIN data for consistency Some processes require manual steps for postings in local systems (example: credit memo posting upon dispute resolution). Early Knowledge Transfer. Real-time operational reporting. SAP HANA. Replication of payments, clearing status, cost differences, discounts, etc into central system. Reporting-related processes could then be orchestrated or run on centralized data set: cash application, credit exposure calculations, dunning, collections prioritization. Mapping of customers/vendors via Central Finance mapping functionality – optional integration with SAP MDG. Customer. 60.

(56) Reporting scenarios at a glance (excerpt) Supported with Central Finance in earlier releases. New scenarios enabled by replication of clearings. General Ledger Accountant • Trial Balance • Display Financial Statement • Display G/L Account Line Items • Display G/L Account Balances. Global Cash Manager • Cash Flow Analysis • Liquidity Forecast (based on AP/AR) Accounts Payables / Receivables Accountant • Display Vendor Balances • Display Customer Balances. Financial Analyst • Cost Center – Plan / Actual • Internal Orders – Plan / Actual • Market Segments – Plan / Actual • Profit and Loss – Plan / Actual • Projects – Plan / Actual. Accounts Payables / Receivables Manager • Future Payables • Aging Analysis • Dunning Level Distribution • Days Beyond Terms • Future Receivables • Overdue Receivables • Total Receivables • Days Payable Outstanding • Vendor Payment Analysis (Open Payments) • Vendor Payment Analysis (Manual and Automatic Payments). Cost Manager • My Spend • My Unusual Items. © 2015 SAP SE or an SAP affiliate company. All rights reserved.. Early Knowledge Transfer. Customer. 61.

(57) Central Finance: Replication of Document Changes. Central Finance. Posting of document Change of FI document (e.g. via FB02). FI Document changed FI Document. FI/CO Postings. Central Simple Finance Add-on Finance Universal Accounting Journal Entry Interface Suite on HANA. Error correction in AIF-Tool. Replicate a change to an FIdocument from the source system to update the corresponding FI-document in the Central Finance System. FI Document Change. SAP HANA. Decentral source systems. © 2015 SAP SE or an SAP affiliate company. All rights reserved.. Central Finance instance. Early Knowledge Transfer. Customer. 62.

(58) Cost Object Mapping Framework new scenarios and support of cost object changes. Currently supported cost objects and mapping scenarios. See more information in note 2180924.. Cost Object in Source System Production Order Product Cost Collector Internal Order Service Order(PM Order) QM Order Production Order Service Order(PM Order) QM Order. Cost Object in Central system Product Cost Collector Product Cost Collector Internal Order Service Order(PM Order) QM Order Internal Order Internal Order Internal Order. © 2015 SAP SE or an SAP affiliate company. All rights reserved.. Early Knowledge Transfer. Changes of cost objects now replicated see note 2308365. Customer. 63.

(59) Replication of Cost Object Change. Order in Source System. Replicate and mapping. Order in Central Finance System. Order in Source System Attributes Attributes change Change. Attributes Changes. Order in Central Finance System. Replicate. Changes of cost objects now replicated see note 2308365. © 2015 SAP SE or an SAP affiliate company. All rights reserved.. Early Knowledge Transfer. Customer. 64.

(60) Functionalities supporting Central Finance. SAP MDG Existing Master Data Governance Tool. SAP S/4HANA Finance – Central Finance. Central Finance Accounting Interface ERP. Business Mapping. Error correction handling. Real-time replication with. SAP Landscape Transformation Replication Server . Transaction-level. . Reconciled. . Harmonized. SAP ERP. SAP HANA. © 2015 SAP SE or an SAP affiliate company. All rights reserved.. Early Knowledge Transfer. Universal Journal Entry. Customer. 65.

(61) New Error Handling Tool (AIF) for Central Finance Scenarios. © 2015 SAP SE or an SAP affiliate company. All rights reserved.. Early Knowledge Transfer. •. Single place for error handling of all Central Finance Replication Scenarios. •. Quick Overview. •. Role based view. •. No need to select. •. User can toggle Email Notifications. •. Show and confirm Alerts. •. Prec-calculated and role based statistics. Customer. 66.

(62) New Error Handling Tool (AIF) for Central Finance Scenarios. Calendar based view User has mouse-over feature to see how many messages and how many errors there are on a certain date Color of calendar day changes based on message status User can click in calendar (click on month, week, day) to show only selected time frame or a time range can be entered. © 2015 SAP SE or an SAP affiliate company. All rights reserved.. Early Knowledge Transfer. Customer. 67.

(63) New Error Handling Tool (AIF) for Central Finance Scenarios. AIF shows multiple errors, not just the main message. Field names can be shown with own texts. Messages can be rephrased if a message text is not meaningful. Messages can be assigned to SAP-transaction codes (e.g. IMG activities) which allows users to navigate the place where the error can be solved. Emergency correction mode (requires special authorization) allows changing any posting data field by entering the correct value. © 2015 SAP SE or an SAP affiliate company. All rights reserved.. Early Knowledge Transfer. Customer. 68.

(64) Error Correction via AIF. AIF is used as the error handling tool in Central Finance for • Errors during FI-document replication (new documents & document changes) • Errors during CO-document replication. • Errors during cost object replication (new cost objects and cost object changes) • Errors during the Initial Load of cost object • Errors during the Initial Load of CO-internal postings The Initial Load of FI balances and FI documents uses a different error monitor Usually AIF requires a separate license. But it is included in the Central Finance license for the delivered Central Finance scenarios listed above. Performance improvements have been achieved (see next slide). © 2015 SAP SE or an SAP affiliate company. All rights reserved.. Early Knowledge Transfer. Customer. 69.

(65) AIF Bulk Processing Performance improvement With this new functionality SLT and AIF process the financial transactions being replicated to Central Finance bulk mode. Advantages •. Reduced number of background processes started by AIF. •. Improved througput (performance). Deployment •. New standard configuration. •. Available per Note 2291942 for lower releases. •. SLT content to be adapted according to note 2154420. © 2015 SAP SE or an SAP affiliate company. All rights reserved.. Early Knowledge Transfer. Customer. 70.

(66) New Tools supporting the Initial Load. •. Simulation of Initial Load (FI) see IMG activities. •. Simulation of Initial Load (CO-internal postings & cost objects) triggered via SLT (see EKT material for application consultant). •. Smoke Test Tool (test replication for a number of CO-internal postings & cost objects) (see EKT material for application consultant). •. Initial Load (FI): Initial Load by company codes (see EKT material for application consultant). •. Initial Load (FI): Aggregated Message Monitor: program RFINS_CFIN_DISPLAY_LOG. © 2015 SAP SE or an SAP affiliate company. All rights reserved.. Early Knowledge Transfer. Customer. 71.

(67) Other new tools. •. Correct Cost Object Mappings (see next slides). •. Delete Cost Object Mappings (see next slides). © 2015 SAP SE or an SAP affiliate company. All rights reserved.. Early Knowledge Transfer. Customer. 72.

(68) New Tools: Cost Object Mapping Framework Correct Cost Object Mapping. Delete Cost Object Mapping and Cost Objects. © 2015 SAP SE or an SAP affiliate company. All rights reserved.. Early Knowledge Transfer. Customer. 73.

(69) Planned Future Scenarios. SAP has no obligation to pursue any course of business outlined in this slide or to develop or release any functionality mentioned on this slide. This slide and SAP's strategy and possible future developments are subject to change and may be changed by SAP at any time for any reason without notice. This document is provided without a warranty of any kind, either express or implied, including but not limited to, the implied warranties of merchantability, fitness for a particular purpose, or non-infringement..

(70) Way forward. Central Processes* (Collections. Centralization of Processes**. Management, Dispute Management). (Central Payments, Asset Accounting, CO allocations…). Legal and Management Consolidation. Consolidation Preparation Reporting Scenarios (GL Reporting,. Reporting Scenarios. Reporting Scenarios**. Overhead Cost Reporting, Profitability). (AP/AR*, DSO*, Overdue Analysis* etc., Liquidity Forecast*). (Profit Center, Profitability, Assets,...). Foundation (replication, error handling, Mapping, Initial Load). First release. Today. SAP has no obligation to pursue any course of business outlined in this slide or to develop or release any functionality mentioned on this slide. This slide and SAP's strategy and possible future developments are subject to change and may be changed by SAP at any time for any reason without notice. This document is provided without a warranty of any kind, either express or implied, including but not limited to, the implied warranties of merchantability, fitness for a particular purpose, or non-infringement.. © 2015 SAP SE or an SAP affiliate company. All rights reserved.. Early Knowledge Transfer. Customer. 75.

(71) Open Item Management in Central Finance. Open items are replicated into Central Finance. To avoid duplication of effort to pay/clear, there are the following options: Local Open item. Central Finance SLT. Open item. Clearing. Tech Cleared. Local. Central Finance SLT. Open item. Open item SLT. Clearing. Clearing. Local Open item Tech Cleared. Central Finance SLT. Open item. Replicate open item and automatically/technically clear in Central Finance •. Available as of 1503. •. Continued open item management in source system. Not suitable for central reporting or central processing (since clearing status not correct). Replicate open item and clearing status in Central Finance. Centralization of finance operations reporting and central process orchestration. •. Continued open item management in source system. •. A/R and A/P reporting (cross-system view of customer or vendor account). •. For restrictions and further information, please see note 2292043. •. Central Disputes, Collections, Invoice Mgmt, Credit, Shared Services. •. Local clearing processes optimized based on central clearing advices**. Replicate open item and automatically/technically clear in Central Finance •. **Not yet available. •. Centralized open item management in Central Finance system. Clearing •. No posting back to the source systems. Similar to existing ALE scenarios, this is a customerspecific process where consistency in certain local logistics processes has to be determined in a case-bycase analysis *ALE, RFC, other **roadmap item, not committed. SAP has no obligation to pursue any course of business outlined in this slide or to develop or release any functionality mentioned on this slide. This slide and SAP's strategy and possible future developments are subject to change and may be changed by SAP at any time for any reason without notice. This document is provided without a warranty of any kind, either express or implied, including but not limited to, the implied warranties of merchantability, fitness for a particular purpose, or non-infringement.. © 2015 SAP SE or an SAP affiliate company. All rights reserved.. Early Knowledge Transfer. Customer. 76.

(72) Central process execution for AP / AR processes Central Finance. Business Values. Credit, Collections, Disputes. Reducing the number of external bank accounts / fees. Central Payments. Central Internal Payment. ERP. BANKS. Central External Payment Open Item. Open items technically cleared in source system via report. Bank statements processed in Central System. Open Item. Limit credit charges in case of overdraft. Central Incoming Payment. Bundle external payments and save charges on cross border payments SAP HANA. Real status of open item tracked in Central Finance system. Centralize payment knowledge and optimize process in shared service center. Bank connections maintained in CF system (optional SAP MDG). HANA optimization of payment proposal generation All open item related processes must be executed in Central Finance instance as well (example: dunning, collections, disputes) When logistics processes need data, they must be changed to pint to Central Finance to avoid inconsistencies. Use SAP Standard interface for uploading bank statements to a central platform Monitoring of bank communications and transactions. *Needed for direct bank connectivity SAP has no obligation to pursue any course of business outlined in this slide or to develop or release any functionality mentioned on this slide. This slide and SAP's strategy and possible future developments are subject to change and may be changed by SAP at any time for any reason without notice. This document is provided without a warranty of any kind, either express or implied, including but not limited to, the implied warranties of merchantability, fitness for a particular purpose, or non-infringement.. © 2015 SAP SE or an SAP affiliate company. All rights reserved.. Early Knowledge Transfer. Customer. 77.

(73) Strategy for Go Live 1. Initial Load Central Finance. Source System Test system (copy of PROD). 2 SLT. Test system. Test system. 3. Initial Load. 4 Source System PROD. Central Finance. 5. 6. © 2015 SAP SE or an SAP affiliate company. All rights reserved.. Initial Load SLT PROD. Early Knowledge Transfer. PROD system. Customer. 78.

(74) Lesson Summary. You should now be able to  Judge whether Central Finance would be an approach to adopt S/4 HANA for a customer without disrupting the existing system landscape  Explain howCentral Finance can be used as a harmonized Reporting and Planning Platform  Discuss with a customer a possible roadmap of how to centralize processes in future  Design with the customer how master data could be harmonized in the Central Finance system. © 2015 SAP SE or an SAP affiliate company. All rights reserved.. Early Knowledge Transfer. Customer. 79.

(75)

No results found