sap accounting powered by sap hana plenary-141124140529-conversion-gate01

44

Upload: nmike

Post on 08-Nov-2015

34 views

Category:

Documents


4 download

DESCRIPTION

SAP Hana

TRANSCRIPT

Session Title

R 150G 140B 140R 213G 209B 209R 0G 176B 240R 292G 0B 0R 255G 192B 0R 234G 40B 57R 123G 167B 157R 146G 208B 80R 60G 61B 62R 7G 43B 128SAP Accounting powered by SAP HANA Moving Controlling and Finance Closer TogetherJanet SalmonSAP AG 2014 ERP Corp. All rights reserved.R 150G 140B 140R 213G 209B 209R 0G 176B 240R 292G 0B 0R 255G 192B 0R 234G 40B 57R 123G 167B 157R 146G 208B 80R 60G 61B 62R 7G 43B 128Introduction3The vision for SAP Accounting powered by SAP HANASAP Accounting powered by SAP HANA No More AggregatesA Common P&L: Linking FI and CO line itemsAccount-based CO-PA: Changes to report revenue and cost of goods sold by the CO-PA dimensions Enhancements to provide the necessary detailAllocations and Top-Down Distribution: How overhead is captured and allocated from cost centers to CO-PA dimensionsTop-Down distribution to disaggregate revenues and costs Work in Process: New reports and new approaches at period closeR 150G 140B 140R 213G 209B 209R 0G 176B 240R 292G 0B 0R 255G 192B 0R 234G 40B 57R 123G 167B 157R 146G 208B 80R 60G 61B 62R 7G 43B 128TopicsSAP Accounting powered by SAP HANA Removing RedundancyReducing Reconciliation EffortWhy Account-Based CO-PA?What Happens to the Allocations?WIP, Variances, and Results AnalysisSummary4Start of first section:List the main points in your presentation and insert this slide at the start of each new topic. Move the highlighted box down for each new section. This divides your presentation into easy to follow sections.

R 150G 140B 140R 213G 209B 209R 0G 176B 240R 292G 0B 0R 255G 192B 0R 234G 40B 57R 123G 167B 157R 146G 208B 80R 60G 61B 62R 7G 43B 128One atomic copy of data for Transactions + Analysis, all in MemoryEliminate unnecessary complexity and latencyLess hardware to manageAccelerate through innovation, simplification + in-memory3 copies of data in different data modelsInherent data latencyPoor innovation leading to wastageTransactions + Analysis + Acceleration processes separated

SAP HANA(DRAM)

TransactETLAnalyze

ETLHasso Plattner and Real-time Business

A Common Database Approach for OLTP and OLAP Using an In-Memory Column DatabaseHasso PlattnerAccelerate

Cache

VSR 150G 140B 140R 213G 209B 209R 0G 176B 240R 292G 0B 0R 255G 192B 0R 234G 40B 57R 123G 167B 157R 146G 208B 80R 60G 61B 62R 7G 43B 1283 copies of dataIn different data modelsInherent data latencyAccelerate through cache

In recent years, computer systems have increased number of processing cores with large integrated caches. Main memory space has become practically unlimited with the ability to hold all the business data of enterprises of every size. Falling prices have moved processing from Disk/SSD to In-Memory.Memory access is 1M 10M times faster than disk.

Disk-centric computing was also one of the major factors that forced separation of transactional and analytical workloads. Moving data to various locations was necessary for reporting to circumvent network issues. Pre-processing of data then became the necessity to optimize linear data transfers. We do not have to live with those limitations any more. Feasibility is given.

Through advances in data sciences combined with relevant hardware trends, SAP is leading the real-time computing revolution leveraging the power of in-memory computing to bringing OLAP and OLTP back together in one database.

This transforms how we construct business applications and our expectations in consuming them. Adopting this new technology will sharpen your competitive edge by dramatically accelerating not only data querying speed but also business processing speed.

5The Vision for SAP Accounting powered by SAP HANAUser experienceSingle source of truthOne source for financial and management accountingBeautiful user interfacesAvailability on multiple devices

