In Cloud Integration Gateway the mappings for all cXML “QuoteMessage” payloads are delivered only in the ARBCI2 add-on.

ARBCI2 therefore must be present for

• QuoteMessageContractServices (service quote against a contract) and

• QuoteMessageOrder (quote against an RFQ/Purchase Order).

“ContractRequest” and “ContractRequestServices” are processed through the mappings contained in ARBCI1, so they do not require ARBCI2.

C. ContractRequestServices – Uses ARBCI1 mappings; no objects in ARBCI2 for this document type.

D. Contract Request – Like C, processed by ARBCI1; ARBCI2 not referenced for contract-request flows.

1. SAP SE

“SAP Ariba Cloud Integration Gateway – Implementation Guide for SAP ERP” (rev. 2023-05)

§7.4 “Installing Software Components”

Table “Document Types Supported by Each ARBCI Add-On”

lines for QuoteMessageOrder & QuoteMessageContractServices → ARBCI2; ContractRequest → ARBCI1.

2. SAP Note 2483967 (v4

2022-09-12)

“Overview of ARBCI1 and ARBCI2 content”

section “Document-to-component matrix” – lists QuoteMessage under ARBCI2 only.

3. Jaiswal

S. “Integrating SAP Ariba with SAP ERP and SAP S/4HANA” (SAP Press

2021)

ch. 10.2

pp. 284-286 – confirms QuoteMessage flows require ARBCI2 while contract requests use ARBCI1.

In SAP Ariba Cloud Integration Gateway the “Interface Setup” program (/ARBA/IFSET) lists the technical interfaces that can be activated in ERP for each Ariba process.

For the demand-aggregation scenario, purchase requisitions must be grouped and sent to Ariba Buying through the dedicated interface AGGREGATEREQUISITION, which appears in the Interface Setup screen with the description “Aggregate Requisition”. Activating this interface enables ERP to bundle multiple purchase-requisition lines into a single aggregate file that Ariba Buying can process for demand aggregation. No other interface provides this specific functionality.

A. Aggregate MRO – used for aggregating MRO reservation data, not purchase-requisition demand aggregation.

B. Purchase Requisition – transmits individual requisitions; does not support aggregation logic.

C. Demand Aggregation – such a named interface is not present in Interface Setup; aggregation is handled through “Aggregate Requisition”.

1. SAP Help Portal

“SAP Ariba Cloud Integration Gateway for SAP ERP – Implementation Guide” (release 2402)

Section 7.5 “Demand Aggregation of Purchase Requisitions”

Step 1

p. 109: “Activate interface AGGREGATEREQUISITION (Aggregate Requisition) in /ARBA/IFSET.”

2. SAP Note 2689076

Attachment “Interface Setup Program – Interface Descriptions”

row “AGGREGATEREQUISITION”.

3. SAP Ariba Integration Toolkit for SAP NetWeaver 2023

ch. 4.3 “Interface Definitions”

table entry “AGGREGATEREQUISITION – Groups purchase-requisition demand for Ariba Buying”.

According to SAP’s “Migration from Ariba Network Adapter for SAP NetWeaver to SAP Ariba Cloud Integration Gateway – Guide,” only adapter releases 8.0 (any support-pack) and 9.0 (SP0 or higher) are recognized by the migration utilities delivered with CIG. Customers on earlier adapter releases (6.0 or 7.0) must first upgrade the adapter before they can run the migration program; therefore, these earlier releases are not listed as supported starting points.

A. 6.0 – Guide states versions ≤ 7.0 must be upgraded before migration; tooling does not accept 6.0 directly.

C. 7.0 – Same restriction as 6.0; direct migration from 7.0 is not supported.

1. SAP Ariba Cloud Integration Gateway – Migration Guide

“Supported Ariba Network Adapter Releases

” pp. 6-7

SAP Help Portal (ARBCIG-MIG-ERP

Oct 2023).

2. SAP Note 2553316

“Ariba Network Adapter to CIG Migration – Supported Versions

” ver. 7

§2

lines 25-33

SAP ONE Support Launchpad.

3. SAP Help Portal > SAP Ariba Cloud Integration Gateway for SAP ERP > Preparing for Migration

para. “Prerequisite adapter release

” 2023 edition.

For integrating catalog upload requests from SAP Ariba via the Cloud Integration Gateway (CIG), specific parameters must be maintained in the /ARBA/TVARV table within the SAP ERP system. The parameter BUYERCATCLASSTYPE is used to define the class type for the catalog (e.g., 026 for material/service class). BUYERCATCLASS specifies the class name under which catalog items are grouped. BUYERCATINTCHARNO defines the internal characteristic number for the catalog. These parameters are crucial for the correct classification and processing of incoming catalog data from SAP Ariba solutions.

B. BUYERCATGROUP: This is not a standard parameter defined in the /ARBA/TVARV table for configuring CIG-mediated catalog integration.

E. BUYERCATTYPE: This parameter is invalid. The correct parameter to specify the class type for the catalog is BUYERCATCLASSTYPE.

1. SAP Help Portal

SAP Ariba Cloud Integration Gateway Documentation: "How to configure catalog integration with SAP Ariba solutions". This guide details the necessary configuration steps in SAP ERP. In the section for maintaining parameters in the /ARBA/TVARV table

it explicitly lists BUYERCATCLASSTYPE

BUYERCATCLASS

and BUYERCATINTCHARNO as required parameters for the catalog upload request process. The parameters BUYERCATGROUP and BUYERCATTYPE are not mentioned. (Accessed for SAP Ariba Cloud Integration Gateway

May 2024 release).

The authorization object ARBCIGPRG is specifically designed to control the execution of special programs and reports within the SAP Ariba Cloud Integration Gateway (CIG) add-on. This object is a critical component of the security roles delivered with CIG, such as /ARBCIG/ADMIN or /ARBCIG/MONITOR. Administrators assign this authorization to users who need to run CIG-related reports for transaction monitoring, master data extraction, or other administrative tasks, ensuring that only authorized personnel can execute these potentially sensitive programs.

B. ARBCIGRFC: This authorization object is used to control access to Remote Function Call (RFC) destinations, not for executing local reports or programs.

C. ARBCIGSPR: This object governs authorization for accessing and modifying CIG-specific customizing activities within the SAP Project Reference Object (SPRO) or Implementation Guide (IMG).

D. ARBCIGCLS: This authorization object is used to restrict access to specific ABAP classes and their methods within the Ariba CIG add-on namespace.

1. SAP Help Portal

SAP Ariba Cloud Integration Gateway Configuration Guide: "Roles and Authorizations for SAP Ariba Cloud Integration Gateway". This document lists the authorization objects delivered with the CIG add-on. It explicitly states:

ARBCIGPRG: Authorization object for special programs.

ARBCIGRFC: Authorization object for RFC.

ARBCIGSPR: Authorization object for SPRO.

ARBCIGCLS: Authorization object for CIG class.

(This information is consistently found in the configuration guides for various releases of the CIG add-on).

2. SAP Help Portal

SAP Ariba Cloud Integration Gateway Overview Guide: The "Security Information" section discusses the importance of assigning appropriate roles and authorizations

which include the objects for specific tasks like program execution (ARBCIGPRG) and configuration (ARBCIGSPR).