Introduction

Purpose

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

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

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

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.

The following describes the transport process for Ariba Sourcing:

For objects that are managed 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 CIG has similar corresponding tenant for each Ariba Sourcing Tenant: Supplemental, Test and Production.

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 landscape consists of 2 tiers: non-PRD and Production.

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

DocuSign landscape consists of 2 tiers: non-PRD and Production.

The following describes the transport process for DocuSign:

<TBD>