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 |
|
| Test |
|
| 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 |
|
| Production |
|
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
<TBD>