AR822 - EN - Col2008 - 2 SAP Ariba Cloud Integration Gateway Configuration [PDF]

Zitiervorschau

AR822 SAP Ariba Integration: Cloud Integration Gateway Collection 2008

© SAP SE

AR822

1

HOME

LOGO HERE

Course Title

Outline SAP Ariba Cloud Integration Gateway: Overview and Getting Started Network Integration

Master Data Integration

Transactional Data Integration

Migration, Multiple ANIDs, and More

@ Copyright. All rights reserved.

© SAP SE

AR822

2

HOME

LOGO HERE

Course Title

SAP Ariba Cloud Integration Gateway: Overview and Getting Started 1

5

CIG Configuration

Getting Started with CIG 2

6

Integration Add-Ons

Custom Mapping Tool 7

3

Content Based Routing

Cloud Connector 4

Configure SAP Ariba Add-On

@ Copyright. All rights reserved.

© SAP SE

AR822

3

LOGO HERE

SAP Ariba Cloud Integration Gateway Configuration

@ Copyright. All rights reserved.

© SAP SE

AR822

4

LOGO HERE

About This Lesson Lesson 1: Architecture

By the end of this lesson, you will be able to: •

Match SAP Ariba Cloud Integration Gateway features to their associated benefit(s)

This lesson includes the following topics: i.

Quick CIG video

ii.

10 Key Features

@ Copyright. All rights reserved.

© SAP SE

AR822

5

LOGO HERE

Architecture By leveraging the SAP Cloud Platform Integration, the SAP Ariba Cloud Integration Gateway: üSimplifies integration with guidance-based setup üReduces the integration deployment time üProvides an integrated test framework by default to test the scenarios üAligns with SAP standard software lifecycle

In addition, the SAP Ariba Cloud Integration Gateway: ü Facilitates smoother upgrades. ü Supports download through the SAP Service Marketplace. ü Addresses issues with standard SAP Notes and correction instructions. ü Uses the single sign-on functionality, to allow buyers to access their SAP Ariba Cloud Integration Gateway account from their Ariba Network account or Ariba Application realms. ü Supports management of a single configuration based on your core ERP capabilities when you connect to the Ariba Network. ü Supports certificate-based or basic username and password based authentication for connectivity. ü Provide innovative tools

@ Copyright. All rights reserved.

© SAP SE

AR822

6

LOGO HERE

About This Lesson Lesson 2: Connecting to CIG via SAP Ariba Applications

By the end of this lesson, you will be able to: •

Identify pre-requisites for connecting and assigning permissions

•

Access CIG via various SAP Ariba Applications

This lesson includes the following topics: i.

Connecting CIG to Ariba Network

ii.

Connecting CIG to SAP Ariba Sourcing

iii.

Connecting CIG to SAP Ariba Procurement

@ Copyright. All rights reserved.

© SAP SE

AR822

7

LOGO HERE

Connecting to CIG via Ariba Network

Connecting via Ariba Network

Pre-Requisites

Assign User Permissions

Access CIG

@ Copyright. All rights reserved.

© SAP SE

AR822

8

LOGO HERE

Connecting to CIG via Ariba Network

Connecting via Ariba Network

Pre-Requisites

Assign User Permissions

Access CIG

@ Copyright. All rights reserved.

© SAP SE

AR822

9

LOGO HERE

Connecting to CIG via Ariba Network (Pre-Requisites)

ü Buyer Account on Ariba Network ü Enable your AN Buyer account to access CIG In order to start testing once all the configurations are done, you need to: ü Maintain valid trading Buyer-Supplier relationship on Ariba Network ü Have access to SAP Marketplace to download SAP Ariba Cloud Integration Gateway add-on for SAP ERP or SAP S/4HANA ü Download/Install/Configure SAP Ariba CIG AddOn on your SAP system ü Configure necessary certificates

@ Copyright. All rights reserved.

© SAP SE

AR822

10

LOGO HERE

Connecting to CIG via Ariba Network

Connecting via Ariba Network

Pre-Requisites

Assign User Permissions

Access CIG

@ Copyright. All rights reserved.

© SAP SE

AR822

11

LOGO HERE

Connecting to CIG via Ariba Network (Assign User Permissions)

You will now need to create users (as required) and assign necessary permissions to access & configure CIG.

Even though AN Buyer account is added to the Feature Availability list, users still need to have necessary permissions assigned to access CIG.

@ Copyright. All rights reserved.

© SAP SE

AR822

12

LOGO HERE

Connecting to CIG via Ariba Network (Assign User Permissions)

Step 1 of 6 The Administrator of the Buyer AN account will need to login with their administrator credentials. Click on the Administration dropdown menu and click on Users.

@ Copyright. All rights reserved.

© SAP SE

AR822

13

LOGO HERE

Connecting to CIG via Ariba Network (Assign User Permissions)

Step 2 of 6

Under manage Role section, click on Create Role.

@ Copyright. All rights reserved.

© SAP SE

AR822

14

LOGO HERE

Connecting to CIG via Ariba Network (Assign User Permissions)

Step 3 of 6

Enter a distinctive Name for the role. (Optional – Enter a description for the role. Descriptions can be useful later, if you want to review or revise the structure of your roles). Click Save.

@ Copyright. All rights reserved.

© SAP SE

AR822

15

LOGO HERE

Connecting to CIG via Ariba Network (Assign User Permissions)

Step 4 of 6

Each role must have at least one permission: ü Ariba Cloud Integration Gateway Configuration: Allows you to create, modify, & maintain projects on the SAP Ariba Cloud Integration Gateway. ü Ariba Cloud Integration Gateway Access: Allows you to view & search for projects available on the SAP Ariba Cloud Integration Gateway. Click Save.

Buyer administrator can assign predefined permissions to users accessing the CIG. Creating a role must be done before you create users.

@ Copyright. All rights reserved.

© SAP SE

AR822

16

LOGO HERE

Connecting to CIG via Ariba Network (Assign User Permissions)

Step 5 of 6

Under Manage Users, click Create User.

@ Copyright. All rights reserved.

© SAP SE

AR822

17

LOGO HERE

Connecting to CIG via Ariba Network (Assign User Permissions)

Step 6 of 6

ü Provide required user related information. ü Assign the newly created role to that user. ü Click Done.

@ Copyright. All rights reserved.

© SAP SE

AR822

18

LOGO HERE

Connecting to CIG via Ariba Network

Connecting via Ariba Network

Pre-Requisites

Assign User Permissions

Access CIG

@ Copyright. All rights reserved.

© SAP SE

AR822

19

LOGO HERE

Connecting to CIG via Ariba Network (Access CIG)

• Login to your Ariba Network Buyer account having permission to access CIG. • Click on the Administration dropdown • Click Configuration.

Step 1 of 7

@ Copyright. All rights reserved.

© SAP SE

AR822

20

LOGO HERE

Connecting to CIG via Ariba Network (Access CIG)

Step 2 of 7

Click on Cloud Integration Gateway Setup option.

@ Copyright. All rights reserved.

© SAP SE

AR822

21

LOGO HERE

Connecting to CIG via Ariba Network (Access CIG)

Step 3 of 7

• After reading & agreeing to Terms of Use & Privacy Statement, check the box next to Enable the Ariba Cloud Integration Gateway. • Click Save.

@ Copyright. All rights reserved.

© SAP SE

AR822

22

LOGO HERE

Connecting to CIG via Ariba Network (Access CIG)

Step 4 of 7

You will be navigated back to the configuration page. Click Cloud Integration Gateway Setup.

@ Copyright. All rights reserved.

© SAP SE

AR822

23

LOGO HERE You will see Go to the Ariba Cloud Integration Gateway link enabled.

Connecting to CIG via Ariba Network (Access CIG)

Click on the link.

Step 5 of 7

Recommendation: send your backend SAP system information before accessing & configuring your CIG account very first time. @ Copyright. All rights reserved.

© SAP SE

AR822

24

LOGO HERE

Connecting to CIG via Ariba Network (Access CIG)

Step 6 of 7

Upon enabling CIG from Ariba Network in step 4, you will get an automated email from [email protected] to set the password of your P User, a unique user ID for your account in CIG. This P User information will be needed for following: 1. 2. 3.

Sending SAP system information to CIG. Execute Interface Setup program in SAP system. Cloud Connector configuration.

The auto generation P user ID required to connect to CIG is triggered when you enable CIG. @ Copyright. All rights reserved.

© SAP SE

AR822

25

LOGO HERE

Connecting to CIG via Ariba Network (Access CIG)

Step 7 of 7

While accessing CIG very first time, if you have not sent the backend system information to CIG via SAP Data Sync report, you will land on Trading Partner System information page where you would need to provide required information of your SAP system. Until you provide the backend system information, CIG will not allow you to proceed further.

Recommendation: send your backend SAP system information before accessing & configuring your CIG account very first time. @ Copyright. All rights reserved.

© SAP SE

AR822

26

LOGO HERE

Connecting to CIG via SAP Ariba Sourcing

Connecting via SAP Ariba Sourcing

Pre-Requisites

Access CIG

@ Copyright. All rights reserved.

© SAP SE

AR822

27

LOGO HERE

Connecting to CIG via SAP Ariba Sourcing (Pre-Requisites)

ü SAP Ariba Sourcing Realm connected to an active Buyer Account on Ariba Network. ü Enable your Sourcing Realm to access CIG (for Master Data Integration). ü Enable your AN Buyer account to access CIG (for transaction integration). In order to start testing once all the configurations are done, you need to: ü Access to SAP Marketplace to download SAP Ariba Cloud Integration Gateway add-on for SAP ERP or SAP S/4HANA. ü Configure AddOn on your SAP system. ü Configure your certificates.

• For SAP Ariba Sourcing Integration, enabling CIG through Ariba Sourcing Realm is only meant for Sourcing Master Data Integration. • For Sourcing Transactions Integration such as Quote Request; Award & Contract, you need to enable CIG from Ariba Network as well. @ Copyright. All rights reserved.

