user guide | public

40
User Guide | PUBLIC Cloud Integration Automation Service User Guide © 2021 SAP SE or an SAP affiliate company. All rights reserved. THE BEST RUN

Upload: others

Post on 09-Dec-2021

4 views

Category:

Documents


0 download

TRANSCRIPT

Page 1: User Guide | PUBLIC

User Guide | PUBLIC

Cloud Integration Automation Service User Guide

© 2

021 S

AP S

E or

an

SAP affi

liate

com

pany

. All r

ight

s re

serv

ed.

THE BEST RUN

Page 2: User Guide | PUBLIC

Content

1 What Is Cloud Integration Automation Service?. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .41.1 Advantages. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41.2 Important Disclaimers. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41.3 Limitations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51.4 Supported Scenarios. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5

2 Cloud Integration Automation Service. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

3 Initial Setup. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .113.1 Pre-Requisites. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 113.2 Subscription to Cloud Integration Automation Service. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11

Subscription to Standard Plan. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11Create Instance in OAuth2 Service Plan. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12

4 Administration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 144.1 Assigning Roles to the Users. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .144.2 Planning a CIAS Scenario. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .15

Using CIAS Application. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15Using Maintenance Planner. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .16

4.3 Monitoring Scenario Implementation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17Add or Change Destination. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19

4.4 My Inbox. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20Working with Instruction Tasks. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21Summary. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28

5 Security. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 305.1 Security Architecture. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 305.2 Service and Application Plans. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .315.3 Security Restrictions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 315.4 Identity Provider and Identity Management. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 325.5 Roles and Authorizations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .325.6 Destinations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .335.7 Data Protection and Privacy. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .33

Audit Logging. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34Sensitive Data. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34

5.8 Unsubscribe. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .34

6 Monitoring and Troubleshooting. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .35

2 PUBLICCloud Integration Automation Service User Guide

Content

Page 3: User Guide | PUBLIC

7 Glossary. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36

Cloud Integration Automation Service User GuideContent PUBLIC 3

Page 4: User Guide | PUBLIC

1 What Is Cloud Integration Automation Service?

Overview

Cloud Integration Automation service provides you a guided workflow to integrate SAP cloud solutions to On-premise and other SAP Cloud solutions. The guided workflow contains instructions for manual and automated tasks to enable an easy and quick integration configuration setup.

NoteThe previous CIAS infrastructure on the NEO environment is available until the end of July, so you can download or save the workflows that have already been created.

For any backup queries, please create a support ticket in component BC-INS-CIT-RT. Also, we recommend creating new workflows in the Cloud Foundry environment to apply current changes in the workflows.

1.1 Advantages

● User and task centric approach in integration configuration scenarios, using guided workflows.● Planning capabilities to plan an integration scenario● The guided workflow covers an integration setup for a specific scenario.● Instructions are provided in a task format and can be assigned to a dedicated role.● Instructions are provided based on your landscape and the chosen integration scenario.● Automated technical configuration steps on selected targets are available and enabled.● Monitoring capabilities for the integration scenario guided workflow.

1.2 Important Disclaimers

● User ID, Email-Id, SAP Business Technology Platform subaccount/subdomain name, and landscape-related data (System ID, Host) will be persisted into CIAS database tables to enable guided workflow execution.

● It is expected that you follow the instructions as described in the guided workflows and acknowledge the same upon completion.

● For automation APIs, Destinations to the respective system needs to be created in the SAP Business Technology Platform (BTP) subaccount.

4 PUBLICCloud Integration Automation Service User Guide

What Is Cloud Integration Automation Service?

Page 5: User Guide | PUBLIC

1.3 Limitations

● The number of active workflows supported for a BTP subaccount/subdomain is currently limited to 20.● Explicit deletion of User ID, Email-Id or transactional data as a self-service from CIAS consumer

subaccount is not offered in the current release of CIAS. Hence, you need to raise an explicit support request to the component BC-INS-CIT-RT to remove the complete transactional data (status should be completed or terminated) including User IDs or Email IDs.The ticket must contain the User ID or Email ID that needs to be removed, as well as the SAP Business Technology Platform consumer subaccount/subdomain name.

● Deleting a transaction in Maintenance Planner does not automatically delete its associated data in CIAS, and needs to be manually deleted by SAP.Refer SAP Note 2608492

● CIAS currently does not perform checks on connecting inter-landscape tenants. Hence, please check explicitly if the landscape chosen for integration is valid.

● The following browsers are supported on Microsoft Windows PCs:

Browser Versions

Mozilla Firefox Extended Support Release (ESR) and latest e-version

Google Chrome Latest version

1.4 Supported Scenarios

The following integration scenarios are currently supported:

Intelligent Enterprise - Lead to Cash - Contact to Lead● Onboard Company: Integration Commerce Cloud with S/4 Cloud (S4HC)● Capture Interaction: Integrate SAP Commerce Cloud with SAP Marketing Cloud● SAP Customer Data Cloud Integration with SAP S/4HANA Cloud

Intelligent Enterprise - Lead to Cash - Lead to Opportunity● SAP Marketing Cloud Integration with SAP Cloud for Customer (1J9)

Intelligent Enterprise - Lead to Cash - Master Data● MDM Business Partner Integration with Sales Cloud (MDM SC)● MDM Business Partner Integration with Subscription Billing (MDM SB)● MDM Business Partner Integration with Marketing Cloud (MDM MC)● MDI Business Partner Integration with S/4HANA Cloud (MDI BP)● SAP Master Data Service for Business Partners Integration with SAP Commerce Cloud● MDM Business Partner Integration with Field Service Management (MDM FSM)

Cloud Integration Automation Service User GuideWhat Is Cloud Integration Automation Service? PUBLIC 5

Page 6: User Guide | PUBLIC

● MDI Business Partner Integration with SAP Cloud for Customer(MDI C4C)● SAP Master Data Integration with SAP Customer Data Cloud● SAP Configure Price Quote with SAP Master Data Service for Business Partners● SAP Customer Data Cloud Integration with SAP Commerce Cloud (B2B Scenario)● SAP Customer Data Cloud Integration with SAP Commerce Cloud (B2C Scenario)

