Purpose

The purpose of this document is to define the conversion approach for RE-FX Contract and Lease Management (CLM) master data in SyWay S/4 HANA. 

The main object of RE-FX migration is Lease contract master data and conditions. Due to the technical structure of RE-FX, there are also several tightly connected migration objects such as Business Partners  (i.e., Vendors), Right of Use (RoU) Assets & their balances, GL Liability balances and Lease related Purchase Orders. The scope of this conversion specification is the Lease contract master records. Migration of Lease contracts are however dependent on the other objects mentioned above to migrate Lease contracts data and their conditions completely and accurately, hence the dependent objects are also identified in this conversion specification.

The data migration activities for RE-FX is going to be managed via an ETL approach defined in the data migration strategy

The conversion approach for Group entities currently using SAP ECC shall use S/4 HANA CLM for IFRS 16 Lease Accounting in SyWay. S/4 HANA CLM provides a standardized framework, single source of truth and processes for a streamlined management of lease contracts across all Syensqo group entities directly in S/4 HANA.

Conversion Scope

The scope of this document covers the approach for converting active IFRS 16 Lease Contracts from Legacy Source Systems into S/4HANA following the DD-FUN-050 Master Data  Standard_1076-RE-FX Contract.xlsx Standard. The BPML process for RE-FX contracts will be followed as below

The data from legacy system includes:

1. IFRS 16 Lease-in and Lease-out contracts: Lease contract master data and Condition values migrated via this conversion specification
2. Lease Liabilities Balances: Short Term, Long Term and Accrued Lease Liability Balances will be migrated via Object Number 9010
3. ROU Assets and Balances: The master and transactional data will be migrated via Object Number 9108
4. Business Partners: Vendor & Customer Business Partner master data with a specific RE-FX role will be migrated via Object Number 3021
5. Purchase Orders for Leases: All Open POs for RE-FX Leases and with remaining Quantity will be migrated via Object Number 9045

The data from legacy system excludes:

1. Inactive Lease Contracts
2. Deactivated ROU Assets
3. Lease contracts will be ended as of go-live dates defined in the project plan

Additional Information

Multi-language Requirement

RE-FX Lease Contracts will primarily be managed in English. However, according to KDD055, this master data standard will be implemented in 4 core languages. 

• English (EN)
• French (FR)
• Italian (IT)
• Chinese (ZN)

 Note: Other language requirements were not finalized while developing this document, A custom WRICEF development is proposed.

Document Management

N/A

Legal Requirement

There are no legal requirements relevant to data migration of RE-FX Lease Contracts

Special Requirements

N/A

Target Design

The technical design of the target for this conversion approach.

Data Cleansing

Conversion Process

The high-level ETL process is illustrate by the diagram below. Note: DCT is not applicable for this object 1076. DCT is shown in table below, for reference only.

Data Privacy and Sensitivity

Extraction

The RE-FX Lease contract master data records shall be extracted from SAP ECC and migrated using the Syniti Migrate. There are 2 possibilities:

1. The data exists. Syniti Migrate connects to the source and loads the data into Syniti Migrate. There are 3 methods:
   1. Perform full data extraction from relevant tables in the source system(s).
   2. Perform extraction through the application layer.
   3. Only if cannot connect to the source, data is loaded to the repository from the provided source system extract/report.
2. The data does not exist (or cannot be converted from its current state). The data is manually collected by the business directly in Syniti Migrate. This is to be conducted using DCT (Data Collection Template) in Syniti Migrate. Note: DCT is not applicable for this object 1076

The agreed Relevancy criteria is applied to the extracted records to identify the records that are applicable for the Target loads

Extraction Run Sheet

Selection Screen

Data Collection Template (DCT)

DCT Rules

Extraction Dependencies

Transformation

The Target fields are mapped to the applicable Legacy field that will be its source, this is a 3-way activity involving the Business, Functional team and Data team. This identifies the transformation activity required to allow to make the data Target ready:

1. Perform value mapping and data transformation rules.
   1. Legacy values are mapped to the to-be values (this could include a default value)
   2. Values are transformed according to the rules defined in
2. Prepare target-ready data in the structure and format that is required for loading via prescribed Load Tool. This step also produces the load data ready for business to perform Pre-load Data Validation

Transformation Run Sheet

Transformation Rules

List of Custom Target Reports for this object is maintained here: Conversion Specification - Custom Reports Register.

Transformation Mapping

Transformation Dependencies

Pre-Load Validation

Project Team

Completeness

Accuracy

Business

Completeness

Accuracy

Load

The load process includes:

1. Execute the automated data load into target system using load tool or product the load file if the load must be done manually
2. Once the data is loaded to the target system, it will be extracted and prepared for Post Load Data Validation

Load Run Sheet

Load Phase and Dependencies

Configuration

Conversion Objects

Error Handling

Post-Load Validation

Project Team

Completeness

Accuracy

Business

Completeness

Accuracy

Key Assumptions

• Master Data Standard is up to date as on the date of documenting this conversion approach and data load.
• is in scope based on data design and any exception requested by business.

See also

Change log