© SAP SE

AR822

28

LOGO HERE

Connecting to CIG via SAP Ariba Sourcing

Connecting via SAP Ariba Sourcing

Pre-Requisites

Access CIG

@ Copyright. All rights reserved.

© SAP SE

AR822

29

LOGO HERE

Connecting to CIG via SAP Ariba Sourcing (Access CIG)

Login to your Ariba Sourcing realm with a user having “Customer Administrator” permission. Click the dropdown menu for Manage. Click Administration.

Step 1 of 6

@ Copyright. All rights reserved.

© SAP SE

AR822

30

LOGO HERE

Connecting to CIG via SAP Ariba Sourcing (Access CIG) Click the dropdown menu for Integration Manager. Click Cloud Integration Gateway Step 2 of 6

@ Copyright. All rights reserved.

© SAP SE

AR822

31

LOGO HERE After reading & agreeing to Terms of Use & Privacy Statement, check the boxes next to I have read and agree.… & Enable the Ariba Cloud Integration Gateway Capability.

Connecting to CIG via SAP Ariba Sourcing (Access CIG)

Also check the boxes of the tasks / Integration Events you want to adopt to enable them. Then click Save. These tasks / events are only meant for integration with S/4 HANA Cloud version and not applicable for integration with on-premise SAP system.

Step 3 of 6

1)

Export Purchase Contract Request to CIG-S4HANA – This parameter is to enable Ariba Contract CLID integration with S/4 HANA cloud. This integration is slightly different from our Add-On integration because it doesn’t go through AN(meaning it is not cXML based integration). Hence we introduced a new parameter.

2)

Export RFX Awards to S4HANA – This parameter is to enable Quote Message from Ariba Sourcing to S/4 HANA Cloud.

3)

Import Purchase Contract Status Update Request from CIG-S/4HANA – This parameter is to enable Contract Status update from S/4 HANA Cloud to Ariba Contracts (Response flow for integration of Export Purchase Contract Request to CIG-S4HANA)

4)

Import Sourcing Request from S/4HANA – This parameter is to enable Quote Request flow from S/4HANA cloud to Ariba Sourcing. In S/4 HANA cloud the RFQ created is called Sourcing Request.

5)

SMExternalValidation – Do not have info about this parameter. In SLP, we can have validations within SLP/SM or in the external system like MDG. This parameter may be controlling that behaviour. Need to check with the PM for SLP.

6)

Send RFQ Confirmation to S4HANA – This is a new flow. Once we send the Quote Request from S/4 HANA Cloud to Ariba Sourcing, they will send a response back to S/4 HANA. This will be called RFQ confirmation. This is currently under development and Murali is working on it. This parameter is to enable this flow.

@ Copyright. All rights reserved.

© SAP SE

AR822

32

LOGO HERE

Connecting to CIG via SAP Ariba Sourcing (Access CIG)

Step 4 of 6

The CIG status is now Enabled.

Click the link Visit the cloud integration gateway

@ Copyright. All rights reserved.

© SAP SE

AR822

33

LOGO HERE

Connecting to CIG via SAP Ariba Sourcing (Access CIG)

Step 5 of 6

Upon enabling CIG from Ariba Sourcing Realm in previous step, you will get an automated email from [email protected] to set the password of your P User, a unique user ID for your account in CIG. This P User information will be needed for following: 1. 2. 3. 4.

Sending SAP system information to CIG. Execute Interface Setup program in SAP system. Cloud Connector configuration. Sending Master Data from your SAP system to Ariba Sourcing.

• Each P User is associated with only one AN Buyer Account. • The system has built-in intelligence to check AN Buyer ID connected to your Sourcing Realm to avoid duplicate creation on P User. • Thus, as an SAP Ariba Sourcing Customer even tough you enable CIG through your Sourcing Realm for Sourcing Master Data Integration, NO new P User will get created when you enable CIG again through Ariba Network for Sourcing Transaction Integration. @ Copyright. All rights reserved.

© SAP SE

AR822

34

LOGO HERE

Connecting to CIG via SAP Ariba Sourcing (Access CIG)

Step 6 of 6

While accessing CIG very first time, if you have not sent the backend system information to CIG via SAP Data Sync report, you will land on Trading Partner System information page where you would need to provide required information of your SAP system. Until you provide the backend system information, CIG will not allow you to proceed further.

Recommendation: send your backend SAP system information before accessing & configuring your CIG account very first time. @ Copyright. All rights reserved.

© SAP SE

AR822

35

LOGO HERE

Connecting to CIG via SAP Ariba Procurement

Connecting via SAP Ariba Procurement

Pre-Requisites

Access CIG

@ Copyright. All rights reserved.

© SAP SE

AR822

36

LOGO HERE

Connecting to CIG via SAP Ariba Procurement (Pre-Requisites)

ü SAP Ariba Procurement Realm ü Enable your Procurement Realm to access CIG ü Enable your associated AN Buyer account to access CIG (for transaction integration for Invoice Management Realm & Combo Realm)

In order to start testing once all the configurations are done, you need to: ü Access to SAP Marketplace to download SAP Ariba Cloud Integration Gateway add-on for SAP ERP or SAP S/4HANA. ü Configure AddOn on your SAP system. ü Configure your certificates.

@ Copyright. All rights reserved.

© SAP SE

AR822

37

LOGO HERE

Connecting to CIG via SAP Ariba Procurement (Pre-Requisites)

Please note that for SAP Ariba Procurement Integration, enabling CIG through SAP Ariba Procurement realm is meant for both Procurement Master Data Integration & Procurement Transaction Integration. For Procurement Transactions Integration through solutions such as Invoice Management (aka Invoice Pro) & Combo Realm, you need to enable CIG from Ariba Network as well.

@ Copyright. All rights reserved.

© SAP SE

AR822

38

LOGO HERE

Connecting to CIG via SAP Ariba Procurement

Connecting via SAP Ariba Procurement

Pre-Requisites

Access CIG

@ Copyright. All rights reserved.

© SAP SE

AR822

39

LOGO HERE

Connecting to CIG via SAP Ariba Procurement (Access CIG) Login to your SAP Ariba Procurement realm (login requires user with “Customer Administrator” permission) Click the dropdown menu for Manage

Step 1 of 6

Click Core Administration

@ Copyright. All rights reserved.

© SAP SE

AR822

40

LOGO HERE

Connecting to CIG via SAP Ariba Procurement (Access CIG) Under Integration Manager Click Cloud Integration Gateway Step 2 of 6

@ Copyright. All rights reserved.

© SAP SE

AR822

41

LOGO HERE

Connecting to CIG via SAP Ariba Procurement (Access CIG) After reading & agreeing to Terms of Use & Privacy Statement, check the boxes next to I have read and agree.… & Enable the Ariba Cloud Integration Gateway Capability.

Step 4 of 6

Also check the boxes of the tasks / Integration Events you want to adopt to enable them. Then click Save.

@ Copyright. All rights reserved.

© SAP SE

AR822

42

LOGO HERE

Connecting to CIG via SAP Ariba Procurement (Access CIG)

The Status is now Enabled. Step 4 of 6 Click the link Visit the cloud integration gateway.

@ Copyright. All rights reserved.

© SAP SE

AR822

43

LOGO HERE

Connecting to CIG via SAP Ariba Procurement (Access CIG)

Step 5 of 6

Upon enabling CIG from SAP Ariba Procurement realm, you will recieve an automated email from [email protected] to set the password of your P User, a unique user ID for your account in CIG. This P User information will be needed for following: 1. 2. 3. 4.

Sending SAP system information to CIG. Execute Interface Setup program in SAP system. Cloud Connector configuration. Sending Master Data from your SAP system to Ariba Sourcing.

• Each P User is associated with only one AN Buyer Account. • The system has built-in intelligence to check the AN Buyer ID connected to your Procurement realm to avoid duplicate creation on P User. • Thus, as an SAP Ariba Procurement Customer even tough you enable CIG through your Procurement realm for Procurement Master Data Integration, NO new P User will get created when you enable CIG again through Ariba Network for Procurement Transaction Integration. @ Copyright. All rights reserved.

© SAP SE

AR822

44

LOGO HERE

Connecting to CIG via SAP Ariba Procurement (Access CIG)

Step 6 of 6

While accessing CIG very first time, if you have not sent the backend system information to CIG via SAP Data Sync report, you will land on Trading Partner System information page where you would need to provide required information of your SAP system. Until you provide the backend system information, CIG will not allow you to proceed further.

@ Copyright. All rights reserved.

2 text pop-ups

© SAP SE

AR822

45

LOGO HERE

About This Lesson Lesson 3: Adding & Editing ERP information

By the end of this lesson, you will be able to: •

Add or edit ERP system information

This lesson includes the following topics: i.

Step-by-step instruction on how to add or edit ERP system information

@ Copyright. All rights reserved.

© SAP SE

AR822

46

LOGO HERE

Adding & Editing ERP information Click on the User Name appearing at the top/right corner of the screen. Step 1 of 6

Click Basic Data

@ Copyright. All rights reserved.

© SAP SE

AR822

47

LOGO HERE

Adding & Editing ERP information The Trading Partner System Information page is now displayed. Step 2 of 6

Click Add to define a new backend system

@ Copyright. All rights reserved.

© SAP SE

AR822

48

LOGO HERE

Adding & Editing ERP information Add new backend SAP system information When you want to add ERP system information manually (not recommended), you need to provide following information:

Step 3 of 6 A. ERP Name (Select from the list of available values) B. ERP version (Select from the list of available values) C. System ID – Logical System ID of your ERP. D. Service Pack E. Middleware (Select from the list of available values) F. Middleware Version G. Time Zone (of your ERP system) H. AddOnInfo1 – ERP Software Component ARBCI1. Specify the version of the add-on SP you are using. I. AddOnInfo2 – ERP Software Component ARBCI2. Specify the version of the add-on SP you are using. J. AddOnInfoR – ERP Software Component ARBCIGR. Specify the version of the add-on SP you are using. Click Save @ Copyright. All rights reserved.

