Scribd
Upload
2 views

SAP ARIBA INTEGRATION AND EXTENSION_

The document outlines the integration of SAP Ariba with various systems, detailing the differences between master and transactional data, as well as integration methods and connection protocols. It highlights best practices for data transfer, including the use of batch loads for master data and real-time loads for transactional data. Additionally, it introduces the Cloud Integration Gateway (CIG) and its architecture, supported systems, and requirements for effective integration.

Uploaded by

sanjaybohra1496
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
2 views

SAP ARIBA INTEGRATION AND EXTENSION_

The document outlines the integration of SAP Ariba with various systems, detailing the differences between master and transactional data, as well as integration methods and connection protocols. It highlights best practices for data transfer, including the use of batch loads for master data and real-time loads for transactional data. Additionally, it introduces the Cloud Integration Gateway (CIG) and its architecture, supported systems, and requirements for effective integration.

Uploaded by

sanjaybohra1496
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
You are on page 1/ 4

SAP ARIBA INTEGRATION: SAP ARIBA INTEGRATION AND EXTENSION

Unit 1: Integration Basic


1. Integration: Transfer of data from one system to another system. SAP Ariba
can be integrated with SAP S/4 HANA / SAP ERP, Non-SAP solutions, Other SAP
Applications.
2. Master vs Transactional Data:
Master Data are core operational business data which is shared across an
organisations. Ex- Supplier data, user data, inventory, etc.
Transactional Data are electronic business documents.
Ex- Invoices, PO, Receipts, etc.
3. Integration Method vs Connection Protocol:
An Integration Method is a standard formatting language or “computer
language” used to structure business data in business documents like POs and
Invoices. Ex: cXML, EDI etc.

A Connection Protocol is the mechanism used to communicate the


transactions– the WAY transactions are sent from one system to another.
Data Transfer Options:
Batch File Options Web Services SAP Ariba Cloud Integration
Gateway (CIG)

For Non-SAP ERP For SAP and Non-SAP ERP For SAP Integration
Integration Integration

.csv over https cXML over https

Send in a batch Real-time Real-time

Best Integration Practices


a) Integrate master data with batch load.
b) Integrate transactional data with real-time load.
c) UI or Data Dictionary to verify the data, for both custom and
standard data.
d) Create custom Flex fields when tabular data is required within SAP
Ariba.
Consider deploying CIG to makSAPe integration more efficient and less time
consuming.
Unit 2: Introduction to the cloud integration gateway.
1. Cloud Integration Gateway VS Traditional Integration
2. SAP Ariba CIG Architecture.
3.

SAP Ariba CIG: Supported System


Following Versions of SAP ERP and SAP S/4 HANA
 EHP0-EHP8 for SAP ERP 6.0
 SAP s/4 HANA on-premises 1610-2020
Requirement to use SAP Ariba CIG by buyer
 Access of SAP Marketplace to download SAP Ariba CIG
 Ariba Network buyer account or ‘Procure-to-pay’ or ‘relam’
4. Both Inbound and Outbound transactions are supported by SAP Ariba
CIG.

Unit 3: SAP Strategic Sourcing Integration (Often called Strategic


procurement)
Product line
 SAP Ariba Sourcing.
 SAP Ariba Contract
 SAP Ariba lifecycle and performance

1. Master Data Integration


SAP ERP Buyer integrated with SAP Ariba Sourcing or Contract
can import the following Master data:
A). Organisational data
B). Cross/application Configuration data.
C). Material Master Data.

You might also like