Migrating to SAP Business One 9.

0
integration for SAP NetWeaver
August, 2014 Public
Agenda

 Integration Options
 Subsidiary Integration Installation Scope
 Main Aspects for Migration from 8.8 to 9.0
 New Integration Framework Functions to Support Subsidiary Integration
 Why Migration?
 Migration Prerequisites
 More Information and Support

© 2014 SAP SE or an SAP affiliate company. All rights reserved. Public 2

Integration Options
Integration Options
One integration framework - two deployments

SAP Business One 9.0 integration for SAP NetWeaver

(B1iSN 9.0)
 Solution especially for integration of headquarters (i.e. SAP ERP)
and SAP Business One in the subsidiaries or affiliates
 B1iSN is implemented centrally at HQ and integrates the
subsidiaries into the company‘s business processes
 B1iSN is delivered with out-of-the box integration content for the
most common business process requirements. Actually there is
also content available for integration of SAP Business One to SAP
Business One.

Integration framework of SAP Business One (B1if)

 Integration framework is integral part of SAP Business One
 Integration framework is used to run „inbuilt“ functions of SAP
Business One, such as dashboards or the mobile app
 Supports development of additional individual integration
content, for example, integration content for subsidiaries and
ecosystems
 SAP Partners can develop own and protected solutions

© 2014 SAP SE or an SAP affiliate company. All rights reserved. Public 4

Subsidiary Integration
Subsidiary Integration
Installation Scope

SAP Business One 9.0 integration

for SAP NetWeaver

Integration Framework

+
Business Integration Scenarios that
 Integrate SAP Business One running in subsidiaries with SAP Business Suite and
SAP NetWeaver components of their headquarter
 Provide data harmonization, financial consolidation, business process
standardization, and supply chain optimization

© 2014 SAP SE or an SAP affiliate company. All rights reserved. Public 6

Migrating from 8.8 to 9.0
Subsidiary Integration
Main Aspects Going from Release 8.8 to 9.0

Already familiar with the integration framework?

Check the new functions in the integration framework supporting the subsidiary
integration use case.

New to the integration framework?

Integration framework is part of the SAP Business One delivery, supporting the mobile
app, enabling the RFQ scenario, enabling dashboards, etc.
For more information, refer to the Learning Map

Connection to SAP ERP, SAP Business Warehouse,

SAP Business One
The configuration steps in the applications have not changed.

Business Integration Scenarios

The new release provides the same scenarios as the 8.8 release. They run in the
same way as before.

© 2014 SAP SE or an SAP affiliate company. All rights reserved. Public 8

New Integration Framework
Functions for Subsidiary
Integration
New Function Supporting Subsidiary Integration
Overview

To support SAP Business One integration for SAP NetWeaver, the integration
framework provides:
 Scenario administration user interfaces in English, German, French, Chinese
 System type-specific properties in SLD
 Scenario setup wizard
 Defining and setting local and global properties
 New timer-triggered database inbound
 Daily Actions
 Outbound Error Actions
 Message Log History
 For scenario development: new key expansion atom
 Support for SAP HANA, MySQL, Linux SUSE
 Offline support to occasionally connect SAP Business One systems

© 2014 SAP SE or an SAP affiliate company. All rights reserved. Public 10

New Function Supporting Subsidiary Integration
System Type-Specific Properties

System Type-Specific Properties

Choose SLD  SysType Properties.

To add your own properties,

choose Add.

You can provide a default value, a

description and enumerations.

© 2014 SAP SE or an SAP affiliate company. All rights reserved. Public 11

New Function Supporting Subsidiary Integration
Scenario Setup Wizard

To open the scenario setup wizard:

Choose Scenarios  Setup.
Choose the scenario you want to set up.

Choose .

Steps:
 Scenario step(s)
 Define global and local property values
 Sender and Receiver systems  Enter value mappings
 Enter filter definitions  Define scheduler settings
 Deploy the scenario

