Integration framework for SAP Business One 03 Tutorial

Integration framework
for SAP Business One

Guide 03

Tutorial

Author: Heinz Pauly Version: 1.0 Date: June 21, 2010

-1-

Integration framework for SAP Business One 03 Tutorial

Content
1. Creating a Scenario Package ......................................................................3 2. File System to Database..............................................................................5 2.1 Inbound ..................................................................................................6 2.2 Outbound................................................................................................8 2.3 Processing..............................................................................................9 Copyrights, Trademarks, and Disclaimers .....................................................10

-2-

Integration framework for SAP Business One 03 Tutorial

1. Creating a Scenario Package

For the complete tutorial we will have one Scenario Package. All Scenario Steps, we develop, will be linked to this Scenario Package. In case youre not familiar with the concept of scenario development in B1i Framework, please refer to the B1iFramework reference 02 Scenario Development, chapter 1. To create our Scenario Package, please open the UI for the Scenario Step design from the administration console of the B1i Framework. Scenarios Scenario Package Design

First we have to agree to a name which should represent the Scenario Package. For our example step, we give the name B1iFW-Test. As Im working in the SAP namespace, in my case the identifier results in sap.B1iFW-Test. In your case the actual identifier is dependent on your settings (Maintenance Config Dev Environment). In case youre working in the Vendor mode, your Development Prefix is added instead of sap. In case youre working in Customer mode, a Z is added instead of sap. For Authentication we choose No Authentication.as long as we do not have HTTP Scenario Steps. In the field Vendor you specify the vendor information -3-

Integration framework for SAP Business One 03 Tutorial

for the Scenario Package. Im working in the SAP namespace, therefore automatically the text SAP AG, Walldorf, Germany is displayed. The displayed text is depending on your settings (Maintenance Config Dev Environment). The Version field is generated automatically. Its your responsibility to maintain the version. The field Timestamp is maintained by B1i Framework. In the field Description we enter a short description for our Scenario Package. The field Scenario Steps is empty because currently there is no Scenario Step assigned to our Scenario Package. Please click the button [Save] to save the configuration.

-4-

Integration framework for SAP Business One 03 Tutorial

2. File System to Database

In this first lesson we will learn how to develop a Scenario Step which is sending data from a file system to a database. To develop a Scenario Step, we have to run through the following steps: Specification of the Inbound Phase Specification of the Outbound Phase Development of the Processing Flow First we have to agree to a name which should represent the Scenario Step. For our example step, we give the name Tutor-FileToDB. As Im working in the SAP namespace, in my case the identifier results in sap.Tutor-FileToDB. In your case the actual identifier is dependent on your settings (Maintenance Config Dev Environment). In case youre working in the Vendor mode, your Development Prefix is added instead of sap. In case youre working in Customer mode, a Z is added instead of sap. We open the UI for the Scenario Step design from the administration console of the B1i Framework. Scenarios Scenario Step Design

-5-

Integration framework for SAP Business One 03 Tutorial

We enter the name Tutor-FileToDB in the field Scenario Step Identifier. As the next step we will associate this Scenario Step to our Scenario Package, that we created. Please click the button for the field Scenario Package Identifier to open a drop-down list with all available Scenario Packages and select our B1iFW-Test package. The (D) in front of the package identifier indicates that the Scenario Package is currently in Design mode.

2.1 Inbound
Please call the screen to maintain the inbound settings by clicking the [Inbound] button. First you need the specify the inbound channel. Please open the dialog by clicking the [Channel] button. You have to clarify the real requirements with your customer. For the example we are defining the following: The incoming flat file is provided in xml format The incoming file has always the name infile.xml As soon as a file exists in the inbound directory, the process should be triggered

-6-

Integration framework for SAP Business One 03 Tutorial

Inbound Type: Process Mode: Process Trigger: Identification Method: Identification Parameter: Identifier: Identification Namespace:

Flat File Asynchronous File exist File Name infile

The inbound channel INB_FI_EXST_ASYN_NAM is calculated automatically. Now please click the [Save] button to store the settings and close the window. You will be back in the inbound overview screen. Here you click now the [Retrieval] button. The retrieval specification screen opens.

The Retrieval Method is set automatically to the value Handover. You can just close this screen and the complete inbound configuration is done. The overview screen will display the defined values now. Scenario Step identifier: Inbound Channel (IPO): Data Retrieval: Formatting: sap.Tutor-FileToDB INB_FI_EXST_ASYN_NAM Handover dynamic

-7-

Integration framework for SAP Business One 03 Tutorial

Please close the inbound screen as all logical inbound settings are done. The technical inbound configuration (e.g. name of the inbound directory) is part of the definition in the System Landscape Directory (SLD), which we will do later. Back in the Scenario Step Definition screen, you will see the Inbound settings (FI(EXST,ASYN) Handover - dynamic) in the field Inbound. Inbound definition is done Outbound definition is open Processing is open

2.2 Outbound
Please call the screen to maintain the outbound settings by clicking the [Outbound] button. Here you define the outbound channel and the outbound format. Per definition we want to send data to a database system. Therefore we choose the database as the outbound channel. The format is jdbc. As our destination database system is MS SQL Server, it supports multiple sql statements, concatenated by semicolon. Outbound Channel: Outbound Format: [Details] SQL Procesing Mode: Datatabase jdbc

multiple -8-

Integration framework for SAP Business One 03 Tutorial

We do not trigger another Scenario Step. Therefore the outbound definition is finished. Please click the [Save] button to store the information. Back to the main screen for Scenario Step Definition, we have the following situation:

Inbound definition is done Outbound definition is done Processing is open

2.3 Processing
During the processing phase the Integration framework will transform the sender message to the receiver format by calling the processing instructions, defined by the particular Scenario Step.

-9-

Integration framework for SAP Business One 03 Tutorial

Copyrights, Trademarks, and Disclaimers

Copyright 2010 SAP AG. All rights reserved. The current version of the copyrights, trademarks, and disclaimers at http://service.sap.com/smb/sbocustomer/documentation is valid for this document.

- 10 -