© SAP SE

AR822

49

LOGO HERE

Adding & Editing ERP information

The new backend system is now visible Click Finish

Step 4 of 6

@ Copyright. All rights reserved.

© SAP SE

AR822

50

LOGO HERE

Adding & Editing ERP information

Step 5 of 6

Click on the pencil icon to edit the information in the existing entry.

@ Copyright. All rights reserved.

© SAP SE

AR822

51

LOGO HERE Change the required fields (from the list of available values).

Adding & Editing ERP information

Click Save

Step 6 of 6

@ Copyright. All rights reserved.

© SAP SE

AR822

52

LOGO HERE

About This Lesson Lesson 4: Home Page By the end of this lesson, you will be able to: •

Navigate the CIG Home Page

This lesson includes the following topics: i.

Home Page navigation

@ Copyright. All rights reserved.

© SAP SE

AR822

53

LOGO HERE

Home Page

Once ERP system information is added, you will be navigated to Home page of your CIG account.

1. Integration Projects ü Displays all the projects & it’s statuses. ü Allows user to view; create; edit or delete the project. 2. Supplier Reporting ü Displays all the projects of connected suppliers & it’s statuses. ü Provides visibility on the status of supplier on-boarding. 3. Transaction Tracker ü Track the transaction documents that you have sent & received. ü Download payloads & attachments 4. Under My Projects, you will see a list of available integration projects 5. Create a New Integration Project button. @ Copyright. All rights reserved.

© SAP SE

AR822

54

LOGO HERE

About This Lesson Lesson 5: Configuring Ariba Cloud Integration Project By the end of this lesson, you will be able to: •

Configure an SAP Ariba Cloud Integration Project

This lesson includes the following topics: i.

Integration Project Wizard

ii.

Step-by-step instructions on how to configure an SAP Ariba Cloud Integration Project

@ Copyright. All rights reserved.

© SAP SE

AR822

55

LOGO HERE

Configuring Ariba Cloud Integration Project Integration Project Wizard • The Integration Project Wizard automates complex integration tasks by asking a series of easy-toanswer questions. • The answers you provide help Cloud Integration Gateway derive transaction configurations. • Tip: you can reuse the connection information for future integrations with other Ariba products. Let’s take a look at the steps!

@ Copyright. All rights reserved.

© SAP SE

AR822

56

LOGO HERE

Configuring Ariba Cloud Integration Project

Click Create a New Integration Project

Does this step look familiar? It should because we completed this step at the end of the “Home Page” lesson. Now, let’s take a look at the rest of the steps! @ Copyright. All rights reserved.

© SAP SE

AR822

57

LOGO HERE

Configuring Ariba Cloud Integration Project: Basic Information

We are now in the Project Wizard! Provide following basic information: • Project Name of your choice. Users are recommended to enter a meaningful name that helps to identify the project easily. • Select Product – Depending upon your solution adoption, choose the product – Ariba Network; Ariba Procurement or Ariba Sourcing.

You need to create a separate project for integrating with each SAP Ariba product.

• Click Next @ Copyright. All rights reserved.

© SAP SE

AR822

58

LOGO HERE

Configuring Ariba Cloud Integration Project: Connection for Direct Connectivity (1/5)

Step 1 of 5 To define Connection for a project you can do either of the following: Option A: Select from available connections by clicking on the down arrow sign of the connection listed in Reusable Connections table. This option is available only when you are creating second project. OR Option B: Create a fresh connection by clicking on Add New Connection button.

@ Copyright. All rights reserved.

© SAP SE

AR822

59

LOGO HERE

Configuring Ariba Cloud Integration Project: Connection for Direct Connectivity (2/5)

Step 2 of 5

•

Select from available connections by clicking on the down arrow sign of the connection listed in Reusable Connections table.

Option A: Select from available connections by clicking on the down arrow sign of the connection listed in Reusable Connections table. This option is available only when you are creating second project.

@ Copyright. All rights reserved.

© SAP SE

AR822

60

LOGO HERE

Configuring Ariba Cloud Integration Project: Connection for Direct Connectivity (3/5)

Step 3 of 5

In this example, the Connection Details drop down menu provides the Edit option. This means the connection is New and you can edit the connection information because it is not associated with any other project.

In this example, the Connection Details drop down menu excludes the Edit option. This means the connection is associated with other project, and can only be resued but can not be edited.

@ Copyright. All rights reserved.

© SAP SE

AR822

61

LOGO HERE

Configuring Ariba Cloud Integration Project: Connection for Direct Connectivity (4/5) Step 4 of 5 Option B: Create a fresh connection by clicking on Add new Connection button.

@ Copyright. All rights reserved.

© SAP SE

AR822

62

LOGO HERE To add a new connection, define or select appropriate values:

Configuring Ariba Cloud Integration Project: Connection for Direct Connectivity (1/5)

Transport Type – Choose Addon if you are integrating via Cloud Connector. If using middleware: choose HTTPS Environment – Choose the environment of your backend SAP system for which you are setting up the connection as TEST or PRODUCTION, or TEST/ PRODUCTION.

Step 5 of 5

Name – When you create a connection manually, the name can be of your choice. Spaces or Special Characters in the name are not allowed. System ID – Choose your SAP system’s Logical System ID.

Duplicate connection for a unique combination of SAP System ID + Document Type is prohibited. @ Copyright. All rights reserved.

© SAP SE

AR822

63

LOGO HERE

Configuring Ariba Cloud Integration Project: Connection for Direct Connectivity

There are two Connection Details pages:

This section holds information for connecting from CIG to your SAP system.

Connect to Backend

Connect Trading Partner to CIG

This section holds information for connecting from your SAP system to CIG.

@ Copyright. All rights reserved.

© SAP SE

AR822

64

LOGO HERE

Configuring Ariba Cloud Integration Project: Connection for Direct Connectivity - Connect to Banckend (1/2) Connect to Backend section:

Document Type: Choose “Any” to have all the document types covered under a single connection. Else, you will need to create separate connection for each of the document type.

Step 1 of 2

Domain Name – Virtual Host name of your SAP system maintained in SAP Cloud Connector configuration. Port – Virtual Port number of your SAP system maintained in SAP Cloud Connector configuration. Client ID – Your SAP system’s Client ID. Location ID – Your SAP Cloud Connector’s unique Location ID defined in SAP Cloud Connector configuration.

Document Type Example: In Ariba Network Integration scenario, customer may want to route inbound invoices (from Ariba Network) to ERP system through their Tax Management System or Vendor Invoice Management (VIM) System & rest of the incoming documents directlyto their backend ERP system. Then, customer can create 2 connections - one for inbound Invoice to Tax management System or VIM & other for rest of the inbound documents to ERP system. In such case, customer need to ensure that The Tax Management System or VIM is capable of handling & processing the IDOC or SOAP messages. Connectivity is built between their Tax Management System or VIM.

© SAP SE

AR822

@ Copyright. All rights reserved.

65

LOGO HERE

Configuring Ariba Cloud Integration Project: Connection for Direct Connectivity - Connect to Banckend (2/2) Connect to Backend section continued:

Step 2 of 2

Authentication – You can choose from the available values – Basic or Certificate Ø Basic: For this mode of authentication, provide Username & Password of your SAP system manually.

Ø Currently certificate authentication mode is not supported while connecting to backend on-premise SAP system via cloud connector (Direct Connect option).

@ Copyright. All rights reserved.

© SAP SE

AR822

66

LOGO HERE

Configuring Ariba Cloud Integration Project: Connection for Direct Connectivity - Connect Trading Partner to CIG (1/2)

Connect Trading Partner to CIG section:

Step 1 of 2

Authentication Type – You can choose from the available values – Basic or Certificate.

Ø Basic: For this mode of authentication, Username (P User ID) will be set automatically. You can not change the value of P User ID.

Ø

Certificate: If you select this mode of authentication, you need to add the public key of the certificate received from trusted CAs. (Certificate that is to be added should be in the BASE64 encoded format.)

@ Copyright. All rights reserved.

© SAP SE

AR822

67

LOGO HERE

Configuring Ariba Cloud Integration Project: Connection for Direct Connectivity - Connect Trading Partner to CIG (2/2)

Step 2 of 2 Duplicate certificates are prohibited.

@ Copyright. All rights reserved.

© SAP SE

AR822

68

Once all the required information is provided / verified:

LOGO HERE Click Save Click Next

Configuring Ariba Cloud Integration Project: Connection for Direct Connectivity

The connection is made available for production as soon as the project in which it has been configured is deployed to production.

© SAP SE

AR822

@ Copyright. All rights reserved.

69

LOGO HERE

Configuring Ariba Cloud Integration Project: Connection for Mediated Connectivity (1/2)

If you are connecting via middleware perform the following steps: 1. On the Connection tab either select existing connection from the list of Reusable Connections or click on Add New Connection. 2. Choose HTTPS as the Transport Type. 3. Choose the Environment of your connection as Test or Production or Test / Production. 4. Enter a Name for your connection in the Name field. 5. Choose the system to which you would like to connect to in the System ID field.

@ Copyright. All rights reserved.

© SAP SE

AR822

70

LOGO HERE

Configuring Ariba Cloud Integration Project: Connection for Mediated Connectivity (2/2)

@ Copyright. All rights reserved.

© SAP SE

AR822

71

LOGO HERE

Configuring Ariba Cloud Integration Project: Connection for Mediated Connectivity

There are two Connection Details pages:

This section holds information for connecting from CIG to your middleware.

Connect CIG to Trading Partner

Connect Trading Partner to CIG

This section holds information for connecting from your middleware to CIG.

@ Copyright. All rights reserved.

© SAP SE

AR822

72

LOGO HERE

Configuring Ariba Cloud Integration Project: Connection for Mediated Connectivity - Connect CIG to Trading Partner (1/3)