© 2014 SAP SE or an SAP affiliate company. All rights reserved. Public 12

New Function Supporting Subsidiary Integration
Global and Local Properties

Global and Local Properties Definitions

To define global properties choose Package Design  Definitions button and

choose Global Properties.

Define local properties in the graphical flow designer.

Choose the button.

Choose Details to provide

a default value, a description
and enumerations.

© 2014 SAP SE or an SAP affiliate company. All rights reserved. Public 13

New Function Supporting Subsidiary Integration
Timer-Triggered Database Inbound

Timer-triggered database inbound

Define a timer to schedule the retrieval of database records using JDBC.

© 2014 SAP SE or an SAP affiliate company. All rights reserved. Public 14

New Function Supporting Subsidiary Integration
Daily Actions and Message Log History

Daily Actions:
Choose Maintenance  Daily Actions.

Configure the Message Log and

Garbage Collection.

To display the message log history, choose Monitoring  Message Log History.

© 2014 SAP SE or an SAP affiliate company. All rights reserved. Public 15

New Function Supporting Subsidiary Integration
Key Expansion Atom

Key expansion atom

Enrich incoming messages and messages on the receiver side
by defining additional calls.
Sender key expansions enrich incoming messages; receiver key expansions enrich
messages on the receiver side.

© 2014 SAP SE or an SAP affiliate company. All rights reserved. Public 16

Offline Support

Offline support is a development for

local SAP Business One systems with
limited or intentionally deactivated
network connections due to poor
connections or high connection costs.

Offline Clients (SAP Business One

Systems)

• Local integration framework must be

installed on the SAP Business One
server.

Offline Server (SAP Business One 9.0

integration for SAP Netweaver)

© 2014 SAP SE or an SAP affiliate company. All rights reserved. Public 17

Why Migration?
Why Migration?

Why migrating to B1iSN 9.0?

 B1iSN 8.8 release is out of maintenance as of end of December, 2013
 If you are already familiar with the integration framework of SAP Business One, run all
scenarios based on the same technology.
 Benefit from the enhanced features and flexibility of the integration framework

Why migration and not upgrade?

The B1iSN 9.0 release is based on the integration framework, a different platform with other
objects, artifacts and procedures.
Upgrade and reuse of the B1iSN 8.8 database is not possible!

Why not migrate automatically?

The migration steps depend on the definitions of your scenario, many options are possible.
An automated procedure would be very complex and error-prone.

© 2014 SAP SE or an SAP affiliate company. All rights reserved. Public 19

Prerequisites
Prerequisites

System Landscape
 You are running scenarios in an SAP Business One integration 8.8 for SAP NetWeaver
productive environment.
 You have a separate machine available, where you can install and set up SAP Business
One 9.0 integration for SAP NetWeaver.

Knowledge
 You are familiar with the integration framework of SAP Business One (B1iF).
 You are familiar with the logic of your B1iSN8.8 integration scenarios.

© 2014 SAP SE or an SAP affiliate company. All rights reserved. Public 21

Scenario Description
Scenario Description

Getting Started Scenario Description

This presentation uses a very simple scenario to show you in general, how to migrate your
scenarios to the 9.0 release. The scenario provides:
 Data transfer from SAP Business One 8.8 to SAP Business One 8.8
 Sender: central SAP Business One, receiver: SAP Business One
 Scenario task: Items distribution from central SAP Business One
 Contains one transformation for the SAP Business One items (local object ID 4)

Prerequisite
 Always start a migration project with the analysis of your B1iSN8.8 scenarios.

© 2014 SAP SE or an SAP affiliate company. All rights reserved. Public 23

Step by Step Approach
Steps

Step 1: Exporting Scenario from B1iSN 8.8

Step 2: Installing 9.0 Version on Separate Machine

Step 3: Creating Systems in 9.0 SLD

Step 4: Creating Scenario Package

