Administration Guide
CUSTOMER
Document Version: 1.0 – 2017-12-15
Buyer's Guide for SP06 of SAP SRM Connectivity
with Ariba Network
Ariba Network Integration 1.0 for SAP Business Suite
Content
1
Overview of Ariba Network Integration 1.0 for SAP Business Suite. . . . . . . . . . . . . . . . . . . . . . . . . 5
1.1
Introduction. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
1.2
Prerequisites. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6
1.3
Installation of Software Components. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
1.4
Supported Ariba Network Processes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
Integration of SAP SRM with SAP Ariba Quote Automation and SAP Ariba Sourcing. . . . . . . . . . . . . .12
2
Configuration Settings. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .16
2.1
Prerequisites for Connecting SAP SRM to Ariba Network. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
Required Notes in SAP SRM. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
Establishing the Technical Connection to Ariba Network. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
2.2
Framework Customizing for Connecting SAP Business Suite to Ariba Network. . . . . . . . . . . . . . . . . . . . 21
2.3
SAP SRM-Specific Customizing for Connecting SAP Business Suite to Ariba Network. . . . . . . . . . . . . . 23
2.4
Required Settings in SAP SRM. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
2.5
Customizing Settings for QuoteRequest and QuoteMessage cXML Messages. . . . . . . . . . . . . . . . . . . . 27
2.6
Jobs to Be Scheduled. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .28
3
Security. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30
3.1
SAP Business Suite System Acting as a Client. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30
3.2
SAP Business Suite System Acting as a Server. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33
3.3
Virus Scan for Attachments. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33
3.4
Roles and Authorizations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33
4
Operation and Troubleshooting. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35
4.1
Message Monitoring. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .35
Message Monitoring for Direct Connectivity. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35
Message Monitoring for Mediated Connectivity. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41
4.2
Application Log. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46
4.3
Forward Error Handling (FEH). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47
Prerequisites: Customizing Settings for FEH. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47
Postprocessing Desktop. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48
Postprocessing Desktop: Edit Task. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49
4.4
Troubleshooting Outbound Messages. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50
4.5
Troubleshooting Inbound Messages. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .52
5
Appendix. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57
5.1
Configuration of SOA Manager. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57
Define Inbound Services. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57
2
CUSTOMER
Buyer's Guide for SP06 of SAP SRM Connectivity with Ariba Network
Content
Define Outbound Consumers. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .59
5.2
Extrinsic Elements (Extensibility). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64
Extrinsics in Outbound cXML Messages. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64
Extrinsics in Inbound cXML messages. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64
5.3
End Points. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64
Customizing Settings for End Points. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65
Buyer's Guide for SP06 of SAP SRM Connectivity with Ariba Network
Content
CUSTOMER
3
Document History
Note
Before you start the implementation, make sure you have the latest version of this document. You can find the
latest version at: https://service.sap.com/instguides .
The following table provides an overview of the most important document changes:
Table 1:
Version
Date
Description
1.0
2017-12-15
SP06 - Initial version
1.0
2017-09-08
SP05 - Initial version
1.0
2016-06-17
Initial version
4
CUSTOMER
Buyer's Guide for SP06 of SAP SRM Connectivity with Ariba Network
Document History
1
Overview of Ariba Network Integration 1.0
for SAP Business Suite
1.1
Introduction
Ariba Network Integration 1.0 for SAP Business Suite contains non-modifying add-ons for SAP Business Suite
systems. The add-on to SAP SRM is required if you want to connect SAP SRM to Ariba Network. It enables the SAP
SRM extended classic scenario for supplier collaboration using the Ariba Network. In the extended classic
scenario, the purchase order in SAP SRM is the leading purchase order. Therefore the SAP SRM purchase order
must be processed by Ariba Network, and the purchase order confirmation must be sent from Ariba Network to
SAP SRM.
In the extended classic scenario of SAP SRM, follow-on documents, for example invoices, are sent from Ariba
Network directly to SAP ERP. Therefore you must also enable the integration of SAP ERP with Ariba Network. For
more information, see the document Ariba Network Integration 1.0 for SAP Business Suite: Version SP06 of SAP
ERP Connectivity for Buyers on Ariba Network or higher versions of this document.
The SAP SRM add-on enables your SAP system to send and receive messages in the Ariba-supported format
cXML SAP SRM can be integrated directly with Ariba Network (direct connectivity) or using a middleware
(mediated connectivity). For detailed information, see SAP Community Network at http://scn.sap.com/docs/
DOC-51873 , System Landscape Recommendations for Ariba Network Integration 1.0 for SAP Business Suite.
Buyer's Guide for SP06 of SAP SRM Connectivity with Ariba Network
Overview of Ariba Network Integration 1.0 for SAP Business Suite
CUSTOMER
5
The following figure gives an overview of the system landscape for connecting an SAP SRM system to Ariba
Network:
Figure 1: System Landscape for Ariba Network Integration 1.0 for SAP SRM
1.2
Prerequisites
Supported SAP SRM Releases
Ariba Network Integration 1.0 for SAP Business Suite is available for the following releases and minimum support
package stacks of SAP SRM Systems:
● SAP SRM 7.0 (SRM_SERVER 700 SPS03)
● EHP1 for SAP SRM 7.0 (SRM_SERVER 701 SPS00)
● EHP2 for SAP SRM 7.0 (SRM_SERVER 702 SPS00)
● EHP3 for SAP SRM 7.0 (SRM_SERVER 7.13 SPS00)
● EHP4 for SAP SRM 7.0 (SRM_SERVER 7.14 SPS01)
Note
SAP strongly recommends that you use higher support package stacks of SAP SRM; at least use support
package stacks that have the status “general availability”. If you are using releases lower than the following,
implement the SAP Notes given below, in the specified order.
6
CUSTOMER
Buyer's Guide for SP06 of SAP SRM Connectivity with Ariba Network
Overview of Ariba Network Integration 1.0 for SAP Business Suite
● SAP SRM 7.0 (SRM_SERVER 700 SPS21)
● EHP1 for SAP SRM 7.0 (SRM_SERVER 701 SPS17)
● EHP2 for SAP SRM 7.0 (SRM_SERVER 702 SPS20)
● EHP3 for SAP SRM 7.0 (SRM_SERVER 7.13 SPS15)
● EHP4 for SAP SRM 7.0 (SRM_SERVER 7.14 SPS08)
SAP Notes to be implemented in order:
1. 2474996
2. 2486371
3. 2486486
4. 2486563
5. 2486427
Process Integration (Optional)
If you decide to use mediated connectivity, the Ariba Network Adapter for SAP NetWeaver for SAP Suite Add-On is
required. For information about which version is relevant, see SAP Note 2148831 . The document Ariba Network
Adapter for SAP NetWeaver Setup Guide is available for customers as part of the Ariba product documentation. It
contains a chapter describing the Ariba Network Adapter for SAP NetWeaver for SAP Suite Add-On. Note that this
document is also relevant for integrating SAP SRM, even though currently only SAP ERP is mentioned explicitly.
When making some of the settings described in the document, you have to substitute ERP by SRM.
1.3
Installation of Software Components
Ariba Network Integration 1.0 for SAP Business Suite consists of several components. For the integration of SAP
SRM, download the following components and install them on your SAP SRM system:
● ARBFNDI1 100
● ARBFNDI2 100
● ARBSRMI1 100
General instructions for the installation of add-ons can be found in SAP Note 1841471
.
The installation information for Ariba Integration for SAP Business Suite - SAP SRM add-on - is available in SAP
Note 2148831 .
Buyer's Guide for SP06 of SAP SRM Connectivity with Ariba Network
Overview of Ariba Network Integration 1.0 for SAP Business Suite
CUSTOMER
7
1.4
Supported Ariba Network Processes
Ariba Network Integration for SAP SRM (Buy Side)
Ariba Network Integration 1.0 for SAP Business Suite supports the integration of the SAP SRM extended classic
scenario with Ariba Network for Collaborative Commerce. This includes the following processes:
● Order Collaboration (using SAP SRM and SAP ERP)
Note
The cXML messages transferred between SAP SRM and Ariba Network are technically enabled to support
the service procurement process. This does not include any standard mappings or an out-of-the-box
business process. You can implement service procurement in customer projects.
● Invoice Collaboration (using SAP ERP)
Further processes, such as Discount Management, are supported by the integration with SAP ERP.
Message Types Used for the Integration
To support the processes listed above, the transfer of documents between Ariba Network and SAP Business Suite
systems is enabled by cXML messages.
Figure 2: Message Flow Between SAP SRM and Ariba Network
Communication Between Ariba Network and SAP SRM
All messages are exchanged in cXML format via Web services. The document output for purchase orders in SAP
SRM is handled by the standard output management in SAP SRM, which includes event management and the
Post-Processing Framework (PPF).
8
CUSTOMER
Buyer's Guide for SP06 of SAP SRM Connectivity with Ariba Network
Overview of Ariba Network Integration 1.0 for SAP Business Suite
Messages that reside on Ariba Network in the outbound queue are either polled by the Polling Agent (report
ARBFND_FETCH_CXML_MESSAGES_NEW) (direct connectivity) in SAP SRM, or they are pushed to SAP SRM by the
Ariba Network Adapter for SAP NetWeaver (mediated connectivity).
The following cXML message types are used to enable the exchange of documents with between SAP SRM and the
Ariba Network:
● OrderRequest (outbound)
This message type is used for transferring purchase order data from SAP SRM to Ariba Network.
● ConfirmationRequest (inbound)
This message type is used for transferring order confirmation data from Ariba Network to SAP SRM.
Communication Between Ariba Network and SAP ERP
In the extended classic scenario of SAP SRM, follow-on documents are sent directly from Ariba Network to SAP
ERP. Therefore, the message types used for the integration of SAP ERP are also relevant. Please see the
Administrator's Guide for Buyer Integration of SAP ERP. This document is available on SAP Help Portal at http://
help.sap.com/se4aribanet10 .
Integration of SAP SRM with Ariba Collaborative Commerce - Order
Collaboration
OrderRequest (Outbound)
This cXML message enables you to transfer purchase orders (PO), changes to purchase orders, and cancellations
of purchase order to Ariba Network.
There are no limitations regarding purchase order types. However, only the following SAP SRM purchase order
item types are supported:
● Standard items (they correspond to the item type “Regular” on Ariba Network)
● Limit items (they correspond to the item type “Blanket” on Ariba Network)
Note that a start date and an end date must be specified in limit items.
The cXML order types ( “regular” and “blanket”) are derived from the purchase order item types in SAP SRM.
Within one purchase order, do not mix standard line items and limit items. Instead, we recommend that you
configure one purchase order type that allows only standard items and one that allows only limit items.
Note
● Schedule lines are supported.
● Condition types, shipping costs, account assignment, and tax information in SAP SRM purchase orders
cannot be transmitted. You can use an outbound BAdI implementation to create your own logic. For more
information, see the documentation that is available in Customizing for SAP Business Suite Integration
Component for Ariba under
Business Add-Ins (BAdIs)
Application Specific Settings
SAP SRM Integration Component for Ariba
Outbound Mapping .
OrderConfirmationRequest (Inbound)
Order confirmations can be created in two ways:
● Suppliers create order confirmations directly on Ariba Network.
Buyer's Guide for SP06 of SAP SRM Connectivity with Ariba Network
Overview of Ariba Network Integration 1.0 for SAP Business Suite
CUSTOMER
9
● Suppliers create corresponding documents in their ERP system and send order confirmations to Ariba
Network as cXMLmessages.
The ConfirmationRequest message can only reference one purchase order. Each inbound cXML
ConfirmationRequest message leads to creation of a purchase order response in SAP SRM (BUS2209). This
document is posted against the corresponding purchase order in SAP SRM.
Note
SAP SRM does not support updating an existing purchase order response. If a supplier changes an existing
order confirmation on Ariba Network, the existing order confirmation is changed and resent. In SAP SRM, a new
purchase order response is created and the previous purchase order response is set to “out-of-date”.
The process runs as follows:
1. An order confirmation is created Ariba Network and the cXML message is transferred to SAP SRM.
2. A purchase order response is created in SAP SRM.
3. In SAP SRM, the data of the purchase order response is compared with the data of the corresponding
purchase order. This leads to either of the following:
○ If the data in the purchase order response does not deviate from the PO data, or if the deviation lies within
the tolerances defined in Customizing for SAP SRM, an auto-approval workflow is started that updates the
purchase order with this data.
○ If the tolerances are exceeded, a dialog approval workflow is started. The purchaser responsible for the
purchase order then decides whether the purchase order is updated with the response data or not.
4. Once a deviating purchase order response has been accepted, an update of the purchase order is sent to Ariba
Network, where it must be confirmed again by the supplier. This process is repeated until there are no more
deviations.
5. When SAP SRM receives a purchase order response without deviations, the purchase order receives the
status “confirmed by supplier” at header and at item level.
On Ariba Network, suppliers can confirm or reject entire purchase orders, they can confirm, reject, or update
individual line items, or they can confirm, reject, or update specific quantities within a line item. All cases are
supported by the cXML message type OrderConfirmationRequest. In SAP SRM, the following statuses exist for line
items of purchase orders:
● Open
● Accepted
● Rejected
The table below gives you an overview of the statuses that line items or quantities of line items can have in an order
confirmation on Ariba Network and the of corresponding statuses of line items in an SAP SRM purchase order
response:
Table 2:
Item Status in Order Confirmation (Ariba Network)
Item Status in Corresponding Purchase Order Response
(SAP SRM)
Accepted full
Accepted
Accepted partial
Accepted
10
CUSTOMER
Buyer's Guide for SP06 of SAP SRM Connectivity with Ariba Network
Overview of Ariba Network Integration 1.0 for SAP Business Suite
Item Status in Order Confirmation (Ariba Network)
Item Status in Corresponding Purchase Order Response
(SAP SRM)
Backordered full
Open
Backordered partial
Open
Rejected full
Rejected
Rejected partial
(An exception is raised)
Accepted + Backordered
Accepted
Accepted + Backordered + Rejected
Accepted
Accepted + Rejected
Accepted
Backordered + Rejected
Open
Note
Only order confirmations are supported where the price currency of the line items is the same as the price
currency in the purchase order.
Service Procurement
The cXML messages transferred between SAP SRM and Ariba Network are technically enabled to support the
service procurement process. This does not include any standard mappings or an out-of-the-box business
process. You can implement service procurement in customer projects.
If you want to enable service procurement, you have to do the following:
● Allow the transmission of purchase order item types that are not supported in the standard mapping. To do
this, you have to implement the following methods of the Outbound Mapping BAdI
( ARBSRM_OUTBOUND_MAPPING):
○ BUS2201_ORDR_ALLOW_SEND_ITTYPE
○ MAP_BUS2201_TO_ORDR_OUT
● Implement the processing of ServiceEntryRequest messages. To do this, you have to implement the following
method of the Inbound Mapping BAdI ( ARBSRM_INBOUND_MAPPING)
○ DEFINE_CUST_SPEC_PROCESSING
When implementing this method, ensure that the inp_type field on the header of the service entry sheet
( bbp_pds_header) is filled with the value “2”, indicating XML.
● Implement the creation of StatusUpdateRequest messages for service entry sheets. To do this, you have to
implement the following method of the Outbound Mapping BAdI ( ARBSRM_OUTBOUND_MAPPING):
○ DEFINE_CUST_SPEC_MAPPING
You can access these BAdIs in Customizing for SAP Business Suite Integration Component for Ariba under
Application-Specific Settings
SAP SRM Integration Component for Ariba
Business Add-Ins (BAdIs) .
If you want to send StatusUpdateRequest messages for service entry sheets, you have to implement SAP Note
2312134
in your SAP SRM system.
Buyer's Guide for SP06 of SAP SRM Connectivity with Ariba Network
Overview of Ariba Network Integration 1.0 for SAP Business Suite
CUSTOMER
11
1.4.1 Integration of SAP SRM with SAP Ariba Quote
Automation and SAP Ariba Sourcing
RFQ and RFQ response SAP SRM business documents can be exchanged with Ariba Network using Ariba’s cXML
messages. With the SAP SRM Add-On for Ariba Network integration, cXML documents can be created and send
for outbound documents, as well as received and processed for inbound documents.
Business documents exchange between SAP SRM and Ariba Network:
● RFx is sent from SAP SRM to Ariba Discovery (Quote Automation – All bids, Leading Bids & Winning Bids
scenarios)
● RFx is sent from SAP SRM to Ariba Sourcing (Sourcing Request – Winning Bids)
● cXML Quote Message is sent from Ariba Network to SAP SRM, leading to creation of RFx responses (with
Submitted and Accepted status) in SAP SRM.
Figure 3: SAP Ariba Quote Automation Integration - Ariba Discovery
Figure 4: SAP SRM – SAP Ariba Sourcing Integration
RFQ
RFQs can be created by buyers in SAP SRM for a set of invited bidders, that are enabled for Ariba Network. After
the RFQ is published (Approval Workflow completed, if appicable), the RFQ is sent to Ariba Network as a cXML
message of type QuoteRequest.
The value set in the extrinsic field <Processing Target> that is added in the cXML message indicates the
destination of the cXML message.
12
CUSTOMER
Buyer's Guide for SP06 of SAP SRM Connectivity with Ariba Network
Overview of Ariba Network Integration 1.0 for SAP Business Suite
Complex Pricing
To use complex pricing, create RFQs in SAP SRM with price conditions enabled. You can use the Customizing
activity Map cXML Price Modifications to SRM Conditions under
SAP Business Suite Integration Component for Ariba
Component for Ariba
see 2500747 .
Complex Pricing
Integration with Other SAP Components
Application-Specific Settings
SAP SRM Integration
to map the values from SAP Ariba to SAP SRM. For more information,
SAP Ariba Discovery
When the value QuoteAutomation is set for the extrinsic field <Processing Target>, the destination of the
RFQ is Ariba Discovery.
<Extrinsic name="processingTarget">QuoteAutomation</Extrinsic>
The RFQ is posted to Ariba Discovery in Preview or Open mode based on the start date of the RFQ. Change and
Delete of RFQs are supported for the Quote Automation process.
Change RFQ
SAP SRM supports editing fields in RFQs. If an RFQ contains changes to any of the supported fields, the message
type is set as Update. You can update the following fields in an RFQ:
● RFQ Start Date
● RFQ Submission Deadline
● RFQ Header currency
● RFQ Item Delivery Date
● RFQ Item Requested Quantity
● RFQ Item Unit of Measure
You can also add the following information:
● New suppliers
● Header and Item Attachments
● Notes - Supplier Remarks
You can update the RFQ only until the start date is reached.
Note
You cannot add any new items to the RFQ during an update.
Close RFQ
You can cancel the RFQ by clicking Close RFx in SAP SRM. A cXML message QuoteRequest of type Delete is sent
to Ariba Discovery.
Create Follow-On-RFQ
You can close an existing RFQ and create a Follow-On-RFQ by clicking Create-Follow-on RFQ. This creates a copy of
the existing RFQ as a Follow-On-RFQ, and closes the existing RFQ.
SAP SRM triggers a cXML message QuoteRequest of type Delete to delete the existing RFQ. Along with this, SAP
SRM triggers another cXML message QuoteRequest with type New to create the Follow-On-RFQ.
Buyer's Guide for SP06 of SAP SRM Connectivity with Ariba Network
Overview of Ariba Network Integration 1.0 for SAP Business Suite
CUSTOMER
13
SAP Ariba Sourcing
When the value sourcingRequest is set for the extrinsic field <Processing Target>, the destination of the
RFQ is Ariba Sourcing.
<Extrinsic name="processingTarget">souricngRequest</Extrinsic>
Buyers can access the sourcing requests in Ariba and create the Sourcing Projects. After the sourcing project is
published and is in Open mode, suppliers can place their bid.
Note
The Change RFQ and Close RFQ scenarios are not supported for SAP Ariba Sourcing Integration. After the RFx
is published and posted to SAP Ariba Sourcing, no further changes are allowed in SAP SRM.
RFQ Response
RFQ responses are created by suppliers (as Bids) and these responses are sent to SAP SRM from Ariba Discovery
or Ariba Sourcing as cXML messages. The cXML message QuoteMessage represents the RFQ response.
For direct connectivity, you can fetch the cXML message for RFQ response from Ariba Network by executing the
polling report in SAP SRM. For mediated connectivity via SAP Netweaver PI server, the RFQ responses are
automatically fetched.
Each inbound cXML QuoteMessage leads to the creation of a RFQ response (BUS2202) document for the
corresponding RFQ in SAP SRM.
RFQ response scenarios:
● All Bids – All the bids will be sent to SAP SRM (including new bids and updated bids).
● Leading Bids – Only the final bid from each supplier will be sent to SAP SRM after the RFQ is closed.
● Winning Bids – The awarded bid is sent to SAP SRM, and the RFQ response is created with status Accepted,
surpassing the approval workflow.
RFQ Response types and corresponding statuses in SAP SRM for the cXML message of type QuoteMessage:
Table 3:
RFQ Response Type
Corresponding status in SAP SRM
Accept
Submitted
Award
Accepted
SAP Ariba Discovery
Attachment Transfer
From Ariba Discovery, attachments can be transferred in QuoteMessage at item level. The attachments are
displayed in the RFQ response. You can enable attachment transfer using the Customizing activity Define
Document-Specific Customizing for Attachments under
Business Suite Integration Component for Ariba
Integration with Other SAP Components
Application-Specific Settings
SAP
SAP SRM Integration Component
for Ariba .
14
CUSTOMER
Buyer's Guide for SP06 of SAP SRM Connectivity with Ariba Network
Overview of Ariba Network Integration 1.0 for SAP Business Suite
Change RFQ Response
From Ariba Discovery, when an existing RFQ response is changed and sent to SAP SRM, SAP SRM creates a new
version of the RFQ response, and updates the existing RFQ response. This is enabled through the All Bids
scenario. SAP SRM can also receive only the awarded bid or the final bid from each supplier based on the quote
receiving preference done in Customizing.
Note
The decision to create a Follow-on-Document based on the RFQ response can only be done in SAP SRM.
SAP Ariba Sourcing
In Ariba Sourcing, only the Winning Bids RFQ response scenario is supported.
Follow-on-Document Creation
In SAP Ariba Sourcing, the decision to create a follow-on-document can be made either in Ariba or SAP SRM
system.
To ensure that the decision for creating the follow-on-document is implemented only at SAP SRM, you can clear
the values of the following extrinsic fields using the BAdI BAdI: Inbound Mapping under
Integration Component for Ariba
Application-Specific Settings
SAP Business Suite
SAP SRM Integration Component for Ariba
Business Add-Ins (BAdIs) .
<Extrinsic name="DocumentType"> PurchaseOrder </Extrinsic>
<Extrinsic name="DocumentCategory">XXXX</Extrinsic>
New Supplier registration
Suppliers can be added to an RFQ from Ariba Sourcing. When the RFQ response containing these suppliers are
received by SAP SRM, SAP SRM registers these new suppliers to the original RFQ.
Note
The new supplier must be enabled and mapped in both Ariba Network and SAP SRM Customizing.
Limitations
Currently, the integration of SAP SRM with SAP Ariba Sourcing and SAP Ariba Discovery have the following
limitations:
1. Tax information is not sent in cXML message QuoteRequest.
2. Service Hierarchy and Limit Items are not supported.
3. Inbound Attachments from Ariba Sourcing are not supported.
Buyer's Guide for SP06 of SAP SRM Connectivity with Ariba Network
Overview of Ariba Network Integration 1.0 for SAP Business Suite
CUSTOMER
15
2
Configuration Settings
This chapter describes the settings you have to make in your SAP SRM system for communication with Ariba
Network. It also describes the Customizing details for Ariba Network Integration 1.0 for SAP Business Suite.
2.1
Prerequisites for Connecting SAP SRM to Ariba Network
The following prerequisites apply:
● You have signed up for an Ariba Network membership.
● You have received one or several IDs, known as Ariba Network IDs (ANID). You use either a password (shared
secret) or a client certificate with each ANID. Each credential represents a unique entity on Ariba Network, that
is, your appearance to the suppliers on Ariba Network.
● Ariba has provided you with a list of your suppliers who have already signed up to the network, so you can start
collaboration immediately. To connect with the suppliers on the network, get support from your Ariba contact.
2.1.1 Required Notes in SAP SRM
SAP Note 2150268
Ariba cXML.
provides a documentation of the mapping between SAP SRM application interfaces and
Depending on your SAP SRM release, implementation of SAP Notes may be required. See the Release Information
Note 2148831
for a list of the required SAP Notes.
2.1.2 Establishing the Technical Connection to Ariba Network
As described in the introduction, you can decide whether you connect your SAP SRM system either directly or
through SAP NetWeaver PI to Ariba Network. A mixture is not recommended.
This decision is a prerequisite for choosing the relevant Customizing activities later.
16
CUSTOMER
Buyer's Guide for SP06 of SAP SRM Connectivity with Ariba Network
Configuration Settings
The following figure shows an overall picture of the interfaces used for direct connectivity:
Figure 5: Interfaces for Direct Connectivity
Buyer's Guide for SP06 of SAP SRM Connectivity with Ariba Network
Configuration Settings
CUSTOMER
17
The following figure shows an overall picture of the interfaces used for mediated connectivity:
Figure 6: Interfaces for Mediated Connectivity
For similar graphics describing the connections between SAP ERP systems and Ariba Network, see the document
Ariba Network Integration 1.0 for SAP Business Suite - Buyer's Guide for SAP ERP Connectivity with Ariba Network.
Even though it is not technically required, we recommend that you establish an SM59 connection to Ariba
Network, so that you can ping the network and check its technical availability.
18
CUSTOMER
Buyer's Guide for SP06 of SAP SRM Connectivity with Ariba Network
Configuration Settings
The following figure shows the technical settings of this test connection:
Figure 7: Technical Settings for Testing Direct Connectivity
Buyer's Guide for SP06 of SAP SRM Connectivity with Ariba Network
Configuration Settings
CUSTOMER
19
The following figure shows the logon and security details of this connection:
Figure 8: Logon and Security Settings for Direct Connectivity
Note
For HTTPS SSL encryption, you first have to obtain the server certificate from Ariba and then import it into the
SAP SRM system using Trust Manager (transaction STRUST). For more information about security, see chapter
Security [page 30].
For HTTPS communication, the HTTPS service must be active in your SAP SRM system. To display active
services, on the ICM Monitor screen (transaction SMICM), double-click the Services button in the menu bar.
20
CUSTOMER
Buyer's Guide for SP06 of SAP SRM Connectivity with Ariba Network
Configuration Settings
2.2
Framework Customizing for Connecting SAP Business
Suite to Ariba Network
To connect SAP Business Suite systems to Ariba Network, choose
SAP Business Suite Integration Component for Ariba
Customizing activities:
Integration with Other SAP Components
Framework Settings , and make settings in the following
General
Define Credentials and End Points for Ariba Network:
1. Enter your Ariba credentials, that is, ANID(s) and the corresponding password(s).
2. Leave the Shared Secret blank if you authenticate with client certificate on Ariba Network.
3. If you have not yet switched your system to productive use, select the Test Account checkbox.
4. Select one of the following options for Enable End Points
○ End points not enabled
Use this option if the end points are not activated on Ariba Network.
○ Enable end points for authentication
Use this option if you use end points only for authentication.
○ Enable end points for authentication and polling
Use this option if you use end points for authentication and polling.
○ If you have decided to configure end points on Ariba Network, the credentials must only be specified on
the subscreen End Points for Ariba Network. Make the following entries:
○ SAP-Internal Key
This is an SAP-internal name for the end point; it must be unique in your SAP Business Suite system.
This key value is used later in the Customizing activity Define Settings for Polling Agent for using end
points in polling.
○ Ariba End Point ID
This is the end point name defined on Ariba Network for your SAP system.
○ Enter Shared Secret
Provide your shared secret value if you use a password for the communication between the SAP
system and Ariba Network.
For more information about end points, see Appendix.
Direct Connectivity
● Define Basic Message Settings
Specify which Ariba cXML message types you intend to send and receive, and fill the corresponding Object
Type, Message Type, Direction, Mapping Version, and cXML version fields.
Note
cXML version 1.2.025 and higher is supported.
Buyer's Guide for SP06 of SAP SRM Connectivity with Ariba Network
Configuration Settings
CUSTOMER
21
The indicator Send cXML StatusUpdateRequest Message is only valid for inbound Purchase Order response
cXML messages; it informs Ariba Network about successful or erroneous processing of your messages in the
backend. Note that the error status is restricted to SAP Business Suite systems based on SAP_BS_FND 701
(and higher) that support active Forward Error Handling (FEH).
Based on your system architecture and connectivity decision, make settings in Customizing for either direct
connectivity or mediated connectivity.
For direct connectivity, choose
Integration with Other SAP Components
Component for Ariba Framework Settings
following Customizing activities:
SAP Business Suite Integration
Direct Connectivity Settings , and make settings in the
○ Manage and Test Enterprise Services
The Web services used for communication with Ariba Network have to be configured in the SOA Manager. For
more information, see Configuration of SOA Manager [page 57] in the Appendix.
Note
After the SOA configuration you have to execute the technical configuration of Simple Object Access
Protocol (SOAP) runtime (transaction SRT_TOOLS). For more information, search for the keyword
Configuring the Web Service Runtime in the documentation of SAP NetWeaver under http://help.sap.com
and SAP Note 1043195 .
● Maintain Certificate
As the connection is established through HTTPS, a certificate for authentication is required. For more
information, see chapter SAP Business Suite System Acting as a Client [page 30].
● Define Settings for Polling Agent
A polling mechanism is used for retrieving messages. For each Ariba Network ID you can specify which
message types are expected to be received from Ariba Network. If you use end points in polling, specify the
SAP-internal key value of the end point ID. You can also define the maximum number of messages that can be
retrieved within one call to Ariba Network (no more than 100 messages is recommended). All pending
messages are retrieved, but if they exceed the defined maximum, additional calls are performed. The logical
port name has to match the one you have defined in the SOA Manager. For more information about SOA
Manager, see Configuration of SOA Manager [page 57] in the Appendix.
● Define bgRFC Supervisor Destination
You define a supervisor destination for the background RFC (bgRFC) in this Customizing activity. For more
information, see Customizing for Integration with Other SAP Components under
Integration Component for Ariba
Framework Settings
SAP Business Suite
Direct Connectivity Settings
Define bgRFC
Supervisor Destination .
You can also implement the BAdI Notification About Communication Errors ( ARBFND_INTEGRATION) to trigger
actions in situations where errors occur during the communication between your SAP SRM system and Ariba
Network. This BAdI is called if a cXML message cannot be transferred to Ariba Network (outbound direction), or a
cXML message is received but cannot be processed (inbound direction). For more information, see Customizing
for Integration with Other SAP Components under
Framework Settings
22
CUSTOMER
Business Add-Ins (BAdIs)
SAP Business Suite Integration Component for Ariba
BAdI: Notification About Communication Errors .
Buyer's Guide for SP06 of SAP SRM Connectivity with Ariba Network
Configuration Settings
Mediated Connectivity
For mediated connectivity, make settings in Customizing for Integration with Other SAP Components under
Business Suite Integration Component for Ariba
Framework Settings
SAP
Mediated Connectivity Settings
Integration Engine Administration .
Your SAP NetWeaver PI system must be set up and connected to the SAP SRM system. The Integration Engine
configuration should already contain global configuration data. If this is not the case, check the set-up guides for
your SAP NetWeaver PI system.
You can also implement the BAdI Notification About Communication Errors ( ARBFND_INTEGRATION). This BAdI is
called if a cXML message cannot be created (outbound direction), or if a cXML message is received from SAP
NetWeaver PI but cannot be processed (inbound direction). Note that if the message cannot be transferred to SAP
NetWeaver PI, the BAdI is not triggered. For more information, see Customizing for Integration with Other SAP
Components under
Ins (BAdIs)
SAP Business Suite Integration Component for Ariba
Framework Settings
Business Add-
BAdI: Notification About Communication Errors .
Direct and Mediated Connectivity
For both direct and mediated connectivity, the Notification About Communication Errors ( ARBFND_INTEGRATION)
BAdI is called when there are errors in cXML message communication between your SAP SRM system and Ariba
Network. In this BAdI, you can implement the actions (for example, an email notification) that you want to trigger if
errors occur. A sample implementation is available. For more information, see Customizing for SAP Business Suite
Integration Component for Ariba under
Framework Settings
Business Add-Ins (BAdIs)
BAdI: Notification
About Communication Errors .
2.3
SAP SRM-Specific Customizing for Connecting SAP
Business Suite to Ariba Network
In Customizing for Integration with Other SAP Components under
Ariba Application Specific Settings
Customizing activities:
SAP Business Suite Integration Component for
SAP SRM Integration Component for Ariba , make settings in the following
● Assign Ariba Network ID to Logical System
Assign your ANID(s) to the logical systems of the SAP ERP back-end systems that you want to be connected
to Ariba Network.
You can refine this functionality further and specify which ANID must be used for which purpose. To do this,
implement the BAdI method ASSIGN_SENDER_ANID method in the BAdI: Outbound Mapping
( ARBSRM_OUTBOUND_MAPPING).
Note
As of SP05 of of SAP SRM Connectivity with Ariba Network, the above customizing has been changed from
Assign Ariba Network ID to Company Code to Assign Ariba Network ID to Logical System and the table
Buyer's Guide for SP06 of SAP SRM Connectivity with Ariba Network
Configuration Settings
CUSTOMER
23
column Company code has been removed. If you are upgrading to SP05 from lower releases, you must
execute the migration reports for re-creating the existing customizing data in the new table. For information
about the migration reports, see 2486576
and 2480856
.
● Define and Enable Suppliers for Ariba Network
In this Customizing activity, you enable suppliers to engage in business with you via the Ariba Network. You
also define which outbound cXML message types you will exchange with a supplier. (For inbound message
types, see Customizing for SAP Business Suite Integration Component for Ariba under
Framework Settings
Direct Connectivity Settings Define Settings for Polling Agent .)
Ariba Network Integration 1.0 for SAP Business Suite addresses suppliers in SAP SRM by the ID of the
business partner with the role “supplier”. You must map the Ariba Network IDs of the suppliers with their SAP
SRM supplier IDs and their SAP SRM system IDs. You do this in the settings of your buyer account on Ariba
Network.
In this Customizing activity you can enter suppliers that are not yet part of Ariba Network. You can invite them
by setting the Quick Enablement checkbox. Before executing the quick enablement function, you must first
maintain the supplier's email address in the master data.
○ OrderRequest message - You must specify the logical system IDs of the relevant SAP ERP back-end
systems. If you have several SAP ERP back-end systems in your system landscape, you must create the
corresponding number of entries for the same supplier. Also, select the corresponding ORDR Enabled
checkbox to enable the OrderRequest (ORDR) Integration.
○ QuoteRequest message - The Quick Enablement functionality is not used for the QuoteRequest message.
Suppliers that are already maintained for OrderRequest can be enabled for QuoteRequest process by
setting the QTEQ Enabled (QuoteRequest) checkbox. Additionally, for QuoteRequest, supplier’s contact
business partner's ID must be maintained in the table column Contact, to be used as the contact person
for the supplier while creating the RFx in SAP SRM. This Contact is the value entered for Contact in Ariba.
You can create and update the above data in the SAP SRM table using the Supplier Upload tool. For
information about the Supplier Upload Tool, see 2486575
.
Note
As of SP05 of of SAP SRM Connectivity with Ariba Network, this customizing has been changed and the
table columns Company code and cXML Message Type have been removed. Three columns QTEQ
Enabled, ORDR Enabled and Contact have been added in the customizing view. If you are upgrading to
SP05 from lower releases, you must execute the migration reports for re-creating the existing
and
customizing data in the new table. For information about the migration reports, see 2486576
2480856
.
● Define Document-Specific Message Customizing
The message configuration allows you to decide on attachment transfer. Also, for incoming messages, you
have the option of attaching the original cXML message to the created object.
● Map Texts of SAP SRM and Ariba Network
It is possible to send texts from SAP SRM using outbound cXML messages, and it is possible to receive texts in
SAP SRM using inbound cXML messages. To enable this, you make settings to map cXML text elements to
SAP SRM text schemas and text IDs. Use the activities Define Text Mapping for Outbound Messages and Define
Text Mapping for Inbound Messages.
If cXML comment types are used, they can be defined in SAP SRM and used in the text mapping for outbound
and inbound messages. You can define different mappings for different comment types. To map texts
independent of their comment types, enter an asterisk (*) as a wildcard in the SAP SRM-Internal ID of cXML
Comment Type column in the activity Define cXML Comment Types for Text Mapping.
24
CUSTOMER
Buyer's Guide for SP06 of SAP SRM Connectivity with Ariba Network
Configuration Settings
Business Add-Ins (BAdIs)
You can also implement the following BAdIs by choosing
Business Suite Integration Component for Ariba
for Ariba
Integration with Other SAP Components
Application Specific Settings
SAP
SAP SRM Integration Component
Business Add-Ins (BAdIs) :
● BAdI: Outbound Mapping
For example, you can do the following:
○ You can substitute the logic for all outgoing cXML messages by implementing the
DEFINE_CUST_SPEC_MAPPING method. The cXML message has not yet been created at this time, and
you can decide to build the cXML message yourself. Anywhere in the BAdI, you can decide to go back to
the standard implementation by setting the CV_PROCEED_WITH_APPL_PROC parameter.
○ For OrderRequest cXML messages, you can enrich, filter, and exchange the standard mapping by
implementing the MAP_BUS2201_TO_ORDR_OUT method.
○ If a company code corresponds to more than one ANID, you can specify the desired ANID in the cXML
header by implementing the ASSIGN_SENDER_ANID method for all outbound messages. For example, you
can assign one ANID to each purchasing organization.
○ If you use endpoints, you must implement the method ASSIGN_SENDER_ENDPOINT to provide the logic
for selecting the endpoint that needs to be included for all outbound messages.
○ You can use the FORMAT_COMMENTS method to format the texts used in outbound SAP SRM documents.
● BAdI: Inbound Mapping
For all incoming messages, pre-mapping and post-mapping methods are available. The pre-mapping methods are
meant to enrich, filter, and exchange the data passed to the application interface, while the post-mapping methods
make it possible to enrich the created business documents. For example, you can do the following:
● You can define your own mapping and processing logic, using the method DEFINE_CUST_SPEC_PROCESSING.
At any time in the BAdI, you can decide to go back to the standard implementation by setting the
CV_PROCEED_WITH_APPL_PROC indicator.
● You can map field types or cXML elements that are not part of the standard mapping, using the
DEFINE_CUST_SPEC_PROCESSING method.
● You can perform additional functions after the application interface processing, using the
MAP_CONF_TO_BUS2209_IN_POST method.
2.4
Required Settings in SAP SRM
To support the Order Collaboration process between SAP SRM and Ariba Network, you must make the specific
settings described below in Customizing of SAP Supplier Relationship Management.
Post-Processing Framework
For the purchase order and RFQ output to Ariba Network, the standard output management in SAP SRM, which is,
based on the Post-Processing Framework (PPF), is used as the message trigger. As a prerequisite, you have to
Buyer's Guide for SP06 of SAP SRM Connectivity with Ariba Network
Configuration Settings
CUSTOMER
25
make the following setting in Customizing of SAP Supplier Relationship Management under
Cross-Application Basic Settings
Set Output Actions and Output Format
SRM Server
Define Actions for Document Output .
For Purchase Order
1. Select the Action Profile BBP_PD_PO for standard purchase orders.
2. Navigate to the Action Definition named STANDARD_PO.
3. Navigate to the Processing Types for the Action Definition STANDARD_PO.
4. Double-click the processing type Method Call and replace the standard processing method
BBP_PO_SEND_XML by the method ARBSRM_PO_SEND_CXML.
Technically, this method belongs to the new implementation ARBSRM_CXMLCALL_PPF of the BAdI
EXEC_METHODCALL_PPF with the implementing class CL_IM_ARBSRM_CXMLCALL_PPF.
When a business user orders a purchase order, this implementation is called, provided that XML is the default
output medium for the supplier who is assigned to the purchase order. To determine whether a purchase order
assigned to a specific supplier is to be sent to Ariba Network, the settings in the following Customizing activity are
used:
SAP Business Suite Integration Component for Ariba
Application Specific Settings
SAP SRM
Integration Component for Ariba Define and Enable Suppliers for Ariba Network . If the supplier is maintained in
this Customizing activity, the purchase order is sent to Ariba Network.
For RFQ
1. Select the Action Profile BBP_PD_BID for standard RFQs.
2. Navigate to the Action Definition named STANDARD_BID.
3. Navigate to the Processing Types for the Action Definition STANDARD_BID.
4. Double-click the processing type Method Call and replace the standard processing method
BBP_RFQ_SEND_XML by the method ARBSRM_RFQ_SEND_CXML.
Technically, this method belongs to the new implementation ARBSRM_CXMLCALL_RFQ of the BAdI
EXEC_METHODCALL_PPF with the implementing class CL_IM_ARBSRM_CXMLCALL_RFQ.
When a business user publishes an RFQ, this implementation is called, provided that the Process Type for RFQ is
enabled for Ariba Integration in the Customizing activity
Application Specific Settings
Ariba
SAP Business Suite Integration Component for Ariba
SAP SRM Integration Component for Ariba
Supplier Quotation Process
SAP SRM Integration Component for
Map Transaction Types for RFQ .
Workflow
The handling of purchase orders and of purchase order responses in SAP SRM includes processing via SAP SRM
workflow. You must activate the corresponding workflows and their start conditions for the following business
object types:
● For purchase orders: BUS2201
● For purchase order responses: BUS2209
These workflows and their start conditions are part of the SAP SRM standard delivery.
26
CUSTOMER
Buyer's Guide for SP06 of SAP SRM Connectivity with Ariba Network
Configuration Settings
2.5
Customizing Settings for QuoteRequest and
QuoteMessage cXML Messages
In Customizing for Integration with Other SAP Components under
for Ariba
Process
Application Specific Settings
SAP Business Suite Integration Component
SAP SRM Integration Component for Ariba
Supplier Quotation
, make settings in the following Customizing activities:
Define External Processing for Supplier Quotation
In this Customizing activity, you can define the external processing types for the Request for Quotation.
Here are the supported external processing types:
● SPOT - Ariba Quote Automation
● SREQ - Ariba Sourcing Request
The external processing types defined is used in the Customizing activity Map Transaction Types for RFQ.
Map Transaction Types for RFQ
In this Customizing activity, you can map the transaction type BUS2200 to the Ariba Processing Types.
1. In the column Transaction Type, choose the RFx transaction type using F4 Help. Any RFx document created
with this transaction type gets routed to Ariba Discovery or Ariba Sourcing after the Publish.
2. In the column External Processing, map the RFx transaction type to one of the following Ariba Processing
Types:
○ SPOT - Ariba Quote Automation
○ SREQ - Ariba Sourcing Request
3. Define the Quote Receiving Preference for each RFx transaction type mapped to the Ariba Processing Types.
Here are the available Quote Receiving Preference types:
○ All Bids - All the bids, including all versions from all suppliers, are transferred to SRM.
○ Leading Bids - Only the latest version of the bids from each supplier are transferred to SRM.
○ Winning Bids - Only awarded bids are transferred to SRM.
Note
For Ariba Sourcing Request, only Winning Bids can be the Quote Receiving Preference.
Define Document-Specific Customizing for Attachments
For inbound and outbound messages, enable the Attachment Transfer checkbox.
Buyer's Guide for SP06 of SAP SRM Connectivity with Ariba Network
Configuration Settings
CUSTOMER
27
Note
Attachments marked as "Internal" are not transferred to Ariba Network.
Attachments for Inbound RFQ response from Ariba Sourcing is not currently supported.
Texts and Comments
SAP SRM Connectivity with Ariba Network supports mapping and transmission of the following RFQ texts to the
Ariba Network RFQ posting, which are visible to the supplier.
● Supplier Remarks at RFQ header level
● Supplier Remarks at RFQ Item level
● Bidder Remarks at RFQ response Item level
2.6
Jobs to Be Scheduled
The following reports are available and need to be scheduled as regular jobs:
● Fetch cXML messages for different message types from Ariba Network
( ARBFND_FETCH_CXML_MESSAGES_NEW)
This report, that is also referred to as the Polling Agent, polls pending messages from Ariba Network and is
only relevant for direct connectivity. It has to be scheduled as a variant in which you select all cXML messages
types that you wish to receive and process in your SAP SRM system.
● Cleanup serialization tables for Ariba integration ( ARBSRM_CLEANUP_DB_TABLES)
The basic message header data (for example, payload ID, timestamp) of all cXML messages to and from the
Ariba Network are stored in database tables in order to guarantee serialization and duplication checks. We
recommend that you schedule this report to archive these entries when they are no longer needed and thus
keep the database tables to a reasonable size.
Note
We recommend that you do not schedule this job too often.
For more information about the above described reports, see the report documentation that is available in the
system.
If the connection to Ariba Network is not working for a certain period and many cXML messages in SAP SRM
cannot be transmitted, a mass restart of messages that have errors is helpful. Once the connection is working
again, you can run the report and start a mass resending of messages with errors.
Depending on your connectivity options, run the following reports to resend mass messages with errors:
● Restart Messages with Errors ( RSXMB_RESTART_MESSAGES)
This report is intended for mediated connectivity using SAP NetWeaver PI.
It searches for failed messages (messages that could not be processed correctly) or missing messages
(messages that have been deleted from the queue manually) and tries to restart the sending of these
28
CUSTOMER
Buyer's Guide for SP06 of SAP SRM Connectivity with Ariba Network
Configuration Settings
messages automatically. The maximum number of restart attempts and the interval between these attempts
is set with the queued remote function call (qRFC) scheduler.
For more information, search for the phrase Periodical Tasks in the documentation for SAP NetWeaver that is
available at http://help.sap.com .
● Web Service Utilities: Message Restart ( SRT_UTIL_RESTART)
This report is intended for direct connectivity. It can be used for restarting multiple messages on the basis of
specific selection criteria. The report can be used for manual execution and for automatic execution using
jobs. If this report is not available in your SAP system, use the report Restart Failed Outbound Messages
( ARBFND_MASS_MESSAGE_RESTART).
● Restart Failed Outbound Messages ( ARBFND_MASS_MESSAGE_RESTART)
This report is intended for direct connectivity if report Web Service Utilities: Message Restart
( SRT_UTIL_RESTART) is not available in your SAP system.
It searches for failed messages (messages that could not be processed correctly) and tries to restart sending
these messages automatically.
Note
Do not schedule this report but execute it on demand.
● Send Status Update for Canceled Inbound Messages to Ariba Network ( ARBFND_SEND_STATUS_CANCELLED)
Inbound cXML messages that cannot be processed in SAP SRM can be canceled manually in the XML monitor
(transaction sxmb_moni). This report selects such messages and transfers the failed status to Ariba Network.
Note
○ This report is relevant if you do not use Forward Error Handling (FEH).
○ Do not schedule this report but execute it on demand.
Buyer's Guide for SP06 of SAP SRM Connectivity with Ariba Network
Configuration Settings
CUSTOMER
29
3
Security
For direct connectivity, the SAP Business Suite system always opens the connection by executing the following
actions:
● The SAP Business Suite system pushes cXML messages to Ariba Network (synchronous)
● The Polling Agent of Ariba Network Integration 1.0 for SAP Business Suite fetches pending messages from
Ariba Network (synchronous)
For mediated connectivity, the SAP Business Suite system connects through SAP NetWeaver PI. The connection
functions as follows:
● The SAP Business Suite system pushes cXML messages to SAP NetWeaver PI (asynchronous)
● The Ariba PI adapter triggers its Polling Agent to fetch pending cXML messages from Ariba Network. The
Polling Agent in the PI adapter then pushes the cXML messages to the SAP Business Suite system
(asynchronous).
In both use cases, only the on-premise component opens the connection to the Cloud, thus supporting the highest
level of security. A proxy or reverse proxy in the demilitarized zone (DMZ) is not required.
The SAP Business Suite system communicates with Ariba Network through the HTTPS protocol, encrypting
transmitted data.
If Ariba Network Integration 1.0 for SAP Business Suite communicates with Ariba Network through SAP
NetWeaver PI, there are no special security requirements.
Ariba provides information on how to communicate with Ariba Network in the Ariba Network Adapter for SAP
NetWeaver Setup Guide. You can contact Ariba for more information.
As the security topics for mediated connectivity through SAP NetWeaver PI are covered by the Ariba Network
Adapter for SAP NetWeaver Setup Guide, the next chapter focuses on direct connectivity.
Note
Advanced Security Configuration is available for the Ariba Network and will be the default setting as of
September 30, 2016. To ensure that your Business Suite system can continue to communicate with the Ariba
Network, check whether your SAP AS ABAP kernel release patch level is up-to-date. For more information, see
SAP Note 2335891 .
3.1
SAP Business Suite System Acting as a Client
When sending a cXML message to Ariba Network, the sender must authenticate itself. Ariba Network offers
different authentication methods (authentication with client certificate or shared secret password) that are also
supported by Ariba Network Integration 1.0 for SAP Business Suite.
For more information about the authentication methods on Ariba Network, contact Ariba.
30
CUSTOMER
Buyer's Guide for SP06 of SAP SRM Connectivity with Ariba Network
Security
Note
Communication with Ariba Network is based on HTTPS. For HTTPS SSL encryption, SAP Cryptographic Library
is required. For information about installation of SAP Cryptographic Library, search for the phrase The SAP
Cryptographic Library Installation Package in the documentation of SAP NetWeaver at http://help.sap.com
.
Authentication with Client Certificate
For authentication with client certificate it is strongly recommended that you use the latest version of the SAP
Cryptographic Library ( SAPCRYPTOLIB). For more information about latest SAP Cryptographic Library versions,
bugs, and fixes see SAP Note 455033
.
To set up authentication with client certificate, proceed as follows:
1. Get the client certificate from a Certification Authority (CA) that is trusted by Ariba.
2. Import the private key of the certificate into the SAP Business Suite system by using Trust Manager
(transaction STRUST).
Note
Only certificates in Personal Security Environment (PSE) format can be imported. Certificates in other
formats must first be converted to PSE format. The conversion can be done using the command line tool
SAPGENPSE. The tool can be installed with SAP Cryptographic Library installation package. For more
information, see The SAP Cryptographic Library Installation Package.
For example, to convert from P12 (Public-Key Cryptography Standards) format to PSE format, enter the
following command line:
sapgenpse import_p12 -v -r <root certificate> -p <Target PSE file> <Source File>
First, create a new Client Identity in Trust Manager. Choose Environment SSL Client Identities , enter
ARIBA as the identity name and Ariba Network Client as the description. Save your entries.
Second, import the private key of the certificate in Trust Manager. Proceed as follows:
1. Select the created ARIBA SSL Client ID and choose
PSE
Import
to import the PSE file.
2. Enter the password for the certificate if required.
3. Save your PSE file by choosing
PSE
Save as
SSL Client , and enter ARIBA as the SSL Client.
4. Navigate to the Own Certificate group box on the Trust Manager screen, and double-click the certificate to
add it to the certificate list. The certificate is now shown in Trust Manager in Certificate List.
3. Import the root certificate into the SAP Business Suite system by using Trust Manager. Proceed as follows:
1. Double-click the SSL Client Identity ARIBA that you have created.
2. Navigate to the Certificate group box and choose Import certificate. Add the imported certificate to the
certificate list by clicking Add to Certificate List .
4. For HTTPS SSL encryption, obtain the server certificate from Ariba. Proceed as follows:
1. Go to http://buyer.ariba.com
.
2. Download the certificate using your browser.
Buyer's Guide for SP06 of SAP SRM Connectivity with Ariba Network
Security
CUSTOMER
31
For example, if you are using Internet Explorer, choose View Security Report View Certificates . On
the Details tab page, choose Copy to File and export it in the Base-64 encoded X.509 format.
3. Import the server certificate into the SAP Business Suite system using Trust Manager.
4. Double click the ARIBA SSL Client ID that you have created.
5. Navigate to the Certificate group box and choose Import certificate. Add the imported certificate to the
certificate list by clicking Add to Certificate List.
5. To activate the changes, restart the Internet Communication Manager (ICM) using transaction SMICM and
choose Administration ICM Restart Yes . For more information, search for the phrase “Using the ICM
Monitor” in the documentation of SAP NetWeaver at http://help.sap.com .
6. Configure the Web services in SOA Manager (transaction SOAMANAGER). Follow the steps described under
Configuration of SOA Manager and find the following consumer proxies:
○ cXMLSynchronousOutboundAdapterMessage_Out ( CO_ARBFND_PRX_OADP_OUT)
○ cXMLGetPendingDataRequest_Out ( CO_ARBFND_PRX_GPDQ_OUT)
In the Details of Consumer Proxy group box, navigate to the Configurations tab page, select the logical port. In
the Configuration of Logical Port group box, navigate to the Consumer Security tab page, choose the X.509 SSL
Client Certificate radio button and enter Ariba in the SSL Client PSE of transaction STRUST field.
7. In the profile of your account on Ariba Network, select the Certificate authentication method in the cXML
setup and enter the public key of the certificate.
Authentication with Shared Secret Password
To set up authentication with shared secret password, proceed as follows:
1. Maintain the shared secret password in the Define Credentials for Ariba Network Customizing activity. For
more information, see Add-On Customizing.
The shared secret password is stored in the secure storage ABAP DB in SAP Business Suite system. Ariba
Network Integration 1.0 for SAP Business Suite supports a shared secret password for Ariba Network with a
maximum length of 36 characters.
Note
Note: for authentication with shared secret password, the shared secret password has to be provided in the
Sender element of the cXML payload.
According to security requirements, passwords must not be written to logs, protocols or traces. Therefore,
the shared secret password is not visible in transactions such as SXMB_MONI where the XML message
monitoring and tracing takes place, as business users can also have authorization for the message
monitoring transactions. However when activating an Internet Communication Framework (ICF) recording
using transaction SICF, the system logs the shared secret password in the corresponding ICF trace. ICF
recording is only intended for administrators and requires the S_ADMI_FCD authorization.
2. For HTTPS SSL encryption, obtain the server certificate from Ariba. Proceed as follows:
1. Go to http://buyer.ariba.com
.
2. Download the certificate using your browser.
For example, if you are using Internet Explorer, choose View Security Report . Choose View
Certificates. On the Details tab page, choose Copy to File and export it in the Base-64 encoded X.509
format.
32
CUSTOMER
Buyer's Guide for SP06 of SAP SRM Connectivity with Ariba Network
Security
3. Import the server certificate into the SAP Business Suite system using Trust Manager.
4. Double-click the SSL Client SSL Client (Anonymous) node.
Navigate to the Certificate group box and choose Import certificate. Add the imported certificate to the
certificate list by clicking Add to Certificate List.
3. To activate the changes, restart the Internet Communication Manager (ICM) using transaction SMICM and
choose
Administration
ICM
Restart
Yes .
4. In the profile of your account in the Ariba Network, select the shared secret authentication method in the cXML
setup.
3.2
SAP Business Suite System Acting as a Server
No proxy or reverse proxy is required. The asynchronous inbound application service interfaces are called either
internally in the SAP Business Suite system or by SAP NetWeaver PI.
3.3
Virus Scan for Attachments
For attachments arriving with cXML messages, Ariba Network Integration 1.0 for SAP Business Suite calls the SAP
NetWeaver virus scan interface (VSI).The VSI also provides an interface to an external virus scan.
Note that you must install your own virus scan software, as we do not provide virus scan software with Ariba
Network Integration 1.0 for SAP Business Suite.
For more information, search for the phrase Virus Scan Interface in the documentation of SAP NetWeaver under
http://help.sap.com .
3.4
Roles and Authorizations
In Ariba Network Integration 1.0 for SAP Business Suite you can use the authorization object ARBFND_ARB to
execute reports and to process inbound messages. This object is assigned to the role SAP Business Suite
Integration Component for Ariba ( SAP_ARBFND_INTEGRATION), which provides general authorization for using
Ariba Network Integration 1.0 for SAP Business Suite. You must assign this role to the user executing reports. To
make sure the corresponding profile is available and active, generate the role profile using transaction PFCG.
Also for processing incoming messages in SAP SRM, a technical user is required. This user must not have the
SAP_ALL authorization but needs the Operational Purchaser role. This role provides authorization for handling
purchase orders and purchase order responses.
Depending on whether you use direct or mediated connectivity, you also have to assign one of the following roles
to the technical user:
● For direct connectivity:
Web Service Consumer ( SAP_BC_WEBSERVICE_CONSUMER)
Buyer's Guide for SP06 of SAP SRM Connectivity with Ariba Network
Security
CUSTOMER
33
This role is required for using Web service protocol to communicate in direct connectivity.
● For mediated connectivity:
Exchange Infrastructure: Service User for Application Systems ( SAP_XI_APPL_SERV_USER)
This role is required to communicate through XI protocol in mediated connectivity.
34
CUSTOMER
Buyer's Guide for SP06 of SAP SRM Connectivity with Ariba Network
Security
4
Operation and Troubleshooting
4.1
Message Monitoring
4.1.1 Message Monitoring for Direct Connectivity
Outbound Messages
Outbound messages are triggered by the SAP SRM application itself when a purchaser orders a purchase order.
On the PO Header under Output, you can display an output status and further details.
Example:
Figure 9: Output Information in SAP SRM Purchase Order
If the output was successful, the details list the cXML message ID, which can be used for monitoring in the XML
monitor (transaction SXMB_MONI), and cXML message payloadID, which can be used for monitoring in the SAP
SRM application log (transaction SLG1) or on the Ariba Network.
Buyer's Guide for SP06 of SAP SRM Connectivity with Ariba Network
Operation and Troubleshooting
CUSTOMER
35
The success entry in the output information means that the cXML message was successfully forwarded to the
synchronous outbound adapter for transmission. However, this does not necessarily imply that the purchase order
has already been transferred to and created on Ariba Network.
A complete trace of the message processing is available in the SAP SRM application log (transaction SLG1) under
the Ariba Integration ( Ariba_Integration) object.
You can search by XML message ID, payload ID, or ID of the object (for example, PO number). You can enter the ID
in the External ID field. Note that you have to insert an asterisk before and after an external ID, as shown in the
following figure:
Figure 10: Search for a Message in the Application Log by External ID
For a purchase order, you will find two entries:
● An entry informing you whether the cXML message has been forwarded to the synchronous outbound adapter
for transmission
● An entry reflecting the transmission status to Ariba Network
36
CUSTOMER
Buyer's Guide for SP06 of SAP SRM Connectivity with Ariba Network
Operation and Troubleshooting
The following figure shows the processing log of a successfully created message:
Figure 11: Processing Log of a Successfully Created Message
Note
As of SAP_BASIS 7.40, you have to use the message monitor of Web Service Utilities (transaction SRT_MONI)
for monitoring XML messages instead of the XML monitor (transaction SXI_MONITOR).
The XML message IDs can be used as selection parameters for the XML monitor (transaction SXI_MONITOR) to
directly access a cXML message.
Buyer's Guide for SP06 of SAP SRM Connectivity with Ariba Network
Operation and Troubleshooting
CUSTOMER
37
The following figure shows how to select a cXML message by its message ID in SXI_MONITOR:
Figure 12: Search for a cXML Message by Message ID
The monitor displays a checkered flag status for a successfully transferred message, as shown in the figure below.
Given that the call to Ariba Network is synchronous, Ariba Network accepts and creates the message.
38
CUSTOMER
Buyer's Guide for SP06 of SAP SRM Connectivity with Ariba Network
Operation and Troubleshooting
Figure 13: A Successfully Transferred Message in the Monitor
Inbound Messages
Inbound messages are polled from Ariba Network by running the report Fetch cXML messages for different
message types from Ariba Network (ARBFND_FETCH_CXML_MESSAGES_NEW). You must schedule the report to run
regularly. For more information, see chapter Jobs to Be Scheduled [page 28].
Ariba Network Integration 1.0 for SAP Business Suite writes an application log entry for each executed poll and for
each message retrieved from Ariba Network.
Note
As of SAP_BASIS 7.40, you have to use the message monitor of Web Service Utilities (transaction SRT_MONI)
for monitoring XML messages instead of the XML monitor (transaction SXI_MONITOR).
All cXML messages are displayed in the XML message monitor (transaction SXI_MONITOR).
To filter the messages, you can specify the interface name of the receiver by using the standard selection criterion
cXMLConfirmationRequest_In.
The system displays the status for a message as follows:
● Checkered flag for successful processing
Buyer's Guide for SP06 of SAP SRM Connectivity with Ariba Network
Operation and Troubleshooting
CUSTOMER
39
● Red for failed processing
● Green for queued processing
If your SAP Business Suite system is on SAP_BS_FND 701 or higher and Forward Error Handling (FEH) is
activated, the system can display a yellow status. This means that the system has forwarded the issue to the FEH
application.
The framework of Ariba Network Integration 1.0 for SAP Business Suite additionally offers to send the processing
status of an inbound message back to Ariba Network. You can activate this functionality in the Customizing activity
Define Basic Message Settings by selecting the Send cXMLStatusUpdateRequest Message checkbox. For more
information, see Customizing under
Component for Ariba
Integration with Other SAP Components
Framework Settings
SAP Business Suite Integration
Define Basic Message Settings.
If this functionality is activated, an inbound message that has successfully been processed by the SAP SRM
system changes the routing status of a document from Sent to Acknowledged on Ariba Network.
Inbound messages that have not been successfully processed by the SAP SRM system will change the status from
Sent to Failed - provided that Forward Error Handling (FEH) is activated and the message is discarded.
The following figure shows order confirmations with different statuses in the supplier's outbox on Ariba Network:
Figure 14: Different Statuses of Order Confirmations in the Supplier's Outbox on Ariba Network
40
CUSTOMER
Buyer's Guide for SP06 of SAP SRM Connectivity with Ariba Network
Operation and Troubleshooting
4.1.2 Message Monitoring for Mediated Connectivity
Outbound Messages
Outbound messages are triggered by the SAP SRM application itself when a purchaser orders a purchase order.
On the PO Header under Output, you can display an output status and further details.
Example:
Figure 15: Output Information in SAP SRM Purchase Order
If the output was successful, the details list the cXML message ID, which can be used for monitoring in the XML
monitor (transaction SXMB_MONI), and cXML message payloadID, which can be used for monitoring in the SAP
SRM application log (transaction SLG1) or on the Ariba Network.
The success entry in the output information means that the cXML message was successfully forwarded to the
synchronous outbound adapter for transmission. However, this does not necessarily imply that the purchase order
has already been transferred to and created on Ariba Network.
A complete trace of the message processing is available in the SAP SRM application log (transaction SLG1) under
the Ariba Integration ( Ariba_Integration) object.
Buyer's Guide for SP06 of SAP SRM Connectivity with Ariba Network
Operation and Troubleshooting
CUSTOMER
41
You can search by XML message ID, payload ID, or ID of the object (for example, PO number). You can enter the ID
in the External ID field. Note that you have to insert an asterisk before and after an external ID, as shown in the
following figure:
Figure 16: Search for a Message in the Application Log by External ID
The application log displays exactly one entry for your outbound message. This entry records the creation of the
cXML message.
If the message is successful, the system displays a green status in the application log and passes the message to
your middleware.
The message transfer to Ariba Network has to be centrally monitored on SAP NetWeaver PI.
The application uses a green status for successful processing. This means that the system has created a cXML
message that will automatically be transferred to SAP NetWeaver PI. The message log contains the PO ID, the
cXML message payload ID, and the XML message ID.
42
CUSTOMER
Buyer's Guide for SP06 of SAP SRM Connectivity with Ariba Network
Operation and Troubleshooting
The following figure shows the processing log of a successfully created message:
Figure 17: Processing Log of a Successfully Created message
Note
As of SAP_BASIS 7.40, you have to use the message monitor of Web Service Utilities (transaction SRT_MONI)
for monitoring XML messages instead of the XML monitor (transaction SXI_MONITOR).
The XML message IDs can be used as selection parameters for the XML monitor (transaction SXI_MONITOR) to
directly access a cXML message.
The monitor displays a checkered flag status for a successfully transferred message, as shown in the figure below.
The monitor displays an error status if there is a technical connectivity issue between SAP SRM and SAP
NetWeaver PI. The system firsts sends a cXML message to SAP NetWeaver PI, and then transfers the cXML
message to Ariba Network.
Buyer's Guide for SP06 of SAP SRM Connectivity with Ariba Network
Operation and Troubleshooting
CUSTOMER
43
Figure 18: A Successfully Transferred Message in the Monitor
Inbound Messages
Inbound messages are sent from SAP NetWeaver PI to the SAP SRM system.
Ariba Network Integration 1.0 for SAP Business Suite writes an application log entry for each message retrieved
from SAP NetWeaver PI.
All cXML messages are displayed in the XML message monitor (transaction SXI_MONITOR).
Note
As of SAP_BASIS 7.40, you have to use the message monitor of Web Service Utilities (transaction SRT_MONI)
for monitoring XML messages instead of the XML monitor (transaction SXI_MONITOR.
To filter the messages, you can specify the interface name of the receiver by using the standard selection criterion
cXMLConfirmationRequest_In.
The system displays a status for a message as follows:
● Checkered flag for successful processing
● Red for failed processing
● Green for queued processing
44
CUSTOMER
Buyer's Guide for SP06 of SAP SRM Connectivity with Ariba Network
Operation and Troubleshooting
If your SAP Business Suite system is based on SAP_BS_FND 701 or higher and Forward Error Handling (FEH) is
activated, the system can display a yellow status. This means that the system has forwarded the issue to the FEH
application.
The framework of Ariba Network Integration 1.0 for SAP Business Suite additionally offers to send the processing
status of an inbound message back to Ariba Network. You can activate this functionality in Customizing activity
Define Basic Message Settings by selecting the Send cXMLStatusUpdateRequest Message checkbox. For more
information, see Customizing under
Component for Ariba
Integration with Other SAP Components
Framework Settings
SAP Business Suite Integration
Define Basic Message Settings .
If this functionality is activated, an inbound message that has successfully been processed by the SAP Business
Suite system changes the routing status of a document from Sent to Acknowledged on Ariba Network.
Inbound messages that have not been successfully processed by the SAP Business Suite system will change the
status from Sent to Failed - provided that Forward Error Handling (FEH) is activated and the message is discarded.
The following figure shows order confirmations with different statuses in the supplier's outbox on Ariba Network:
Figure 19: Different Statuses of Order Confirmations in the Supplier's Outbox on Ariba Network
Buyer's Guide for SP06 of SAP SRM Connectivity with Ariba Network
Operation and Troubleshooting
CUSTOMER
45
4.2
Application Log
The application log is the central tool for monitoring all activities in SAP Business Suite systems that are
connected to Ariba Network Integration 1.0 for SAP Business Suite. You can access the application log using
transaction SLG1.
The SAP Business Suite system records all messages triggered to Ariba or received from Ariba in one or more
entries under the Ariba Integration ( ARIBA_INTEGRATION) object.
There are four subobjects for further filtering:
● INBOUND
Ariba Network Integration 1.0 for SAP Business Suite processes all messages belonging to the namespace http://
sap.com/xi/ARBFND1
and the below defined interfaces. Ariba Network Integration 1.0 for SAP Business Suite
writes an entry to the application log. You can also review the processing status of the entries.
Messages that have been pushed into the SAP Business Suite system by middleware create an entry only with the
subobject Inbound. Messages that have been polled from Ariba Network directly into the SAP Business Suite
system are included in both an entry with the subobject INBOUND and an entry with the subobject POLLING.
● POLLING
If you run the integration to Ariba Network through direct connectivity, you must schedule a polling job to retrieve
messages. Each time the polling job runs, it writes an entry in the application log, listing the message type and
timestampwhen the system has polled.
After messages have been polled from Ariba Network, the log entry lists all message IDs (XML ID and payload ID)
that have been retrieved and put in the queue for message processing.
● OUTBOUND
Every message leaving the SAP Business Suite system writes an entry to the application log with this subtype. For
direct connectivity, there are two entries, one for the creation of the cXML message and the other indicating
whether the message has successfully been transferred to Ariba Network.
● EXTRACTION
This subobject is relevant for all messages triggered by extraction reports. When a corresponding background job
for sending such message has run and created messages, the log entry contains all relevant document ID. For
more information about jobs, see chapter Jobs to Be Scheduled.
Search in the Application Log
You can filter the application log entries by object and subobject as described above. Date and Time is also a filter
criterion.
If you are searching for specific entries, you can also use the External ID field by entering a business object ID, a
payload ID, or a XML message ID. Note that you have to insert an asterisk before and after the entered ID.
Since Ariba Network Integration 1.0 for SAP Business Suite creates many entries to record the message exchange
with Ariba Network, we recommend that you double check your settings for archiving your application log and
make necessary adjustments. For more information, search for the phrase Application Log - User Guidelines (BCSRV-BAL) in the documentation of SAP NetWeaver at http://help.sap.com .
46
CUSTOMER
Buyer's Guide for SP06 of SAP SRM Connectivity with Ariba Network
Operation and Troubleshooting
4.3
Forward Error Handling (FEH)
The Forward Error Handling (FEH) framework is available with SAP_BS_FND 70 and higher. For more information,
search for the phrase Error and Conflict Handler in the documentation of SAP NetWeaver under http://
help.sap.com .
You can use FEH for error handling of incoming documents. You can also use it to send acknowledgements to your
business partners on Ariba Network about documents you have received with errors. To send such
acknowledgements, you can schedule the report Send Acknowledgements for Incoming cXML Messages to Ariba
Network ( ARBFND_FEH_SEND_STAT_ACKNO). For more information, see the report documentation that is
available in the system.
4.3.1 Prerequisites: Customizing Settings for FEH
Activate Error and Conflict Handler
You have activated Error and Conflict Handler (ECH) in your SAP application client. For more information, see
Customizing for Cross-Application Components under
Enterprise Services Error and Conflict Handler
Clients view, select the Activated checkbox.
Processes and Tools for Enterprise Applications
Activate Error and Conflict Handler . In the Activate ECH for
Define Resolution Strategy
You have defined a resolution strategy that specifies whether and how processes are executed again or ended after
errors or conflicts occur. You can define, for example, the periods during which a certain error can be corrected by
automatically repeating the process.
For more information, see Customizing for Cross-Application Components under
Enterprise Applications
Enterprise Services
Error and Conflict Handler
Processes and Tools for
Define Resolution Strategy
.
Ariba Network Integration 1.0 for SAP Business Suite provides the component BNS-ARI-SE-FND for which a
resolution strategy can be created.
When defining error resolution strategy, you can find the following source fields:
● Business Process ( PROCESS)
● Error Category ( ERROR_CATEGORY)
Ariba Network Integration 1.0 for SAP Business Suite currently supports the following combinations of business
processes and error categories:
● Receive cXML ConfirmationRequest Message ( ARBFNDCONF)
This business process can have the following error categories:
○ Processing Error ( PRE)
Buyer's Guide for SP06 of SAP SRM Connectivity with Ariba Network
Operation and Troubleshooting
CUSTOMER
47
○ Authorization Error ( PRE.AUE)
○ Temporary Error ( PRE.TEE)
This category of error should trigger an automatic retry.
● Receive cXML ServiceEntrRequest Message ( ARBFNDSRVE)
This business process can have the following error categories:
○ Processing Error ( PRE)
○ Authorization Error ( PRE.AUE)
○ Temporary Error ( PRE.TEE)
This category of error should trigger an automatic retry.
● Send cXML Message ( ARBFNDOADP)
This business process only applies if you use direct connectivity, and it can have the following error categories:
○ Format Error ( FOE)
For example, Ariba Network may return the status codes “400” (Bad Request) or “406” (Not Acceptable),
with the latter meaning that the sent cXML message was not accepted by Ariba.
○ Authorization Error ( PRE.AUE)
Ariba Network returned for example the status codes “401” (Unauthorized) or “403” (Forbidden).
○ Temporary Error ( PRE.TEE)
Ariba Network returned for example the status codes “560” (Temporary Server Error). This category of
error should trigger an automatic retry.
○ Processing Error ( PRE)
This category includes all other errors.
To process an order for which you have specified automatic retry, schedule the report Resubmission of
Postprocessing Orders ( /SAPPO/RESUBMIT_ORDERS_2).
4.3.2 Postprocessing Desktop
A process postprocessing order (PPO) is created in FEH when there is an error in either inbound or outbound
processing. Use Error and Conflict Handler: Process Postprocessing Orders (transaction ECH_MONI_SEL) that is
available as of SAP_BS_FND 702) to analyze the errors. If this transaction is not available in your system, you can
use the Postprocessing Desktop (transaction /SAPPO/PPO2.
The following table provides an overview of the business objects and the corresponding cXML messages for which
errors may occur. Note that the business objects in the sense of FEH correspond to cXML message types.
Table 4:
Business Object Type / Business Process
ARBFNDOADP
cXML Message
N/a. This object is used for error handling of all outbound
cXML messages.
ARBFNDCONF
48
CUSTOMER
Receive cXML ConfirmationRequest Message
Buyer's Guide for SP06 of SAP SRM Connectivity with Ariba Network
Operation and Troubleshooting
4.3.3 Postprocessing Desktop: Edit Task
Double-click on a task to edit the details of the postprocessing order. In the Postprocessing Desktop - Edit Order:
Details screen you can perform the following actions to resolve the error:
● Repeat
The Repeat action restarts the processing of the cXML message. This is usually done after resolving an error,
for example by changing the business object, by changing the payload, or after a temporary system issue has
been resolved.
● Display or change payload
To resolve an error, it may be necessary that you change the payload of a cXML message (see image below).
You can make the required authorization settings in Customizing for Cross-Application Components under
General Application Functions
Error and Conflict Handler
Authorization for Payload Editor .
Figure 20: Changing Payload of a cXML Message
Note
You can use the Details icon in the message table (see the arrow in image above) to navigate from the
Postprocessing Desktop to the application log, where you can display further information.
● Confirm
The Confirm action changes the order status in the Postprocessing Office to Completed, closes the order, and
sets the status to green. You normally use this option if an inbound cXML message could not be transferred
and you have applied the changes to the business document manually .
Buyer's Guide for SP06 of SAP SRM Connectivity with Ariba Network
Operation and Troubleshooting
CUSTOMER
49
● Discard
The Discard action also changes the order status in the Postprocessing Office to Completed, closes the order,
and sends a cXML StatusUpdateRequest message to Ariba Network to set the acknowledgement status of the
corresponding Ariba document to Failed.
If you do not use Forward Error Handling, you can use the report Send Status Update for Canceled Inbound
Messages to Ariba Network ( ARBFND_SEND_STATUS_CANCELLED) to discard messages: The report selects
messages that you have canceled manually in the XML monitor and transfers the Failed status to Ariba
Network.
4.4
Troubleshooting Outbound Messages
Messages can fail to be transferred from SAP SRM system to Ariba Network due to the following reasons:
● The cXML message cannot be created
● The cXML message cannot be transferred to SAP NetWeaver PI (in case of mediated connectivity)
● The cXML message cannot be sent to Ariba Network
Troubleshooting Messages Transferring Purchase Orders
For purchase orders, you can track the creation of the cXML messages in the SAP SRM application where business
users create purchase orders. This information also persists in the application log. For more information, see
chapter Application Log [page 46].
Ariba Network Integration 1.0 for SAP Business Suite does not create cXML messages containing data that is not
supported by Ariba Network. Neither does it create cXML messages that do not contain the minimum set of
required fields.
Once a cXML message has been created and you want find out whether it has successfully reached Ariba Network,
use the XML message monitor (transaction SXI_MONITOR).
50
CUSTOMER
Buyer's Guide for SP06 of SAP SRM Connectivity with Ariba Network
Operation and Troubleshooting
The monitor displays messages that have not been transferred to Ariba Network with a red status (error status), as
shown in the following figure:
Figure 21: Error Status of a Failed Message Displayed in the Monitor
Depending on whether you use mediated connectivity or direct connectivity, the cause of the error must be
analyzed differently:
● If you integrate with Ariba Network using mediated connectivity, analyze the communication between SAP
SRM and your middleware.
● If you integrate with Ariba Network using direct connectivity, a synchronous call is performed from the SAP
SRM to Ariba Network. The error status of the message indicates the following possible issues:
○ Ariba Network can currently not be reached.
In this case, you must reprocess your failed messages once Ariba Network is available again. To enable
mass processing, the report Restart failed outbound messages ( ARBFND_MASS_MESSAGE_RESTART) is
available. For more information, see chapter Jobs to Be Scheduled [page 28].
○ Your cXML message cannot be accepted by Ariba Network.
In this case, you can view the short text of the error message by double-clicking the message. The long
text of the error message, which describes the details of the error, can be found in the application log
(transaction SLG1). You can search in the application log by entering the XML message ID as an external
ID (insert an asterisk before and after the XML message ID). As a result, you receive two log entries: the
first one with a green status, indicating that the cXML message has successfully been created; the second
one with a red status, indicating that the cXML message has not been transferred to Ariba Network.
Double-click the red log entry to see the messages. The error message contains a long text that you can
Buyer's Guide for SP06 of SAP SRM Connectivity with Ariba Network
Operation and Troubleshooting
CUSTOMER
51
display by clicking on Details. This error message is issued by Ariba Network. For more information, see
Application Log [page 46]
If your SAP SRM system is based on SAP_BS_FND 701 or higher and FEH is activated, errors that occur during the
transfer of cXML messagex to Ariba create an object in FEH, and the error handling is done through FEH. For more
information, see chapter Forward Error Handling (FEH) [page 47].
If a newly created purchase order has not arrived on the Ariba Network or if a purchase order has not been
updated correctly, you can run the report Reconciliation of the cXML message OrderRequest
( ARBSRM_RECONCIL_ORDERREQ_CXML). It allows you to resend cXML messages for selected purchase orders. A
message can be resent as the initial one or as a message that updates or deletes a purchase order. For more
information, see the system documentation of the report.
4.5
Troubleshooting Inbound Messages
Messages that reside on Ariba Network in the outbound queue are either polled by the Polling Agent (report
ARBFND_FETCH_CXML_MESSAGES_NEW) in SAP SRM, or they are pushed to SAP SRM by the Ariba Network
Adapter for SAP NetWeaver that is installed on SAP NetWeaver PI.
If you use mediated connectivity, the polled messages are pushed into SAP Business Suite system, where the
inbound processing is triggered. If the handover from the middleware to the SAP Business Suite system is not
successful, the technical connectivity is likely to be the issue. Besides checking the connectivity setup between the
SAP Business Suite system and the middleware, consider issues regarding the user name and password as well as
authorization issues.
For both connectivity options, application-specific message processing issues can be recognized using transaction
SXI_MONITOR.
By searching by the cXML message ID or cXML payload ID, you can also find an entry in the application log
(transaction SLG1) that displays the error message.
Note
cXML messages are always retrieved from Ariba Network and placed into the inbound processing queue of the
SAP Business Suite system, no matter whether they can be processed or not.
If you use direct connectivity, polling errors occur mainly due to authorization issues or due to temporary
downtime of Ariba Network. For information about authorizations, see chapter Roles and Authorizations [page
33]. Failed polling attempts can be found in the application log of the SAP SRM system (transaction SLG1). The
cXML messages remain on Ariba Network until the next successful polling, when all pending messages are picked
up.
If your SAP Business Suite system is on SAP_BS_FND 701 or higher and FEH is activated, unsuccessful incoming
cXML messages create an object in FEH, and the error handling is done using FEH. For more information, see
chapter Forward Error Handling (FEH) [page 47].
An inbound message can fail to be processed for many reasons, for example, authorization issues or application
errors. For information about authorizations, see chapter Roles and Authorizations [page 33].
You can try to resolve the error and restart the message using transaction SXI_MONITOR.
52
CUSTOMER
Buyer's Guide for SP06 of SAP SRM Connectivity with Ariba Network
Operation and Troubleshooting
The following figure shows an example of a purchase order confirmation cXML message that failed in inbound
processing:
Figure 22: A Failed ConfirmationRequest Message in Inbound Processing
You can double-click the cXML message and see the error message. You can also view the error message by
entering the XML message ID or cXML payload ID in the application log (transaction SLG1).
You will find one entry with the red error status.
Buyer's Guide for SP06 of SAP SRM Connectivity with Ariba Network
Operation and Troubleshooting
CUSTOMER
53
After resolving the issue, go back to the XML monitor, select the message and click the Restart button, as shown in
the following figure:
Figure 23: Restart Function in the XML Monitor
54
CUSTOMER
Buyer's Guide for SP06 of SAP SRM Connectivity with Ariba Network
Operation and Troubleshooting
Refresh the monitor and check the status of the message again. The error status is changed to successful status
(marked by a checked flag), as shown in the following figure:
Figure 24: Successful Status of a cXML Message in the Monitor
If the message contains data that you cannot process, you have the following options:
● Recurring issue
You can permanently influence the data mapping and forward the data to the applications by implementing
the pre-processing inbound BAdI. For more information, see chapter SAP SRM-Specific Customizing for
Connecting SAP Business Suite [page 23].
● One-time issue
If the issues is caused by incorrect data that you have received from the supplier, you can ask the supplier to
correct the issue and resend the message. The failed cXML message in your inbound queue has to be
cancelled manually; you can cancel the message by clicking Cancel Processing of Messages with Errors in the
XML Monitor.
Buyer's Guide for SP06 of SAP SRM Connectivity with Ariba Network
Operation and Troubleshooting
CUSTOMER
55
Figure 25: XML Monitor: Cancel Processing of Messages with Errors
56
CUSTOMER
Buyer's Guide for SP06 of SAP SRM Connectivity with Ariba Network
Operation and Troubleshooting
5
Appendix
5.1
Configuration of SOA Manager
As a prerequisite, you have added Ariba's security certificate to SAP SRM and set up the security settings. For
more information, see chapter SAP Business Suite System Acting as a Client [page 30].
Note
The configuration of Web services is required only for direct connectivity.
5.1.1 Define Inbound Services
In Customizing for Integration with Other SAP Components under
SAP Business Suite Integration Component for
Ariba Framework Settings Direct Connectivity Settings Manage and Test Enterprise Services , double-click
this node and a new browser window opens. You make configuration on the SOA Management screen as follows:
1. On the Business Administration (or Service Administration) tab page, choose Web Service Administration (or
Web Service Configuration).
2. Enter Service (or Service Definition) in the Search by field and CXML* in the Search Pattern field, then
choose Go.
The system displays the following inbound services:
○ CXMLCONFIRMATIONREQUEST_IN
○ CXMLSYNCHRONOUSOUTBOUNDADAPTER
Note
The inbound service CXMLSYNCHRONOUSOUTBOUNDADAPTER receives cXML messages from the outbound
consumers and sends the cXML messages to Ariba Network.
The inbound service CXMLCONFIRMATIONSREQUEST_IN receives cXML messages from Ariba Network
through the outbound consumer of the Polling Agent and processes these cXML messages in the SAP SRM
system.
Buyer's Guide for SP06 of SAP SRM Connectivity with Ariba Network
Appendix
CUSTOMER
57
Configuration of the Inbound Service
CXMLSYNCHRONOUSOUTBOUNDADAPTER
Proceed as follows:
1. Choose CXMLSYNCHRONOUSOUTBOUNDADAPTER and choose Apply Selection.
2. Navigate to the Configurations tab page and choose Create Service.The SOA Management dialog box appears.
3. Enter the required values, and choose Apply Settings. The following table contains an example of a set of
values you can enter:
Table 5:
New Service Name
Description
New Binding Name
SYNC_OUTB_ADAPTER
Synchronous Outbound Consumer
SYNC_OUTB_ADAPTER
4. In the Configuration of Web Service 'SYNC_OUTB_ADAPTER': Endpoint 'SYNC_OUTB_ADAPTER' group box,
navigate to the Transport settings tab page and choose Local System Call in the Make Local Call field.
5. Navigate to the Provider Security tab page of the group box and select the User ID/Password checkbox for the
HTTP Authentication method.
6. Save your configuration.
The system displays a successful message such as Binding 'SYNC_OUTB_ADAPTER' activated in Service
'SYNC_OUTB_ADAPTER'. Alternatively, check the error messages and other messages at the top of the
screen.
Note
You will need to know the location of your newly defined inbound services to define the ports of the
outbound consumers later on. Before you leave this transaction, note down this destination address. We
recommend you also do this for the other inbound services.
To note down the location information, continue with the following steps:
7. In the Details of Service Definition: CXMLSYNCHRONOUSOUTBOUNDADAPTER group box and on the
Overview tab page, click the link Open WSDL document for selected binding or service. The system displays a
new window.
8. Scroll down to the last line that starts with the text soap:address location= and copy this link to a
separate document, for example, a Microsoft Word or Excel document. You need this link later on when
defining outbound consumers. The following is an example of a link: http://abc1234.wdf.sap.corp:
12345/sap/bc/srt/xip/sap/cxmlsynchronousoutboundadapter/002/sync_outb_adapter/sync_outb_adapter
Taking the above link as an example, you can divide the link into the following parts:
○ Computer name: abc1234.wdf.sap.corp
○ Port number: 12345
○ SICF path: /sap/bc/srt/xip/sap/cxmlsynchronousoutboundadapter/002/
sync_outb_adapter/sync_outb_adapter
Note
Double-check the correctness of this part of the URL in transaction SICF by navigating through the
default host services.
58
CUSTOMER
Buyer's Guide for SP06 of SAP SRM Connectivity with Ariba Network
Appendix
Result: You have defined the first inbound service CXMLSYNCHRONOUSOUTBOUNDADAPTER.
Repeat all of the above steps for the service CXMLCONFIRMATIONREQUEST_IN.
We recommend that you use the service definition to name the services you create. For example, you can use a
name such as CONF_REQ_IN. Note down the names you use, as you need so specify them when configuring the
Polling Agent later on.
Note
Refresh the screen after carrying out the described activities.
5.1.2 Define Outbound Consumers
Start again from the Web Service Administration screen. On the Search tab page, enter Consumer Proxy in the
Search by field and co_arbfnd* in the Search Pattern field, then choose Go.
The system displays the following outbound consumers:
● CO_ARBFND_PRX_GPDQ_OUT
● CO_ARBFND_PRX_OADP_OUT
● CO_ARBFND_PRX_ORDR_OUT
There are three types of outbound consumers:
● Consumers communicating directly with Ariba Network
The outbound consumer CO_ARBFND_PRX_GPDQ_OUT is for the Polling Agent. This consumer fetches cXML
messages from Ariba Network synchronously.
The outbound consumer CO_ARBFND_PRX_OADP_OUT is for the synchronous outbound adapter. This
consumer sends cXML messages to Ariba Network.
● Consumers getting data from SAP SRM and sending it to the synchronous outbound adapter
The outbound consumer CO_ARBFND_PRX_ORDR_OUT transfers purchase order data from SAP SRM to Ariba
Network.
● Consumers sending data from the Polling Agent to inbound services
The adapter CO_ARBFND_PRX_PCAS_OUT is part of the Polling Agent and provides data to the following
inbound services that send data to SAP SRM:
○ CXMLCONFIRMATIONREQUEST_IN
Buyer's Guide for SP06 of SAP SRM Connectivity with Ariba Network
Appendix
CUSTOMER
59
The following figure shows an overview of the data communication:
Figure 26: Data Communication
Configuration of the Outbound Consumer CO_ARBFND_PRX_ORDR_OUT
Proceed as follows:
1. Choose the outbound consumer CO_ARBFND_PRX_ORDR_OUT and choose Apply Selection.
2. On the Configurations tab page, choose Create Logical Port.
The SOA Management dialog box appears.
3. In the General Configuration Settings group box, select the Manual configuration radio button and select the
Logical Port is Default checkbox.
4. Fill the required fields and choose Apply Settings. The following table contains an example of values that you
can enter:
Table 6:
60
Logical Port Name
Description
SYNCH_ADAPTER_IN
Outbound Order Request
CUSTOMER
Buyer's Guide for SP06 of SAP SRM Connectivity with Ariba Network
Appendix
5. Navigate to the Transport settings tab page and fill the required fields. Note that the data is taken from the
inbound service CXMLSYNCHRONOUSOUTBOUNDADAPTER that you have configured in chapter Define Inbound
Services (Type Services). The following table contains a set of values you can enter:
Table 7:
URL Access Path
<Enter URL Access Path for the
CXMLSYNCHRONOUSOUTBOUNDADAPTER service>
URL Protocol Information
HTTP
Computer Name of Access URL
<Enter Computer Name of Access URL for the
CXMLSYNCHRONOUSOUTBOUNDADAPTER service>
Port Number of Access URL
<Enter Port Number of Access URL for the
CXMLSYNCHRONOUSOUTBOUNDADAPTER service>
Make Local Call
Local System Call
Compress Response
True
6. Navigate to the Consumer Security tab page, and select the User ID/Password checkbox. Save your
configuration. The system displays a successful message such as Logical Port SYNCH_ADAPTER_IN
successfully activated. Alternatively, check the error messages and other messages at the top of the screen.
You can use the same name for the port.
Note
If the system displays an error message at the top of the screen, we recommend that you close the screen,
reopen it, and repeat the steps.
Configuration of the Outbound Consumer CO_ARBFND_PRX_PCAS_OUT
As mentioned above, this consumer sends data from the Polling Agent to several inbound services. Therefore, you
must define a corresponding number of logical ports as follows:
1. Choose the outbound consumer CO_ARBFND_PRX_PCAS_OUT and choose Apply Selection.
2. Navigate to the Configurations tab page and choose Create Logical Port.
The SOA Management dialog box appears.
3. Choose Manual configuration as the configuration type, and deselect the Logical Port is Default checkbox.
4. Fill the required fields and choose Apply Setting. The following table contains an example of values you can
enter:
Table 8:
Logical Port Name
Description
OUT_POLLCLNT_ORDCONF
Order Confirmation
Buyer's Guide for SP06 of SAP SRM Connectivity with Ariba Network
Appendix
CUSTOMER
61
5. Navigate to the Transport settings tab page, and check or fill the required fields. Note that the data is taken
from the inbound service CXMLCONFIRMATIONREQUEST_IN that you have configured in chapter Define
Inbound Services (Type Services). The following table contains a set of values you can check or enter:
Table 9:
URL Access Path
<Enter URL Access Path for the
CXMLCONFIRMATIONREQUEST_IN service>
URL Protocol Information
HTTP
Computer Name of Access URL
<Enter Computer Name of Access URL for the
CXMLCONFIRMATIONREQUEST_IN service>
Port Number of Access URL
<Enter Port Number of Access URL for the
CXMLCONFIRMATIONREQUEST_IN service
Make Local Call
Local System Call
Compress Response
True
6. On the Consumer Security tab page, select the User ID/Password checkbox.
7. Save your configuration. The system displays a successful message such as Logical Port
'OUT_POLLCLNT_CONFIRM' successfully activated. Alternatively, check the error messages and other
messages at the top of the screen.
Note that the required data on the Transport settings tab page is taken from the corresponding inbound service
CXMLINVOICEDETAILREQUEST_IN that you have configured in chapter Define Inbound Services (Type Services).
Note
Note down the names of the logical ports. You will need them later on when you specify the settings for the
Polling Agent in the Customizing activity Define Settings for Polling Agent. For more information, see
Customizing for Integration with Other SAP Components under
for Ariba
Framework Settings
Direct Connectivity Settings
SAP Business Suite Integration Component
Define Settings for Polling Agent .
Configuration of the Outbound Consumer CO_ARBFND_PRX_GPDQ_OUT
Proceed as follows:
1. Choose the outbound consumer CO_ARBFND_PRX_GPDQ_OUT and choose Apply Selection.
2. Navigate to the Configurations tab page and choose Create Logical Port.
The SOA Management dialog box appears.
3. Choose Manual Configuration as the configuration type and select the Logical Port is Default checkbox.
62
CUSTOMER
Buyer's Guide for SP06 of SAP SRM Connectivity with Ariba Network
Appendix
4. Fill the required fields and choose Apply Settings. The following table contains an example of the values you
can enter:
Table 10:
Logical Port Name
Description
ARIBA_GATEWAY
ARIBA GATEWAY Polling Agent
5. On the Transport settings tab page, check or fill the fields. The following table contains a set of values you can
check or enter:
Table 11:
URL Access Path
/ANSapGateway.aw/ad/cxml
URL Protocol Information
HTTPS
Computer Name of Access URL
service.ariba.com
Port Number of Access URL
443
Name of Proxy Host
<Enter the name of your Proxy Host>
Port Number of Proxy Host
<Enter the Port Number of your Proxy Host>
Make Local Call
No Call in Local System
Compress Response
False
Note
You will receive the URL information from Ariba.
6. On the Consumer Security tab page, select the User ID/Password checkbox.
7. Save your configuration. The system displays a successful message such as Logical Port 'ARIBA_GATEWAY'
successfully activated. Alternatively, check the error messages and other messages at the top of the screen.
Repeat the steps above to configure the settings for the outbound consumer CO_ARBFND_PRX_OADP_OUT.
Note
You can test the ping Web service for every consumer proxy. To perform the test, click the Ping Web Service icon
on the Configurations tab page in the Details page of each outbound consumer proxy. If successful, the system
displays a successful message such as Web service ping successful for LP 'OUT_STATUS_UPD_REQU', proxy
'CO_ARBFND_PRX_STAT_OUT'.
You can now find your generated Web services in your SAP SRM system in the Maintain Services tool (transaction
SICF). Make sure the services are active; activate them, if necessary. To find the services, double-click the
default_host node, choose
sap
bc
srt
Buyer's Guide for SP06 of SAP SRM Connectivity with Ariba Network
Appendix
xip
sap .
CUSTOMER
63
5.2
Extrinsic Elements (Extensibility)
Extensibility in the communication with Ariba Network is enabled by extrinsic elements in cXML messages. For
more information, see the cXML User's guide that is available at http://cxml.org .
Ariba Network Integration 1.0 for SAP Business Suite supports enhancements for all types of outgoing messages
with additional fields (extrinsics), as well as the processing of extrinsics in all types of incoming messages.
5.2.1 Extrinsics in Outbound cXML Messages
To enhance a cXML message that you send to Ariba Network you have to add it in the outbound message mapping.
To do this, use the enhancement spot ARBSRM_OUTBOUND with the BAdI Definition ARBSRM_OUTBOUND_MAPPING.
This BAdI is available in Customizing for SAP Business Suite Integration Component for Ariba under
Application-Specific Settings
SAP SRM Integration Component for Ariba
Business Add-Ins (BAdIs)
BAdI:
Outbound Mapping .
To enhance the OrderRequest message type, you can use method MAP_BUS2201_TO_ORDR_OUT. See the
Customizing documentation for further information.
For the OrderRequest message, a sample BAdI implementation is available.
5.2.2 Extrinsics in Inbound cXML messages
A cXML message that comes in from Ariba Network can hold additional data that you would like to process and
store in SAP SRM. Therefore you must enhance the inbound message mapping. To do this, use the enhancement
spot ARBSRM_INBOUND with the BAdI Definition ARBSRM_INBOUND_MAPPING. This BAdI is available in
Customizing for SAP Business Suite Integration Component for Ariba under
SRM Integration Component for Ariba
Business Add-Ins (BAdIs)
Application-Specific Settings
SAP
BAdI: Inbound Mapping .
To enhance the ConfirmationRequest message type, you can use methods MAP_CONF_TO_BUS2209_IN_PRE and
MAP_CONF_TO_BUS2209_IN_POST. See the Customizing documentation for further information.
5.3
End Points
The end points in Ariba Network manage and control the flow of data from Ariba Network to the various systems
that are connected. An end point on Ariba Network acts as a document routing placeholder that ensures that
documents from Ariba Network are sent to the intended target system. You can create end points on Ariba
Network according to your business requirements.
64
CUSTOMER
Buyer's Guide for SP06 of SAP SRM Connectivity with Ariba Network
Appendix
Example Scenarios
● Scenario 1
In your system landscape, you have an SAP ERP system and an SAP SRM system and that are both integrated
with Ariba Network. In such a scenario, you create two end points, one for SAP ERP and the other for SAP
SRM. Based on the routing rules defined on Ariba Network, this allows Ariba Network to send the invoices to
the correct system.
● Scenario 2 (see image below)
In your system landscape, you have two SAP ERP systems and an SAP SRM system that are integrated with
Ariba Network. In such a scenario, you create two end points for the SAP ERP systems and the other for SAP
SRM. When integrating the extended classic scenario of SAP SRM, the system ID that you send in outbound
cXML messages from SAP SRM must be the ID of the SAP ERP system to which you want to replicate the SAP
SRM purchase order. This is required to ensure that Ariba Network sends follow-on documents such as
shipping notifications and invoices to the correct system.
Figure 27: Routing in Ariba Network for Supporting A Multiple-System Landscape
5.3.1 Customizing Settings for End Points
You have received one or several IDs, known as Ariba Network IDs (ANID). You use either a password (shared
secret) or a client certificate with each ANID. Each credential represents a unique entity on Ariba Network, that is,
your appearance to your business partners on the network. Maintain this information in Customizing for SAP
Buyer's Guide for SP06 of SAP SRM Connectivity with Ariba Network
Appendix
CUSTOMER
65
Business Suite Integration Component for Ariba under
Framework Settings
Define Credentials and End Points
for Ariba Network . Proceed as follows:
1. Enter the ANID in the Ariba Network ID column.
2. If you use end points, do not enter the shared secret right away. (In step 4, you will have to specify a shared
secret for each end point.) Use one of the following options:
○ If you want to use end points only for authentication, select Enable end points for authentication.
○ If you use direct connectivity, that is, you integrate with Ariba Network without a middleware, you use end
points also to poll messages. In this case, select Enable end points for authentication and polling. As a
result, the end point is available in the Customizing activity Define Settings for Polling Agent and is used for
polling cXML messages from Ariba Network.
3. Select the above specified ANID, and double click End points for Ariba Network in the left hand pane.
4. Maintain the required data for each end point on the screen End points for Ariba Network: Overview.
The SAP-internal key can be freely defined; it is used to reference the Ariba end point ID in the SAP system.
66
CUSTOMER
Buyer's Guide for SP06 of SAP SRM Connectivity with Ariba Network
Appendix
Important Disclaimers and Legal Information
Coding Samples
Any software coding and/or code lines / strings ("Code") included in this documentation are only examples and are not intended to be used in a productive system
environment. The Code is only intended to better explain and visualize the syntax and phrasing rules of certain coding. SAP does not warrant the correctness and
completeness of the Code given herein, and SAP shall not be liable for errors or damages caused by the usage of the Code, unless damages were caused by SAP
intentionally or by SAP's gross negligence.
Gender-Neutral Language
As far as possible, SAP documentation is gender neutral. Depending on the context, the reader is addressed directly with "you", or a gender-neutral noun (such as "sales
person" or "working days") is used. If when referring to members of both sexes, however, the third-person singular cannot be avoided or a gender-neutral noun does not
exist, SAP reserves the right to use the masculine form of the noun and pronoun. This is to ensure that the documentation remains comprehensible.
Internet Hyperlinks
The SAP documentation may contain hyperlinks to the Internet. These hyperlinks are intended to serve as a hint about where to find related information. SAP does not
warrant the availability and correctness of this related information or the ability of this information to serve a particular purpose. SAP shall not be liable for any damages
caused by the use of related information unless damages have been caused by SAP's gross negligence or willful misconduct. All links are categorized for transparency (see:
https://help.sap.com/viewer/disclaimer).
Buyer's Guide for SP06 of SAP SRM Connectivity with Ariba Network
Important Disclaimers and Legal Information
CUSTOMER
67
go.sap.com/registration/
contact.html
© 2017 SAP SE or an SAP affiliate company. All rights reserved.
No part of this publication may be reproduced or transmitted in any
form or for any purpose without the express permission of SAP SE
or an SAP affiliate company. The information contained herein may
be changed without prior notice.
Some software products marketed by SAP SE and its distributors
contain proprietary software components of other software vendors.
National product specifications may vary.
These materials are provided by SAP SE or an SAP affiliate company
for informational purposes only, without representation or warranty
of any kind, and SAP or its affiliated companies shall not be liable for
errors or omissions with respect to the materials. The only
warranties for SAP or SAP affiliate company products and services
are those that are set forth in the express warranty statements
accompanying such products and services, if any. Nothing herein
should be construed as constituting an additional warranty.
SAP and other SAP products and services mentioned herein as well
as their respective logos are trademarks or registered trademarks of
SAP SE (or an SAP affiliate company) in Germany and other
countries. All other product and service names mentioned are the
trademarks of their respective companies.
Please see https://www.sap.com/corporate/en/legal/copyright.html
for additional trademark information and notices.