6. In the Connect CIG To Trading Partner section:

Choose the Document Type for the connections of this integration project. Choose ANY to support all document types. Choose a specific document type, if you want to restrict the project.

Enter the URL to connect to the middleware. See the information on next 2 pages.

Choose the Authentication Type for the middleware connection: •

Basic: Enter your middleware Username and Password to authenticate.

•

Certificate: Download the certificate & save on your middleware system.

@ Copyright. All rights reserved.

© SAP SE

AR822

73

LOGO HERE

Configuring Ariba Cloud Integration Project: Connection for Mediated Connectivity - Connect CIG to Trading Partner (2/3)

Middleware: SAP Process Integration A generic URL would be: https://:/XISOAPAdapter/MessageServlet?channel=::" Sample URL: https://samplepi:51101/XISOAPAdapter/MessageServlet?channel=:BS_ACIG:CC_CIG_S OAP_Sender Where: ü samplepi: is the server name ü 51101: is the port ü BS_ACIG: is the business system name ü CC_CIG_SOAP_Sender: is the communication channel name for the SAP Process Integration configuration scenario

@ Copyright. All rights reserved.

© SAP SE

AR822

74

LOGO HERE

Configuring Ariba Cloud Integration Project: Connection for Mediated Connectivity - Connect CIG to Trading Partner (3/3) Middleware: SAP CPI https://:/cxf/receiveCIGSOAP & / Or https://:/ cxf/receiveCIGSyncDocument Sample URL: https://arlkgt1-hcioem.avtsbhf.eu1.hana.ondemand.com:443/cxf/receiveCIGSOAP Where: ü arlkgt1-hcioem.avtsbhf.eu1.hana.ondemand.com: is the hostname ü 443: is the port For Network Integration; Sourcing Integration & Procurement Integration Async Flows: https://:/cxf/receiveCIGSOAP For Procurement Integration Sync Flows: https://:/ cxf/receiveCIGSyncDocument

If you are implementing Ariba Procurement Integration & deploying all the integration flows, then you need to create separate connections – one with synchronous document type and one with Document Type = Any for rest of the document types. @ Copyright. All rights reserved.

© SAP SE

AR822

75

LOGO HERE

Configuring Ariba Cloud Integration Project: Connection for Mediated Connectivity - Connect Trading Partner to CIG (1/2)

7. In the Connect Trading Partner to CIG section:

Choose the Authentication Type for the middleware connection: •

Basic: Your P User ID will get populated in Username filed. No password needed.

•

Certificate: Add your certificate or reuse an existing one. If you want to reuse a certificate that you already added, choose it in the Certificate Name section.

TEST URL & PROD URL of CIG will be displayed.

8. Click Save.

@ Copyright. All rights reserved.

© SAP SE

AR822

76

LOGO HERE

Configuring Ariba Cloud Integration Project: Connection for Mediated Connectivity - Connect Trading Partner to CIG (2/2)

About opening ports in SAP PI/PO When using any On Premise solution – there is only 1 IP (or “data center address”). However, when CIG is present, there is no static IP. Therefore, we must instead configure the IP Range in SAP PI. Please contact Ariba Customer Support to get the information on IP ranges for opening ports in SAP PI. @ Copyright. All rights reserved.

© SAP SE

AR822

77

LOGO HERE

Configuring Ariba Cloud Integration Project: Mappings In the CIG Buy Side Integration, standard mappings are developed in XSLT & stored in the database. Thus, you don’t need to perform any activities in this step. Click Next

@ Copyright. All rights reserved.

© SAP SE

AR822

78

LOGO HERE

Configuring Ariba Cloud Integration Project: Cross Reference-Parameters Follow these steps to define parameters:

In this section you need to define values in the parameter fields which you want to map. • The transactions & the related parameters are added by the administrator. • You can define the values for both test & production environments.

• Within the Parameters tab, select the Document Type from the dropdown menu •

Choose the document type being adopted/add the cross-reference mappings.

• Click Add

@ Copyright. All rights reserved.

© SAP SE

AR822

79

79

LOGO HERE Configuring Ariba Cloud Integration Project: Cross Reference-Parameters In this section you need to define values in the parameter fields which you want to map. • The transactions & the related parameters are added by the administrator. • You can define the values for both test & production environments.

Follow these steps to define parameters (continued): • Click the pencil icon to edit the entry

• Enter values for the parameters in the TEST Environment and PROD Environment. • If you want to have different value in PROD Environment, uncheck the box Use same values. Then click Save. These fields are part of the message that will be sent/received based on the document – the field must be mapped to the value – can be a standard value or created.

@ Copyright. All rights reserved.

© SAP SE

AR822

80

LOGO HERE

Configuring Ariba Cloud Integration Project: Cross Reference-Parameters In this section you need to define values in the parameter fields which you want to map. • The transactions & the related parameters are added by the administrator. Follow these steps to define parameters (continued): • You can define the values for both test & production environments. • Enter parameter values for another Document Type as needed or click Next.

@ Copyright. All rights reserved.

© SAP SE

AR822

81

LOGO HERE

Configuring Ariba Cloud Integration Project: Cross Reference-UOM Mappings

Once you define parameter values for all required Document Types, you will land on the UOM Template page:

UOM Mapping Requirements • Ariba Network (required) • SAP Ariba Sourcing (required) • SAP Ariba Procurement (excluded)

Follow these steps to define UOM Mappings: •

Click Download link to obtain the UOM.csv file.

@ Copyright. All rights reserved.

© SAP SE

AR822

82

LOGO HERE

Configuring Ariba Cloud Integration Project: Cross Reference-UOM Mappings

Once you define parameters values for all required Document Types, you will land on UOM Template page

UOM Mapping Requirements • Ariba Network (required) • SAP Ariba Sourcing (required) • SAP Ariba Procurement (excluded)

Follow these steps to define UOM Mappings (continued): •

Define the corresponding SAP ERP value for each Ariba Network specific UOM, and save the template.

@ Copyright. All rights reserved.

© SAP SE

AR822

83

LOGO HERE

Configuring Ariba Cloud Integration Project: Cross Reference-UOM Mappings

UOM Mapping Requirements • Ariba Network (required) • SAP Ariba Sourcing (required) • SAP Ariba Procurement (excluded)

Follow these steps to define UOM Mappings (continued): •

Select the System ID for which you would like to upload UOM maps; click on Upload link to add the template & click Next.

.

@ Copyright. All rights reserved.

© SAP SE

AR822

84

LOGO HERE

Configuring Ariba Cloud Integration Project: Cross Reference-UOM Mappings

UOM Mapping Requirements • Ariba Network (required) • SAP Ariba Sourcing (required) • SAP Ariba Procurement (excluded)

Example shown: For integration with SAP Ariba Procurement, UOM Mappings are maintained in the SAP Ariba Procurement realm. You don’t need to define it in CIG.

@ Copyright. All rights reserved.

© SAP SE

AR822

85

LOGO HERE

Configuring Ariba Cloud Integration Project: Cross Reference-Defining Lookup Values

Once you define UOM Mappings, you will land on Lookup Table page. Values in Lookup Table are required mainly for Real Time Budget Check; Total Landing Cost & Withholding Tax features of Ariba Procurement Integration & Quote Request feature of Ariba Sourcing Integration. • In the Document Types/Names column, click on Select to add document type & from the available list, choose the document type. The associated template to that document type will get displayed.

Follow these steps to define Lookup Values Mappings:

@ Copyright. All rights reserved.

© SAP SE

AR822

86

LOGO HERE

Configuring Ariba Cloud Integration Project: Cross Reference-Defining Lookup Values

• Expand the template node & enter the Ariba value & Customer value for the template in the TEST Environment and PROD Environment. • Click Next when values for all the required document types are configured.

@ Copyright. All rights reserved.

© SAP SE

AR822

87

LOGO HERE

Configuring Ariba Cloud Integration Project: Cross Reference-Defining Lookup Values

Additional document type example:

• Expand the template node & enter the Ariba value & Customer value for the template in the TEST Environment and PROD Environment. • Click Next when values for all the required document types are configured.

@ Copyright. All rights reserved.

© SAP SE

AR822

88

LOGO HERE

Configuring Ariba Cloud Integration Project: Cross Reference-Defining Lookup Values • Expand the template node & enter the Ariba value & Customer value for the template in the TEST Environment and PROD Environment.

Additional document type example:

• Click Next when values for all the required document types are configured.

@ Copyright. All rights reserved.

© SAP SE

AR822

89

LOGO HERE

Configuring Ariba Cloud Integration Project: Cross Reference-Defining Lookup Values Refer to the sample values per template given in below table:

Document type

Template Name

Sample SAP Ariba value

Sample customer value

RequisitionRealTimeBudgetExportRequest

TaxOnCompanyCode

3000

TRUE

PurchaseOrderExportRequest

ProcurementConditionType

PurchaseOrderChangeExportRequest

PaymentExportRequest

ProcurementConditionType

WithholdingTaxMap

Road Freight

FRBI

Air Freight

FRB2

Handling Charge

ZB00

Road Freight

FRB3

Handling

ZB00

WHTTAX1

T1

WHTTAX2

T2

WHTTAX3

T3

@ Copyright. All rights reserved.

© SAP SE

AR822

90

LOGO HERE

Configuring Ariba Cloud Integration Project: Cross Reference-Defining Realm If you are working on a project for Ariba Sourcing integration or Ariba Procurement integration, then once you define Lookup Table values, you will land on Realm ID page. Here you need to select the realm you would like the project to connect to. This is more important when you have multi-ERP (FPC) environment & creating different projects for each back-end system. Follow these steps to define Realm ID: 1. Select Realm ID to which you are connecting the specific back-end system ID you have defined while creating connection. 2. Click Next.

@ Copyright. All rights reserved.

© SAP SE

AR822

91

LOGO HERE

