Connecting and Integrating with Multiple Ariba Network Accounts

• Perform necessary activities to enable CIG from your respective / individual Ariba Network Buyer accounts.
• Secure P User ID & password of each CIG account associated with respective Ariba Network Buyer accounts.

Remote Function Call (RFC) is the standard SAP interface for communication between SAP systems. RFC calls a function to be executed in a remote system.

There is now a whole series of different RFC variants, each of which has different properties and is used for a specific purpose.

You will need to create RFC Destinations for each Ariba Network Account ID (also referred to as ANID).

To create your RFC Destinations, navigate to:

• Integration with Other SAP Components
• SAP Ariba Cloud Integration Gateway
• Global Settings
• Create RFC Destination
• Example: You have two AN Buyer Accounts: ANID-1 and ANID-2.
  • The first RFC Destination will use P User ID & Password of CIG account enabled from ANID-1 with appropriate Path Prefix.
  • The second RFC Destination will use P User ID & Password of CIG account enabled from ANID-2 with appropriate Path Prefix.
  • If you are also adopting Article Master Data integration, then you will create 1 more RFC Destination per ANID using the appropriate Path Prefix.

You need to create 2 separate Ports & assign appropriate RFC Destinations created in the previous steps (2.2).

To create your Ports, navigate to:

• Integration with Other SAP Components
• SAP Ariba Cloud Integration Gateway
• Global Settings
• Create Port definition
• Example: You have two AN Buyer Accounts: ANID-1 and ANID-2.
  • In the first Port, you will assign RFC Destination created for ANID-1.
  • In the second Port, you will assign RFC Destination created for ANID-2.
  • If you are adopting Article Master Data integration, then you will create 1 more Port Definition per RFC Destination.

Configuring Receiver Port is to establish association of Port with a specific solution – Ariba Network or Ariba Applications (for Article Master Data Integration only).

To create your Ports, navigate to:

• Integration with Other SAP Components
• SAP Ariba Cloud Integration Gateway
• Global Settings
• Configure Receiver Port

Ariba AddOn program uses value configured in Receive Port for a specific solution in Receiver Port field while creating Partner Profile (WE20) via Interface Setup report for a given Logical System.

Ariba AddOn allows assigning only one value per solution in Receiver Port configuration.

Example: You have two AN Buyer Accounts: ANID-1 and ANID-2

• In this case, you need to create 2 Logical Systems to have 2 separate set of Partner Profiles created pointing to 2 separate AN Buyer / CIG accounts.
• Separate Logical Systems are required to create 2 separate sets of Inbound & Outbound parameters in Partner Profile configuration to communicate with 2 separate Ariba Network Buyer / CIG accounts.
• Logical System ID created for ANID-1 will be used in Interface Setup program to automatically create Partner Profiles (in WE20) for the selected documents you would work with for ANID-1.
• Logical System ID created for ANID-2 will be used to manually create Partner Profiles (in WE20) for the selected documents you would work with for ANID-2.

To create Logical Systems, navigate to:

• Integration with Other SAP Components
• SAP Ariba Cloud Integration Gateway
• Global Settings
• Create Logical System

Click New Entries, create a Logical System for each ANID

ANID-1 example naming for Logical System: ARBCIG1

ANID-2 example naming for Logical System ARBCIG2

You need to execute the report provided in Ariba AddOn SPRO to programmatically send SAP system information to respective CIG accounts.

Since you will be working with multiple AN Buyer / CIG accounts, you will have to execute the report for each AN Buyer / CIG account by providing appropriate credentials & information.

To create your Ports, navigate to:

• Integration with Other SAP Components
• SAP Ariba Cloud Integration Gateway
• Global Settings
• Send SAP Information to SAP Ariba Cloud Integration Gateway

Click IMG activity Synchronize SAP Information with SAP Ariba Cloud Integration Gateway.

Interface Setup will create:

• Partner Profile (Inbound & Outbound parameters in WE20) for IDOCs
• Logical Ports (in SOAMANAGER) for Web Services / Proxies

You need to execute Interface Setup report for each solution (Ariba Network & Sourcing Integration).

Interface Setup report refers to Logical System (for creating Partner Profile) & P User information (for creating Logical Ports).

Creating Partner Profile

Example: You have 2 AN Buyer Accounts, for example ANID-1 & ANID-2.

For creating Partner Profile, when you provide Logical System, Ariba AddOn program uses Receiver Port information created as a part of Global Settings activity to create Inbound & Outbound parameters for that particular Logical System.

