Skip to Content

With the introduction of NetWeaver Process Orchestration B2B add-on  SAP is covering all aspect of business to business integration without 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 the procedure of basics configuration on your PO to integrate OTC and P2P scenarios fast and quick.

Outbound scenarios  B2B-addon implementation scenarios PO part II outbound EDI

Documents has been created by Integration Community team Federico Abait and Roberto Cantero


B2B add-on and Process Orchestration

With latest versions of PO (7.31, 7.4 and 7.5) B2B add-on is included without extra license payment. SAP provide with these versions a powerful tool for B2B integrations in an easy and quick way without obligation to include any other supplier as Seeburger.

  There is a bunch of documents and blogs what explain what 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 two different  examples scenarios. We have implemented these flows to use TPM configuration.  You can find a great explanation on that TPM blog post series about what 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 we are using Mendelson software 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.

Two interfaces corresponding with next integration flows at PO:

  • Integration flow I: from 3rd  Party to EDISeparator (Asynchronous)
  • Integration flow II: from EDISeparator to Order Reception (SAP ERP system asynchronous)
  • Integration flow III: from EDISeparator to Invoice Reception (SAP ERP System synchronous)

Prerequisites

    Next  installations are required to follow step by step document.

***After a couple of tries we decide to share in here only test Parts to show you what you can do with PO B2B add-on full step by step document can be found in here. Full document is hard to handle on SCN documents tables with screenshots.


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)

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

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

**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)

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

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

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

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

T1

Prepare test file to use it.

T2

Open Mendelson  tool and send a file to your PO system:

1 send file to Partner

2 Choose file

3 Click: OK

T3

Message is sent to PO OK  from Mendelson and MDN received.

T4

Go to monitoring in PO server

As you can see file 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

To report this post you need to login first.

9 Comments

You must be Logged on to comment or reply to a post.

  1. Albert Esteve Tomillero

    Hi Robert

    Thanks for this post it helps a lot. Following the document, when we create the partner that represents the VAN with Partner Type= VAN provider and we try to create the agreement, the created partner is not shown. But if we switch the type from VAN provider to Customer then the agreement can be created.

    Is there any particularity when we use partner type = VAN provider to create agreement?

    Kindly Advise.

    BR,

    Albert Esteve

    (0) 

Leave a Reply