<p>about your learning experience to help us improve.</p>

You've completed

cleanFiles/bookmap_SystemSetupGuide_v2-3_en-US_learning-sap-com_lsc-prod.zip (MMCP-DROPZONE) - 2023-10-25T12:50:34.000Z

Explaining Buyer Landscape

<div id="content"><div class="parentsection"><div class="section"><p tabindex="0">This video provides a high-level overview of the buyer landscape when integrating SAP Ariba solutions with SAP ERP or SAP S/4HANA with SAP Integration Suite, managed gateway for spend management and SAP Business Network.</p><div class="kalturaVideoLessonWrapper"><div id="1_shv2338x" data-testid="video" class="kalturaVideoLessonContainer"></div></div></div></div></div>

Buyer Landscape Overview

Administering SAP Integration Suite, managed gateway for spend management and SAP Business Network

Buyer Landscape Overview.mp4

Let's look into the buyer landscape when you want to integrate SAP Ariba solutions with SAP ERP or SAP S for HANA on-premise via the SAP Ariba Cloud Integration Gateway, or CIG. In the SAP Ariba cloud environment, the CIG is tightly coupled with Ariba Network and SAP Ariba applications such as SAP Ariba Sourcing and SAP Ariba Buying and Invoicing. In the customer environment, there could be a single or multiple instances of SAP ERP or SAP S4HANA on-premise systems, and CIG enables you to integrate all your backend systems with Ariba Network and SAP Ariba Solutions that helps you to efficiently manage supplier interactions across the spend management lifecycle. CIG is the only cloud provider with true bidirectional integration into SAP ERP and SAP S for HANA on-premise that includes more than 250 integration processes and over 8,000 fields integrated to the SAP Core. As discussed in earlier lessons, CIG is built using various capabilities of SAP Cloud Platform, also referred to as SCP and SAP Cloud Platform Integration, also referred to as CPI. When customers access CIG, they will be automatically able to use the capabilities of SCP and CPI via the CIG portal. CIG add-on solution provides two deployment options for customers. The first option is Direct Connectivity. In the Direct Connectivity option, you can integrate with an on-premise backend system via SAP Cloud Platform Cloud Connector, which is also known as SAP Cloud Connector. Direct connectivity is the SAP Ariba-recommended deployment option as it takes care of the required security aspects. SAP Cloud Connector allows you to securely transfer the data between CIG and single or multiple SAP ERP or SAP S for HANA on-premise systems. In CIG add-on solution, the Cloud Connector is used only for inbound communication to the on-premise SAP system. For outbound communication, documents are directly sent from the on-premise SAP system to CIG. Here the cloud connector acts as a reverse invoke proxy between CIG and the on-premise SAP system. In the Cloud Connector, you can specify a dummy hostname and dummy port for a configured on-premise back-end system, which will be used in the CIG project. By doing this, Cloud Connector masks the identity of the on-premise backend system and avoids exposing the information on physical hosts to the cloud world CIG. Using a unique combination of specific values defined during sub-account configuration, the SSL tunnel is established from the Cloud Connector to CIG via reverse-invoke approach. This gives full control of the tunnel into the hands of the Cloud Connector Administrator. That means the tunnel can't be established from the cloud or from anywhere else outside the company network, and the cloud connector administrator is the one who decides when the tunnel is established or closed. The second option is mediated connectivity. In the mediated connectivity option, you can integrate with an on-premise back-end system either via SAP Process Integration, SAP PI, middleware, or SAP Cloud Platform Integration Private Tenant, CPI Private Tenant, middleware. Many customers may have an internal IT or security policy to route the inbound and the outbound communication to and from their on-premise backend system via a middleware. In this scenario, the customer can choose to deploy with the mediated connectivity option by configuring the provided pass-through software component on their middleware. SAP PI and SAP CPI Private Tenant are the only supported middleware in the standard solution. SAP PI is an on-premise middleware, however, SAP CPI Private Tenant is a cloud-based middleware. Therefore, you need to install SAP Cloud Connector to send documents from SAP CPI Private Tenant to your backend on-premise SAP system.