Line item based and extensibleNot limited by totals or pre-configurationHighest granularity

Fast and flexibleBeautiful user interfacesApps for improved quality

Reporting & analysisAccelerated month-end closing processes and postingsIntra-month processes andsimulations

Closing on the flyConsolidation methods on the flyBasis for comprehensive ConsolidationNo data replication necessary

Consolidation *

* plannedR 150G 140B 140R 213G 209B 209R 0G 176B 240R 292G 0B 0R 255G 192B 0R 234G 40B 57R 123G 167B 157R 146G 208B 80R 60G 61B 62R 7G 43B 128What are the capabilities of an accounting system based on SAP HANA ?

There is only one single source of truth for Financial and Managerial Accounting. All General Ledger will be stored in one repository, the revenue and cost part of the P&L has all relevant detail like as to customers, products and regions.

The processing and analysis is based on line items rather than pre-configured totals. Thus you have the highest granularity available, your analysis is not restricted by first setting up aggregates in order to evaluate data fast enough. The aggregates would limit the kind of analysis you can do fast. With HANA you can do all analysis fast, you have all dimensions available which you have in your line items.

The solution is easy to adapt. Any number of customer specific dimensions can be added consistently in Accounting. Some industries like banking and insurance see more and more regulations, which require to add fields to accounting, sometimes 30 or even 80 fields.

Reporting based on this data is fast and flexible. State of the art BI frontend tools can be used for operational reporting, thus the benefits of BI tools are inherited to the transactional system.

The month end closing process is accelerated, some steps can even be run on a daily/weekly basis rather than just at period end. Thus the accounting system can give you insight on a daily/weekly basis.

Finally consolidations could also be run on the original accounting data. Data replication would become obsolete, some consolidation functionality could even be run on the fly in reporting.

! Achtung Demo ! Receivables Manager6Three Financial Offerings Today

AnyDBClientSAP Business SuiteSAP ERP FinanceBusiness Suiteon SAP HANASAP HANA DBSAP Business SuiteBW SAP HANA DB ERP Business SuiteFinancials Add-On for SAP Business Suite powered by SAP HANA

Client Financials Add-OnBWAppsEhP 7EhP 7ClientAny DBBased on InMemory Technology (e.g. HANA)FinanceFinance incl.AcceleratorsAppsR 150G 140B 140R 213G 209B 209R 0G 176B 240R 292G 0B 0R 255G 192B 0R 234G 40B 57R 123G 167B 157R 146G 208B 80R 60G 61B 62R 7G 43B 1287TopicsSAP Accounting powered by SAP HANARemoving RedundancyReducing Reconciliation EffortWhy Account-Based CO-PA?What Happens to the Allocations?WIP, Variances and Results AnalysisSummary8Start of first section:List the main points in your presentation and insert this slide at the start of each new topic. Move the highlighted box down for each new section. This divides your presentation into easy to follow sections.

R 150G 140B 140R 213G 209B 209R 0G 176B 240R 292G 0B 0R 255G 192B 0R 234G 40B 57R 123G 167B 157R 146G 208B 80R 60G 61B 62R 7G 43B 128Materialized Aggregates (Totals and Index Tables) Real WorldProcesse.g. InvoiceCODocumentFIDocumentTotals & Indices

Financial AccountingTotals & Indices

Management Account.ERP Financials any classic DBFinancials powered by HANAStabilityProcessingAnalyticsReal WorldProcesse.g. InvoiceCO DocumentFI DocumentFlexibilityProcessingTotals for Financial AccountingTotals for Management AccountingHANA views on the flyPre-Defined Aggregates

Flexibility

StabilityAnalyticshttp://www.saphana.com/community/blogs/blog/authors/D000002Data RedundancyReconciliation EffortMinor Flexibility

Higher ThroughputReduced ReconciliationHigher FlexibilityReduced Data VolumeHigh PerformanceR 150G 140B 140R 213G 209B 209R 0G 176B 240R 292G 0B 0R 255G 192B 0R 234G 40B 57R 123G 167B 157R 146G 208B 80R 60G 61B 62R 7G 43B 128ThroughputBoost data throughput by overcoming the lock issue and reducing data volume to be posted(Non)-ReconcialitionNo reconciliation because of One DocumentFlexibilityOne starting point to extend and adapt simply and straightforwardlyData VolumeReduce data volume dramatically by eliminating redundanciesPerformance Expectation: achieve identical response times as before plus optimize9

