SAP Business One integration for SAP NetWeaver (B1iSN 8.8)

SAP Business One integration for SAP NetWeaver (B1iSN 8.8) Liquidity Forecasting Bastian Schäfer SAP Business One Integration June 2010

Agenda 1. Scenario Overview Liquidity Forecasting 1.1. Purpose and Benefits 1.2. SAP Applications and user roles 2. Detailed Process Description 3. System Configuration 3.1. Settings in SAP ERP ECC6.0 3.2. Settings in SAP Business One 8.8 3.3. Settings in SAP B1iSN 8.8 4. Recorded Demo SAP 2010 / Page 2

1. Scenario Overview Liquidity Forecasting Purpose and Benefits: Benefits Liquidity Forecasting gathers cash management information from multiple subsidiaries, located in different SAP Business One systems, and provides that information to a central SAP ERP system located at the headquarters. Purpose Liquidity Forecasting provides central information on the current state of your bank accounts. It also provides an overview of the mid term financial situation based on memo records and the posted invoices (both outgoing and incoming) of all subsidiaries. It is the starting point for cash concentration where the balances from various bank accounts are concentrated in one target account, taking minimum balances and payment optimization into consideration. The example in this document shows a posting process that affects liquidity (customer invoice and incoming payment). It presents the main functions for connecting subsidiaries to headquarters and exchanging information to compile a central short term and mid term forecast. Key process flows covered Collection of cash management status analysis in different subsidiaries Send datasets of different subsidiaries via B1iSN to headquarters Retrieve and concentrate subsidiary data in headquarters SAP 2010 / Page 3

1. Scenario Overview Liquidity Forecasting SAP Applications Required: Required SAP Business One 8.8 integration for SAP NetWeaver (B1iSN 8.8) SAP ERP ECC6.0 SAP Business One 8.8 SAP Best Practices Deliverables Configuration guide System Landscape setup (B1iSN 8.8) Configuration guide Liquidity Forecasting (B1iSN 8.8) Additional information about Liquidity Forecasting SAP Best Practices for Cash Management, see the documentation for the Building Block Cash Management (160). SAP Best Practice for Business Network Integration, documentation for Building Block Liquidity Forecasting (806). Company roles involved in process flows Treasurer (Headquarters) Accountant Payables (Subsidiary) Accountant Receivables (Subsidiary) Bank Accountant (Subsidiary) SAP 2010 / Page 4

2. Detailed Process Description Liquidity Forecasting Detailed Process Description: Subsidiary: Posting of a vendor invoice in local and foreign currency Subsidiary: Posting of a customer invoice in local currency (from a sales order) Subsidiary: After posting the bank statement and processing the payment and collection run, the flow between the planning levels will be demonstrated. Subsidiary: (optional) Import bank statement (electronic bank statement) Send selection to headquarters by scheduler in B1iSN 8.8 (daily, weekly or monthly) Headquarters: Retrieve selection via IDoc Headquarters: Evaluate status and take appropriate action 4 1 Headquarters 2 House Bank 3 3 Information Collection Subsidiary 1 Subsidiary 2 1 1 2 2 House Bank S1 House Bank S2 SAP 2010 / Page 5

2. Detailed Process Description Liquidity Forecasting House Bank Subsidiary Headquarters Liquidity Forecasting Provide bank statement Receive/post payment file Receive/post bank statement Post accounts payable invoice Perform financial overview report (optional) Create/send liquidity forecast data Perform financial overview report Post accounts payable invoice Receive liquidity forecast data from subsidiaries Check completeness of data from all subsidiaries Perform financial overview report Analyze liquidity situation Create/send payment file SAP 2010 / Page 6

2. Detailed Process Description Liquidity Forecasting Event Manual Planning Payables / Receivables Posting Bank Statement Financial Overview Import/Post Bank Statement Bank Accountant in Subsidiary Post Memo Record Post Accounts Payable Invoice Post Outgoing Payments Post Accounts Receivable Invoice Perform Financial Overview (optional) Create/send liquidity forecast data Receive liquidity forecast data Post Accounts Payable Invoice Treasurer in HQ Post Memo Record Post Accounts Receivable Invoice Check completeness of delivered data Perform Financial Overview Analyze liquidity situation SAP 2010 / Page 7

