Versions Compared

Old Version 28

changes.mady.by.user WENNINGER-ext, Sascha

Saved on

compared with

New Version Current

changes.mady.by.user TILBEE-ext, Amanda

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Status

Page Status

Owner

NARAHARI-ext, Bhargavi 

Stakeholders

Purpose

This document outlines the SyWay Program approach to data migration and readiness to move to new business processes as part of Release 2. It establishes an operational framework to ensure data is clean, reliable, structured and available at go-live.

The objectives are:

  • To establish a forward-looking data strategy in Release 2 that minimizes the volume of data migration required during Release 4, thereby reducing risk, effort, and rework in later phases of the program.

  • To identify and define the data objects and migration requirements from ECC and other third-party systems to Ariba, Keelvar, and Icertis as part of Release 2


Background

This document outlines the data migration and cleansing approach for Release 2, which focuses on the implementation of the Source to Contract (S2C) process as part of the broader program roadmap. Release 2 is an intermediate deployment that introduces standardised procurement processes and integrates with existing ECC systems and third-party applications such as Convergence.

The primary objective of this release is to establish foundational S2C capabilities that can be reused and scaled during subsequent releases, particularly Release 4 (R4), which will involve a broader S/4HANA transformation. As such, the data migration strategy for Release 2 is designed with reusability and future scalability in mind.

Due to the continued reliance on legacy ECC systems in this phase, there are limitations in the extent of data cleansing that can be performed. Existing data in ECC will be migrated largely in its current state, with only targeted validations and enrichment applied where feasible. Cleansing activities will be focused on data sets required for the new S2C processes and integrations, ensuring functional readiness without major disruption to upstream or downstream systems.


Data Scope

The scope encompasses all master data, open transactional data and historical records required to ensure business continuity, legal compliance and readiness for Release 2. Data will be migrated from multiple SAP ECC source systems and legacy third-party applications into a Standardized SyWay environment.

Data Sources

Data will be extract data from a range of legacy systems that currently support Syensqo’s global operations. These sources span SAP and non-SAP applications and include structured and semi-structured data repositories. 

Primary Data Sources include:

  • SAP ECC systems – multiple instances

  • Convergence

  • Contract repositories (other than convergence) / Local drives


Data Migration Process

For Release 2, the data migration process supports the enablement of Source to Contract (S2C) functionality within SAP Ariba, with downstream integration to Icertis, which acts as a slave system consuming master data from Ariba. Unlike traditional ERP implementations, most relevant data for S2C is treated as configuration within Ariba, requiring a data-driven approach to setup rather than transactional migration.

The data team’s primary responsibility is to populate Data tables / Ariba upload templates, which define the system’s configuration and reference data. These templates serve as the foundation for both Ariba and Icertis, as Icertis relies on Ariba to provide key master data objects such as suppliers, categories, and organizational structures.

The process follows these key steps:

Activity  Business 
StepActivityOwned By
Template FinalisationStandard Ariba/Icertis templates for key data objects (e.g., suppliers, commodity codes, sourcing templates, approval flows)Functional Team
Data CollectionSource data is gathered from existing ECC systems, third-party applications (e.g., Convergence) etc.Data Team / Contract Migration team
Template PopulationSource data is provided to the function team for populating the templatesFunctional Team / Data team / Contract Migration team
Validation and ReviewValidation of the values with BusinessFunctional team
Upload TemplatesValidated templates are uploaded into Ariba/ICertis using its import toolsFunctional Team



Data Objects in Scope

Following are the data objects that are in scope for Release 2

Data ObjectCategoryHow is it loaded in AribaHow is it loaded in IcertisHow is it loaded in Keelvar
Company CodeEnterprise StructureInterface
Replication from Ariba

Manually Upload

N/A

Purchasing OrganizationEnterprise StructureInterface
Replication from Ariba

Manually Upload

N/A
Purchasing GroupsEnterprise StructureInterface

N/A

N/A
Replication from Ariba
PlantEnterprise StructureInterface

N/A

N/A
Replication from Ariba

Suppliers

Master Data

Interface from ECC

/ Convergence

Replication from Ariba

Replication from Ariba

BiddersMaster Data
Interface from ECC / Convergence
Manually created in AribaReplication from AribaReplication from Ariba
MaterialsMaster DataNot RequiredN/A
Material Groups / Commodity CodesMaster DataInterface
N/A
Material Groups Master Data

Interface

(L3 - used in Line Item Level)

Manually Upload

(L3 - used in Line Item Level)

N/A
Commodity Codes Master Data