Avoiding Redundancy in FI: Non Disruptive with Equally Named Views For Previous Total/Index Tables

10

R 150G 140B 140R 213G 209B 209R 0G 176B 240R 292G 0B 0R 255G 192B 0R 234G 40B 57R 123G 167B 157R 146G 208B 80R 60G 61B 62R 7G 43B 128The basis tables BKPF, BSEG/BSEG_ADD and FAGLFLEXA remain almost unchanged. Index and totals tables have been replaced with compatibility views (aka equally named views). These views have the same name as the original tables, contain the same fields and shall allow for a smooth transition to the new data model in the standard as well as in the partner and customer coding.

10Views Replace DDIC Tables (GLT0)

ABAP Programs that previously read table GLT0 now select directly from BSEGBack up tables (GLT0_BCK) are used during the migration progress R 150G 140B 140R 213G 209B 209R 0G 176B 240R 292G 0B 0R 255G 192B 0R 234G 40B 57R 123G 167B 157R 146G 208B 80R 60G 61B 62R 7G 43B 128

Avoid Redundancy in CONon-disruptive with equally named views for previous total tables

R 150G 140B 140R 213G 209B 209R 0G 176B 240R 292G 0B 0R 255G 192B 0R 234G 40B 57R 123G 167B 157R 146G 208B 80R 60G 61B 62R 7G 43B 128

Views Replace DDIC Tables (COSP)ABAP Programs that previously read table COSP now select directly from COEPBack up tables (COSP_BAK) are used during the migration progress and for non-redundant data, e.g. commitments R 150G 140B 140R 213G 209B 209R 0G 176B 240R 292G 0B 0R 255G 192B 0R 234G 40B 57R 123G 167B 157R 146G 208B 80R 60G 61B 62R 7G 43B 128

Other Aggregates: Summarization ReportsSummarization reports are used to summarize values according to hierarchical structures defined by your organization. This makes it possible to analyze values and quantities at higher levels, such as at plant level A summarization hierarchy is used to summarize the values of the following objects:Maintenance and service orders Internal orders Projects

Sales orders and their items Manufacturing orders, QM orders, and PCC

R 150G 140B 140R 213G 209B 209R 0G 176B 240R 292G 0B 0R 255G 192B 0R 234G 40B 57R 123G 167B 157R 146G 208B 80R 60G 61B 62R 7G 43B 128Summarization: Before and After

Goal: Remove VD* objects from tablesGoal: Aggregate along hierarchy on the flyR 150G 140B 140R 213G 209B 209R 0G 176B 240R 292G 0B 0R 255G 192B 0R 234G 40B 57R 123G 167B 157R 146G 208B 80R 60G 61B 62R 7G 43B 128TopicsSAP Accounting powered by SAP HANARemoving RedundancyReducing Reconciliation Effort Why Account-Based CO-PA?What Happens to the Allocations?WIP, Variances, and Results AnalysisSummary16Start of first section:List the main points in your presentation and insert this slide at the start of each new topic. Move the highlighted box down for each new section. This divides your presentation into easy to follow sections.

