https://w ww.linkedin.com/groups/8483193

2016-02-17

INTEGRATION COMMUNITY

0

PO B2B Add-on implementation

scenarios.

Applies to: SAP NetWeaver Process Orchestration 7.31, 7.4, 7.5 and B2B add-on SP04

Summary:

With the introduction of NetWeaver Process Orchestration B2B add-on SAP is covering all aspect of business to

business integration w ithout necessary deploy of others vendors adapters, it’s true that PO license is higher that only

PI AEX but from our point of view invest could be easy returned.

This article describe step by step procedure of basics configuration on your PO to integrate OTC and P2P scenarios

fast and quick.

Author: Integration Community

Created on: 2016/03/17

PO B2B Add-on implementation scenarios.

Table of Contents

B2B add-on and Process Orchestration 2

Netweaver PO design and configuration 2

Step-by-Step procedure 3

References 20

Version

number Purpose / Changes Author Date

1 Initial draft show n to line manager Integration Community 07/03/2016

PO B2B Add-on implementation scenarios.

B2B add-on and Process Orchestration With latest versions of PO (7.31, 7.4 and 7.5) B2B add-on is included w ithout extra license payment. SAP provide

w ith these versions a pow erful tool for B2B integrations in an easy and quick w ay w ithout obligation to include any

other supplier as Seeburger.

There is a bunch of documents and blogs w hat explain w hat it’s B2B add-on and how to do basis installation on your

PO server, objective of that document it’s to clarify and put all those explanations on a step by step document

together and create tw o different examples scenarios. We have implemented these f low s to use TPM configuration.

You can f ind a great explanation on that TPM blog post series about w hat it’s TPM and how to use it. We are not

using all TPM possibilities and only simple agreements and set up are develop to simplify scenarios.

In order to emulate AS2 client connection w e are using Mendelson softw are follow Dimitri Sannen Mendelson blog

post series to configure tool on your machine.

Netweaver PO design and configuration 1. Order to cash: Incoming orders

2. Supplier Invoice: Incoming Invoices.

SAP ERP3rd Party

FTP/VAN

EDISeparator RCV

SAP PO

EDISeparator SND

EDISeparator SND

INVOIC02

ORDERS05

AS2/FTP

RFC(IDOC)

EDIFACT

(Orders &

Invoices)

Tw o interfaces corresponding w ith next integration f low s at PO:

Integration f low I: from 3rd Party to EDISeparator (Asynchronous)

Integration f low II: from EDISeparator to Order Reception (SAP ERP system asynchronous)

Integration f low III: from EDISeparator to Invoice Reception (SAP ERP System synchronous)

Prerequisites Next installations are required to follow step by step document.

Mendelson softw are.

SMP: Installation Guide/Master Guide/Supported EDI Formats/Security Guide

SAP Note 1695520 : SMP Dow nload location of Business to Business Add-On B2B SP04

NWDS installation

PO B2B Add-on implementation scenarios.

Step-by-Step procedure All objects to use on ESR part al already deploy and created at B2B MAPPING KIT 1.0 SWC w e are going to follow

EDIFACT D96D standards so no object should be created at ESR. We w ill assume too that corresponding connection

from ECC and PO for iDoc are already in place and business system and technical system created.

We can start at configuration level on NWDS.

Step

Description

Screenshot

Start NWDS development – Process Integration Designer perspective and create Integration directory objects for

Integration flow I: from 3rd Party to EDISeparator (Asynchronous)

1 Run NWDS and open PI designer

perspective

Click: OK

2 Under PI Explorer --> Right click on

Systems

Create two news Parties:

1 Party_ABC: VAN/Group of Client

Click: Finish

2 Party_DEF : Will be SAP ERP

system.

Click: Finish

and

PO B2B Add-on implementation scenarios.

3 Right Click on Party_ABC and

create Business component:

BC: EDI_VAN

Click: Finish

and

4 Under EDI_VAN BC create AS2

Sender Communication channel:

EDI_Mendelson_AS2_Sender

Click: Finish

PO B2B Add-on implementation scenarios.