Step 5: Creating Scenario Step Inbound/Outbound/Processing

Step 6: Identifying and Migrating Criteria Fields

Step 7: Identifying and Migrating BIU Properties

Step 8: Defining Variables in B1iSN9.0

Step 9/1: Defining Key Expansions

Step 9/2: Importing B1iSN8.8 Key Expansions

Step 10: Migrating and Importing B1iSN8.8 Value Mappings

Step 11: Setting Up and Activating the Scenario Package

© 2014 SAP SE or an SAP affiliate company. All rights reserved. Public 25
Step 1: Exporting Scenario from B1iSN 8.8

To export your scenario from B1iSN 8.8

 From the SAP iApp Explorer, open the Subsidiary Integration Console.
 Select Tools, and then Repository Tools  BizPackage Export.
 In the BizPackage field, select the package for export and click the Export button.
The system creates the bizpackage.zip file.
 Store the file.
 Open the zip file, and you can find the structure definition in the following place:
• Open sim.com.sap.b1i.datasync.001
• Open the XSL document that contains the structure definition.

© 2014 SAP SE or an SAP affiliate company. All rights reserved. Public 26

Step 2: Installing 9.0 Version on Separate Machine

Installation Procedure
 Refer to the delta training material at sappartneredge.com/B1/b1isn.
 Choose the Training & Documentation tab.
 In the E-Learning section, choose the SAP Business One 9.0 integration for SAP NetWeaver
(B1iSN9.0) – Delta Training link.
 Choose Open all.
 Click the Installation and Technical Configuration link.
Event Sender Setup
 Refer to the settings in the 8.8 event sender and set up the 9.0 event sender accordingly.
DI Proxy
 Install or update the existing DI Proxy using the installation program of B1iSN9.0
Setting Up Integration Framework for Development
 To set up the development environment, choose Maintenance  Cfg Dev. Environment
For more information, click the icon in the user interface

© 2014 SAP SE or an SAP affiliate company. All rights reserved. Public 27

Step 3: Creating Systems in 9.0 SLD

Creating Systems in SLD

 In the integration framework, choose SLD  Create System.
 Select the B1<release> System Type, and enter
the system name.
 Enter all connection parameters used in B1iSN8.8. (Integration Application Explorer 
Landscape), and test the connection.

(optional) Reusing B1iSN8.8 SysIds

Integration framework generates the SysIds. But if you want to have the same SysIds in
B1iSN9.0, you have used in B1iSN8.8:
 Choose Tools  Control Center  Development  Execute BizFlow.
 Select com.sap.B1i.vPlatform.System, select bfd, select
SLDcreateSysId.bfd(unified).
 In the Parameters field, enter sysid=<8.8SysId>,systype=<8.8SysType>
For example: sysid=0010000118,systype=B1.8.8
 Choose Submit!.

© 2014 SAP SE or an SAP affiliate company. All rights reserved. Public 28

Step 4: Creating Scenario Package
In B1iSN8.8 Known as BizPackage

Creating Scenario Package

 Choose Scenarios  Package Design  New.
 In the Scenario Package Identifier field, enter the package name.
For the package name, you have less characters available than in 8.8:
19 – development prefix = available space for package name
 Select the business area of your package and click .

© 2014 SAP SE or an SAP affiliate company. All rights reserved. Public 29

Step 5: Creating Scenario Step
In B1iSN8.8 Known as vBIU

Creating Scenario Step

 Choose Scenarios  Step Design  New.
 In the Scenario Step Identifier field, enter the step name.
You have the following number of characters available:
23 – development prefix = available space for step name
 In the Scenario Package Identifier field, select the package you want the step to
assign to, and click .

© 2014 SAP SE or an SAP affiliate company. All rights reserved. Public 30

Step 5: Creating Scenario Step - Inbound

Inbound
 To define the inbound phase,
click the Inbound button,
then the Channel button,
enter the parameters,
and click:

 Click the Retrieval button,

