becs sap connector documentation · 2.1 becs sap connector objects becs sap connector is from “e...

BECS Connector Documentation B000xxxxx

BECS SAP Connector Documentation of 18

Synopsis: This document describes

implementation of BECS SAP connector.

BECS SAP Connector Documentation 1 BECS (Bentley Enterprise Connection Services) ................................................................................ 2

2 BECS Licensing processes in detail .................................................................................................... 2

2.1 BECS SAP Connector prerequisites ........................................................................................... 2

2.2 BECS SAP connector Installation Procedure .............................................................................. 2

2.2.1 Step by step procedure..................................................................................................... 2

2.1 BECS SAP connector objects ..................................................................................................... 3

2.1.1 SAP system object ............................................................................................................ 3

2.1.2 BECS SAP connector data objects...................................................................................... 4

2.2 BECS SAP connector usage ....................................................................................................... 5

2.2.1 BECS SAP connector data objects...................................................................................... 5

3 References ..................................................................................................................................... 18

4 Glossary ......................................................................................................................................... 18

Number: B000xxxxx

Updated: 6th September 2018

By: Alex Cimbalak, Bentley SK

State: Draft Scope: BECS connector 5.5x



1 BECS (Bentley Enterprise Connection Services) BECS enables trusted and certified integration between Bentley software and mission critical enterprise

applications such as enterprise resource planning (ERP) systems based on visual modeling of integration

projects. BECS automates the flow of data between Bentley applications, such as ALIM, and enterprise

applications to provide two-way communications for data creation, updates, and modifications, keeping

the data in both systems accurate and up to date. Bentley Enterprise Connection Services is certified for

integration with SAP® NetWeaver™ as well as SAP® HANA™ and provides the ability to exchange both

business object metadata and table data with SAP.

BECS is essentially a service bus with typical service bus related functionality. This functionality includes

an ability to create and use native "connectors" to external applications, including but not limited to

SAP®, Maximo®, Oracle® and many others.

Connectors are used in conjunction with data flow controls such as merge, split etc., to form a data

exchange solution template. BECS solution templates may be as simple as an incoming and outgoing

connector with pass through data flow, or very complex comprising many connectors with very

sophisticated data flow controls, internal BECS mappings and validations.

2 BECS Licensing processes in detail In this chapter, we will describe all relevant processes related to new licensing model in detail. For

better understanding we will use also schemas for each process with definition of relevant flows marked

by numbers (in chronological order).

2.1 BECS SAP Connector prerequisites BECS SAP connector requires:

BECS Server version 5.5 or higher

BECS Visual Architect version 5.5 or higher

SAP GUI

2.2 BECS SAP connector Installation Procedure This connector is from the BECS connector family. It means that it have implemented BECS Licensing

separately (“FeatureID licensing” – see BECS SELECT Licensing implementation document) and Product

ID of this connector is 2193.

2.2.1 Step by step procedure Whole process will drive following steps:

1. Installation of standard BECS package 2. This connector requires fully activated BECS server and BECS Visual Architect product 3. After installation (if standard package does not include SAP Connector), is necessary copy dll file

“Ace.Integrator.Sap.dll”, “Ace.Integrator.Sap.Connector.dll”,”Sapnco.dll” and “Sapnco_utils.dll” to BECS installation path.



4. After installation (if standard package does not include SAP Connector), is necessary copy dll file “Ace.Integrator.Sap.dll”, “Ace.Integrator.Sap.Connector.dll”,”Sapnco.dll” and “Sapnco_utils.dll” to BECS Visual Architect installation path(Architect\Extensions\Application).

5. Product will be after Activation ready to use.

2.1 BECS SAP connector objects BECS SAP connector is from “BECS connector family”. In a vision to allow same kind of work independent

of concrete connector we keep similar object structure and way of work for any “BECS family

connector”.

Connector consist of:

2.1.1 SAP system object

BECS SAP connector has blue color.

Properties for connection:

- AppServerHost (SAP server IP address)



- Client - Password - SystemNumber - User - Language

2.1.2 BECS SAP connector data objects BECS SAP connector has implemented following set of functions:

- SAP Outbound IDoc

- SAP Table Join



- SAP BAPI or RFC Call

- SAP Table or View

2.2 BECS SAP connector usage In following section, we will describe how to use data object Send Message on short example:

2.2.1 BECS SAP connector data objects

2.2.1.1 Step by step procedure– SAP Table or View

After successful BECS installation and activation will be possible to use development tool – BECS Visual

Architect (similar as today) for deployment of new solution template. Whole process will drive following

steps:



1. Via standard BECS development client tool called BECS Visual Architect will be open new template (Menu File – New)

2. Drag and drop system 3. After drop BECS VA shows following dialog:

4. Select SAP ERP connector 5. Set connection properties 6. Drag and Drop object 7. Select object SAP Table or View



8. Choose SAP Table or search table with Locate function

9. Set object name and write filter for table

10. Set Execution with steps:

a. Insert execution object Systems/SAP Enterprise Resource Planning/Objects/Table name / Read which will PUSH the table data into defined target Integration Object.



2.2.1.2 Step by step procedure– Create a Subscription



steps:



4. Select SAP ERP connector 5. Set connection properties 6. Drag and Drop object 7. Select object SAP BAPI or RFC Call



8. You can search for required BAPI/RFC in tree structure of SAP objects clicking OK in the dialog from step 7.

9. BAPI/RFC will appear in SAP system as an integration object with structure



10. In the step 7 you can click Create Empty Object 11. If you choose Empty Object function, fill Method field with BAPI/RFC exact name

12. Click read structure in the right click menu of object

13. BAPI/RFC will load in SAP system as an integration object with structure



14. Fill required parameter tables from source e.g. SQL table, XML source table etc.

15. Set Execution with steps: a. Insert source execution object for importing data into SAP Integration object b. Insert execution object Systems/SAP Enterprise Resource Planning/Objects/BAPI/RFC

Execute which will PUSH the table data into defined target Integration Object.

2.2.1.3 Step by step procedure– Table Join



steps:





4. Select SAP connector 5. Set connection properties 6. Drag and Drop object 7. Select object SAP Table Join

8. Properties: a. Filter b. JoinedTables c. Joins d. Select e. TableName

9. Example of properties:



10. Example of SELECT property

2.2.1.4 Step by step procedure– Outbound IDoc



steps:



4. Select SAP ERP connector 5. Set connection properties



6. Drag and Drop object 7. Select object SAP Outbound IDoc

8. Properties:

a. Data b. IdocSchemaString c. SchemaName

9. First fill SchemaName Property – basic Type of IDoc 10. Then right click on SAP Outbound IDoc integration object and click Read Structure



11. IDocSchemaString property will be filled with xml schema of IDoc



12. Fill property field Data with similar data – example:

13. Define execution



14. After successful execution, you can open WE02 transaction in SAP and search for received IDoc



3 References Number Revision Title Status

4 Glossary Term Description

End of document

becs sap connector documentation · 2.1 becs sap connector objects becs sap connector is from “e...

Documents