R 150G 140B 140R 213G 209B 209R 0G 176B 240R 292G 0B 0R 255G 192B 0R 234G 40B 57R 123G 167B 157R 146G 208B 80R 60G 61B 62R 7G 43B 128Reducing Reconciliation: Logical DocumentBalance Sheet AccountsProfit and Loss Accountse.g. Payroll, COGS, RevenuePrimary Cost Elementse.g. Payroll by Cost Center, COGS & Revenue by CO-PA DimensionsSecondary Cost Elements e.g. profit center boundaries are crossedOne to one link by line itemSecondary Cost Elementse.g. no change to profit centersReal Time Integration AccountsAccount extended by CO dimension(s)Different account granularitySwitch in account structureR 150G 140B 140R 213G 209B 209R 0G 176B 240R 292G 0B 0R 255G 192B 0R 234G 40B 57R 123G 167B 157R 146G 208B 80R 60G 61B 62R 7G 43B 128Balance Sheet Accounts are typically independent of CO whereas Profit and Loss Accounts generally include a CO account assignment. All profit and loss accounts are now linked to their equivalent postings in CO. This means that all profit and loss items are effectively one long posting string with fields from the BSEG table, fields from the COEP table and in the case of CO-PA (revenue and COGS postings) dimensions from the CE4 table.Taking the example of Payroll Accounts, two types of posting are possible an allocation that crosses dimensions in FI (profit center, business area,) and an allocation that has no impact in CO. Allocations that cross FI dimensions are captured via Real Time Integration. Again these documents are linked and can be reported, but there is a transformation from the CO cost element to the FI account. Other allocations are only in the COEP table. The logical document allows you to select not just those accounts with a link but also the balance sheet accounts and secondary cost elements with no link to FI.17Harmonized Internal and External Reporting SAP ERP Financials Postings to FI and COManagement Accounting Cost and revenue relevant postings create line items for P&L accounts in FI and cost elements in CO. FI line items are often aggregated compared to CO line items. Even if posted with the same granularity, there is no link on line-item level. This makes reconciliation of FI versus CO difficult. FI and CO documents are only linked on header level.MMSDHRPPHeader Table

COEPCOBKLine Item TableCO line item nr. 123

Cost element: 400000100 DRCost center: ABKPFBSEGFI line item nr. 10

Vendor:4711 100 CRCost account: 400000100 DR - Header TableLine Item TableFinancial AccountingMM = Material MgmtSD = Sales & DistributionPP = Production PlanningHR = Human ResourcesNo linkbetweenFI andCO lineitems inSAP ERP1:1R 150G 140B 140R 213G 209B 209R 0G 176B 240R 292G 0B 0R 255G 192B 0R 234G 40B 57R 123G 167B 157R 146G 208B 80R 60G 61B 62R 7G 43B 128All cost or revenue relevant postings in HR, MM, PP, SD like good issues, material consumption, creation of a billing document for a sales order result in a posting of a line item in Financial Accounting at the relevant profit and loss accounts. This line item is stored in the line item table BSEG. The header data for this document are stored in the table BKPF.

At the same time this posting data are also transfered as costs or revenues to Management Accounting. A specific CO line item is posted and stored in the line item table COEP. The header data for this CO document are stored in the table COBK.

Up to now there is no link between the FI line item and the CO line item on the level of the line item tables COEP and BSEG. There is only a link between the document headers: the tables COBK and BKPF are linked to each other.

This leads to a high reconciliation effort between FI and CO, because it is hard to reconcile documents of different granularity e.g. payroll records with more FI items than CO items. Overall reporting bringing together the legal view with details of responsibility and/ or market segments on a glance is not yet available. The lack of a link on line item level makes reporting and reconciliation cross the financial applications difficult especially between FI and CO-PA.5 With SAP Accounting powered by SAP HANA, the FI and CO line items are stored on the same level of granularity and are linked 1:1. This facilitates an easy reconciliation and drill-down to full detail in reporting. MMSDHRPPHeader Table

COEPCOBKLine Item TableCO line item nr. 123

Cost element: 400000100 DRCost center: ABKPFBSEGFI line item nr. 10

Vendor:4711100 CRCost account: 400000100 DRHeader TableLine Item TableManagement AccountingFinancial AccountingNEW1:11:1Samegranularityof line itemsand 1:1 linkin SmartAccountingHarmonized Internal and External Reporting SAP Accounting powered by SAP HANA Postings to FI and COR 150G 140B 140R 213G 209B 209R 0G 176B 240R 292G 0B 0R 255G 192B 0R 234G 40B 57R 123G 167B 157R 146G 208B 80R 60G 61B 62R 7G 43B 128All cost or revenue relevant postings in HR, MM, PP, SD like good issues, material consumption, creation of a billing document for a sales order result in a posting of a line item in Financial Accounting at the relevant profit and loss accounts. This line item is stored in the line item table BSEG. The header data for this document are stored in the table BKPF.