Configuring Ariba Cloud Integration Project: Configuration Confirmation After you have defined values for all the Cross References, you will land on Configuration Confirmation page. Here you can review the configuration details & modify any information as & if needed. 1. Click the pencil icon to edit, and modify the details of any configuration if needed. 2. Click Confirm.

@ Copyright. All rights reserved.

© SAP SE

AR822

92

LOGO HERE

Configuring Ariba Cloud Integration Project: Configuration Confirmation

Before you confirm the project, it will hold In Progress status.

Once the project is confirmed, the project status will be In Testing.

@ Copyright. All rights reserved.

© SAP SE

AR822

93

LOGO HERE

Configuring Ariba Cloud Integration Project: Test At this stage you need to decide whether to test the configured documents manually or you would want to use TestCentral, the automated test tool to execute the test scenarios programmatically / in automated way. 1. If you do not want to use TestCentral & perform manual testing, click on Skip Test. 2. If you want to use TestCentral, click on Run Test. The Execution Start Date can be set in either case.

• This is just a stop gap arrangement. Since the Self-Test framework is not ready, you will not find complete functionality of the framework working. • It is strongly recommended to execute all of your UAT scenarios in this phase before you Go Live.

@ Copyright. All rights reserved.

© SAP SE

AR822

94

LOGO HERE

Configuring Ariba Cloud Integration Project: Test At this stage you need to run the mandatory test cases either manually or via TestCentral. • When you choose Skip Test, system will ask your confirmation which represents your responsibility to execute all the necessary business test scenarios & achieve desired quality criteria. It is advisable to schedule / set the Execution Start Date to accommodate the timeframe, you need to complete UAT phase. • When you choose Run Test, you can schedule the testing activity at a specific date & time. All the test scenarios that you select will get executed.

@ Copyright. All rights reserved.

© SAP SE

AR822

95

LOGO HERE

Configuring Ariba Cloud Integration Project: Test

Once the testing is complete, the project status will be Tested.

@ Copyright. All rights reserved.

© SAP SE

AR822

96

LOGO HERE

Configuring Ariba Cloud Integration Project: Deployment Once you complete execution of UAT scenarios, the results will be captured in the background for each scenario defined in TestCentral as well as a successful execution of those scenarios,

Status will be updated as Completed. You can see result of individual test scenario in Pass / Fail column & the Go Live button activated. This means your project is ready to get deployed on production. Click the button to Go Live.

@ Copyright. All rights reserved.

© SAP SE

AR822

97

LOGO HERE

Managing Multiple Landscapes Usually, in SAP, a three-system landscape exists which consist of: •

Development Server –DEV

•

Test or Quality Assurance Server – TEST / QA

•

Production Server - PROD

This configuration is not meant as a system-failure preemptive measure but, as a configuration pipeline management. This pipeline approach is for a landscape where the configuration in the Development system is moved to the Quality Assurance / Test system and, finally, to the Production system. The advantages of the pipeline approach are as follows: ü All systems are synchronized for Production functionalities. ü Configuration changes are first done in Development, thoroughly tested in Quality Assurance and finally published in Production. ü The migration path from one server to the next is simple & often, automated. However, SAP Ariba exclusively features a landscape offering: •

Test Realm –TEST

•

Production Realm -PROD

@ Copyright. All rights reserved.

© SAP SE

AR822

98

LOGO HERE

Managing Multiple Landscapes The SAP Ariba standard landscape is based on a two-environment platform. All prework, design, configuration, testing and training is done in Test while Production is solely reserved for live business processes.

The advantages of this landscape are as follows: • Simplicity of maintenance due to low number of environments. • Limited synchronization efforts due to low number of environments.

@ Copyright. All rights reserved.

© SAP SE

AR822

99

LOGO HERE

Managing Multiple Landscapes If you have 3-tier landscape in SAP environment (SAP Dev; SAP Test & SAP Prod) & want to connect all 3 tiers with SAP Ariba, one of the following 3 options can be considered: 1. Disconnected SAP Dev environment: SAP Dev

>>>

Not connected with SAP Ariba

SAP Test

>>>

SAP Ariba Test

SAP Prod

>>>

SAP Ariba Prod

•

SAP DEV server disconnected from SAP Ariba environment.

•

SAP side development work done in SAP Dev & can be tested at component level only (may be using some simulators).

•

SAP side development work done in SAP Dev is then transported to SAP Test for further end-to-end configuration & testing.

•

Configuration and integration efforts are done in SAP Test.

•

SAP Test is paired with SAP Ariba Test.

•

Once the solution is ready, it is transported from SAP Test to SAP PROD while SAP Ariba Test is moved to SAP Ariba Prod.

•

Master Data from SAP Prod can also be loaded into SAP Ariba Test (as & if necessary).

•

Configuration or integration changes, as necessary, are done in SAP Test / SAP Ariba Test and, after testing, validation & approval, moved to SAP Prod / SAP Ariba Production.

•

In CIG portal, regular (single) project with 2 separate connections (Environment = TEST & Environment = PROD) is created.

@ Copyright. All rights reserved.

© SAP SE

AR822

100

LOGO HERE

Managing Multiple Landscapes 2. SAP Dev environment connected with SAP Ariba Test: SAP Dev

>>>

SAP Ariba Test

SAP Test

>>>

SAP Ariba Test

SAP Prod

>>>

SAP Ariba Prod

•

SAP Dev & SAP Test are paired with SAP Ariba Test.

•

SAP side development work done in SAP Dev & tested with SAP Ariba Test.

•

SAP side development work done in SAP Dev is then transported to SAP Test for further end-to-end configuration & testing.

•

Configuration & integration efforts start in SAP Dev.

•

Configuration & interfaces are then migrated to SAP Test.

•

A limited & specific set of data can be used to connect SAP Dev with SAP Ariba Test to avoid uploading duplicate master data in SAP Ariba Test (from SAP Dev & SAP Test).

•

If SAP Dev & SAP Test has overlapping master data, then consider using Content-based Routing in CIG to transmit the documents to appropriate back-end system (SAP Dev or SAP test).

•

With this approach, you will be able to keep & use 2 projects in CIG. One pointing to SAP Dev & other pointing to SAP Test + SAP Prod.

•

Once the solution is ready, SAP Test is moved to SAP PROD while SAP Ariba Test is moved to SAP Ariba Prod.

•

Master Data from SAP Prod can also be loaded into SAP Ariba Test (as & if necessary).

•

Configuration or integration changes, as necessary are done in SAP Dev / SAP Test / SAP Ariba Test and, after testing, validation & approval, moved to SAP Prod & SAP Ariba Prod.

•

In CIG portal: o o

Create a (single) project with 1 connection (Environment = TEST / PROD) is created & use for connecting SAP Dev to SAP Ariba Test. Make sure that this project is NOT deployed to PROD. Create another (single) project with 2 separate connections (Environment = TEST & Environment = PROD) is created & use for connecting SAP Test to SAP Ariba Test & SAP Prod to SAP Ariba Prod. @ Copyright. All rights reserved.

© SAP SE

AR822

101

LOGO HERE

Managing Multiple Landscapes 3. SAP Dev environment connected with SAP Ariba Supplemental realm (additional cost involved): SAP Dev

>>>

SAP Ariba Supplemental

SAP Test

>>>

SAP Ariba Test

SAP Prod

>>>

SAP Ariba Prod

•

SAP DEV server paired with SAP Ariba Supplemental.

•

SAP side development work done in SAP Dev & tested with SAP Ariba Supplemental.

•

SAP side development work done in SAP Dev is then transported to SAP Test for further end-to-end configuration & testing.

•

Configuration & integration done in SAP Ariba Dev is manually migrated / replicated to SAP Ariba Test.

•

Configuration & integration efforts start in SAP Dev.

•

Configuration & interfaces are then migrated to SAP Test.

•

SAP Test is paired with SAP Ariba Test.

•

Once the solution is ready, it is transported from SAP Test to SAP PROD while SAP Ariba Test is moved to SAP Ariba Prod.

•

Master Data from SAP Prod can also be loaded into SAP Ariba Test (as & if necessary).

•

Configuration or integration changes, as necessary are done in SAP Test / SAP Ariba Test and, after testing, validation & approval, moved to SAP Prod / SAP Ariba Production.

•

In CIG portal (Note that SAP Ariba Supplemental is an independent site with different ANID & CIG account. Thus, create projects in respective CIG account): o Create a (single) project with 1 connection (Environment = TEST / PROD) is created & use for connecting SAP Dev to SAP Ariba Supplemental.

•

Make sure that this project is NOT deployed to PROD. o Create another (single) project with 2 separate connections (Environment = TEST & Environment = PROD) is created & use for connecting SAP Test to SAP Ariba Test & SAP Prod to SAP Ariba Prod. o Custom mappings & / or engineering-driven custom mappings done in CIG account associated with SAP Ariba Supplemental need to be manually redone in CIG account associated with SAP Ariba Test.

@ Copyright. All rights reserved.

© SAP SE

AR822

102

LOGO HERE

Managing Multiple Landscapes Important considerations to be noted: • A supplemental site is an additional SAP Ariba Test realm completely disconnected from the standard environment where the SAP Ariba solution is being deployed. • A Supplemental site requires licenses & subscription services to be purchased for the additional environment. • Migration from SAP Ariba Dev to SAP Ariba Test is a manual process that must be considered accordingly in the Project Plan as it may take several days to be completed. • There is no standard or automated migration between the SAP Ariba Supplemental site & the SAP Ariba Test site. Thus, Supplemental site requires services, as configuration cannot be done in a self-service mode. • Supplemental site is created with a different ANID and linked to a different Ariba Network account. • Such Ariba Network account does not include any supplier enablement services as it only serves the purpose of integration testing. • Supplemental site behaves as any standard site, supporting CIG & not limiting the number of concurrent users. • Trying to simulate a Development environment with Supplemental site is theoretically possible but, it would require increasing the subscription services associated with the project, increasing the cost and the timelines. • As they lack Ariba Network support, additional cost in the shape of additional hours is required to cover any required configuration or change in the Ariba Network side. • Supplemental site is not meant to become the pair of the SAP Dev server. The most common use case for a Supplemental site is “Education and Training”. @ Copyright. All rights reserved.