• Since Ariba AddOn allows assigning only one value per solution in Receiver Port configuration, you can execute Interface Setup program ONLY for ANID-1.
• The Receiver Port will have a specific RFC Destination associated with it which will hold end-point information such as Target Host; Target Port & Authentication (P User ID & Password).
• Thus, you should NOT execute Interface Setup program for both the Logical Systems. This will not help in creating 2 separate Partner Profiles for 2 separate Logical Systems in WE20.
• Thus, you need to manually create Partner Profile (LS) entries & inbound / outbound parameters for ANID-2 using respective Port Definition value created for ANID-2.

Creating Logical Ports

Example: You have 2 AN Buyer Accounts, for example ANID-1 & ANID-2 which will have 2 separate P User IDs, for example, P01234 & P05678.

For creating Logical Ports, when you provide P User as an authentication method, Ariba AddOn program uses that information to create Logical Ports.

• Since Ariba AddOn program overwrites the Logical Ports each time you execute Interface Setup program, you can not use the report to create Logical Ports for connecting to both CIG accounts.
• Executing Interface Setup program one-by-one even using respective / different P User information will not help in creating 2 separate set of Logical Ports for 2 separate CIG accounts in SOAMANAGER.
• You should execute the Interface Setup report by providing necessary information ONLY for ANID-1.
• Thus, you need to manually create Logical Port entries in SOAMANAGER for ANID-2 using respective P User information for ANID-2.

To execute Interface Setup report, navigate to:

• Integration with Other SAP Components
• SAP Ariba Cloud Integration Gateway
• Ariba Network Integration
• General Settings
• Setup the Interface

Click on IMG activity Configure the Connections to Send Messages

Provide Logical System ID created for ANID-1 & P User information of ANID-1.

Example: You have two AN Buyer Accounts: ANID-1 and ANID-2 which will have separate P User IDs:

• ANID-1 example P User ID: P01234
• ANID-2 example P User ID: P05678

By executing Interface Setup report, you have created Partner Profile (Inbound & Outbound parameters in WE20) for IDOCs for ANID-1 / P01234.

Now, you need to manually create Partner Profile for ANID-2 / P05678 by accessing TCode WE20.

To manually create Partner Profile:

1. On the SAP Easy Access page, run the TCode WE20 – The Partner profiles screen appears.
2. Click on Create icon.
3. Enter following information:
   • Partner No.: Enter the value of Logical System you have created in earlier step for ANID-2.
   • Partner Type: Select LS (Logical System).
4. In Post processing: permitted agent tab, enter following information
   • Ty: Select US (User).
   • Agent: Select User Name.
5. Click Save.
6. Click on Create outbound parameter icon under Outbound parmtrs section – the Partner profiles: Outbound parameters screen appears.
7. Create Outbound parameter for the documents you are going to adopt by entering values in following fields:
   • Partner No.: Auto populated.
   • Partner Type: Auto populated.
   • Partner Role: Select LS (Logical System).
   • Message Type: Select a message type corresponding to the document. For example, ORDERS for Purchase Order.

     In the Outbound Options tab,

   • Receiver Port: Provide / select the Port you have created for ANID-2 in earlier step.
   • Output Mode: Select Pass IDoc immediately.
   • IDoc Type: Select Basic Type of IDoc with "ARBCIG_ "namespace. For example, ARBCIG_ORDERS for Purchase Order.
   • Check Cancel Processing After Syntax Error box.

     In the Message Control tab.

   • Add entry & select relevant values for Application; Message Type; Process Code & check the Change Message box.

     The Message Type you select here should be used while defining Output Determination via NACE.

   
8. Click Save.
9. Click Create inbound parameter icon under Inbound parameters section – the Partner profiles: Inbound parameters screen appears.
10. Create Inbound parameter for the documents you are going to adopt by entering values in following fields:
    • Partner No.: Auto populated.
    • Partner Type: Auto populated.
    • Partner Role: Select LS (Logical System)
    • Message Type: Select a message type corresponding to the document. For example, INVOIC for Invoice.

      In the Inbound Options tab,

    • Process Code: Provide / select the relevant value for the Message Type. For example, INVM for the Message Type INVOIC (Invoice).
    • Check Cancel Processing After Syntax Error box.

      In the Processing by Function Module section,

    • Select Trigger Immediately
11. Click Save.

List of Transaction of IDOC types:

Example: You have two AN Buyer Accounts: ANID-1 and ANID-2 which will have separate P User IDs:

• ANID-1 example P User ID: P01234
• ANID-2 example P User ID: P05678

By executing Interface Setup report, you have created Logical Ports (in SOAMANAGER) for Web Services / Proxies for ANID-1 / P01234.

Now, you need to manually create Logical Port for ANID-2 / P05678 by accessing TCode SOAMANAGER.

You would need to select this newly & manually created Logical Port while maintaining ARBCIG_CCANID table in this activity.