At the same time this posting data are also transfered as costs or revenues to Management Accounting. A specific CO line item is posted and stored in the line item table COEP. The header data for this CO document are stored in the table COBK.

Up to now there is no link between the FI line item and the CO line item on the level of the line item tables COEP and BSEG. There is only a link between the document headers: the tables COBK and BKPF are linked to each other.

This leads to a high reconciliation effort between FI and CO, because it is hard to reconcile documents of different granularity e.g. payroll records with more FI items than CO items. Overall reporting bringing together the legal view with details of responsibility and/ or market segments on a glance is not yet available. The lack of a link on line item level makes reporting and reconciliation cross the financial applications difficult especially between FI and CO-PA.5Extensions to the CO Line Item Table (1)

COEP line items contain a link to the source line item in FI (profit and loss items) or to the real-time integration postings in FI R 150G 140B 140R 213G 209B 209R 0G 176B 240R 292G 0B 0R 255G 192B 0R 234G 40B 57R 123G 167B 157R 146G 208B 80R 60G 61B 62R 7G 43B 128 MMSDHRPPHeader Table

COEPCOBKLine Item TableCO line item nr. 123

Cost element: 800000100 CRCO-PA Object No. 4711BKPFBSEGFI line item nr. 10

Receivables100 DRRevenues (acc. 800000)100 CRHeader TableLine Item TableManagement AccountingFinancial AccountingNEWCE4xxxxAccount-basedProfitability Analysis (CO-PA) CO-PA Object number: 4711 Material: F-01 Material group: FERT Sales org.: S001NEW Each CO lineitem for primary postings includes aconsistent object number from CO-PAfor improved multi-dimensional P&L reporting.Harmonized Internal and External ReportingSAP Accounting powered by SAP HANA CO and Account-Based CO-PAR 150G 140B 140R 213G 209B 209R 0G 176B 240R 292G 0B 0R 255G 192B 0R 234G 40B 57R 123G 167B 157R 146G 208B 80R 60G 61B 62R 7G 43B 128All cost or revenue relevant postings in HR, MM, PP, SD like good issues, material consumption, creation of a billing document for a sales order result in a posting of a line item in Financial Accounting at the relevant profit and loss accounts. This line item is stored in the line item table BSEG. The header data for this document are stored in the table BKPF.

At the same time this posting data are also transfered as costs or revenues to Management Accounting. A specific CO line item is posted and stored in the line item table COEP. The header data for this CO document are stored in the table COBK.

Up to now there is no link between the FI line item and the CO line item on the level of the line item tables COEP and BSEG. There is only a link between the document headers: the tables COBK and BKPF are linked to each other.

This leads to a high reconciliation effort between FI and CO, because it is hard to reconcile documents of different granularity e.g. payroll records with more FI items than CO items. Overall reporting bringing together the legal view with details of responsibility and/ or market segments on a glance is not yet available. The lack of a link on line item level makes reporting and reconciliation cross the financial applications difficult especially between FI and CO-PA.5Extensions to the CO Line Item Table (2)COEP line items contain a link to the CE4 table where the CO-PA dimensions are stored. COEP line items break out the CO object number by account assigment for easier reporting.

R 150G 140B 140R 213G 209B 209R 0G 176B 240R 292G 0B 0R 255G 192B 0R 234G 40B 57R 123G 167B 157R 146G 208B 80R 60G 61B 62R 7G 43B 128Reporting Architectural OverviewHANA Views on Financials Logical DocumentBSEG/BKPFCOEP/COBKCE4SFINCrystal ReportsAnalysis OfficeFiori Apps. . .Financials Logical DocumentReporting InterfacesEmbedded BW (queries)Master DataR 150G 140B 140R 213G 209B 209R 0G 176B 240R 292G 0B 0R 255G 192B 0R 234G 40B 57R 123G 167B 157R 146G 208B 80R 60G 61B 62R 7G 43B 128Sample Report: Income Statement