© SAP SE

AR822

103

LOGO HERE

About This Lesson Lesson 6: Resetting P User Password By the end of this lesson, you will be able to:

• Reset P User password of SAP Ariba Cloud Integration Gateway.

@ Copyright. All rights reserved.

© SAP SE

AR822

104

LOGO HERE Resetting P User Password

In the event where you don’t remember your P User Password or you want to change the P User Password, you can use one of the following options to reset your P User Password of your Cloud Integration Gateway: 1. Through SAP Cloud Identity portal 2. Through CIG portal

@ Copyright. All rights reserved.

© SAP SE

AR822

105

LOGO HERE

Resetting P User Password – through SAP Cloud Identity Portal

1. Access https://aribaoperations.accounts.ondemand.com/

2. Provide email ID associated with your CIG & click Forgot Password

3. Once again provide email ID associated with your CIG & click Send

@ Copyright. All rights reserved.

© SAP SE

AR822

106

LOGO HERE

Resetting P User Password – through SAP Cloud Identity Portal (continued)

4. Open the email from your inbox & press Click here to reset your password

5. Provide new password and click Save

@ Copyright. All rights reserved.

© SAP SE

AR822

107

LOGO HERE

Resetting P User Password – through CIG Portal

1. Access CIG and navigate to My Configurations>>>Authorization. Click Change Password 2. On the Warning popup, click Accept. The warning popup is shown basically to remind you that when you change P User password, you need to make changes to the corresponding configuration objects where P User ID & password information is used. For example: 1. SAP Data Sync 2. RFC Destination’s Logon & Security info 3. Interface Setup for Web Services

3. Provide new password & click Submit.

@ Copyright. All rights reserved.

© SAP SE

AR822

108

LOGO HERE

About This Lesson Lesson 7: Configuring Multi-ERP for Network Integration

By the end of this lesson, you will be able to: •

Link one ore more SAP systems (Multiple ERP) to a single Ariba Network Buyer account through the Cloud Integration Gateway (CIG).

This lesson includes the following topics: Steps to configure multi-ERP in: i. ii.

Ariba Network Buyer Account CIG

iii. Cloud Connector iv. SAP NetWeaver PI v.

SAP CPI

Prerequisites: Raise a Service Request (SR) with Ariba Customer Support to enable your Ariba Network Buyer account for multi-ERP support.

@ Copyright. All rights reserved.

© SAP SE

AR822

109

LOGO HERE

Configuring Multi-ERP for Network Integration in Ariba Network Buyer account 1. Once Ariba Customer Support confirms the enablement of multi ERP for your AN Buyer Account, login to your AN Buyer account. Click on Administration dropdown & then click on Configuration

2. You will see Business Application IDs link enabled. You can see this link only if your AN Buyer Account is multi ERP enabled. Click on the link

@ Copyright. All rights reserved.

© SAP SE

AR822

110

LOGO HERE

Configuring Multi-ERP for Network Integration in Ariba Network Buyer account 3. You will see option to create Business Application IDs. Click Create

4. Provide details of your Business (SAP) System & other details. Click Save

@ Copyright. All rights reserved.

© SAP SE

AR822

111

LOGO HERE

Configuring Multi-ERP for Network Integration in Ariba Network Buyer account 5. You will see the Business System getting displayed under List of System IDs. Click Create again to provide details of your another Business (SAP) System if needed.

6. Provide details of your another Business (SAP) System & click Save. You will see all your Business Systems listed. Click Save & then click Done

@ Copyright. All rights reserved.

© SAP SE

AR822

112

LOGO HERE

Configuring Multi-ERP for Network Integration in Ariba Network Buyer account 7. Once all your Business Systems are created, you can assign it to your suppliers accordingly. To do so, click on Supplier Enablement dropdown & then click Active Relationships. You will see all suppliers connected to your AN Buyer.

8. Select the supplier to which you want to add Business System ID info & from More Actions dropdown, click Edit.

@ Copyright. All rights reserved.

© SAP SE

AR822

113

LOGO HERE

Configuring Multi-ERP for Network Integration in Ariba Network Buyer account 9. Go to Unique Supplier ID Configuration section & click Add.

10. Select System ID from the list you created & Vendor ID of the supplier in that Business System. Click Save.

11. If you have the same supplier in another Business System, repeat the step#13 and add Vendor ID of the supplier defined in that Business System.

All the Vendor IDs associated with respective Business Systems will then be displayed on the UI.

@ Copyright. All rights reserved.

© SAP SE

AR822

114

LOGO HERE

Configuring Multi-ERP for Network Integration in CIG In CIG, you would need to create separate project per ERP / Business System. Follow the below steps: 1. Send the ERP information of each SAP system to CIG. 2. Ensure that information of each SAP system is available in CIG>>>Basic Data & is accurate. 3. Create separate projects per SAP system & select relevant information in the connection tab while creating projects.

@ Copyright. All rights reserved.

© SAP SE

AR822

115

LOGO HERE

Configuring Multi-ERP for Network Integration in Cloud Connector In Cloud Connector, you would need to define different Internal Systems corresponding to each ERP system.

@ Copyright. All rights reserved.

© SAP SE

AR822

116

LOGO HERE

Configuring Multi-ERP for Network Integration in SAP NetWeaver PI In PI, you would need to add the condition in Receiver Determination.

@ Copyright. All rights reserved.

© SAP SE

AR822

117

LOGO HERE

Configuring Multi-ERP for Network Integration in SAP CPI 1. Maintain value mappings for SAP System ID & Virtual Host / Port. Virtual host & port should be the same as defined in Cloud Connector for that particular SAP System ID.

2. Maintain value mappings for SAP System ID & SAP Credentials.

These are virtual user credentials for which you will need to define mappings with actual user credentials in a later step. @ Copyright. All rights reserved.

© SAP SE

AR822

118

LOGO HERE

Configuring Multi-ERP for Network Integration in SAP CPI 3. Maintain value mappings for SAP System ID & Cloud Connector Location ID.

4. Maintain mappings for SAP Credentials & SAP Login Info: a. Under Manage Security, click on Security Material.

@ Copyright. All rights reserved.

© SAP SE

AR822

119

LOGO HERE

Configuring Multi-ERP for Network Integration in SAP CPI 5. Maintain mappings for SAP Credentials & SAP Login Info b. Click on User Credentials.

6. Maintain mappings for SAP Credentials & SAP Login Info c. Add SAP User ID & Password for the Credentials maintained in Value Mappings in step#2.

@ Copyright. All rights reserved.

© SAP SE

AR822

120

LOGO HERE

Custom Mapping Tool

@ Copyright. All rights reserved.

© SAP SE

AR822

121

LOGO HERE

About This Lesson Lesson 1: Overview By the end of this lesson, you will be able to: •

Navigate the Custom Routing Tool

•

Understand the feature and functions of Custom Mapping Tool

This lesson contains the following use cases: i.

Feature Overview

ii. Execution Flow iii. Supported Version @ Copyright. All rights reserved.

© SAP SE

AR822

122

LOGO HERE

Mapping Tool Overview Mapping Tool The mapping tool provides added self-service in CIG which helps support the hefty demand of custom mappings. Using this feature the buyer can do the following:

Create & Edit Customization Deploy/ Undeploy & Manage versions Test Compare

@ Copyright. All rights reserved.

© SAP SE

AR822

123

LOGO HERE

Mapping Tool Overview Flow:

ØCIG executes the standard mappings. ØCustom XLSTs via SRs. ØCIG executes the mappings done via mapping tool.

Standard Mappings

SR Custom Mappings

Mapping tool Custom Mappings

@ Copyright. All rights reserved.

© SAP SE

AR822

124

LOGO HERE

Mapping Tool Overview Access Mapping tool: • Log in to Cloud Integration Gateway. • Go to My Configurations. • Navigate to Mappings.

@ Copyright. All rights reserved.

© SAP SE

AR822

125

LOGO HERE

Mapping Tool Overview

Supported CIG AddOn Versions: Ø

Starts from ADDONINFO 1 - ARBCI10003

Ø

Starts from ADDONINFO 2 - ARBCI20003

Ø

Please check the support policy for updated information, SAP Note: 2400737

@ Copyright. All rights reserved.

© SAP SE

AR822

126

LOGO HERE

About This Lesson Lesson 2: Features By the end of this lesson, you’ll be able to : • • •

Create & Edit Customizations Deploy, Un-deploy, and Manage Versions Test a Custom Map

Lesson Topics • Create Customization • Edit Customization • Deploy Customization • Testing Customization

@ Copyright. All rights reserved.

© SAP SE

AR822

127

LOGO HERE

Features: Create & Edit Customization Create a new custom mapping: Go to the Mappings tab under My Configuration: 1. Select the Transaction for which you want to do the customization; Click ADD.

2. On the Document Mapper screen; Select the System ID from the drop down menu and Click OK.

3. On the Document Mapping screen, Map the Source Node to Target Node and Click Save Mapping

@ Copyright. All rights reserved.

© SAP SE

AR822

128

LOGO HERE

Features: Create & Edit Customization Edit custom mappings: Go to the Mappings tab under My Configuration: 1. Select the transaction for which you want to edit the customization. Click Edit icon

2. On the Document Mapping screen, Edit the Source Node to Target Node mapping and click Save Mapping

@ Copyright. All rights reserved.

© SAP SE

AR822

129

LOGO HERE

Features: Deploy/Un-deploy & Manage Versions Deploy custom mappings: Go to the Mappings tab under My Configuration: 1.

Select the Transaction you want to manage. Click List Versions

2.

On the Mapping Version Details screen, select Version & Deployment mode and click Close

@ Copyright. All rights reserved.

© SAP SE