Intelligent Enterprise - Lead to Cash - Order to Cash● Orchestrate Fulfilment Process: Order Management Data Replication to SAP Marketing Cloud (1UG)● Integration Commerce Cloud with S/4 Cloud (CC2S4)● Deliver Services: Integration FSM with SAP S/4 HANA Cloud (FSM)● Subscription Management with Sales Billing (BP SB)● Orchestrate Fulfillment Process: Integration Commerce Cloud with Subscription Billing (SB)

Intelligent Enterprise - Lead to Cash - Opportunity to Quote● SAP Marketing Cloud Integration with SAP Cloud for Customer (1J9)● Integration SAP Cloud for Customer with SAP S/4HANA Cloud (C4C S4)

Intelligent Enterprise - Lead to Cash - Quote to Order● Automation of Order-to-Invoice with Ariba Network (4A1)

Intelligent Enterprise - Recruit to Retire - Hire to Retire● Payroll Processing with SAP SuccessFactors Employee Central Payroll (1NL)● Workforce Management with SAP Cloud Platform Services (4AF)● Financial Data Harmonization with SAP SuccessFactors Employee Central (4AJ)● Integration with SAP SuccessFactors Employee Central Payroll (15O)● Integrating master data between EC and MDI● Payroll Processing with SAP ERP HCM Payroll (3UP)● On-Premise: Setting up Payroll Processing with SAP SuccessFactors Employee Central Payroll (1NL) 2020● On-Premise: Integration Setup for EC to EC Payroll (15O) 2020● On-Premise: Workforce Management with SAP Business Technology Platform

Intelligent Enterprise - Recruit to Retire - Travel to Reimburse● Payroll Processing with SAP SuccessFactors Employee Central Payroll (1NL)● Workforce Management with SAP Cloud Platform Services (4AF)● Financial Data Harmonization with SAP SuccessFactors Employee Central (4AJ)● Integration with SAP SuccessFactors Employee Central Payroll (15O)● SAP S/4HANA-Concur-Payroll Integration

Intelligent Enterprise - Recruit to Retire - External Workforce● Workforce Management with SAP Cloud Platform Services (4AF)● Financial Master Data for SAP SuccessFactors Employee Central (4AJ)● External Workforce Procurement via SAP Fieldglass (22K)

Intelligent Enterprise - Source to Pay - Contract● Contract for Central Procurement with SAP Ariba Contracts (4B0)

6 PUBLICCloud Integration Automation Service User Guide

What Is Cloud Integration Automation Service?

Page 7: User Guide | PUBLIC

● Contract Management with SAP Ariba Contracts (4AZ)● On-Premise: Contract Management with SAP Ariba Contracts (4AZ) 2020

Intelligent Enterprise - Source to Pay - Guided Buying● Guided Buying for Central Procurement with SAP Ariba Buying (3EN)● Guided Buying Capability with SAP Ariba Buying (2NV)● On-Premise: Automation of Order-to-Invoice with Ariba Network (4A1) 2020

Intelligent Enterprise - Source to Pay - Sourcing● Sourcing for Central Procurement with SAP Ariba Sourcing (4QN)● Sourcing with SAP Ariba Sourcing (4BL)● On-Premise: Sourcing with SAP Ariba Sourcing (4BL) 2020

Intelligent Enterprise - Source to Pay - Supplier Collaboration/Network● Automation of Source-to-Pay with Ariba Network (42K) 2102● Services Procurement with Ariba Network and SAP Fieldglass (4R2)● Subcontracting with Ariba Network (5I2)● SAP Central Procurement Quote Automation with SAP Ariba Network (5JT)● On-Premise: Automation of Source-to-Pay with Ariba Network (42K) 2020

SAP Business Technology Platform ABAP Environment● Configuring the ABAP Environment to use the custom code Migration app● SAP BTP, ABAP Environment, and SAP S/4HANA Cloud: Integration

SAP Cloud Connector● Configuration of SAP Cloud Connector with Principal Propagation

SAP Integrated Business Planning● Integrated Business Planning - Integrating Data to OBP Using SDI ABAP Adaptor

SAP Launchpad Service Integration● SAP Launchpad Service Integration with SAP S/4HANA● SAP Launchpad Service Integration with SAP S/4HANA Cloud

SAP S/4HANA Cloud Integration Scenarios● Automated Provisioning via SAP Cloud Identity Access Governance (3AB)● Automation of Order-to-Invoice with Ariba Network (4A1)● Automation of Purchase-to-Pay with Ariba Network (42K)● B2B Order Fulfillment with SAP Commerce Cloud (2TY)● Sourcing for Central Procurement w/ SAP Ariba Sourcing (4QN )● Contingent Workforce Procurement via SAP Fieldglass (22K)● Continuous Control Monitoring with SAP Process Control (2OH)● Contract for Central Procurement with SAP Ariba Contracts (4B0)● Contract Management with SAP Ariba Contracts (4AZ)● Credit Agency Integration (1RY)

Cloud Integration Automation Service User GuideWhat Is Cloud Integration Automation Service? PUBLIC 7

Page 8: User Guide | PUBLIC

● Customer Payments (1S0)● Customs Management with SAP Global Trade Services (2U1)● Digital Payments - Sales (1Z1)● Digital Payments (1S2)● External Billing (1Z6)● Financial Master Data for SAP SuccessFactors Employee Central (4AJ)● Guided Buying Capability with SAP Ariba Buying (2NV)● Guided Buying for Central Procurement with SAP Ariba Buying (3EN)● Import Connection setup with SAP Analytics Cloud (1YB)● Integration of Payment Advice with Buyers and Suppliers (2MB)● Integration of Procurement with External Suppliers (2EJ)● Integration of Sales with External Buyers (2EL)● Key Risk Indicator Monitoring with SAP Risk Management (2U2)● Logistics with Third-Party Warehouse Management (1ZQ)● Opportunity-to-Order with SAP Cloud for Customer (1VP)● Payroll Processing with SAP SuccessFactors Employee Central Payroll (1NL)● Restricted Party Screening with SAP Watch List Screening (1WE)● Integration to SAP S/4HANA Cloud for Enterprise Contract Assembly (2OQ)● Sourcing with SAP Ariba Sourcing (4BL)● Payroll Processing with SAP ERP HCM Payroll (3UP)● Automation of Central Procurement Quotes with Ariba Network (5JT)● Core HR with SAP SuccessFactors Employee Central (JB1)● Travel Expense Processing with SAP Concur Expense Professional (1M1)● Workforce Management with SAP Cloud Platform Services (4AF)● SAP S/4HANA for Enterprise Contract Management (1XV)● Services Procurement with Ariba Network and SAP Fieldglass (4R2)● Digital Payments Foundation (53V)● Subcontracting with Ariba Network (5I2)● Subscription Management with Sales Billing (57Z)