5 Set up:

EDI_Mendelson_AS2_Sender

1 Choose AS2 adapter type

2 Direction: Sender

3 on Adapter-Specific tab

configure those 3 parameters

according your Mendelson

configuration

Keep others parameters as default.

ll

PO B2B Add-on implementation scenarios.

4 Configure MDN

MDN tab on channel set up on

Application Acknowledgement

Click: Save

and

6 Create business component without

party:

BC: EDI_Separator

Click: Finish

and

7 Under EDI_Separator BC (without

Party) create EDISeparator

Communication channel:

EDI_Separator_Receiver

Click: Finish

PO B2B Add-on implementation scenarios.

8 Set up: EDI_Separator_Receiver

General tab

1 Choose EDISeprator adapter type

2 Direction: Receiver

Click: Save

9 Set up: EDI_Separator_Receiver

Adapter specific

Check: Read from Dynamic Headers

Click: Save

10 Set up: EDI_Separator_Receiver

Module: add modules is not needed

Click: Save

and

Create Integration flow I: from 3rd Party to EDISeparator (Asynchronous)

11 Right Click on: Integration Flows:

New Integration Flow

PO B2B Add-on implementation scenarios.

Name:

_Party_ABC_EDI_VAN_Dummy_S

eparator_to_EDI_Separator

ID: _Party_ABC_EDI_VAN_

Click: Finish

Set up Integration Flow:

Sender: EDI_VAN from Party_ABC

Receiv er: EDI_Separator

Use dummy interface for that iflow

Click: Save

and

Integration flow I created.

Sender:

Receiv er:

PO B2B Add-on implementation scenarios.

Create Integration directory objects for Integration flow II: from EDISeparator to Order Reception (SAP ERP system

asynchronous)

12 1 Under EDI_Separator create

Sender Communication channel:

EDI_Separator_ORDERS_Sender

Click: Finish

2 set up channel on General Details

tab:

Adapter Type: EDISeparator

Direction: Sender

Protocol: EDIFACT

Click: Save

13 Set up:

EDI_Separator_ORDERS_Sender

Adapter specific tab:

Message type: ORDERS

Click: Save

14 Set up:

EDI_Separator_ORDERS_Sender

Modules Tab:

Number Module Name Type Module Key

1 localejbs/TPMContentAccessModule Local Enterprise Bean

TPM

2 localejbs/EDISearchParametersModule Local Enterprise Bean

EDISEA

3 localejbs/EdifactConverterModule Local Enterprise Bean

EDIFAC

4 localejbs/CallSapAdapter Local Enterprise Bean

entry

Module key Parameter Name Parameter Value

TPM enable.ediAckProfile true

TPM enable.edisepUsage true

EDIFAC edif act.audit true

EDIFAC tpm.enable true

PO B2B Add-on implementation scenarios.

1 Process Sequence

Follow same sequence as picture

2 Module Configuration

Sort is not relevant

Click: Save

and

**note: We are not mention related object about iDoc communication with SAP ERP (nothing about BS and

communication iDoc channels please refer next link to create necessary connections)

Create Integrated Flow II: from EDISeparator to Order Reception (SAP ERP system asynchronous) 15 1 Right Click on: Integration Flows:

New Integration Flow

Name:

_EDI_Separator_ORDERS_to_SA

PSystemDev __

ID:

_EDI_Separator_ORDERS_ECC

Click: Finish

PO B2B Add-on implementation scenarios.

2 assign System

3 Assign Interface

4 Assign referenced channel at

Sender

5 Assign your receiver system:

**SAP Business system

PO B2B Add-on implementation scenarios.

Assign Operation

7 assign Operation Mapping:

OM_ORDERS96A_TO_ORDERS05

8 assign Interface at receiver

9 assign Channel at receiver

Idoc sender channel.

Integration flow II created.

Click: Save

and

PO B2B Add-on implementation scenarios.

Create Integration directory objects for Integration flow III: fr om EDISeparator to Invoice Reception (SAP ERP System

synchronous)

16 1 Under EDI_Separator create

Sender Communication channel:

EDI_Separator_INVOICE_Sender

Click: Finish

2 set up channel on General Details

tab:

Adapter Type: EDISeparator

Direction: Sender

Protocol: EDIFACT

Click: Save

17 Set up:

EDI_Separator_INVOICE_Sender

Adapter specific tab:

Message type: INVOICE

Click: Save

18 Set up:

EDI_Separator_INVOICE_Sender

Modules Tab:

Number Module Name Type Module Key

1 localejbs/TPMContentAccessModule Local Enterprise Bean TPM

2 localejbs/EDISearchParametersModule Local Enterprise Bean EDISEA

3 localejbs/EdifactConverterModule Local Enterprise Bean EDIFAC

4 localejbs/CallSapAdapter Local Enterprise Bean entry

Module key Parameter Name Parameter Value

TPM enable.ediAckProfile true

TPM enable.edisepUsage true

EDIFAC edif act.audit true

EDIFAC tpm.enable true

PO B2B Add-on implementation scenarios.

1 Process Sequence

Follow same sequence as picture

2 Module Configuration

Sort is not relevant

Click: Save

and

Create Integration directory objects for Integration flow III: from EDISeparator to Invoice Reception (SAP ERP System

synchronous)

19 1 Right Click on: Integration Flows:

New Integration Flow

Name:

_EDI_Separator_INVOICE_to_SAP

SystemDev __

ID:

_EDI_Separator_INVOICE_ECC

Click: Finish

PO B2B Add-on implementation scenarios.

2 assign System

3 Assign Interface

4 Assign referenced channel at

Sender

5 Assign your receiver system:

**SAP Business system

6 Assign Operation

PO B2B Add-on implementation scenarios.

7 assign Operation Mapping:

8 assign Interface at receive

9 assign Channel at receiver

Idoc sender channel.

Integration flow II created.

Click: Save

and

20

At these point we have created 3

integrated flows on NWDS and we

need to deploy

Right click on each iFlow and deploy

them

We have to set up Partners and agreements on TPM http:<localhost:port>/b2bic

21 Log on http:<localhost:port>/b2bic

And click on Trading Partner

Management

PO B2B Add-on implementation scenarios.

22

1 add new Partner for Customer

(sender system).

2 at General tab insert a name and

assign to an existing Party

(mandatory)

Partner type: Customer

3 at identities tab:

Add identifier and agency code 014

Identifier is sender GLN incoming

EDIFACT file

4 Add messages types

Click:

Others tabs are not relevant.

23

1 add new Partner for Owncompany

(receiver system).

PO B2B Add-on implementation scenarios.

2 at General tab insert a name and

assign to an existing Party

(mandatory)

Partner type: Self

3 at identities tab:

Add identifier and agency code 014

Click:

Others tabs are not relevant.

24

Once we have created Partners now

i t’s time to add agreements:

One agreements per message.

25

Create INVOICE agreement

between partners

Use match code to fulfi ll right picture

Click:

PO B2B Add-on implementation scenarios.

26

Create ORDERS agreement

between partners

Use match code to fulfi ll right picture

Click:

Configuration is done and now you have to test And monitoring it.

T1 Prepare test fi le to use it.

T2 Open Mendelson tool and send a

fi le to your PO system:

1 send fi le to Partner

2 Choose fi le

3 Click: OK

T3 Message is sent to PO OK from

Mendelson and MDN received.

T4 Go to monitoring in PO server

PO B2B Add-on implementation scenarios.

As you can see fi le is spited and

flows processed.

T5 You can click on success messages

and change to B2B monitoring

And see all details about MDN,

Functional ACK, etc…

To check first ICO MDN by

separated you can check under tab

B2B ACK on monitor.

To get all these details it’s importat

to set up module

localejbs/EDISearchParametersModule

Under EDI separator Sender

Channel.

References ADD-On Solutions for SAP NetWeaver Process Orche stration

Simple Use Cases for B2B NRO and Archive Module Configuration

B2B- EDI Inbound -Step by Step Configuration

Wiki B2B addon

END OF DOCUMENT