AR822

130

LOGO HERE

Features: Deploy/Un-deploy & Manage Versions 3. On the My Configurations screen, verify the selected deployment version and mode is marked correctly.

@ Copyright. All rights reserved.

© SAP SE

AR822

131

LOGO HERE

Features: Testing Custom Map Testing Custom Mappings:

Go to the Mappings tab under My Configuration:

1.

Select the Transaction you want to test, click Test Mapping

2.

On the Mapping Testing Tool screen, Browse or Copy the input content

@ Copyright. All rights reserved.

© SAP SE

AR822

132

LOGO HERE

Features: Testing Custom Map 3. Select SystemID and click Test

4.

On the Mapping Testing Tool screen, check the mapping tool extension transformation

@ Copyright. All rights reserved.

© SAP SE

AR822

133

LOGO HERE

About This Lesson Lesson 3: Node Functions By the end of this lesson, you’ll be able to : •

Describe, and provide examples of, the node functions

•

Identify and execute specific custom mapping use cases

This lesson includes the following topics:

1. Node Functions 2. Use Cases

@ Copyright. All rights reserved.

© SAP SE

AR822

134

LOGO HERE

Node Functions

@ Copyright. All rights reserved.

© SAP SE

AR822

135

LOGO HERE

Use Cases • Map extrinsic at header level • Map extrinsic at item level • Map a new optional element/ Concatenate/ Sub-string • Delete a mapped element • Format Number • Normalize • Format Date • Map a Child Value form source structure to a Parent field in target structure • Choose When • Map text node to item level extrinsic • Create/ Replace node @ Copyright. All rights reserved.

© SAP SE

AR822

136

LOGO HERE

Use Cases: Map Extrinsic at Header Level EXAMPLE: Map SAP Purchase Order document type to OrderRequest cXML extrinsic (Map E1EDK01-BSART to Extrinsic(2) and Add Constant Value to Extrinsic-Name) Go to the Mappings tab under My Configuration and select the Transaction

1. Select the Extrinsic at Header level, click Duplicate Node

@ Copyright. All rights reserved.

© SAP SE

AR822

137

LOGO HERE

Use Cases: Map Extrinsic at Header Level 2. On cXML Order Request Screen verify the new Extrinsic field

3. On cXML Order Request Screen, click the Target Node and click Add Constant Value

@ Copyright. All rights reserved.

© SAP SE

AR822

138

LOGO HERE

Use Cases: Map Extrinsic at Header Level 4. Enter the Extrinsic name and click Ok

5. On the Document Mapping screen, map the Source Node to Target Node and click Save Mapping

6. Give the sample payload and run Test

@ Copyright. All rights reserved.

© SAP SE

AR822

139

LOGO HERE

Use Cases: Map Extrinsic at Item Level EXAMPLE: Map SAP Material Group to cXML OrderRequest in OrderRequest>>ItemOut>>ItemDetail>>Extrinsic

Go to the Mappings tab under My Configuration and select the Transaction

1. Select the Extrinsic at Line level, click the Duplicate Node option.

@ Copyright. All rights reserved.

© SAP SE

AR822

140

LOGO HERE

Use Cases: Map Extrinsic at Item Level 2. Map E1EDP01>>MATKL to ItemDetail>>Extrinsic and hard-code the extrinsic name to MaterialGroup

3. Loop the material group for all the line items, right-click on the mapping line and choose Target Variable, click Add Position Variable

@ Copyright. All rights reserved.

© SAP SE

AR822

141

LOGO HERE

Use Cases: Map Extrinsic at Item Level 4.

Check for the highlighted text Select an Item on the target structure.

5. Select the structure with multiple occurrence, click the root node of extrinsic(2) i.e ItemOut from the structure.

@ Copyright. All rights reserved.

© SAP SE

AR822

142

LOGO HERE

Use Cases: Map Extrinsic at Item Level 6.

Add source condition to loop the segments, right-click on the mapping line and choose Add Source Condition

7. Select a condition item as E1EDP01 since E1EDP01 and ItemOut are in the same level.

@ Copyright. All rights reserved.

© SAP SE

AR822

143

LOGO HERE

Use Cases: Map Extrinsic at Item Level 8. From the pop-up choose Position Variable radio button, click Ok

9. On the Document Mapping screen, click Save Mapping

@ Copyright. All rights reserved.

© SAP SE

AR822

144

LOGO HERE

Use Cases: Map Extrinsic at Item Level 10. Give the sample payload and run Test

@ Copyright. All rights reserved.

© SAP SE

AR822

145

LOGO HERE

Use Cases: Delete a Mapped Element If a buyer does not want to send certain nodes to the target system, then they can suppress the details using this node function. Ex: Buyer does not want to send the accounting details to the supplier. Go to the Mappings tab under My Configuration and select the Transaction 1. Select the target segment to suppress, click on the Distribution Node on cXML Order Request and Delete

2. On cXML Order Request screen, check for the Red Line against Distribution node

@ Copyright. All rights reserved.

© SAP SE

AR822

146

LOGO HERE

Use Cases: Delete a Mapped Element 3. On the Document Mapping screen, click Save Mapping

4. Give the sample payload and run Test

@ Copyright. All rights reserved.

© SAP SE

AR822

147

LOGO HERE

Use Cases: Format Number This function is used for formatting different numeric values. Ex: If the amount value is 10.1999, and if we introduce a format number function with formatting 0.00, then the output would be 10.20. ERPOrder_PurchOrdLineDetails_Item>>ServiceDetails>>MaxAmo unt (fx) à POITEMS>>ITEM>>Maxamount Go to the Mappings tab under My Configuration and select the Transaction 1. Select the mapping where you want to add the function, rightclick on the Mapping Line, click Functions 2. On the selection screen, choose Add Function, click Add Format Number Function

@ Copyright. All rights reserved.

© SAP SE

AR822

148

LOGO HERE

Use Cases: Format Number 3. On the pop-up screen, enter the Number Format Pattern in the box, click OK, click Save Mapping

4. Give the sample payload and run Test

SOURCE

TARGET

@ Copyright. All rights reserved.

© SAP SE

AR822

149

LOGO HERE

Use Cases: Format Date This function is used for formatting different Date types. EX: Source has a date format like 2019-01-28 (YYYY-MM-DD) and if we need to change the date format to 2019-28-01 (YYYY-DD-MM), then add date format function like [Y0001]-[D01]-[M01]. Go to the Mappings tab under My Configuration and select the Transaction 1.

Select the mapping where you want to add the function, right-click on the Mapping Line, click Functions

2.

On the selection screen, choose Add Function, click Add Format Date Function

@ Copyright. All rights reserved.

© SAP SE

AR822

150

LOGO HERE

Use Cases: Format Date 3.

On the Pop-up screen, enter the Date Format Pattern, click OK, click Save Mapping

4.

Give the sample payload and run Test

@ Copyright. All rights reserved.

© SAP SE

AR822

151

LOGO HERE

Use Cases: Normalize Function This function is used for normalizing any field values. Ex: Removes white spaces from the field value. Go to the Mappings tab under My Configuration and select the Transaction 1. Select the mapping where you want to add the function, right-click on the Mapping Line, click Functions

2. On the selection screen, choose Function, click Save Mapping

Add Function, click Add Normalize

@ Copyright. All rights reserved.

© SAP SE

AR822

152

LOGO HERE

Use Cases: Normalize Function 3. Give the sample payload and run Test SOURCE

TARGET

@ Copyright. All rights reserved.

© SAP SE

AR822

153

LOGO HERE

Use Cases: Map a Child Value from Source Structure to Parent Field in Target Structure EXAMPLE: Mapping certain filed at line level to a field in header level based on a condition. Map E1EDP01>>E1EDP02>>BELNR(QUALF = 002) from source to OrderRequestHeader>>@parentAgreementID Go to the Mappings tab under My Configuration and select the Transaction

1. Select the E1EDP01 from source structure, Map E1EDP02>BELNR to OrderRequestHeader-@parentAgreementID.

@ Copyright. All rights reserved.

© SAP SE

AR822

154

LOGO HERE

Use Cases: Map a Child Value from Source Structure to Parent Field in Target Structure 2. Add Source Condition on the mapping line with field QUALF(Qualifier).

3. Select the condition item as QUALF, check for the pop-up

@ Copyright. All rights reserved.

© SAP SE

AR822

155

LOGO HERE

Use Cases: Map a Child Value from Source Structure to Parent Field in Target Structure 4. Enter the qualifier as 002 or the required qualifier, click OK

5.

Now, again click the mapping line, choose Select a Condition Item, then select the first line via mapping (as the reference remains same across all line items); click Add Source condition and click E1EDP01

@ Copyright. All rights reserved.

© SAP SE

AR822

156

LOGO HERE

Use Cases: Map a Child Value from Source Structure to Parent Field in Target Structure 6. Check for the condition pop-up, enter from which line item the value needs to be selected, Enter 1, click OK

7.

Give the sample payload and run Test

@ Copyright. All rights reserved.

© SAP SE

AR822

157

LOGO HERE

Use Cases: Map a Child Value from Source Structure to Parent Field in Target Structure

First line item E1EDP02>>BELNR is 123. This need to be mapped to parentAgreementID at OrderRequestHeader.

@ Copyright. All rights reserved.

© SAP SE

AR822

158

LOGO HERE

Use Cases: Choose When This node function is similar to if and else structure. SOURCE

Ex: If ExternalLineNumber exists, map it to target else map ERPLineItemNumber. ERPOrder_POLineLineDetailItem>>Item>>LineItems>>Item –X/XX à PO_Items>>Item>>PO_Item Go to the Mappings tab under My Configuration and select the Transaction 1. Select the mapping where you want to add the function, right-click on the Mapping Line, click on Choose When and create.

@ Copyright. All rights reserved.

© SAP SE

AR822

159

LOGO HERE

Use Cases: Choose When 2. On the selection Screen, choose operator as non empty