R 150G 140B 140R 213G 209B 209R 0G 176B 240R 292G 0B 0R 255G 192B 0R 234G 40B 57R 123G 167B 157R 146G 208B 80R 60G 61B 62R 7G 43B 128TopicsSAP Accounting powered by SAP HANARemoving RedundancyReducing Reconciliation EffortWhy Account-Based CO-PA?What Happens to the Allocations?WIP, Variances, and Results AnalysisSummary25Start of first section:List the main points in your presentation and insert this slide at the start of each new topic. Move the highlighted box down for each new section. This divides your presentation into easy to follow sections.

R 150G 140B 140R 213G 209B 209R 0G 176B 240R 292G 0B 0R 255G 192B 0R 234G 40B 57R 123G 167B 157R 146G 208B 80R 60G 61B 62R 7G 43B 128

Types of Profitability Analysis

26Profitability Analysis prior to SAP Accounting powered by SAP HANA

Costing-Based

Value Fields

Revenue 1,000,000Sales Deductions 100,000------------Net Revenue 900,000Variable Mat. Costs 400,000Variable Prod. Costs 190,000Production Variances 10,000------------Contribution Margin 1 300,000Material Overhead 50,000Production Overhead 50,000

Contribution Margin 2 200,000Res & Development 10,000Marketing Costs 50,000Administrative Costs 40,000------------Contribution Margin 3 100,000 Account-Based

Cost/Revenue Elements

800000 Revenue 1,000,000808000 Sales Deductions 100,000----------Net Revenue 900,000893000 Cost of Goods Sold 690,000

231000 Price Difference Account 10,000

651000 R & D Costs 10,000671000 Marketing Costs 50,000655000 Administrative Costs 40,000----------Operating Profit 100,000R 150G 140B 140R 213G 209B 209R 0G 176B 240R 292G 0B 0R 255G 192B 0R 234G 40B 57R 123G 167B 157R 146G 208B 80R 60G 61B 62R 7G 43B 128Changes to Cost of Goods Sold, Variances & CO-PA Quantities

Cost of Goods Sold posting >Split by Cost ComponentsVariance Posting >Split by Variance CategoryAdditional Quantities with BAdI LogicR 150G 140B 140R 213G 209B 209R 0G 176B 240R 292G 0B 0R 255G 192B 0R 234G 40B 57R 123G 167B 157R 146G 208B 80R 60G 61B 62R 7G 43B 128

Split of COGS Based on Standard Cost Components

Result in FI/CO (delivery quantity 1 pc) Costing:

CO document incl. split in fix:

28

R 150G 140B 140R 213G 209B 209R 0G 176B 240R 292G 0B 0R 255G 192B 0R 234G 40B 57R 123G 167B 157R 146G 208B 80R 60G 61B 62R 7G 43B 12828

Multiple Quantity Fields in the Line Item Tables

Quantity settings:

Three new fields in COEP -> BADI for populating fields

29

R 150G 140B 140R 213G 209B 209R 0G 176B 240R 292G 0B 0R 255G 192B 0R 234G 40B 57R 123G 167B 157R 146G 208B 80R 60G 61B 62R 7G 43B 12829

Split of Price Differences Using Variance CategoriesVariances (delivery with SP3):

account 1account 2

Standard posting would be: New posting logic with CO-PA Object:

30GBB AUA100 PRD PRF100GBB AUA100 PRD PRF100Link each line to one accountAccount 170Account 230R 150G 140B 140R 213G 209B 209R 0G 176B 240R 292G 0B 0R 255G 192B 0R 234G 40B 57R 123G 167B 157R 146G 208B 80R 60G 61B 62R 7G 43B 12830TopicsSAP Accounting powered by SAP HANARemoving RedundancyReducing Reconciliation EffortWhy Account-Based CO-PA?What Happens to the Allocations?WIP, Variances, and Results AnalysisSummary31Start of first section:List the main points in your presentation and insert this slide at the start of each new topic. Move the highlighted box down for each new section. This divides your presentation into easy to follow sections.