3. System Configuration 3.1 Settings in SAP ERP ECC6.0 Prerequisites You have successfully defined and set up the reporting structure for the headquarters Cash Management - Liquidity Forecasting approach in your SAP ERP system, including the planning groups and the planning levels with which your SAP Business One subsidiaries must comply. Basically, all involved subsidiaries should be defined as company in the headquarters system with unique Company Codes. For more information about SAP Best Practices for Cash Management, see the documentation for the Building Block Cash Management (160). http://help.sap.com SAP Best Practices Baseline packages The setup and configuration of your SAP ERP system enables the integration process flow and consists of the following steps: Setting up the cross-company codes (SPRO) Maintaining the distribution model (BD64) Generating and changing partner profiles (BD82, WE20) Checking the relevant Planning Levels (OT14) Checking the relevant Planning Groups (OT13) Maintaining mapping rules to convert Sender Company Code (mandatory) (FF$A) Maintaining mapping rules to convert Sender (Planning) Level (mandatory) (FF$C) Maintaining mapping rules to convert Sender (Planning) Group (mandatory) (FF$B) SAP 2010 / Page 8

3. System Configuration 3.2 Settings in SAP Business One 8.8 Prerequisite You have upgraded to SAP Business One 8.8 SP0 PL06 to support the Planning Level and Planning Group fields. You have determined, with the help of the person responsible for the central treasury management in the headquarters SAP ERP, all planning levels and planning groups that have to be applied to a subsidiary s cash accounts and business partner. Maintain Planning Groups for Business Partner The business partner s A/P and A/R invoice postings have to be subsumed in the headquarters SAP ERP cash management report by the planning group. Accordingly, you have to maintain the planning group relevant for cash management reporting in your subsidiaries business partners. Maintain Planning Level for Cash Accounts The cash management accounts have to be subsumed in the headquarters SAP ERP cash management report by the planning level. Accordingly, you have to maintain the planning level relevant for cash management reporting in your subsidiaries cash accounts. Maintain Planning Level for Control Accounts The cash management accounts have to be subsumed in the headquarters SAP ERP cash management report by the planning level. Accordingly, you have to maintain the planning level relevant for cash management reporting in your subsidiaries control accounts. SAP 2010 / Page 9

3. System Configuration 3.3 Settings in B1iSN 8.8 Prerequisite You have set up the system landscape for your sending and receiving systems in your SAP ERP, as well as in the SAP Business One Integration Application Explorer (iapp) on your B1iSN 8.8 integration server. You have assigned the system landscape entries to the Subsidiary Integration iapp. Maintain System ID-specific properties for Subsidiaries (SAP Business One) System ID-specific properties are defined per system type. When you create a system landscape entry, an instance is created with a unique system ID (SysID). Per SysID, you can maintain fixed values for these properties. These values are accessed during the runtime phase and are used in message processing for different purposes, such as automatic defaulting, option selection, and so on. Maintain property Company Code for each SysID representing a SAP Business One system. Define a Business Package (Instance) for Liquidity Forecasting You have to set up an instance for BizPackage Liquidity Forecasting in BizArea FSCM to define the business integration process for liquidity forecasting from the SAP Business One system(s) in your subsidiaries to your headquarters SAP ERP system. Process and activate the Business Package (Instance) After you have set up the BizPackage instance for a concrete sender and receiver system combination, the BizPackage instance is ready to process the integration message flow. To enable the message process flow, you have to activate the BizPackage instance. SAP 2010 / Page 10

Recorded Demo Demo SAP 2010 / Page 11

Thank you! Bastian Schäfer SAP Business One Integration June 2010 SAP 2010 / Page 12

Disclaimer The information in this document is proprietary to SAP. No part of this document may be reproduced, copied, or transmitted in any form or for any purpose without the express prior written permission of SAP AG. This document is a preliminary version and not subject to your license agreement or any other agreement with SAP. This document contains only intended strategies, developments, and functionalities of the SAP product and is not intended to be binding upon SAP to any particular course of business, product strategy, and/or development. Please note that this document is subject to change and may be changed by SAP at any time without notice. SAP assumes no responsibility for errors or omissions in this document. SAP does not warrant the accuracy or completeness of the information, text, graphics, links, or other items contained within this material. 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. SAP shall have no liability for damages of any kind including without limitation direct, special, indirect, or consequential damages that may result from the use of these materials. This limitation shall not apply in cases of intent or gross negligence. The statutory liability for personal injury and defective products is not affected. SAP has no control over the information that you may access through the use of hot links contained in these materials and does not endorse your use of third-party Web pages nor provide any warranty whatsoever relating to third-party Web pages. SAP 2010 / Page 13