3. Choose the second field and map it to same target, right-click (again) on the Mapping Line, click Choose When and create.

@ Copyright. All rights reserved.

© SAP SE

AR822

160

LOGO HERE

Use Cases: Choose When 4. On the selection Screen, choose Operator as non empty and Order as 2.

5. Give the sample payload and run Test.

@ Copyright. All rights reserved.

© SAP SE

AR822

161

LOGO HERE Map Text Node to Item Level Extrinsic Use Cases:

Mapping item level long text to ne Extrinsic field. Ex: In OrderRequest IDOC E1EDPT1>>E1EDPT2 will contain the long text. This need to be mapped to line level extrinsic. Go to the Mappings tab under My Configuration and select the Transaction

1. Select the mapping where you want to add the condition, map E1EDPT2-TDLINE to Extrinsic at ItemDetail level

@ Copyright. All rights reserved.

© SAP SE

AR822

162

LOGO HERE

Use Cases: Map Text Node to Item Level Extrinsic

2. Right-click on the Mapping Line and choose Target Variable>>Set Variable>> Position

3. Select a condition item and choose ItemOut which is used for loop.

@ Copyright. All rights reserved.

© SAP SE

AR822

163

LOGO HERE Map Text Node to Item Level Extrinsic Use Cases:

4. Add source condition. Choose the similar path in the source condition E1EDP01 with condition type Position Variable and also the specific TDID to be picked.

5. Add the 2nd source condition to pick the specific TDID, the reason is there might be different TDIDs (Long Text)..

@ Copyright. All rights reserved.

© SAP SE

AR822

164

LOGO HERE Use Cases: Map Text Node to Item Level Extrinsic

6. Add condition value as Z.

7. Give the sample payload and run Test.

@ Copyright. All rights reserved.

© SAP SE

AR822

165

LOGO HERE

About This Lesson Lesson 4: Limitations By the end of this lesson, you will be able to: •

Identify custom mapping tool limitations

@ Copyright. All rights reserved.

© SAP SE

AR822

166

LOGO HERE

Limitations • Comments ØIDOC to cXML - We cannot map the IDOC comments to comments node in cXML. ØcXML to IDOC/Proxy - For example in IDOC, the comments need to be mapped to TDLINE and length of TDLINE is 70 characters. In CIG mappings, we cannot split the comments and create multiple TDLINE

• A standard output which got generated cannot be changed. Customer will have to do the mapping from source to target again. • Customer cannot see the standard mapping lines and manual customizations (Done by Engineering). • Concatenate function: Max 3 fields only can be concatenated. • Adding multiple conditions via Choose When is not supported.

@ Copyright. All rights reserved.

© SAP SE

AR822

167

LOGO HERE

Content Based Routing

@ Copyright. All rights reserved.

© SAP SE

AR822

168

LOGO HERE

About This Lesson Lesson 1: Overview By the end of this lesson, you will be able to: •

Navigate the Custom Routing Tool

•

Understand the feature and functions of Custom Routing Tool

This lesson includes the following topics: •

Flow Overviews

•

Feature and Functions

@ Copyright. All rights reserved.

© SAP SE

AR822

169

LOGO HERE

Overview Buyers can use custom routing to route transaction documents to the specific ERP client system based on the system ID of the ERP system and certain conditions. Using this feature the buyer can do the following:

Create & Edit Custom Routing for Document Type

XPath Based Document Routing

@ Copyright. All rights reserved.

© SAP SE

AR822

170

LOGO HERE

Overview

SAP S/4 Hana Company Code - 1000

System ID 1

SAP ECC Company Code - 2000

Ariba Network or SAP Ariba Applications

Cloud Integration Gateway

System ID 2

@ Copyright. All rights reserved.

© SAP SE

AR822

171

LOGO HERE

Overview To navigate to Mapping Tool in CIG follow the below steps: 1. Login to Cloud Integration Gateway. 2. Go to My Configurations. 3. Navigate to Custom Routing.

@ Copyright. All rights reserved.

© SAP SE

AR822

172

LOGO HERE

About This Lesson Lesson 2: Configuration Steps By the end of this lesson, you will be able to: •

Configure content based routing

This lesson includes the following topics: i.

Create custom routing

@ Copyright. All rights reserved.

© SAP SE

AR822

173

LOGO HERE

Configuration Steps

1. Go to the Custom Routing tab under My Configuration.

2. Click Create Custom Routing.

@ Copyright. All rights reserved.

© SAP SE

AR822

174

LOGO HERE

Configuration Steps

3. Select Direction and Document Type, enter values for Name and Description.

4. From the Action Value drop down, select the System ID for which you want to do the CBR.

@ Copyright. All rights reserved.

© SAP SE

AR822

175

LOGO HERE

Configuration Steps

5. On the conditions section click on the + sign to add Xpath

. 6. Either you can select a Possible XPath from the available list, or click New XPath

@ Copyright. All rights reserved.

© SAP SE

AR822

176

LOGO HERE

Configuration Steps

7. Enter values for Name and Description, select the Data Type.

8. Select the XPath of the node for which you want to do the CBR.

@ Copyright. All rights reserved.

© SAP SE

AR822

177

LOGO HERE

Configuration Steps

9. Select the Operand from the drop down.

10. Under Operand, select EXISTS

11. Click Save.

@ Copyright. All rights reserved.

© SAP SE

AR822

178

LOGO HERE

Outbound

AN System ID – AN1

System ID – S1

AN System ID – AN2 Ariba Network Cloud Integration Gateway

Buying and Invoicing

System ID – S2

@ Copyright. All rights reserved.

© SAP SE

AR822

179

LOGO HERE

About This Lesson Lesson 3: Operands By the end of this lesson, you will be able to: •

Describe the operands allowed when defining an XPath

This lesson includes the following topics: i.

Operands allowed for String Data Type

ii.

Operands allowed for Numeric Data Type

@ Copyright. All rights reserved.

© SAP SE

AR822

180

LOGO HERE

Operands This function is used for adding different conditions for defining XPath. Ø For String Data Type. Ø For Numeric Data Type.

Operands Allowed for String Data Type

S.No 1 2 3 4 5 6 7 8 9

© SAP SE

Operand Equals Not equals Not begins with Not null or empty Exists Not exists Contains Not contains Begins with

AR822

Operands Allowed for Numeric Data Type

S.N Operand o 1 Greater than 2 Less than Greater than or 3 equal 4 Less than or equal 5 Equals @ Copyright. All rights reserved.

181

LOGO HERE

About This Lesson Lesson 4: Use Cases By the end of this lesson, you will be able to: •

Configure company code based routing

This lesson includes the following topics: i.

Company code based routing

@ Copyright. All rights reserved.

© SAP SE

AR822

182

LOGO HERE

Company Code Based Routing Ex: Maintain a custom routing condition where company code 1000 and 2000 need to point to one backend system B1 and company code 3000 and 4000 need to point to backend system B2. Go to the Custom Routing tab under My Configuration and click on Create Custom Routing.

1. Select Direction and Document Type, enter values for Name and Description.

2. From the Action Value drop down, select the System ID B1.

@ Copyright. All rights reserved.

© SAP SE

AR822

183

LOGO HERE

Company Code Based Routing 3. Click on the New XPath button, enter Name and Description.

4. Enter value of XPath as: /PurchaseOrderExportRequest/ERPOrder_PurchOrdHeaderDetails _Item/item/CompanyCode[UniqueName=1000 or UniqueName=2000]

@ Copyright. All rights reserved.

© SAP SE

AR822

184

LOGO HERE

Company Code Based Routing 5. Select the Operand as EXISTS, click Save

6.

From the Action Value drop down, select the System ID B2.

@ Copyright. All rights reserved.

© SAP SE

AR822

185

LOGO HERE

Company Code Based Routing 7. Enter value of XPath as /PurchaseOrderExportRequest/ERPOrder_PurchOrdHeaderDetails_Item/it em/CompanyCode[UniqueName=3000 or UniqueName=4000]

Click Save

8. Select the Operand as EXISTS, click Save 9. Check the CBR overview screen.

@ Copyright. All rights reserved.

© SAP SE

AR822

186

LOGO HERE

About This Lesson Lesson 5: Sample XPaths By the end of this lesson, you will be able to: •

Recognize various Xpath Examples

This lesson includes the following topics: i.

XPath examples

@ Copyright. All rights reserved.

© SAP SE

AR822

187

LOGO HERE

Sample XPaths

S.No

XPath Examples

1

/cXML/Request/InvoiceDetailRequest/InvoiceDetailRequestHeader/*[@role ='billTo' and @addressID = '0001']/Name

2

/cXML/Request/InvoiceDetailRequest/InvoiceDetailRequestHeader/InvoicePartner/Contact[@role='remitTo']/PostalAddress/City

3

/cXML/Request[1]/InvoiceDetailRequest[1]/InvoiceDetailOrder[1]/InvoiceDetailItem[LineNum]/InvoiceDetailItemReference[1]/Description[1]

4

/cXML/Header/To/Credential[@domain='SystemID']/Identity

5

/PurchaseOrderExportRequest/ERPOrder_PurchOrdHeaderDetails_Item[1]/item[1]/CompanyCode[1]/UniqueName[1]

@ Copyright. All rights reserved.

© SAP SE

AR822

188

LOGO HERE

About This Lesson Lesson 6: Limitations By the end of this lesson, you will be able to: •

Understand the limitations of content based routing

This lesson includes the following topics: i.

Limitations

@ Copyright. All rights reserved.

© SAP SE

AR822

189

LOGO HERE

Limitations

Content Based Routing Limitations: 1. Adding more than two conditions for a transaction is not possible. 2. SAP Ariba Cloud Integration Gateway doesn’t support custom routing for suppliers.

@ Copyright. All rights reserved.

© SAP SE

AR822

190

LOGO HERE Section Complete

Congratulations! You have now completed this Section!

@ Copyright. All rights reserved.

© SAP SE

AR822

191