R 150G 140B 140R 213G 209B 209R 0G 176B 240R 292G 0B 0R 255G 192B 0R 234G 40B 57R 123G 167B 157R 146G 208B 80R 60G 61B 62R 7G 43B 128Assessment Cycles in Account-Based CO-PA

2 = account-basedAmount field used in combination with cost elements on sender tabR 150G 140B 140R 213G 209B 209R 0G 176B 240R 292G 0B 0R 255G 192B 0R 234G 40B 57R 123G 167B 157R 146G 208B 80R 60G 61B 62R 7G 43B 128Top-Down Distribution in Account-Based CO-PA33Top-down distribution in account-based CO-PA has been available since 4.7

Amount field used in combination with cost elements in selection criteriaR 150G 140B 140R 213G 209B 209R 0G 176B 240R 292G 0B 0R 255G 192B 0R 234G 40B 57R 123G 167B 157R 146G 208B 80R 60G 61B 62R 7G 43B 128TopicsSAP Accounting powered by SAP HANARemoving RedundancyReducing Reconciliation EffortWhy Account-Based CO-PA?What Happens to the Allocations?WIP, Variances, and Results AnalysisSummary34Start of first section:List the main points in your presentation and insert this slide at the start of each new topic. Move the highlighted box down for each new section. This divides your presentation into easy to follow sections.

R 150G 140B 140R 213G 209B 209R 0G 176B 240R 292G 0B 0R 255G 192B 0R 234G 40B 57R 123G 167B 157R 146G 208B 80R 60G 61B 62R 7G 43B 128

SAP Accounting powered by SAP HANA - WIP AnalysisWork in Progress (WIP)WIP positions are now available with a higher granularity that shows the underlying primary and secondary costsThe analysis is achieved by linking GL WIP line items with settlement line items via the order number in the GL line item.

R 150G 140B 140R 213G 209B 209R 0G 176B 240R 292G 0B 0R 255G 192B 0R 234G 40B 57R 123G 167B 157R 146G 208B 80R 60G 61B 62R 7G 43B 1286Select orders dataLoop each orders

EndloopUI displayABAPSelect valid ordersDo aggregationDo calculationDB updateUI displayABAPSelect valid ordersHANASelect orders dataDo aggregation for all ordersOldCode PushdownLoop aggregated data

EndloopDo calculationDB updatePeriod Close ProcessingR 150G 140B 140R 213G 209B 209R 0G 176B 240R 292G 0B 0R 255G 192B 0R 234G 40B 57R 123G 167B 157R 146G 208B 80R 60G 61B 62R 7G 43B 128In the traditional period close, the system created a list of valid orders and then looped through this order list to calculate e.g. WIP for each order in turn. This resulted in relatively small selects with an aggregation per order. This procedure did not benefit from the HANA architecture (in fact sometimes it was slower than on a classic database).In the new approach, stored procedures on HANA are used to select the valid orders, then the costs per order and to aggregate this data so that it is ready for use in the relevant calculation Instead of performing a for each order in turn the system returns to ABAP to perform the calculation on the whole data set and update the tables with the results of the calculation. This results in significant performance improvements.

36Code Pushdown ApproachResults Analysis for Sales Orders

KKAKKKAKHR 150G 140B 140R 213G 209B 209R 0G 176B 240R 292G 0B 0R 255G 192B 0R 234G 40B 57R 123G 167B 157R 146G 208B 80R 60G 61B 62R 7G 43B 128Next, I want to give you a short introduction about our approach for Code Pushdown. Lets take Results Analysis for Sales Orders as an example. In the old ABAP transaction KKAK, the system first selects objects base on user input, and then loops and processes each object individually. Now we moved the data intensive logic highlighted in yellow box to HANA, as shown in this diagram, and skipped the logic which are not capable or not perform well in HANA, such as the authorization check, complex calculation depends on customizing settings etc. 37Optimized Period Close Transactions38Settlement (plant selection) CO88 -> CO88HSettlement (make-to-order sales orders)VA88-> VA88HSettlement (internal orders) KO8G-> KO8GH Settlement (projects) CJ8G -> CJ8GH Results Analysis KKAK -> KKAKH(POC method or revenue-based)WIP Calculation at Actual Costs KKAO -> KKAOHVariance Calculation w. Full Settlement KKS1-> KKS1HVariance Calculation for Cost Centers KSS1-> KSS1H