SAP S/4HANA On-Premise Integration● Configuration for Connectivity S/4HANA to SAP Digital manufacturing Cloud● Asset Intelligence Network - S/4HANA On-Premise Integration

SAP Success Factors Employee Central with SAP S/4HANA On-Premise Integration● Replicating Cost Centers from SAP S/4HANA On-Premise to SAP SuccessFactors Employee Central● Migrating Employee and Organizational Data from SAP S/4HANA On-Premise to SAP SuccessFactors

Employee Central● Replicating Employee and Organizational Data from SAP SuccessFactors Employee Central to SAP S/

4HANA On Premise (1911)

8 PUBLICCloud Integration Automation Service User Guide

What Is Cloud Integration Automation Service?

Page 9: User Guide | PUBLIC

2 Cloud Integration Automation Service

2021

Tech­nical Com­po­nent

Capa­bility

Envi­ron­ment Title Description Action Type

Avail­able as of

Cloud Inte­gration Auto­mation Serv­ice

Inte­gration Suite

Cloud Foun­dry

Sce­nario Tasks

You can now view the list of the selected integration scenario task in the scenario planning UI. The list is displayed in the tab Scenario Task.

Changed

2021-10-01

Cloud Inte­gration Auto­mation Serv­ice

Inte­gration Suite

Cloud Foun­dry

Sub­scrip­tion

CIAS is providing Standard and OAuth2 plans. To learn more, see Subscription to Cloud Integration Automation Service [page 11].

Note1. You can now create scenarios only in Cloud Foundry.

So, you are recommended to save or download all existing workflows. To get support for backup, create an incident in BC-INS-CIT-RT component.

2. You would not be able to access Neo environment af­ter end of July, 2021.

Changed

2021-08-04

Cloud Inte­gration Auto­mation Serv­ice

Inte­gration Suite

Cloud Foun­dry

Neo

Availa­bility of Cloud Inte­gra­tion Auto­mat­ion serv­ice on Cloud Foun­dry.

You can now subscribe to Cloud Integration Automation serv­ice with a Cloud Foundry subaccount.

For more information on CIAS subscription, see Subscription to Standard Plan.

Changed

2021-05-01

Cloud Integration Automation Service User GuideCloud Integration Automation Service PUBLIC 9

Page 10: User Guide | PUBLIC

Tech­nical Com­po­nent

Capa­bility

Envi­ron­ment Title Description Action Type

Avail­able as of

Cloud Inte­gration Auto­mation Serv­ice

Inte­gration Suite

Cloud Foun­dry

Neo

Sce­nario plan­ning in Cloud Inte­gra­tion Auto­mat­ion serv­ice ap­plica­tion

You can now plan a scenario integration from within the CIAS application. For more information, see Using CIAS Applica­tion.

Changed

2021-05-01

Cloud Inte­gration Auto­mation Serv­ice

Inte­gration Suite

Cloud Foun­dry

Neo

Desti­nation crea­tion in BTP subac­count

You can now create a destination in BTP from a CIAS inbox. For more information, see Destination Creation.

Changed

2021-05-01

10 PUBLICCloud Integration Automation Service User Guide

Cloud Integration Automation Service

Page 11: User Guide | PUBLIC

3 Initial Setup

3.1 Pre-Requisites

For an effortless integration, ensure the following pre-requisites:

● An SAP Business Technology Platform subaccount in one of the following CIAS supported regions:○ Europe: Germany - Frankfurt AWS ( EU10)○ United States: US East - VA AWS ( US10)○ Asia Pacific: Australia – Sydney AWS ( AP10)

● System instances of licensed SAP products that are in scope of this service.

3.2 Subscription to Cloud Integration Automation Service

You can subscribe to Cloud Integration Automation Service from the service marketplace of SAP Business Technology Platform cockpit. See View and Manage Services from the Service Marketplace for more details.

Cloud Integration Automation Service provides two plans:

● Standard - This is an application plan that provides capabilities to work with Cloud Integration Automation Service UI application. User can plan an integration scenario, monitor and work on the tasks w.r.t integration scenario. Use this plan to subscribe to the application. To learn more, see Subscription to Standard Plan [page 11].

● OAuth2 - This is a service plan that provides access to the APIs of Cloud Integration Automation Service. Using these APIs, user can fetch, create, update the integration scenarios and its tasks. For few scenarios like ABAP automation, this plan instance is a pre-requisite. To learn more, see Create Instance in OAuth2 Service Plan [page 12].

3.2.1 Subscription to Standard Plan

To subscribe to a standard plan, following are the required steps:

1. Login into your global account in the cockpit.2. Create a subaccount in the CIAS supported regions.3. In the left-side menu, choose Services → Service Marketplace. All the resources you are entitled to consume

in the subaccount appears as tiles.4. In the filters area, select the All Types filter, and from the dropdown menu, select Cloud Integration

Automation Service. You can use other filters to narrow down your search by the environments for which the CIAS is available, capabilities, and its status.Active status means you are currently subscribed to that application.

Cloud Integration Automation Service User GuideInitial Setup PUBLIC 11

Page 12: User Guide | PUBLIC

5. Choose the Cloud Integration Automation Service tile to see the Overview page. Here, you can find more information about the application including all the available plans.

TipYou can also create a new subscription without opening its overview by selecting the three dots in the top-right corner of the tile.

6. Choose Create.7. In the displayed window, select the standard plan of type subscription and choose Create. A confirmation

pop-up appears with the link to the Instances and Subscriptions page, where you can follow the status of your new subscription under the Subscriptions table.The Go to Application link becomes available once the subscription is activated. Choose the link to launch the Cloud Integration Automation Service(CIAS) and obtain its URL. To find the link, either select the subscription row to open more details about the subscription or click on the (Go to Application) icon in the Application column.

