Introduction

Purpose

The document describes the landscape and high-level transport process for R2 applications.

Scope

The transport process for the following applications will be covered in this document.

Application	Type
Ariba Sourcing	Brownfield system managed by Syensqo IT
Ariba Cloud Integration Gateway	Brownfield system managed by Syensqo IT
ICertis Contract Intelligence	Greenfield system managed by SyWay
DocuSign	Brownfield system managed by Syensqo IT
Integration Suite	Brownfield system managed by Syensqo IT
Syniti	Greenfield system managed by SyWay
ECC & PRS	Brownfield system managed by Syensqo IT
Cloud Identity Services	Greenfield system managed by SyWay

Out of Scope

As part of release 2, no changes is expected in the following systems and are considered out of scope for this document.

Ariba Catalog
Ariba Network
Keelvar
SAP Cloud Connector
Convergence
SuccessFactors

Detailed technical steps on how transports will be performed is also considered out of scope as the steps can be found in product documentations.

Transport Management

The following sections will cover the following the the applications in scope.

Landscape - Number of instance in the landscape and its purpose.
Transport Path - How changes will be migrated from different instances
Transport Approach - High level overview of how transports will be performed for the different applications.

Ariba Sourcing

Landscape

There are 3 Ariba Sourcing tenants for Release 2.

Tenant	Description
Supplemental	Provisioned for SyWay project and is not linked to other Ariba Sourcing Tenant. Used for release 2 build and integration test
Test	Existing Syensqo test tenant and is linked with Production Tenant. Used for release 2 UAT and training
Production	Existing Syensqo Production tenant.

Transport Path

Supplemental Realm will be repurposed release 4 after integration test (24-Nov). Hence there will be 2 transport paths for Ariba Sourcing

Transport Approach

The following describes the transport process for Ariba Sourcing:

For objects that can only be updated by SAP (e.g., custom fields, SAP controlled parameters), separate requests will be raised to SAP to perform the changes for the respective tenants.
For objects that support export/import (e.g., templates or data), changes will be exported and uploaded to subsequent tenants.
For all other objects, changes will be manually replicated to subsequent tenants.

Ariba Cloud Integration Gateway (CIG)

Landscape & Transport Path

Ariba Sourcing and CIG tenants are provisioned together and integrated by SAP. Hence the landscape and transport path for Ariba CIG is the same as Ariba Sourcing.

Transport Approach

The following describes the transport process for Ariba CIG:

Since Ariba CIG Supplemental tenant is not linked with Test tenant, changes will be replicated manually.
From Ariba CIG Test to Production, Ariba CIG's deployment mechanism will be used to deploy projects from Test to Production.

ICertis Contract Intelligence

Landscape

ICertis landscape consists of 2 tiers.

Tenant	Description
Non-PRD	Used for all R2 project activities (E.g., Development, Integration Test, UAT)
Production	During project phase, Production instance will be used to practice loading Production contract data loads. Before Go-live, data in Production will be cleared in preparation for Go-Live.

Transport Path

Configurations and changes will be performed in non-PRD and transported to Production instance during project phase (to support data load) and ACO.

Transport Approach

Promote Configurations (P2P) Tool will be used to transport changes from non-PRD to Production.

DocuSign

Landscape

DocuSign landscape consists of 2 tiers.

Tenant	Description
Non-PRD	Existing Syensqo non-PRD system. Used for all R2 project activities (E.g., Development, Integration Test, UAT)
Production	Existing Syensqo PRD system. Changes will be deployed to PRD during ACO.

Transport Path

Configurations and changes will be performed in non-PRD and transported to Production instance during ACO.

Transport Approach

The following describes the transport process for DocuSign:

Configurations will be replicated manually from non-PRD to Production.
Templates can be exported and uploaded from non-PRD to Production.

Integration Suite

Landscape

Since the new R2 interfaces deployed in integration suite will be integrating with ECC, Syensqo's Integration Suite will be leveraged and consists of 3 tier landscape.

Tenant	Description
Development	Syensqo Development tenant and integrates with DEV ECC. Used for R2 integration build and unit test
Test	Syensqo Test tenant and integrates with QAS & Pre-PRD ECC. Used for R2 integration test and UAT.
PRD	Syensqo Production tenant and integrates with PRD ECC. R2 Changes will be deployed during ACO.

Transport Path

Existing transport design will be leveraged for R2: DEV → QAS → PRD.

Transport Approach

Syensqo currently uses BMC Helix and SAP Solution Manager (ChaRM) to manage integration suite transports. For integration suite, the existing urgent change request will be used for R2.

For more details, please refer to Syensqo Transport Process.

Chnages will be transported from DEV to QAS and PRD by Syensqo IT and will be done using a manual approach (export/import and manual configuration in each tenant).

Syniti

Landscape

There will be one instance for Syniti and it will be used for all project activities.

The following diagram describes how one Syniti instance will be integrated with multiple systems.

Each ECC client will extract data to its respective source DB.
3 separate Syniti jobs will be created corresponding to the 3 Ariba tiers.
These Syniti jobs will be extract data from the respective source DB depending on the project phase requirements.
Data will be transferred from Syniti jobs to Ariba tenants via respective interfaces.

Transport Path

Changes will be made in Development job and tested before similar changes are made in Test job and tested. During cut-over, PRD job will be created.

Transport Approach

Each Syniti jobs will be configured manually. Hence the data team will need to replicate changes manually.

ECC & PRS

The following sections are applicable for both WP2 and PF2 ECC landscapes.

Landscape

Syensqo has a 4 tier ECC landscape.

Tenant	Description
Development	Used for R2 integration build and unit test
QAS	Used for R2 integration test and UAT.
Pre-PRD	Not used for R2
PRD	R2 Changes will be deployed during ACO.

Transport Path

Syensqo currently uses BMC Helix and SAP Solution Manager (ChaRM) to manage ECC transports. For R2, a normal change request process will be used.

For more details, please refer to Syensqo Transport Process.

Transport Approach

ECC transports are automated by SAP ChaRM.