Integration Framework for SAP Business One Overview

October 2017

PUBLIC

Agenda

 The Central Platform for Integrating your Company

 Introducing the Integration Framework

 Best Practices of Integration Scenarios

 Best Practices Integration Scenarios in Detail

 The Technical Aspects of the Integration Framework

 Benefits and Key Aspects of the Integration Framework

1 Integration Framework for SAP Business One Platform Capabilities

The integration framework for SAP Business One connects SAP Business One with other applications, services and devices to:

Transform SAP Business One Support SAP Business One Connect subsidiaries, branches CORE processes and with other applications and business networks functionality

Integration Framework for SAP Business One An Integral Part of the SAP Business One Solution

Low cost of ownership Expands the and support solution scope

Robust integration and collaboration

Extensibility Interface for SAP HANA apps

Covers all standard business processes

Runs on in-memory technology

Deployment flexibility

2 Integration Products at a Glance

Standard Integration Scenarios Subsidiary Integration (capability delivered with SAP Business One) (dedicated integration solutions out-of-the-box)

Dashboards, SAP mobile apps, outsourced payroll, automated Integrates SAP Business One running in subsidiaries* with SAP request for quotation, integration of web-based SAP Customer Business Suite software in headquarters’ location Checkout application, Ariba Network integration (purchase order  Data harmonization, financial consolidation, business process and invoice automation), SAP Hybris Cloud for Customer (best standardization, and supply chain optimization practice for sales side), Concur  Pre-configured scenarios for master data, sales, purchasing, HQ reporting, and finance as well as customer-specific content

Possible Integration Scenarios Intercompany Integration Solution (Integration framework as development environment) (dedicated application out-of-the-box)

Non-SAP, cloud-based extensions, electronic data interchange, Integrates different SAP Business One databases in a seamless and social networks, collaboration (business to business, business to easy to consume way: consumer), web shop, web services  Streamline and automate intercompany transactions and processes, such as master data distribution and financial consolidation

Examples of Integrating Business Networks

Companies are part of business networks. To unify the communication and reduce complexity in data exchange the integration framework for SAP Business One gives the possibility to bring dependent and independent units together.

Headquarters Vendors

Franchisees

Shared Service Center

Permanent Establishments

Subsidiaries

3 SAP Business One Integration for SAP NetWeaver

Solution for seamless integration between SAP Business One and SAP Business Suite / SAP NetWeaver or other instances of SAP Business One

● Rapidly integrates large enterprises running SAP solutions with their subsidiaries, operating divisions, trading partners and suppliers ● Provides integration of multiple installations of SAP Business One across the network ● Standardizes and unifies business processes across the business ecosystem around a single platform

Headquarters Subsidiary Manufacturing Headquarters Site

Branch Office Customer

Supplier Branch Office Customer

Business Extension Integration Scenarios

Mobile Covers 124+ Web services for mobile devices

Request for Quotation Publish quotation requests and receive electronic responses from your suppliers

Dashboards Provides generic services to launch dashboards based on SAP Crystal Dashboards

4 Intercompany Solution Integration Scenarios

Intercompany Integration Solution for SAP Business One Key Functions of Intercompany Solution

. Master Data Replication . Centralized Payments . Service Contract and Customer . Financial Data Consolidation Equipment Card Replication . Intercompany Reports . UDFs and UDTs Replication . Remote Query Execution . Intercompany Trade . Consolidated Credit Limit . Expenses Allocation among Check Branch Companies/Subsidiaries . Key Mapping Mechanism . A/P Service Invoice Allocations

Subsidiary Integration Scenarios

SAP Business One Integration for SAP NetWeaver Scenarios to integrate headquarters running SAP ECC / SAP BW / S/4HANA on Premise and SAP Business One . Master Data Distribution (Items & Business Partners) . Intercompany Purchasing . Management Reporting for Sales Analysis* . Liquidity Forecasting* . In-House Cash* . Customizing Data Distribution*

* only relevant for headquarters running SAP ECC / SAP BW

5 Integration of SAP Business One into SAP Business Suite “Headquarters uses SAP Business Suite”

SAP Business Suite Out-of-the-box scenarios

● Customizing data distribution

● Master data distribution (product & customer)

● Intercompany purchasing ● Sales from central stock (3rd party direct ship) ● Sales from local stock (subsidiary has local warehouse)