CautionTo remove an application, select the three dots at the end of the subscription row, and from the menu, select Delete. All data related to the Cloud Integration Automation Service (CIAS) will be deleted in the respective subaccount.

To configure your user access to the application, refer Assigning Roles to the Users [page 14] to assign the roles to the users.

3.2.2 Create Instance in OAuth2 Service Plan

To create an instance in OAuth2 service plan for CIAS:

1. Enable Cloud Foundry - Ensure that you have enabled the Cloud Foundry. Else, choose your subaccount → Enable Cloud Foundry under Cloud Foundry Environment

2. Create Space - After Cloud Foundry is enabled, create space by choosing Create Space under the Cloud Foundry Environment tab or choose Spaces from left-side menu

3. Create Instance -○ Choose Service Marketplace → Cloud Integration Automation Service → Create○ In the pop-up, choose plan OAuth2○ Choose Cloud Foundry as Runtime Environment

NoteCloud Foundry in the dropdown would be witnessed only if Cloud Foundry is enabled

○ Provide an appropriate Instance Name and choose Create○ Choose View Instance from the pop-up or choose Instances and Subscriptions from the left-side menu

4. Create Service Key - Choose Create under Service Keys and give an appropriate name in the Service Key Name field○ Choose create○ Choose the options icon against the appropriate service key

12 PUBLICCloud Integration Automation Service User Guide

Initial Setup

Page 13: User Guide | PUBLIC

○ Choose view to get the credential details such as client ID and client secret5. Using the fetched client id and client secret, you can generate an OAuth JWT token and connect to CIAS. To

learn more, see creating service keys.

Cloud Integration Automation Service User GuideInitial Setup PUBLIC 13

Page 14: User Guide | PUBLIC

4 Administration

4.1 Assigning Roles to the Users

CIAS application requires certain roles to be fulfilled at the subscription level. This section describes them in detail and the steps to add a user to a group from the BTP subaccount.

Pre-RequisitesYour subaccount is subscribed to CIAS in the Cloud Foundry environment. To learn more, see Subscription to Standard Plan [page 11].

RolesThe following table describes the various roles, the role collection that they are assigned to by default, and their privileges:

Pre-Defined Roles

Roles Assigned to Role Collection Privileges

Integration Moni­tor

CIASIntegration Monitor ● Read-only access to Scenario Execution Monitoring application.● Work on assigned tasks.

Integration Expert CIASIntegrationExpert ● Access to My Inbox application.● Work on assigned tasks.

Integration Ad­ministrator

CIASIntegrationAdministra­tor

● Access to My Inbox application.● Access to Plan for Integration● Access to Scenario Execution Monitoring● Review the workflow execution plan like confirm landscape, role as­

signment, and scope selection.● Monitor the workflow execution and terminate a scenario● Plan a new integration scenario

Assign users to groupsAs part of the subscription process, three role collections are created by default. You can add one or more users to these role collections to assign the roles associated with them:

● CIASIntegrationExpert● CIASIntegration Monitor● CIASIntegrationAdministrator

Procedure1. From the left navigation menu, choose Security → Role Collections.2. Choose an appropriate role → Edit → Navigate to Users tab and add user using their email ID or user ID

which is used to login to the subaccount.

14 PUBLICCloud Integration Automation Service User Guide

Administration

Page 15: User Guide | PUBLIC

3. Else, Trust configuration → add a user using SAP IDP or custom IDP or IAS tenant.

Note1. The users you assign to the role collections are managed by the identity provider currently configured

for the subaccount which runs CIAS. In case you configure the subaccount to use a different identity provider afterward, the My Inbox and Scenario Execution Overview applications will not be accessible anymore unless the assigned users are also managed by the new identity provider.

2. CIAS currently supports any SAML assertion Name ID attribute. Once CIAS is active with this Name ID attribute, if identity provider uses a different Name ID attribute, the My Inbox and Scenario Execution Overview applications will not be accessible.

3. To avoid issues resulting from the conditions described above, we strongly recommend that you subscribe to CIAS in a separate subaccount which is configured to use an identity provider with the SAML assertion Name ID attribute.

4.2 Planning a CIAS Scenario

4.2.1 Using CIAS Application

Integration scenario planning can be done in CIAS using the Plan for Integration tile in the CIAS application.

Procedure

1. Launch CIAS application.

NoteThe CIAS application link is available in the Instances and Subscription tab of the BTP subaccount where CIAS is subscribed. Choose the link to launch the Cloud Integration Automation Service(CIAS) and obtain its URL. To find the link, either select the subscription row to open more details about the subscription or click on the (Go to Application) icon in the Application column.

2. Choose Plan for Integration tile3. Select one of the available solutions from the Solutions tab.4. Select one of the available scenarios in the solution.

Alternatively, you can also add a scenario in the search box. This will restrict the number of solutions where the scenario is available.

5. From the available options, select a scenario option.6. Select the systems for integration.

The systems and tenants are listed according to the customer number to which the BTP global account is assigned to where CIAS is subscribed.In case a system or tenant is not visible, proceed with the next steps. You can enter the landscape data manually. To enter the data, navigate to the Confirm System Components task in the My Inbox application of Cloud Integration Automation Service.

7. Invoke the workflow.

Cloud Integration Automation Service User GuideAdministration PUBLIC 15

Page 16: User Guide | PUBLIC

NoteThe selected systems may belong to different landscapes. For such instances, you are prompted to confirm with the integration between such systems. If yes, click Proceed. Click Cancel to choose different systems.

To invoke the workflow, enter the following:1. The subaccount where CIAS workflow will be generated defaults to subaccount where CIAS is

currently accessed.2. In the input field for SAP Business Technology Platform Account Workflow Users: provide the list of

users who receives the first task. Ensure that these users can access the BTP subaccount.3. Provide the CIAS Transaction Name, which will be referred to in the CIAS My Inbox and Scenario

Execution Monitoring applications.

8. Upon successful workflow generation, a link is generated to view the task in the My Inbox application.

4.2.2 Using Maintenance Planner

Context

An S-User assigned to the customer ID for access to Maintenance Planner. For more information, see the Maintenance Planner User Guide.

Procedure

1. Launch Maintenance Planner.