Copyright 2010 SAP AG 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 AG. The information contained herein may be changed without prior notice. Some software products marketed by SAP AG and its distributors contain proprietary software components of other software vendors. SAP, R/3, mysap, mysap.com, xapps, xapp, SAP NetWeaver, Duet, Business ByDesign, ByDesign, 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 and associated logos displayed are the trademarks of their respective companies. Data contained in this document serves informational purposes only. National product specifications may vary. The information in this document is proprietary to SAP. This document is a preliminary version and not subject to your license agreement or any other agreement with SAP. This document contains only intended strategies, developments, and functionalities of the SAP product and is not intended to be binding upon SAP to any particular course of business, product strategy, and/or development. SAP assumes no responsibility for errors or omissions in this document. SAP does not warrant the accuracy or completeness of the information, text, graphics, links, or other items contained within this material. 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. SAP shall have no liability for damages of any kind including without limitation direct, special, indirect, or consequential damages that may result from the use of these materials. This limitation shall not apply in cases of intent or gross negligence. The statutory liability for personal injury and defective products is not affected. SAP has no control over the information that you may access through the use of hot links contained in these materials and does not endorse your use of third-party Web pages nor provide any warranty whatsoever relating to third-party Web pages 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 AG nicht gestattet. In dieser Publikation enthaltene Informationen können ohne vorherige Ankündigung geändert werden. Einige von der SAP AG und deren Vertriebspartnern vertriebene Softwareprodukte können Softwarekomponenten umfassen, die Eigentum anderer Softwarehersteller sind. SAP, R/3, mysap, mysap.com, xapps, xapp, SAP NetWeaver, Duet, Business ByDesign, ByDesign, PartnerEdge und andere in diesem Dokument erwähnte SAP-Produkte und Services sowie die dazugehörigen Logos sind Marken oder eingetragene Marken der SAP AG in Deutschland und in mehreren anderen Ländern weltweit. Alle anderen in diesem Dokument erwähnten Namen von Produkten und Services sowie die damit verbundenen Firmenlogos sind Marken der jeweiligen Unternehmen. Die Angaben im Text sind unverbindlich und dienen lediglich zu Informationszwecken. Produkte können länderspezifische Unterschiede aufweisen. Die in diesem Dokument enthaltenen Informationen sind Eigentum von SAP. Dieses Dokument ist eine Vorabversion und unterliegt nicht Ihrer Lizenzvereinbarung oder einer anderen Vereinbarung mit SAP. Dieses Dokument enthält nur vorgesehene Strategien, Entwicklungen und Funktionen des SAP -Produkts und ist für SAP nicht bindend, einen bestimmten Geschäftsweg, eine Produktstrategie bzw. -entwicklung einzuschlagen. SAP übernimmt keine Verantwortung für Fehler oder Auslassungen in diesen Materialien. SAP garantiert nicht die Richtigkeit oder Vollständigkeit der Informationen, Texte, Grafiken, Links oder anderer in diesen Materialien enthaltenen Elemente. Diese Publikation wird ohne jegliche Gewähr, weder ausdrücklich noch stillschweigend, bereitgestellt. Dies gilt u. a., aber nicht ausschließlich, hinsichtlich der Gewährleistung der Marktgängigkeit und der Eignung für einen bestimmten Zweck sowie für die Gewährleistung der Nichtverletzung geltenden Rechts. SAP übernimmt keine Haftung für Schäden jeglicher Art, einschließlich und ohne Einschränkung für direkte, spezielle, indirekte oder Folgeschäden im Zusammenhang mit der Verwendung dieser Unterlagen. Diese Einschränkung gilt nicht bei Vorsatz oder grober Fahrlässigkeit. Die gesetzliche Haftung bei Personenschäden oder die Produkthaftung bleibt unberührt. Die Informationen, auf die Sie möglicherweise über die in diesem Material enthaltenen Hotlinks zugreifen, unterliegen nicht dem Einfluss von SAP, und SAP unterstützt nicht die Nutzung von Internetseiten Dritter durch Sie und gibt keinerlei Gewährleistungen oder Zusagen über Internetseiten Dritter ab. Alle Rechte vorbehalten. SAP 2010 / Page 14