Show TOC

Procedure documentationConfiguring B2B Integration Locate this document in the navigation structure

 

When configuring B2B processes, proceed as described under Configuring Message Processing.

Take the following into consideration for B2B configuration.

Several companies or business partners are typically involved in a B2B process. Each of these bases their configuration of the B2B process on the information available to them. For example, make business partner details known using your internal system landscape, not outwardly.

To keep things simple, the description below assumes a situation that involves one business process and two business partners. One of the business partners involved uses SAP NetWeaver PI and performs the B2B configuration in the Integration Directory. The second business partner can also use SAP NetWeaver PI and perform a similar (mirror-image) configuration in their Integration Directory. However, they can also use a different integration tool.

This section describes the steps taken by one of the business partners in the Integration Directory.

For more information about the basic concepts, see Configuring B2B Processes.

Prerequisites

Ideally, you have mapped the B2B integration in the Enterprise Services Repository using a process model (process component interaction model or process integration scenario). In the Intergation Directory this enables you to automate much of the configuration of collaboration agreements and logical routing using the model configurator. However, you must define the collaboration profile manually.

If there are no process models that you can use as the configuration template, you need to create all configuration objects manually.

Procedure

Configure Collaboration Profile

In this step you define the required communication parties, communication components, and communication channels.

To define the collaboration profile, perform the following steps:

  1. In the Integration Directory, create a communication party for each business partner involved in the process.

  2. Create a communication component of type Business System for each business system in your internal system landscape.

  3. Create the required business components.

    Note Note

    Business partners involved in B2B processes do not generally make the names of their internal business systems known externally, but instead mask them by using business components.

    End of the note.

    • Assign the business components that your business partner provided for external communication to the communication party that represents this external business partner.

    • Assign the business components that represent your own internal system landscape externally to the communication party that represents your own company.

  4. Create the required communication channels.

    You need one communication channel for each adapter involved. Depending on whether the adapter is a sender adapter or a receiver adapter, you create the communication channel for the relevant sender or receiver communication component as required.

Configure Communication Channels with Industry Standard Adapters

At least one of the involved business partners uses an industry standard adapter (such as the RNIF adapter) to connect to the message protocol supported by the respective industry standard.

In this step, you configure the involved industry standard adapter using the corresponding communication channels.

For information about the values you have to enter for the parameters of the communication channel, see the configuration guide for the respective industry-standard-specific SAP business package.

You can find the configuration guides on SAP Service Marketplace at http://service.sap.com/ibc.

  • For RosettaNet, choose   Industry Solutions   SAP for High Tech   Order to Invoice - RosettaNet  .

  • For CIDX, choose   Industry Solutions   SAP for Chemicals   Order to Invoice  .

Configuring Collaboration Agreements

In this step you configure the require collaboration agreements. In a collaboration agreement you assign the required communication channels to the relevant sender/receiver pairs. You also specify the agreed security settings (if they are supported by the adapters used).

To define a collaboration agreement, perform the following steps:

  1. Create a sender agreement for each sender/receiver pair that requires a sender adapter for inbound processing.

    Note Note

    Note, however, that you do not always need to define a sender agreement.

    More information: Defining Sender Agreements

    End of the note.

  2. Create a receiver agreement for each sender/receiver pair that requires a receiver adapter for outbound processing.

    Define a header mapping for the receiver agreements that describe the communication with your external business partner. This ensures that the name of a business component (and not the name of a business system or an integration process component) is written in the header of the outbound message at runtime.

  3. Specify the required security settings in the relevant sender and receiver agreements.

Configure logical routing

In this step you define the logical routing.

In logical routing you define:

  • The required receiver determinations

    In a B2B process, specify receiver-dependent receiver determinations for all messages that are to be sent from your business partner to the business components that you published. As the configured receivers, specify the business system components of your internal system landscape to which the message is to be forwarded.

  • The required interface determinations