https://maintenanceplanner.cfapps.eu10.hana.ondemand.com2. Click the Plan for Cloud Integration Scenario tile.3. Select one of the available solutions from the Solutions tab..

Alternatively, you can enter the cloud integration solution in the search.4. Select one of the available scenarios.5. From the available options, select a scenario option.6. Select the systems for integration.

The systems and tenants are listed according to the customer number based on the S-User.

In case a system or tenant is not visible, proceed with the next steps. You can enter the landscape data manually. To enter the data, navigate to the Confirm System Components task in the My Inbox application of Cloud Integration Automation Service.

You can also search for systems using the Tenant URL.

16 PUBLICCloud Integration Automation Service User Guide

Administration

Page 17: User Guide | PUBLIC

7. Invoke the workflow.

NoteThe selected systems may belong to different landscapes. For such instances, you are prompted to confirm with the integration between such systems. If yes, click Proceed. Click Cancel to choose different systems.

To invoke the workflow, enter the following:

a. In the input field for SAP Business Technology Platform Region: select the data center region in which CIAS is subscribed.

b. In the input field for SAP Business Technology Platform Account Technical Name: provide a valid BTP Account name in which CIAS solution is subscribed.

If not subscribed, follow the Subscription to Cloud Integration Automation Service [page 11] section.c. In the input field for SAP Business Technology Platform Account Workflow Users: provide the list of

users who receives the first task.

Ensure that these users can access the BTP subaccount.d. Provide the CIAS Transaction Name, which will be referred to the CIAS My Inbox and Scenario

Execution Monitoring applications.8. Upon successful workflow generation, a link is generated.9. Click the link to launch CIAS.

4.3 Monitoring Scenario Implementation

This section describes the steps to monitor the scenario implementation.

NoteYou need to have Integration Administrator or Integration Monitoring privileges to be able to view this application.

1. Select the Scenario Execution Monitoring app.This app provides a status overview of the active workflow instances. You can view a history of all workflows by filtering it as Running, Completed, or Canceled.

You can also view additional information on the scenario with the following tabs. The tabs visible to you vary based on the scenario:

● Task Details

Cloud Integration Automation Service User GuideAdministration PUBLIC 17

Page 18: User Guide | PUBLIC

If a task status is set to Not Applicable, click the link to view the additional details reasoning this status.

● Targets● Roles and Users● Scope● Support Information● Parameters (visible when you choose the task to view additional details).

You can terminate the scenario execution by clicking the Terminate Execution button. Once this is done, you will no longer see the scenario in CIAS applications.

NoteIf a task is assigned to more than one user and one of them has claimed the task, then a padlock icon is displayed next to this user indicating the same. This task cannot be claimed by another user.

18 PUBLICCloud Integration Automation Service User Guide

Administration

Page 19: User Guide | PUBLIC

Comments

This tab contains the comments entered by a user assigned to the task.

Logs

You can see the execution logs for an automation task. This provides a detailed overview on the execution and the trials.

To view the logs, choose a task and open the Logs tab.

4.3.1 Add or Change Destination

Prerequisites:

You have integration administrator privileges.

At certain points during the scenario execution, you as an integration administrator can change the destination, or enter it if it has not been entered already.

1. Click the Targets tab in the Scenario Execution Monitoring application.2. Click the Edit Destination button.

Cloud Integration Automation Service User GuideAdministration PUBLIC 19

Page 20: User Guide | PUBLIC

3. Choose from the available destinations or click Create Destination if you want to create a new destination.

4. Click Save after you choose the destination.

NoteThe destination cannot be changed if it is already used in an automation task.

4.4 My Inbox

This section describes the steps to access the Inbox tile and to get started with executing tasks.

NoteYou need to have Integration Administrator or Integration Task Expert privileges to be able to view this tile.

20 PUBLICCloud Integration Automation Service User Guide

Administration

Page 21: User Guide | PUBLIC

1. To launch CIAS application:○ Navigate to SAP BTP Cockpit.○ Choose the subaccount where CIAS is subscribed.○ Choose Instance and Subscriptions on the side panel.○ Under Subscriptions, click on Go To Application icon next to Cloud Integration Automation Service.

To find the link, either select the subscription row to open more details about the subscription or click on the (Go to Application) icon in the Application column.

2. Select the My Inbox tile.

4.4.1 Working with Instruction Tasks

Tasks assigned to you will appear in the My Inbox view.

Use the Claim button to lock the task for your user.

1. The Task Instructions tab content you see in the snapshot below is demo content and will vary from the actual instruction.

2. Additional details may be visible under the relevant tabs as follows:○ Scopes – Assign or remove scope of execution from the options provided.○ Assigned To – This shows the user and role assignment.○ Support Information - Provides additional details like Maintenance Planner ID, Transaction Name,

Creation Date and so on.3. Once the task is complete, click the Task Complete button.4. Click the Refresh button on the left pane to show the next task.5. For the consecutive tasks, follow the instructions in the task and click the Task Complete button.

NoteFor tasks that are enabled for automation, offer an Execute Steps button. Clicking on it will perform the described settings automatically.

Refresh the task list and repeat the above steps till you see the summary of the scenario execution.You can monitor the scenario implementation at any time. For more details, see Monitoring Scenario Implementation [page 17]

Cloud Integration Automation Service User GuideAdministration PUBLIC 21

Page 22: User Guide | PUBLIC

4.4.1.1 Disclaimer Task

The Disclaimer Task is the first task you would see in the Inbox. Please read the SAP disclaimer and provide your consent by choosing the I Agree button.

4.4.1.2 Confirm System Components

This section describes the steps to confirm system components.

The system components are populated based on your selection during planning with Maintenance Planner.

Review the components and choose Confirm Systems button.

Assign destination to possible system components. In case of missing destinations, create a destination in the BTP subaccount and refresh the list.

NoteDestination selection is optional. In case a destination is not assigned, the respective automation is not available during task execution.

Currently you need to specify Account Name and Host for SAP Business Technology Platform Account Cockpit, which you already specified in Maintenance Planner.

For more details, see Destination Creation [page 23].

Review the components and choose Confirm System.

NoteTenant information like Name, Host cannot be changed.

22 PUBLICCloud Integration Automation Service User Guide

Administration

Page 23: User Guide | PUBLIC

