To make life easier for Ariba customers, SAP recommends use of “SAP Cloud Integration Gateway”

as a future integration strategy. 

Benefit?

1. Simple
2. Speed
3. Intuitive – UI based

Figure: Understand Ariba Integration Architecture with CIG

1. SAP Cloud Platform (SCP)

2. SAP Cloud Platform Integration (CPI) service
3. SAP Connectivity Service
4. SAP Cloud Connector
5. CIG add-on for SAP ERP/ S/4 HANA
6. SAP Cloud Integration Gateway (CIG)

The idea behind SCP was to make integration easier between on-cloud solutions and on-premise
solutions.

Key purpose of SCP as in the diagram below are:

 Build New Cloud Apps

 Extend On-Premise & Cloud Apps
 Integrate everything

Developers can develop extensions on SAP Cloud Platform and then connect these new extension
apps to the core solution via API available. Thus, the Cloud platform have to have API and as big
picture the integration service to enable the integration with other solutions.
Figure: Use of SAP Cloud Platform for developing Ariba extension applications

AN integrations can be further divided between buy-side or sell-side integrations, or between

integrations applicable to buyers and those applicable to suppliers.

The integrations that pertain to the buyer are document-centric while those pertaining to seller side
are more EDI document integration.
SAP menu path
SPRO • Integration with other mySAP Components· Ariba Cloud Integration · Global Settings (for
the technical configuration)
SPRO · Integration with other mySAP Components · Ariba Cloud Integration · Ariba Network
Integration (for the scenario configuration),

Under Global Settings:

1: Maintain your SSL certificates

2: Maintain your remote function call (RFC) connections for SAP Ariba, via Transaction SM59

3: You'll define the XML HTTP ports for the SAP Ariba CIG, which represent the ports in the ERP
system for transmitting iDocs, as shown in Figure
4: Follow the menu path

SPRO • Integration with other mySAP Components · Ariba Cloud Integration · Global Settings (for
the technical configuration)

SPRO • Integration with other mySAP Components • Ariba Cloud Integration · Ariba Network
Integration • Global Settings · Create Port Definition.

You can also define a receiver port by selecting Configure Receiver Port instead of Create Port
Definition.

5: Then, you'll synchronize the versions and system data between SAP ERP and SAP Ariba.

Follow
6: Selecting the setups you wish to migrate (Sourcing, Procurement, or Both) and entering your user
name and password, you can trigger the job, as shown in Figure 10.94. You can view the status of
this job in Transaction SLGl. You only need run this job once, during the initial configuration.
8: The next step is to map your variant and partition to differentiate between SAP Ariba Sourcing data
and SAP Ariba Buying data by following the menu path
SPRO • Integration with other mySAP Components • Ariba Cloud Integration • Global Settings (for the
technical configu ration)
SPRO • Integration with other mySAP Components • Ariba Cloud Integration • Ariba Network
Integration • Global Settings • Map Variant and Partition to Procurement and Sourcing.

These variants are maintained in a table, shown in Figure 10.95, to avoid confusion in transmitted
messages.