High- Level Specification

Functional Overview

Purchase orders are automatically generated in the Ariba Guided Buying when a requisition is fully approved.  The purchase order is exported to S/4HANA as soon as it is fully approved in Ariba Guided Buying.

Ariba Guided Buying supports purchase order export tasks. The purchase order export feature allows exporting purchase orders from Ariba Guided Buying to S/4HANA via via SAP Integration Suite, Managed Gateway for Spend Management and SAP Business Network (formerly known as Cloud Integration Gateway) through Cloud Connector.  Exporting purchase orders, when using CIG channel occur in real-time.  This interface is triggered when the Purchase Orders are created and fully approved in Ariba Guided Buying and are ready to be sent to S/4HANA.

End-to-end integration via CIG is achieved using Cloud Connector.  The format of the messages that are sent through CIG via Cloud Connector from Ariba Guided Buying to S/4HANA and the format of the expected responses from S/4HANA are defined in WSDL files (Web Service Description Language).

CIG receives and consumes the PO data. CIG maps the web service XML to the required RFC structure by S/4HANA and CIG sends the PO data to S/4HANA through Cloud Connector.

S/4HANA then returns either a success or error message (including error details) to Ariba Guided Buying via CIG.

Scope and Objectives

This document describes S/4HANA System inbound interface for sending purchase order information from Ariba Guided Buying to S/4HANA System. Purchase Order from Ariba Guided Buying will be exported to S/4HANA System via SAP Integration Suite, Managed Gateway for Spend Management and SAP Business Network (formerly known as Cloud Integration Gateway). 

The following Purchase Order web service integration events (and the corresponding document types) will be used to export PO creation, changes and cancellation:

• Export Purchase Orders Asynchronously

Document Type in CIG - PurchaseOrderExportRequest 

• Export Change Purchase Orders Asynchronously

Document Type in CIG - PurchaseChangeOrderExportRequest 

• Export Cancel Purchase Orders Asynchronously

Document Type in CIG - PurchaseCancelOrderExportRequest 

There will be no scheduled task of data transmission as data is transferred in real-time.  Each submission of transactional data from Ariba Buying to the S/4HANA System requires a response from the receiving S/4HANA system that the data was successfully received and imported, or details about the error that occurred during the import.

Process Flow Diagram

PO Create

PO Change

PO Cancel

Assumptions

• Ariba Guided Buying is utilized for integration of Purchase Orders with S/4HANA System.
• Ariba source object and S/4HANA System target field mappings, including custom fields, will be updated based on mapping requirements in S/4HANA System

Dependencies

• All configurations should already be implemented before the interface is deployed.
• Ariba Buying packages have been successfully installed and configured in S/4HANA System.
• The connection information for Web-Services based integration have been successfully configured in Ariba Buying.
• Purchase Order parameters have been configured in Ariba Guided Buying.
• Master data loaded in Ariba Guided Buying is synchronized with S/4HANA System.

Security, Integrity and Controls

The following are the Security and Authorization considerations for this interface:

• Define a Web Services Security certificate and/or the shared secret key to use to secure the End Point connection.
• Access to interface parameters in Ariba Guided Buying are being addressed by Ariba standard security controls. Only authorized person with Ariba administrator’s role can access/ change interface parameters.
• Web service security configuration allows secure communications protocol provides a means for applying security to Web services.

Configuration Requirements

Ariba Configuration

Ariba Web Services enables exchange of data between Ariba Guided Buying and other systems, such as S/4HANA System, for real-time data integration.

Ariba Web Services provide integration tasks that send and receive SOAP messages for web services. An integration task requires an end point for the logical communication channel used by the web service. An end point consists of the URL and authentication information that controls access to the end point. There are two types of end points: inbound and outbound. Inbound end points are used when the task is initiated by the S/4HANA system. Outbound end points are used when the task is initiated by the Ariba Guided Buying.

Here, the Web Services channel provides real-time integration of Ariba Buying with S/4HANA system using SAP Integration Suite, Managed Gateway for Spend Management and SAP Business Network.

• Configure the purchase order integration, change purchase order integration, and close purchase order integration between SAP Ariba Procurement solutions and SAP ERP or SAP S/4HANA.

• Enable the following asynchronous integration events in SAP Ariba Procurement solutions:

• Enable the following parameters in Ariba
  • Application.Procure.PullAckFromERP
  • Application.Purchasing.RenumberReqLineItemSplits
  • POApplication.Procure.UseCancelOrderIntegration
• Attachments:

  • For purchase orders and change purchase orders, enable Application.Procure.AllowAttachmentToERP and Application.Ordering.AllowOrderAttachmentToERP parameters.

  • To control the file formats that can be attached to purchase orders in Ariba, use the parameter Application.Approvable.AllowedAttachmentExtensions. File formats that are not specified cannot be used as attachments. This parameter is useful for restricting file formats (such as EXE files) that might violate company security policies.

The following table lists operations for the integration tasks and end point types needed:

CIG Configuration

Project setup is required in CIG to cover product type Ariba Procurement. One project is required per system ID of the backend S/4 system. With respect to Purchase Order Create and Change, there's additional setting in the Cross Reference → Parameter section where the set of parameters have to be maintained

Project must be published and set to "in testing" in order for transactions to be used