Some scenarios support manually entering system properties if they are not already displayed from the management system.

In such cases, enter the properties in the text field provided, as below:

Multiple Workflow Execution Handling

If there is more than one integration setup workflow with the same system components, an execution lock is implimented. When such a situation occurs you have the following options to choose from:

● Proceed: Proceed without resolving these conflicts. You may have to resolve this manually later.● Terminate: Terminate the selected instance(s).● Terminate Current Instance● Cancel

4.4.1.3 Destination Creation

Depending on the integration scenario, tasks can be executed automatically. This requires a destination to be selected for the respective component. If you do not select a destination, the automatic execution feature will be disabled in the respective tasks.

If there is no destination available for your system, you can use the following steps to create a destination:

1. Login into your CIAS launchpad2. Choose My inbox tile3. Under Confirm System Components, expand SAP Cloud Platform Integration Tenant.4. Against assign destination, choose Create Destination link.5. In the Destination Configuration window, fill the details accordingly:

○ Name - Enter a valid name for the destination○ Description - Describe your destination○ URL - Enter the CPI host name as URL○ Authentication - Choose an appropriate authentication for destination connection. Depending upon

the authentication, provide respective details like username, password etc.○ Type - By default, the type is set as HTTP

6. Choose Save

Your destination is now created.

4.4.1.4 Role Assignment

This section describes the steps to assign one or more users to the available roles. You can assign multiple users per role with comma separated user IDs.

NoteUsers must have access to the BTP subaccount to be assigned roles in CIAS.

Cloud Integration Automation Service User GuideAdministration PUBLIC 23

Page 24: User Guide | PUBLIC

You can view the users assigned to a role in task instructions, while you are executing a task. Clicking the role name displays the role description as well as the list of users assigned to this role.

24 PUBLICCloud Integration Automation Service User Guide

Administration

Page 25: User Guide | PUBLIC

4.4.1.5 Execution Scope Selection

This section describes the steps to confirm the execution scope for a chosen scenario with the following tabs:

NoteOnce you have selected the scope, no further changes are possible.

4.4.1.6 Task Example

Manual or automation tasks appear during a scenario execution, based on your choice during the execution scope selection.

Usually automation tasks require parameters. You can also control the parameter visibility using the button to toggle between:

● View Inputs Only: to display the inputs only.● View All: to display all the parameters.

You can Click Execute Steps to trigger execution of the automated task.

Once you see the success message, click the Task Complete button.

Cloud Integration Automation Service User GuideAdministration PUBLIC 25

Page 26: User Guide | PUBLIC

In case of manual tasks, complete all the tasks on the target system, and click the Task Complete button.

Task DetailsView additional details about the topic in the Overview tab. It displays the hierarchy of tasks in a sequence of execution in an integration scenario.

NoteThe task list is not displayed for disclaimer tasks and other initialization tasks.

You can use the Expand All and Collapse All buttons to toggle the task list view, and current task in execution is indicated with an arrow.

Hover on the tasks to identify the type like concept task, user task and topic task. You can also easily switch between tasks using hyperlinks in the task descriptions wherever available.

26 PUBLICCloud Integration Automation Service User Guide

Administration

Page 27: User Guide | PUBLIC

Task Instructions

This tab contains all the instructions for the task selected.

Overview

This tab contains the task overview for the task selected.

Comments

This tab contains the comments entered by one of the users assigned to the task.

System Access

This tab contains all the systems relevant for the task selected.

Assigned To

This tab contains the list of users that the task is assigned.

Support Information

This tab contains all the support information for your assistance in case you encounter an error.

4.4.1.7 Uploading a file to CIAS

In the My Inbox application, you can upload certificate files to be reused later by systems in your landscape.

This is useful in scenarios where the same file is needed by any other tasks.

In the Task Instructions tab of the My Inbox application, click Browse, to choose and upload an SAP S/4HANA Certificate.

Cloud Integration Automation Service User GuideAdministration PUBLIC 27

Page 28: User Guide | PUBLIC

4.4.2 Summary

The execution summary screen is the last among the tasks for a scenario.

This screen indicates that you have completed all the tasks for the selected scenario. Click the Complete Execution button to mark the scenario as complete.

NoteOnce you click Complete Execution, the scenario no longer appears in the Scenario Execution Monitoring application.

28 PUBLICCloud Integration Automation Service User Guide

Administration

Page 29: User Guide | PUBLIC

4.4.2.1 Downloading the CIAS Execution Summary Report

You can download the CIAS Execution Summary Report as a PDF file to serve as reference for the future, or for auditing purposes.

You can download the report in one of the following ways:

1. From the My Inbox application:Once you have completed all the tasks for a scenario, you will see the Export to PDF button in the Execution Summary screen

2. From the Scenario Execution Overview application:You can download the current execution state of a scenario at any time by clicking the Export to PDF button.

Cloud Integration Automation Service User GuideAdministration PUBLIC 29

Page 30: User Guide | PUBLIC

5 Security

The following sections list some of the security-related information.

Security is vital for Cloud Integration Automation Service as it provides features related to integration setup between SAP products.

See also: SAP Business Technology Platform Security Guide

5.1 Security Architecture

The Cloud Integration Automation Service consists of the following components that are provisioned into the customer subaccount using the SAP Business Technology Platform cross-subaccount subscription concept:

● CIAS Runtime: The backbone framework that renders your integration tasks.● CIAS Planning: An UI application to plan an integration scenario.● CIAS Inbox: An UI application to access the tasks for an end-user.

30 PUBLICCloud Integration Automation Service User Guide

Security

Page 31: User Guide | PUBLIC

● CIAS Monitoring: An UI application to access the complete scenario implementation monitoring.● Managed System: A system to be configured during the integration scenario.● CIAS Automation Runtime: Calls configuration APIs of a managed system.

For more information, see Multitenant Applications in the SAP Business Technology Platform documentation.

Note● Access to all features of the CIAS offering requires a valid user identity in the corresponding identity

provider configured in the customer subaccount where CIAS is subscribed.● In addition, all backend service connectivity calls that can lead to data manipulation in the CIAS

runtime are protected against cross-site request forgery (XSRF).

5.2 Service and Application Plans