enter the parameters,
and click:

© 2014 SAP SE or an SAP affiliate company. All rights reserved. Public 31

Step 5: Creating Scenario Step - Outbound

Outbound
 To define the outbound phase,
click the Outbound button,
enter the parameters,
and click:

 Click the Details button,

enter the parameters,
and click:

© 2014 SAP SE or an SAP affiliate company. All rights reserved. Public 32

Step 5: Creating Scenario Step - Processing

Processing
 To define the processing phase,
click the Processing button, and click the
button. It changes to .
The step runs on the receiver side. (This is
the 8.8 default. In 9.0, running on the
sender side is the default.)

Copying 8.8 Transformation to Final 9.0 Transformation Atom

 In an XML editor, open the 8.8 transformation document and the 9.0 final
transformation atom.
 Find the 8.8 transformation document in the
/sim.com.sap.b1i.datasync.001/biu.<yourBIU> folder…
 Find the atom0.xsl final transformation atom in the
com.sap.b1i.vplatform.scenarios.design/vBIU.<your
namespace>.<your step name> folder.

© 2014 SAP SE or an SAP affiliate company. All rights reserved. Public 33

Step 5: Creating Scenario Step - Processing

atom0.xsl
 You find the msg variable
representing the incoming
message.

 Insert here the message

structure of the 8.8 trans-
formation.

© 2014 SAP SE or an SAP affiliate company. All rights reserved. Public 34

Step 5: Creating Scenario Step - Processing

atom0.xsl
 Replace transform with the
specific name, for example,
B1Product.

 For each field, adjust the path.

Usually, you should only need to
add the $msg variable in front of
the path definition for the value.

.
.
.

© 2014 SAP SE or an SAP affiliate company. All rights reserved. Public 35

Step 6: Identifying and Migrating Criteria Fields
(If you do not use criteria fields in B1iSN8.8, skip the chapter.)

 In B1iSN8.8, to find criteria fields, choose B1iSN Tools  Development Tools 

Graphical scenario design.

 Other than in B1iSN8.8, define criteria fields in B1iSN9.0 at scenario package

level (optionally you can assign the criteria fields to a specific scenario step).
Choose Scenarios  Package Design  Definitions  Criteria Fields.

© 2014 SAP SE or an SAP affiliate company. All rights reserved. Public 36

Step 7: Identifying and Migrating BIU Properties
(If you do not use criteria fields in B1iSN8.8, skip the chapter.)

 In B1iSN8.8, to find BIU Properties, choose

B1iSN Tools  Development Tools 
Graphical scenario design.

 In B1iSN9.0, you can define the following properties:

Global Properties – at scenario
package level, valid for all steps, choose
Scenarios  Package Design  Definitions 
Global Properties, or
Scenarios Step Design Processing P global.
Local Properties - at scenario step
level, choose
Scenarios  Step Design  Processing P local.

© 2014 SAP SE or an SAP affiliate company. All rights reserved. Public 37

Step 8: Defining Variables in B1iSN9.0

 In B1iSN9.0, you can define the following variables:

Global Variables - at scenario package Local Variables - at scenario step

level, valid for all steps, choose level, choose
Scenarios  Package Design  Definitions 
Global Variables. Scenarios  Step Design  Processing V local.

or
Scenarios Step Design Processing V global.

© 2014 SAP SE or an SAP affiliate company. All rights reserved. Public 38

Step 9/1: Defining Key Expansions
(If you do not use criteria fields in B1iSN8.8, skip the chapter.)
Use the key expansion atom to retrieve additional information from sender and receiver
systems. Sender key expansions enrich incoming messages; receiver key expansions enrich
messages on the receiver side. Define the additional calls in a key expansion definition or
BIUMETA document. At runtime, the integration framework retrieves additional data from the
sender system and receiver system and adds them to the message.