CIG Custom Routing

 Project definition in CIG configuration is repeated for every backend S/4 system [ at the moment there's a plan for Global, US and Chine S/4 backends ]. In CIG → My Configurations → Custom Routings there's a definition for 

CIG Addon Configuration

Configuration for CIG addon is consolidated in one place and should be completed in the logical order of the menu items. In the S/4 instance, navigate to SPRO → SAP Reference IMG →SAP Customizing Implementation Guide → Integration with Other SAP Components → Managed Gateway for Spend&Network for Buyer

Logical order of the menu is as following :

• Global Settings:
  • Maintain Certificates - SSL certificate of CIG to be added under SSL client SSL Client (Anonymous). Certificate can be downloaded from CIG → Resources → CIG Certificates. Official documentation covering this section can be found here
  • Create RFC Destination - new RFC destination to be added under HTTP Connections to External Server. Official documentation can be found here. Values are as following:

    • Parameter Name	Value
      Technical Settings.Target System Settings.Host	http://testacig.ariba.com/
      Technical Settings.Target System Settings.Path Prefix	/cxf/receiveERPMD
      Login And Security User	P007937
      Login And Security Password	<confidential>

  • Create Port Definition - new Port to be added under XML HTTP. In the port there's a reference to the previously created RFC Destination. Official documentation can be found here
  • Create Logical System - there is no client specific information in here, only the entry is needed. Official documentation can be found here
  • Send SAP Information to Managed Gateway for Spend&Network 
  • Synchronize SAP Information with Managed Gateway for Spend&Network - enter same credentials as with RFC destination. Choose Test or Prod environment, depending on the instance. Choose EU Data Center and SAP Ariba Procurement Solutions. Execute. This task creates information about the S/4 backend in the CIG itself. Successful execution can be verified in the CIG, by clicking on your user avatar in the right top corner and clicking on Basic Data section. S/4 System ID should be in the list. Official documentation can be found here
  • Support Attachments
    • Maintain Parameter for Line Level Attachments - Define DMS_STORAGE_CATEGORY as SAP-SYSTEM and DOCUMENT_TYPE as DRW
  • Map the Variant and Partition for SAP Ariba solutions - define new entry for BUY Ariba Procurement Integration with values Variant = VREALM_53334 [ to be retrieved from Ariba Guided Buying ] and Partition = PREALM_53334 [ to be retrieved from Ariba Guided Buying ]
• SAP Ariba Procurement Integration
  • General Settings
    • Configure the connections to send messages - enter the same credentials as in RFC destination definition. Choose EU Data Center and choose following transactions
      • • ERP Response to Procurement
        • Purchase Order Export
        • Purchase Order Change Export
        • Purchase Order Cancel Export
      • Documentation can be found here. Upon the successful execution, web services for inbound transactions can be found in SOAMANAGER
        • BUYERPURCHASEORDCREATEREQUEST
        • BUYERPURCHASEORDCHANGEREQUEST
        • BUYERPURCHASEORDERCANCELREQ

Special Requirements

Not Applicable

Design Rationale

Not Applicable

Data Structure

Source Structure and Target Structure

Standard mappings are a subject to change and are not linked in this documentation, latest excel sheet can be downloaded from CIG → Resources → Implementation Guides → Mapping Specs → Ariba Buyer

• CreatePurchaseOrder (Soap to Proxy) 
• ChangePurchaseOrder (Soap to Proxy)
• CancelPurchaseOrder (Soap to Proxy)

Each of the mapping contain basic field mapping from SOAP message into RPC structure with a basic logic explained in the pseudo code

Processing Logic

Processing within Source

Web Service is triggered based on the state of the source document. Once Purchase Requisition is fully approved, Purchase Order is created and the SOAP message is triggered to the backend system. Message is triggered in the asynchronous way, meaning the web service doesn't wait for the reply from S/4, but consider success if reply 200 is received from CIG. 

At this moment, no customisations are agreed on and extension to the standard WSDL data structure for any of the Purchase Order flows is not needed

Processing within Middleware

At this moment, standard transformation as referenced above is in place. In a case of any custom field is needed, custom field will be mapped in the CIG to the predefined custom field structure in the SAP

Processing within Target

Each flow triggers an Ariba specific BAPI, which serves as a wrapper over SAP standard BAPI. On top of it, there's BAdl that can be used to handle customisations if needed. It's called before the data structure is passed to the standard SAP BAPI for processing. 

Posted PO can be viewed in me23n transaction

Interface Dependency

Not Applicable

Interface Constraints

Not Applicable

Delivery Requirements

Not Applicable

Delta or Full Load Requirements

Not Applicable

Interface Alert & Monitoring

Interface Reporting

30 days of history per transactional document type can be retrieved from CIG. It's not possible to pull a consolidated report, just the details of the particular transaction

Language Requirements

Not Applicable

User Interface Requirements

Not Applicable

Volumetrics

Performance Consideration

There are no specific performance requirements or considerations related to this interface.

Error Handling

The S/4HANA System integration provides reliable data exchange between Ariba Guided Buying through CIG. However, in some cases, the integration event on the Ariba Guided Buying cannot recover automatically and must report the error to the appropriate administrator. When an error occurs, the integration event on the Ariba Buying System does the following:

• Recover automatically
• Report the error and wait for an administrator to take action

An administrator can monitor the errors using the transaction code, SRT_MONI.

Testing

How to Test

Test Conditions and Expected Results

Test Considerations/Dependencies

Other Information

Development Details

Package

Other Development Objects

Appendix

See also

Change log

Workflow history