SAP Ariba Cloud Integration Gateway: Features and Functions — Lesson 1: CIG Architecture, Integration Projects, SAP Add-On, Connectivity, Endpoints, and Security

Learning Objectives

• Explain the SAP structures, data, settings, roles, and dependencies governing CIG architecture and project setup.
• Perform and validate SAP add-on, connectivity, and security using reviewable system evidence.
• Evaluate the condition where a procurement document fails in transit because mapping values, cross references, endpoint configuration, and backend master data do not align and select proportionate corrective action.

Detailed Topics

• CIG Architecture applied to the course scenario, expected SAP behavior, dependencies, and evidence.
• Integration Projects applied to the course scenario, expected SAP behavior, dependencies, and evidence.
• SAP Add-On applied to the course scenario, expected SAP behavior, dependencies, and evidence.
• Connectivity applied to the course scenario, expected SAP behavior, dependencies, and evidence.
• Endpoints applied to the course scenario, expected SAP behavior, dependencies, and evidence.
• and Security applied to the course scenario, expected SAP behavior, dependencies, and evidence.

Instructor Demonstration

The instructor traces an integration team connecting SAP ERP or SAP S/4HANA with Ariba applications through controlled, traceable transaction flows. The walkthrough connects navigation, configuration or process logic, system messages, and evidence captured in the CIG integration design, mapping, test, and operations dossier. It also tests the exception where a procurement document fails in transit because mapping values, cross references, endpoint configuration, and backend master data do not align.

Hands-On Exercise

Complete a controlled SAP exercise covering CIG Architecture, Integration Projects, SAP Add-On, Connectivity, Endpoints, and Security and preserve the verified result in the CIG integration design, mapping, test, and operations dossier.

1. Confirm scope, prerequisites, master data, roles, dependencies, and acceptance criteria.
2. Execute the workflow while recording settings, transactions, outputs, and system messages.
3. Test normal behavior, one boundary condition, and the stated exception.
4. Document corrections, evidence, ownership, retest criteria, and handover actions.

Scenario Analysis

• Identify which object, rule, setting, or process step most strongly influences CIG architecture and project setup.
• Compare two defensible responses and explain business, technical, control, and support trade-offs.
• Determine how the CIG integration design, mapping, test, and operations dossier should be approved, retained, retested, and updated.

Troubleshooting Guidance

Start where expected SAP behavior first differs from the observed result. Check master data, configuration sequence, authorization, integration, status, and transaction evidence separately. Treat “a procurement document fails in transit because mapping values, cross references, endpoint configuration, and backend master data do not align” as a hypothesis until system settings, logs, documents, and outcomes confirm the cause.

Validation Checklist

• Required SAP structures, master data, roles, settings, and dependencies are present.
• The CIG integration design, mapping, test, and operations dossier connects each conclusion to objective, reviewable evidence.
• Normal processing, the boundary condition, integration behavior, and exception were tested.
• Corrections, ownership, retest criteria, documentation, and operational handover are complete.

Lesson Outcome

Learners can apply CIG Architecture, Integration Projects, SAP Add-On, Connectivity, Endpoints, and Security, explain the resulting SAP behavior, and defend the outcome through the CIG integration design, mapping, test, and operations dossier.