R 150G 140B 140R 213G 209B 209R 0G 176B 240R 292G 0B 0R 255G 192B 0R 234G 40B 57R 123G 167B 157R 146G 208B 80R 60G 61B 62R 7G 43B 128TopicsSAP Accounting powered by SAP HANARemoving RedundancyReducing Reconciliation EffortWhy Account-Based CO-PA?What Happens to the Allocations?WIP, Variances, and Results AnalysisSummary39Start of first section:List the main points in your presentation and insert this slide at the start of each new topic. Move the highlighted box down for each new section. This divides your presentation into easy to follow sections.

R 150G 140B 140R 213G 209B 209R 0G 176B 240R 292G 0B 0R 255G 192B 0R 234G 40B 57R 123G 167B 157R 146G 208B 80R 60G 61B 62R 7G 43B 128ResourcesSAP Accounting powered by SAP HANA - Frequently Asked Questions Blog Posthttp://www.erpcorp.com/sap-controlling-blog/entry/sap-accounting-powered-by-sap-hana-frequently-asked-questionsJanet Salmon, Controlling with SAP Practical GuideISBN-10: 978-1-4932-1012-1https://www.sap-press.com/controlling-with-sap-practical-guide_3625/Janet Salmon and Ulrich Schlueter, SAP HANA for ERP FinancialsISBN: 978-3-943546-97-2 http://shop.espresso-tutorials.com/Gedruckte-SAP-Buecher/SAP-HANA-fuer-ERP-Financials-2-Auflage::35.htmlhttp://help.sap.com/sfin10040R 150G 140B 140R 213G 209B 209R 0G 176B 240R 292G 0B 0R 255G 192B 0R 234G 40B 57R 123G 167B 157R 146G 208B 80R 60G 61B 62R 7G 43B 128Five Key Ideas SAP Accounting powered by SAP HANA is a new product with a new code line designed specifically for use with SAP HANAGeneral availability began on August 1, 2014 SAP Accounting powered by SAP HANA uses the line items instead of the totals tables, allowing for faster updates and removing redundancySAP Accounting powered by SAP HANA links the FI line items with the CO line items to give a complete profit and loss statement containing all relevant reporting dimensions41R 150G 140B 140R 213G 209B 209R 0G 176B 240R 292G 0B 0R 255G 192B 0R 234G 40B 57R 123G 167B 157R 146G 208B 80R 60G 61B 62R 7G 43B 12841Five Key Ideas (cont.)SAP Accounting powered by SAP HANA focuses on account-based CO-PA for reconcilability, but you can continue to use costing-based CO-PA to meet other business requirementsSAP Accounting powered by SAP HANA significantly improves the period close by offering new transactions for settlement, WIP calculation, variance calculation, and results analysis42R 150G 140B 140R 213G 209B 209R 0G 176B 240R 292G 0B 0R 255G 192B 0R 234G 40B 57R 123G 167B 157R 146G 208B 80R 60G 61B 62R 7G 43B 12842QuestionsNow:Ask questions now for immediate answersLater:[email protected]&AR 150G 140B 140R 213G 209B 209R 0G 176B 240R 292G 0B 0R 255G 192B 0R 234G 40B 57R 123G 167B 157R 146G 208B 80R 60G 61B 62R 7G 43B 12843Disclaimer

SAP, R/3, mySAP, mySAP.com, xApps, xApp, SAP NetWeaver, Duet, PartnerEdge, and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG in Germany and in several other countries all over the world. All other product and service names mentioned are the trademarks of their respective companies. ERP Corp is neither owned nor controlled by SAP.

R 150G 140B 140R 213G 209B 209R 0G 176B 240R 292G 0B 0R 255G 192B 0R 234G 40B 57R 123G 167B 157R 146G 208B 80R 60G 61B 62R 7G 43B 128