In B1iSN9.0, the key expansion atom supports the following key expansion types:
• Simple object call to SAP Business One
• Simple service call to SAP Business One
• Calls to SAP Business One using an XSL stylesheet
• Calls to SAP ERP (R/3, ECC) using an XSL stylesheet
• Calls to database systems (J.AnySystem) using an XSL stylesheet

Recommendations
• Use the Call SQL atom for simple calls.
• Use the key expansion atom especially for calls that depend on each other, because the
atom considers dependencies between calls.
• Use the key expansion atom to migrate scenarios from a previous B1iSN version.

© 2014 SAP SE or an SAP affiliate company. All rights reserved. Public 39

Step 9/2: Importing B1iSN8.8 Key Expansions
1. To import a key expansion definition (BIUMETA) document or an XSL document containing
key expansion actions from the file system, choose the [Import] button.

2. Choose the [Browse…] button and select the file from the file system. The integration
framework checks whether the selected file already exists in the BizStore.
3. To overwrite an existing file, choose the [OK] button.
4. To import the file, choose the [Submit!] button.

Result
The integration framework stores the file to the following BizStore folder:
/com.sap.b1i.vplatform.scenarios.design/vBIU.<step name>/<document><step name>
is the scenario step name. <document> is the document name.

© 2014 SAP SE or an SAP affiliate company. All rights reserved. Public 40

Step 10: Migrating and Importing B1iSN8.8 Value Mappings

 Export value mapping definitions from B1iSN8.8

The zip file (com.sap.b1i.datasync.directory/ValueMapping.xml) contains an XML file for each value mapping field, for
which you have defined value mapping definitions. For value mappings created in Z customer namespace Z, make sure
to manually add the file extension *.xml.

 Import the value mapping definitions into B1iSN9.0.

B1iP displays the Import Status and imports the value definition files to the /com.sap.b1i.datasync.directory/ folder.

 Use a text editor to create the Configuration.xml file, and load it to the BizStore.
The migration tool does not check, whether the value mappings that you have defined in the configuration file, are
required by the integration packages. The migration tool generates all mappings provided in the configuration file. You
have the possibility to delete wrong value mappings in the BizStore.
You can find them in the /com.sap.b1i.vplatform.directory/ValueMapping folder. The documents have the following
name: <Package Id>.<Value Mapping Field Id>.xml

 Run the migration tool.

To run the BizFlow in B1iP, choose Tools  Control Center Development  Execute BizFlow. In the BizFlow field,
select /com.sap.b1i.vplatform.migrationtool/bfd/MigrationTool.bfd(unified), and click the Submit! button.

 Check, whether the value mapping definitions have been correctly imported into
the integration scenarios.
The migration tool creates a report for each migration run.

For more information, see the Administrator‘s Guide, chapter 8

© 2014 SAP SE or an SAP affiliate company. All rights reserved. Public 41

Step 11: Setting Up and Activating the Scenario Package

Setting Up the Scenario Package

 Choose Scenarios  Setup, and in the Scenario Package Identifier field, select
your scenario package.
 Click (Scenario Wizard), and follow the wizard steps.
 Select Activate , choose and choose Next.
 Select the sender and the receiver system, and choose Next until you reach the
last wizard step.
 Choose Deploy.
Activating the Scenario Package
 Choose the Activate button.

© 2014 SAP SE or an SAP affiliate company. All rights reserved. Public 42

More Information and
Support
More Information

Administrator’s Guide 9.0

 Find the guide in the download package, in the System Setup folder
Ramp Up Knowledge Transfer Material
 SAP Partner Edge: B1iSN 9.0 Delta Training
Integration Framework Documentation
 Open the integration framework and choose Help  Online Help.
 If you prefer the PDF format, choose Help  Documents.

© 2014 SAP SE or an SAP affiliate company. All rights reserved. Public 44

Need Migration Support?

If you need support migrating your scenarios, please contact your local
product expert.

© 2014 SAP SE or an SAP affiliate company. All rights reserved. Public 45