● Management reporting – sales analysis (integration into SAP BW)

● In-house cash

● Liquidity forecasting

Integration of SAP Business One into a central SAP Business One “Headquarters uses SAP Business One”

SAP Business One Out-of-the-box scenarios

● Master data distribution (item & customer)

● Intercompany purchasing ● Sales from central stock (3rd party direct ship) ● Sales from local stock (subsidiary has local warehouse)

● Financial consolidation – journal entries

6 Intercompany Purchasing  SAP Business One with SAP Business Suite Scenario Overview  SAP Business One with SAP Business One

Purpose ● This scenario enables inter-company purchasing between subsidiaries and headquarters by providing reliable data exchange and support for required logistical and financial processes across the network. ● Headquarters supplies subsidiaries with sales products, where subsidiaries act as either sales offices (Sales from Central Stock) or local distribution centers (Sales from Local Stock)

Benefits ● Cost reductions due to high amount of automation ● Accelerated sales and supply processes ● Increased visibility within the process chain

Key process flows covered ● Sales from Central Stock (subsidiary as sales office) ● Sales from Local Stock (subsidiary with own warehouse)

Summary

SAP Business One integration for SAP NetWeaver Headquarters Subsidiaries Plus Business Integration Scenarios: ● SAP Business Suite/ ● Customizing data distribution ● SAP Business One SAP NetWeaver ● Master data distribution (product, customer) ● Tailored for small ● Tailored for business ● Intercompany puchasing (sales from central and local stock) standardized and ● Localized and adapted to ● Management reporting, sales analysis into SAP BW sophisticated processes local regulations ● Consolidation and group ● In-house cash ● SAP Best Practices reporting

ALE/RFC IDOC/BAPI/FCM

DI API/ JDBC SAP Business One

HTTP/SOAP Web Services SAP Business One SAP Business One File/HTTP/JDBC SAP Business Suite SAP Business All-in-One Other Integration

7 The Technical Aspects of the Integration Framework

Offline Support

Purpose ● Offline support enables SAP Business One systems to work offline from SAP Business One integration for SAP NetWeaver Headquarters ● SAP Business One systems connect to SAP Subsidiary Business One integration for SAP NetWeaver SAP NW SAP B1 for data exchange triggered by administrator or timer-based

Subsidiary Benefits SAP B1 ● Integrate subsidiaries in spite of poor connections or high connection costs

Key process flows covered ● Gather data while working offline ● Send and receive queues while online

Prerequisites ● Offline support requires a local integration framework installation with SAP Business One

8 The Integration Framework in General

The integration framework for SAP Business One is part of the SAP Business One installation:

Simple to install and runs on SAP HANA SAP Business One Server and Microsoft SQL Server Service Layer Integration Framework Can integrate SAP and non-SAP DI API DI Proxy systems, web and cloud-based SLD applications, and services Event Integration Including message and error handling, Sender Server business process control, tracking, logging, transaction control, security

Uses established integration standards

such as XML and XSLT SAP Business One Database Server

Scenario Step Processing in the Integration Framework

The integration framework is an integration and collaboration server to develop and run integration scenarios. The scenario packages consist of different scenario steps with all required data.

A scenario step consists of these phases and the data is internally processed as XML message.

Inbound Processing Outbound

XML, XSLT, XPath Sender 1 Receiver 1

Sender 2 Receiver 2

…

XML XML

XML To

Sender N From Receiver N

9 Scenario Step Building Blocks

Definitions in the step design: . Inbound and Outbound channels, e.g. SAP Business One, Database, HTTP, File, Timer, Web Service, SAP ERP . Processing Phase Inbound Processing Outbound Inbound Channels Outbound Channels XML, XSLT, XPath Sender 1 Receiver 1 Pre-defined functional units that are

Sender 2 assembled into a sequence for processing Receiver 2

…

XML XML

XML To

Sender N From Receiver N

Benefits and Key Aspects of the Integration Framework

10 Benefits and Key Aspects of the Integration Framework

Connects SAP and non-SAP systems

Supports SAP HANA platform and Microsoft SQL database

Expanding the scope of SAP Business One: - Various use cases - Best practice scenarios

All integration aspects covered in one product: - Supports Business Process Management Notation (BPMN) - Programming language addresses integration requirements

Two deployment options available: On premise and Cloud