You can subscribe to Cloud Integration Automation Service from the service marketplace of SAP Business Technology Platform cockpit. See View and Manage Services from the Service Marketplace for more details.

Cloud Integration Automation Service provides two plans:

● Standard - This is an application plan that provides capabilities to work with Cloud Integration Automation Service UI application. User can plan an integration scenario, monitor and work on the tasks w.r.t integration scenario. Use this plan to subscribe to the application. To learn more, see Subscription to Standard Plan [page 11].

● oauth2 - This is a service plan that provides access to the APIs of Cloud Integration Automation Service. Using these APIs, user can fetch, create, update the integration scenarios and its tasks. For few scenarios like ABAP automation, this plan instance is a pre-requisite. To learn more, see Create Instance in OAuth2 Service Plan [page 12].

5.3 Security Restrictions

● The SAP Business Technology Platform subaccount name provided in Maintenance Planner to invoke CIAS must exist and must be subscribed to CIAS already.

● The user ID provided in Maintenance Planner or in CIAS planning application to invoke CIAS workflow must exist in the SAP Business Technology Platform subaccount specified during the planning.

● The number of running transactions (workflows) for a CIAS consumer SAP Cloud platform subaccount is limited to 15.

● Deleting a transaction in Maintenance Planner does not automatically delete its' associated data in CIAS and needs to be manually deleted in the CIAS.

Cloud Integration Automation Service User GuideSecurity PUBLIC 31

Page 32: User Guide | PUBLIC

5.4 Identity Provider and Identity Management

For identity management and authentication, Cloud Integration Automation Service relies on Identity Provider (IdP). Ensure that your IdP is configured in the customer subaccount that its subscriptions.

All requests handled by Cloud Integration Automation Service subscriptions are authenticated against the identity provider of the consumer subaccount. Further, for Cloud Integration Automation Service in the customer subaccount authorized against the role assignments specified.

You can interact with various features of the Cloud Integration Automation Service by being available in the respective identity provider. You can replace the default SAP Cloud Platform Identity Authentication service with your corporate identity provider.

The users used in destinations of the target systems from consumer subaccount must be authenticated and authorized by the IdP configured in the target systems.

For more information about the concepts and the necessary configuration steps in the SAP BTP subaccount, see Security Administration: Managing Authentication and Authorization in the SAP Business Technology Platform documentation.

5.5 Roles and Authorizations

To assign the necessary roles to the users, the Cloud Integration Automation Service relies on the standard functionality of SAP Business Technology Platform authorization concepts. Individual users or user groups can be assigned to CIAS consumer roles from consumer subaccounts.

To assign a user or user group to roles of CIAS, from consumer subaccount navigation to SAP BTP Cockpit → Security → Role Collection. To learn more, see Assigning Roles to Users.

CIAS subscriptions in the consumer subaccounts are restricted by the CIAS consumer roles to access specific features.

Role Privileges

Integration Administrator ● Access to My Inbox application● Access to Scenario Execution Monitoring● Access to Plan for Integration● Plan an integration scenario and generate a workflow.● Review the workflow execution plan like confirm land­

scape, role assignment, and scope selection.● Monitor the workflow execution and terminate a sce­

nario

Integration Expert ● Access to My Inbox application.● Work on assigned tasks.

32 PUBLICCloud Integration Automation Service User Guide

Security

Page 33: User Guide | PUBLIC

Role Privileges

Integration Monitoring ● Read-only access to Scenario Execution Monitoring ap­plication.

5.6 Destinations

The automation services to configure target systems make use of the destinations created in the consumer SAP Business Technology Platform subaccount to which CIAS is subscribed. SAP BTP subaccount administrator creates and manages these destinations. The destination configuration data is stored only in the consumer subaccount.

CIAS accesses these configurations while executing automation services for a restricted period.

Note1. By default, a ‘CIAS Integration Administrator’ has the authorization to create a destination( delete or

modify of destination not allowed ) in the SAP BTP subaccount where CIAS is subscribed. Creation of destination in the subaccount can be done from the System Component task in the CIAS Inbox application.

2. Configure destinations to use secure communication protocols, such as HTTPS always!3. To know more about Destinations, see Destination in the SAP Business Technology Platform

documentation.

NoteDisclaimer: Cloud Integration Automation Service uses SAP Business Technology Platform destinations to access APIs of the systems to be integrated for automation. Therefore ensure that the users executing the automation are authorized to perform the configuration on the respective systems. CIAS will instruct you to create respective destinations. Consider deleting those after the workflow has finished.

5.7 Data Protection and Privacy

● User IDs and email IDs would be stored in the CIAS provider database against the subscription of an SAP BTP consumer subaccount name.

● System and Tenants selected for an integration setup would be stored in the CIAS provider subaccount to execute the workflow.

● The logs would not store any user-related personal data.● The logs would be stored for 30 days in the CIAS provider subaccount and would be deleted after a specific

time.● Explicit deletion of a user ID or a transactional data as a self-service from CIAS consumer subaccount is

not provided, currently. Hence, you need to raise an explicit support request to the component BC-INS-

Cloud Integration Automation Service User GuideSecurity PUBLIC 33

Page 34: User Guide | PUBLIC

CIT-RT to remove the complete transactional data (status should be completed or terminated) including the user IDs.The ticket must contain the User ID that needs to be removed, as well as the SAP Business Technology Platform consumer subaccount name.

5.7.1 Audit Logging

Cloud Integration Automation Service logs security related events and user actions in the Audit Log service. You can view all audit log entries for your subaccount. For more information, see Audit Log.

Audit Log entries are deleted according to the Audit Log data retention policy. For more information, see Audit Log.

5.7.2 Sensitive Data

Cloud Integration Automation Service requires the user to enter sensitive data for automation of some of the tasks for an integration scenario. The sensitive data is stored securely in the credential store service in the CIAS provider account and is not visible to anyone.

5.8 Unsubscribe

To un-subscribe, the Cloud Integration Automation Service from an SAP BTP consumer subaccount, a user with a platform Administrator role can delete the subscription from the Instance and Subscription in SAP Business Technology Platform cockpit. This operation removes the active subscription technical linkage and all the transactional data for the subscribed subaccount. The transactional data once deleted can not be recovered again.

34 PUBLICCloud Integration Automation Service User Guide

Security