Manually Upload

(L1/L2/L3 - used in Header Field)

Manually Upload

(L1/L2/L3 - used in Header Field)

Manually Upload

(L3 - used in Header Field)

Replication from Ariba

UOM

Master Data

Upload

Replication from Ariba

N/A

N/A

Payment Terms

Master Data

Interface

Manually Upload

N/A

Replication from Ariba

IncotermsMaster DataInterface
Replication from Ariba

Manually Upload

N/A
CurrencyMaster DataStandard. Manually Upload
Replication from Ariba

Manually Upload

N/A
Item CategoriesMaster DataInterface
Replication from Ariba

N/A

N/A
Users (Including Jobs, Roles and org structure)*Master DataInterface from IAG
Upload /
Interface from
SFManual upload for Release 2, Can be partly Interfaced from SF based on the SSO requirements
IAGReplication from Ariba
Legal Contracts Transactional DataN/AUpload (for Legal Migration)N/A
Exchange RatesTransactional DataInterface

Interface

Replicate from Ariba
N/A

*User interfaced from IAG. Roles configured in Ariba and Icertis 

Data approach for R2 and R4

The data strategy for the Source to Contract (S2C) implementation spans across Release 2 and Release 4, with a clear distinction in how data is handled across both Ariba and Icertis.

Release 2 Data Approach

In Release 2, the focus is on enabling Ariba Guided Sourcing / Contracts using a targeted data set derived from existing ECC and third-party systems. This data is used to configure Ariba / Icertis via interfaces / upload templates and to support sourcing and contracting processes. Key characteristics of the Release 2 approach include:

master It doesn't store any master data

  •  No data configuration required

    • AribaIcertisKeelvar

    • Master and reference data required for Ariba Guided Sourcing (e.g., suppliers, commodity codes, organizational units) are collected from ECC and third-party systems. Data is loaded via structured Ariba upload templates.

    • No data cleansing except Payment Terms is performed. Data is validated where feasible but largely migrated in its existing form.

    • Consumes

    • supplier and bidder master data from Ariba based on the Release 2 configuration using standard integration. 

    • Any Icertis specific data is manually configured to align with Ariba/ECC to ensure consistency in contract metadata.

    • Keelvar is used for strategic sourcing and optimization and feeds off master/transactional data in Ariba based on each event.

    •  Master data of Supplier, Commodity Code (L3) and GBU are stored in Keelvar.

    Release 4 Data Approach 

    The Source to Contract (S2C) data strategy spans multiple releases, transitioning from a manually managed data load in Release 2 to a fully integrated and governed master data model in Release 4. The approach differs by system, depending on its role in the S2C landscape.

    This section outlines the data approach for Ariba, Icertis, and Keelvar across both releases.

    and does not persist any master data
    AribaIcertisKeelvar
    • Ariba is integrated with S/4HANA and Master Data Management (MDM) systems. Master data is replicated directly from S/4, replacing the manually loaded Release 2 data.

    • Data is centrally cleansed, validated, and governed before replication, ensuring higher data quality and standardization across the S2C process.

    • Completed/Inflight sourcing documents are not retrofitted. New events will automatically use the integrated S/4-based master data.

    • To stay in sync with the new S/4-driven master data, Icertis requires a retrofit of existing contract data. Leveraging Icertis's find-and-replace capability, master data fields (e.g., supplier names, commodity groups) will be updated to reflect the S/4 data model.
    • Keelvar continues to act as a consumer of Ariba data
    • . 
    • No retrofit or data migration activity is required in Release 4 for Keelvar.

    Following is the table of all the data objects and the approach in Release 2 and Release 4.

    Data ObjectChange in R4R2 R4Pre-requisite
    Company Code

    Numbering 

    Scope

    		Existing company codes are replicated to Ariba and Icertis

    Ariba: The R2 company codes are inactivated, and the new company codes are made active

    Icertis: The R2 company codes are replaced with R4 company codes

    Mapping between R2 and R4 codes

    Purchasing OrganizationNumberingExisting Purchasing Org codes are replicated to Ariba and Icertis

    Ariba: The R2 POrgs are inactivated, and the new codes are made active

    Icertis: The R2 POrgs are replaced with R4 codes

    Mapping between R2 and R4 codes

    Purchasing Groups

    Numbering

    Scope

    		Existing Purchasing
    groups
    Groups codes are replicated to Ariba and Icertis

    Ariba: The R2 Pgroup are inactivated, and the new codes are made active

    Icertis:

    The R2

    Pgroup are

    replaced with

    implemented using R4 codes

    Mapping between R2 and R4 codes

    Plant

    Numbering

    Scope

    		Existing plants are replicated to Ariba
    and Icertis

    Ariba: The R2 plants are inactivated, and the new codes are made active

    Icertis: The R2 plants are replaced with R4 codes

    		Mapping between R2 and R4 codes

    Suppliers

    Numbering

    Scope

    		Existing suppliers are replicated to Ariba, Icertis and
    Icertis
    Keelvar

    Ariba and Keelvar: The R2 suppliers are inactivated, and the new codes are made active

    Icertis: The R2 suppliers are replaced with R4 codes

    Mapping between R2 and R4 codes

    Bidders

    Numbering

    Scope

    Existing bidders are

    Bidders are created in Ariba and replicated to

    Ariba

    Icertis and

    Icertis

    Keelvar

    Ariba and Keelvar: The R2 bidders are inactivated, and the new codes are made active

    Icertis: The R2 bidders are replaced with R4 codes

    Mapping between R2 and R4 codes

    Materials

    Numbering

    Scope

    Not applicable

    Ariba: The R4 codes are made active.

    Icertis: The R4 codes are made active.

    Mapping between R2 and R4 codes

    Material Groups 

    Numbering

    Scope

    Existing

    materials

    material groups are

    replicated

    integrated to Ariba and manually loaded in Icertis

    Ariba: The R2

    materials

    material groups  are inactivated, and the new codes are made active

    Icertis: The R2

    materials

    material groups  are replaced with R4 codes

    Mapping between R2 and R4 codes

    Material Groups /
    Commodity Codes

    Numbering

    Scope

    Existing

    material groups /

    commodity codes are

    replicated to Ariba and Icertis

    manually loaded in Ariba (L1,2,3), Icertis (L1/L2/L3) and Keelvar (L3)

    Ariba and Keelvar

    Ariba

    : The R2

    material groups /

    commodity codes are inactivated, and the new codes are made active

    Icertis: The R2

    material groups /

    commodity codes are replaced with R4 codes

    Mapping between R2 and R4 codes

    UOM

    Scope

    Existing UOM are

    replicated to Ariba and Icertis

    manually loaded in Ariba

    Ariba: The delta UOM for R2 are inactivated, and the new codes are made active

    Icertis: The R2 UOM are replaced with R4 codes

    Mapping between R2 and R4 codes

    Payment Terms

    Scope

    Old Payment terms used on contracts are loaded and marked as inactive

    New Payment terms loaded

    No Action required

    N/A

    IncotermsScopeExisting incoterms are replicated to Ariba and Icertis

    Ariba: The delta incoterms are inactivated, and the new codes are made active

    Icertis: The R2 incoterm codes are replaced with R4 codes

    		N/A
    Currency NoneExisting currencies are
    replicated to Ariba
    loaded in Ariba (Standard) and Icertis (Upload)No Action requiredN/A
    Item CategoriesNoneExisting Item Categories are
    replicated
    integrated to AribaBased on lean services outcome, Lean Services needs to be added in the item categoriesN/A
    Users (Including Jobs, Roles and org structure)

    Numbering

    Scope

    Existing users including their Jobs and Roles are replicated
    Users provisioned based on mapping of R2 role to person, broadly aligned to current jobs and roles.Users with their new Jobs and Roles are replicatedN/A
    Legal Contracts MetaDataNoneMeta Data determined in Release 2 is loadedNo Action RequiredN/A
    Legal Contract Templates (Clauses)NoneLegal contracts and clauses are loadedNo Action RequiredN/A
    Legal Contracts NoneLegal contracts and clauses are loadedNo Action RequiredN/A
    Exchange RatesNoneExchange Rates from ECC are loaded dailyNo Action RequiredN/A


    Legal Contract Migration Approach

    Following is the approach followed for the legal contract migration:Step 1:

    1. Contract attributes are defined by the functional team
    Step 2:
    1. Contracts and existing attributes are extracted from Convergence and other data sources by contract migration team
    Step 3:
    1. Contracts are loaded on to Harvey to extract the contract metadata and relationships
    Step 4:
    1. The contract metadata and relationships are validated - This step is performed only on selected critical contracts which are agreed with Business upfront
    Step 5:
    1. The validated contracts are loaded into Icertis along with the metadata and attachment
    Step 6: Any relavent Ztables
    1. Any relevant Z-tables are updated with Icertis contract
    id
    1. ID - They contain convergence
    id
    1. ID previously


    Change log

    Change History
    limit10