You must assign this Logical Port to all the Proxy messages for transactional documents that you want to route to the second Ariba Network Buyer account from your SAP system.

This is a one time activity when you configure a new / additional Ariba Network Buyer account on SAP system.

In order to save time & efforts of maintaining multiple entries in ARBCIG_CCANID table for each message type, we recommend to use the same / common Logical Port Name for all proxies.

• Example: Logical_Port_For_ANID2

To manually create Logical Port:

1. On the SAP Easy Access page, run the TCode SOAMANAGER – the SOA Management screen appears.
2. On Service Administration tab, click on Web Service Configuration link.
3. In Design Time Object Search tab, under Internal Name column all the Proxy objects will be displayed which are created by Interface Setup report you have executed in earlier step. Select a Proxy object. For example Receipt proxy CO_ARBCIG_RECEIPT_DETAIL_REQ.
4. On the Details of Consumer Proxy: ＜Proxy Name＞ screen, in Configurations tab, following details of the existing logical ports for the proxy message will be displayed:

   Field	Description
   Actions	Icons to View, Edit, Delete, Deactivate & Ping a web service
   Logical Port	Name of the Logical Port
   State	Displays the status of the Logical Port
   Logical Port is default	If this is set to true, this Logical Port will be the default port for the message type
   Description	Description of the Logical Port
   Creation Type	Method used for creation of this object

5. Click Create, select Manual Configuration – the New Manual Configuration of Logical Port for Consumer Proxy ＜Proxy Name＞ screen appears.
6. On the Logical Port Name screen, add values in the following fields, click Next.
   • Logical Port Name: For example, Logical_Port_For_ANID2
   • Description: Meaningful description
   
7. On the Consumer Security screen,
   • In Authentication Settings section, select User ID / Password
   • In User ID / Password section, provide P User ID & Password information of ANID-2
8. Click Next
9. On the HTTP Settings screen, add values to the following fields, click Next.
   • URL Access Path: /cxf/receiveSOAP
   • Computer Name of Access: Depending upon which environment you are working on (test or Production) either https://testacig.ariba.com or https://acig.ariba.com.
   • Port Number of Access URL: For example, 443.
   • URL Protocol Information: Select HTTPS.
   • Logon Language: Select Language of User Context.
   • Name of the Proxy Host (optional): For example, proxy.ariba.com.
   • Port Number of Proxy Host (optional): For example, 8080.

     User Name for Proxy Access (optional):

     Password of Proxy User (optional):

   
10. On the SOAP Protocol screen, add values to the following fields, click Next.
    • Under Reliable Messaging (Asynchr.) section, in RM Protocol, select SAP RM.
    • Under Message ID (Synchronous) section, in Message ID Protocol, select Suppress ID Transfer.
11. Click Finish.

You will get navigated to the Details of Consumer Proxy: ＜Proxy Name＞ screen where you can see newly created Logical Port with Active state.

• The messages are routed to Ariba Network, based on the Company Code assigned to it. If you want to route messages based on any other field, you can use the BAdIs available.
• To configure multiple Ariba Network accounts in SAP system, you must maintain the Company Codes & ANIDs of all the required Ariba Network accounts in the ARBCIG_CCANID table.
• To send messages to appropriate AN Buyer / CIG account, Ariba AddOn code will refer to the values (Logical System & Logical Port) maintained in ARBCIG_CCANID table against the combination of AN ID & Company Code.

To Maintain Company Code & ANID Relationship for all the Ariba Network accounts:

1. On the SAP Easy Access page, run the transaction code ARBCIG_CCANID – the Assign logical system and logical port to Company Code screen appears. Click New Entries.
2. The New Entries: Overview of Added Entries screen appears.

   Enter the following information:

   1. CoCode : Enter the company code for the Ariba Network account.
   2. Logical System: Enter a logical system name.c. Logical Port: Enter.
   3. Logical Port name.
   4. Description: Enter a description for the company code of the Ariba Network account.
   5. Ariba Network ID: Enter the Ariba Network ID for the Ariba Network account.
3. Click Save.

• SAP system routes the Outbound IDOC messages to the Ariba Network Buyer / CIG account, based on the Logical System assigned to the Company Code in the ARBCIG_CCANID table.
• In the usual Output Determination (NACE) configuration process, you need to specifically make some changes to the configuration of Condition Records for all the Output Types of the outbound messages that you want to route to the Ariba Network Buyer / CIG account.
• This activity will help Ariba AddOn to determine appropriate Logical System & in turn appropriate Partner Profile to route the IDOCs to correct AN Buyer / CIG account.

To Configure Conditions Records:

1. On the SAP Easy Access page, run the transaction code NACE – the Conditions for Output Control screen appears.
2. Select a Message Type / Application (that you want to configure for routing) from the list. For example, EF – Purchase Order.
3. Click Condition Records button.
4. Select an Output Type for the message. For example, NEU – the Key Combination popup appears.
5. Select a specific Key Combination you want to configure. For example, Output Determination: Doc. Type / Purch. Org / Vendor & click Choose (green tick mark) – the Change Purchase Order (＜Output Type＞): Selection screen appears.
6. Enter values for following fields & click Execute:
   1. Purchasing Doc Type: For example, NB (Standard PO).
   2. Purch. Organization: For example, 3000.
   
7. On the Change Condition Records (Purchase Order): Fast Change screen, enter / select the values in following fields:
   1. Vendor: Select a Vendor
   2. Function: Select LS (Logical System)
   3. Partner: Leave the field BLANK
   4. Transmission Medium: Select 6 (EDI)
   5. Dispatch Time: Select 4 (Send immediately when saving the application)
   6. Language: Select EN (English)
8. Click Save.
   Note

   Do not maintain any values in Partner field. If there are existing entries in the table, delete the value in Partner field. It must be left blank.

• After configuring Condition Records, you need to configure Check Routine to add Ariba provided INCLUDE. You need to assign the newly created Check Routine to each Output Type of all the outbound messages.
• This INCLUDE has a logic to determine appropriate Logical System for a specific Ariba Network Buyer / CIG account & then to route the Outbound IDOC messages to that Ariba Network Buyer / CIG account, based on the Logical System assigned to the "Company Code＜＞ANID" combination maintained in the ARBCIG_CCANID table.
• In the usual Output Determination (NACE) configuration process, you need to specifically make these changes to the configuration of Procedures for all the Output Types of the outbound messages that you want to route to the Ariba Network Buyer / CIG account.

To Configure Check Routines:

1. On the SAP Easy Access page, run the transaction code NACE – the Conditions for Output Control screen appears.
2. Select a Message Type / Application (that you want to configure for routing) from the list. For example, EF – Purchase Order.
3. Click Procedures button - the Change View "Procedures": Overview screen appears.
4. Select an Output Type for the Procedure & double-click on Control.
5. The Change View "Control": Overview screen appears & displays Reference Step Overview table.
6. For the relevant Output Type / Condition Type check if the Output / Condition Type has an existing Check Routine assigned under Requirement column. If yes, get the Check Routine number. Example: 101
   • Go to TCode VOFM & from Requirements menu select Output Control – the Maintain: Requirements Output Control screen appears.
   • Search for the Check Routine number & double-click on it – the ABAP Editor: Display Include ＜nclude Number＞ screen appears.
   • Click on Display ＜-＞ Change - the ABAP Editor: Modify Include ＜Include Number＞ screen appears.
   • In the Check Routine source text, select the row below the FORM KOBED_XXX line & click Insert.
7. Paste the INCLUDE ARBCIG_DYNAMIC_LOGICAL_SYSTEM IF FOUND. code as the first line of the program, below the FORM KOBED_XXX line & click Save.
8. Click Activate.
9. For the relevant Output Type / Condition Type check if the Output / Condition Type has an existing Check Routine assigned under Requirement column. If no, do the following:
   • Go to TCode VOFM & from Requirements menu select Output Control – the Maintain: Requirements Output Control screen appears.
   • Create a new Check Routine by providing a number & Application / Message Type . For example, 999 & EF. Then double-click on it – The ABAP Editor: Modify Include ＜Include Number＞ screen appears.
   • In the Check Routine source text, select the row below the FORM KOBED_XXX line & click Insert.
   • In the Check Routine source text paste the INCLUDE ARBCIG_DYNAMIC_LOGICAL_SYSTEM IF FOUND. code as the first line of the program, below the FORM KOBED_XXX line, click Save.
   Note

   Step 8: When you create a new Check Routine, do not assign any Output Type / Application to it by maintaining a blank Application field. By doing this, you can use this Check Routine for multiple Output Types.
10. Click Activate.
11. Go back to the Maintain: Requirements Output Control table / page, select the entry / row of newly created Check Routine, delete the value in Application field.
12. From Edit menu, select Activate – the Active box in the entry will get checked.
13. Follow the steps 1 to 5 & assign the newly created Check Routine to the relevant Output Type / Condition Type.
14. Click Save.

By default, Ariba AddOn routes the messages to Ariba Network Buyer / CIG account based on the "Company Code<>ANID" combination maintained in the ARBCIG_CCANID table.

• If you want to route messages for transaction documents to Ariba Network Buyer / CIG account based on any field other than the Company Code, for example, the Purchase Organization or Plant or any other field, you need to implement the BAdIs for the respective messages.
• An implementation method is provided in the BAdIs for each transaction.