Page 35: User Guide | PUBLIC

6 Monitoring and Troubleshooting

This section describes some of the possible scenarios you may encounter and the actions to troubleshoot them.

FAQs

Where do I check CIAS service availability?

Check Service Availability in Consumer account

I have trouble with a particular scenario. How do I proceed?

Procedure-related support for a scenario can be found in the Support Information tab of Task / Monitoring application.

Destination drop-down is empty. What do I do?

● Only SAP Business Technology Platform destinations that exist, and match with the ‘Host Base URL’of the tenant are displayed in the drop-down.

● If no destination list is populated, create it manually by following the instructions in the section Destination Creation [page 23].

● Once you have created the destination, refresh the drop-down.

How do I request for additional support?

You can raise a ticket on the component BC-INS-CIT-RT to receive support from SAP.

To receive support from SAP regarding the manual task instructions, raise an incident on the component shown on the Support Information tab.

Cloud Integration Automation Service User GuideMonitoring and Troubleshooting PUBLIC 35

Page 36: User Guide | PUBLIC

7 Glossary

Term Description

Blocking A method of restricting access to data for which the primary business purpose has ended.

CIAS Cloud Integration Automation Service

Consent The action of the data subject confirming that the usage of his or her data shall be allowed for a given purpose. A con­

sent functionality allows the storage of a consent record about a specific purpose and shows if a data subject has

granted, withdrawn, or denied consent.

MP Maintenance Planner

Personal data Any information relating to an identified or identifiable natu­ral person ("data subject"). An identifiable natural person

can be identified, directly or indirectly, in particular by refer­ence to an identifier such as a name, an identification num­ber, location data, an online identifier, or to one or more fac­tors specific to the physical, physiological, genetic, mental, economic, cultural, or social identity of that natural person.

Residence period The period between the end of the business and the end of purpose (EoP) for a data set during which the data remains

in the database and can be used in case of subsequent proc­esses related to the original purpose.

At the end of the longest configured residence period, the data is blocked or deleted. The residence period is part of

the overall retention period.

Retention period The period between the end of the last business activity in­volving a specific object (for example, a business partner)

and the deletion of the corresponding data, subject to appli­cable laws. The retention period is a combination of the resi­

dence period and the blocking period.

36 PUBLICCloud Integration Automation Service User Guide

Glossary

Page 37: User Guide | PUBLIC

Term Description

Sensitive personal data A category of personal data that usually includes the follow­ing type of information:

● Special categories of personal data, such as data reveal­ing racial or ethnic origin, political opinions, religious or philosophical beliefs, trade union membership, genetic

data, biometric.● Personal data subject to professional secrecy.● Personal data relating to criminal or administrative of­

fenses.● Personal data concerning insurances and bank or credit

card accounts.

BTP Business Technology Platform

Cloud Integration Automation Service User GuideGlossary PUBLIC 37

Page 38: User Guide | PUBLIC

Important Disclaimers and Legal Information

HyperlinksSome links are classified by an icon and/or a mouseover text. These links provide additional information.About the icons:

● Links with the icon : You are entering a Web site that is not hosted by SAP. By using such links, you agree (unless expressly stated otherwise in your agreements with SAP) to this:

● The content of the linked-to site is not SAP documentation. You may not infer any product claims against SAP based on this information.● SAP does not agree or disagree with the content on the linked-to site, nor does SAP warrant the availability and correctness. SAP shall not be liable for any

damages caused by the use of such content unless damages have been caused by SAP's gross negligence or willful misconduct.

● Links with the icon : You are leaving the documentation for that particular SAP product or service and are entering a SAP-hosted Web site. By using such links, you agree that (unless expressly stated otherwise in your agreements with SAP) you may not infer any product claims against SAP based on this information.

Videos Hosted on External PlatformsSome videos may point to third-party video hosting platforms. SAP cannot guarantee the future availability of videos stored on these platforms. Furthermore, any advertisements or other content hosted on these platforms (for example, suggested videos or by navigating to other videos hosted on the same site), are not within the control or responsibility of SAP.

Beta and Other Experimental FeaturesExperimental features are not part of the officially delivered scope that SAP guarantees for future releases. This means that experimental features may be changed by SAP at any time for any reason without notice. Experimental features are not for productive use. You may not demonstrate, test, examine, evaluate or otherwise use the experimental features in a live operating environment or with data that has not been sufficiently backed up.The purpose of experimental features is to get feedback early on, allowing customers and partners to influence the future product accordingly. By providing your feedback (e.g. in the SAP Community), you accept that intellectual property rights of the contributions or derivative works shall remain the exclusive property of SAP.

Example CodeAny software coding and/or code snippets are examples. They are not for productive use. The example code is only intended to better explain and visualize the syntax and phrasing rules. SAP does not warrant the correctness and completeness of the example code. SAP shall not be liable for errors or damages caused by the use of example code unless damages have been caused by SAP's gross negligence or willful misconduct.

Bias-Free LanguageSAP supports a culture of diversity and inclusion. Whenever possible, we use unbiased language in our documentation to refer to people of all cultures, ethnicities, genders, and abilities.

38 PUBLICCloud Integration Automation Service User GuideImportant Disclaimers and Legal Information

Page 39: User Guide | PUBLIC

Cloud Integration Automation Service User GuideImportant Disclaimers and Legal Information PUBLIC 39

Page 40: User Guide | PUBLIC

www.sap.com/contactsap

© 2021 SAP SE or an SAP affiliate company. All rights reserved.

No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP SE or an SAP affiliate company. The information contained herein may be changed without prior notice.

Some software products marketed by SAP SE and its distributors contain proprietary software components of other software vendors. National product specifications may vary.

These materials are provided by SAP SE or an SAP affiliate company for informational purposes only, without representation or warranty of any kind, and SAP or its affiliated companies shall not be liable for errors or omissions with respect to the materials. The only warranties for SAP or SAP affiliate company products and services are those that are set forth in the express warranty statements accompanying such products and services, if any. Nothing herein should be construed as constituting an additional warranty.

SAP and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP SE (or an SAP affiliate company) in Germany and other countries. All other product and service names mentioned are the trademarks of their respective companies.

Please see https://www.sap.com/about/legal/trademark.html for additional trademark information and notices.

THE BEST RUN