You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 36 Next »

Status

50%

Owner

PARA-ext, Anil 

Stakeholders

PILLAY-ext, Lawrence GARCIA-ext, Angel Luis KUMAR-ext, Kamal 

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 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 open Quantity will be migrated via Object Number 9045

The data from legacy system excludes:

  1. Inactive Lease Contracts and it's associated Deactivated ROU Assets (ROU is managed via Object 9108)
  2. Lease contracts that will be ended as of go-live dates defined in the project plan

Relevancy rule: The following relevancy criteria to be considered for extracting active RE-FX Lease Contracts from both WP2 and PF2. Note: PI2 does not have RE-FX Lease Contracts.

  • Go to table VICNCN:
    • Get all contracts from VICNCN-BUKRS where BUKRS is for company codes that are in scope and VICNCN-RECNENDABS is greater than or equal to 'system date'


List of source systems and approximate number of records
SourceScope

Source Approx No. of Records

Target SystemTarget Approx.

No. of Records

PF2RE-FX Lease Contracts (Lease-In and Lease-Out)1,870S/4 HANAWill be same as Source, unless any new contracts and/or deactivation before Go-live
WP2RE-FX Lease Contracts (Lease-In and Lease-Out)2,070S/4 HANAWill be same as Source, unless any new contracts and/or deactivation before Go-live

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.

Sheet NameTableFieldData ElementField DescriptionData TypeLengthRequirement
Real Estate Contract - DataVICNCNBUKRSBUKRSCompany CodeCHAR4Mandatory
Real Estate Contract - DataVICNCNRECNNRRECNNUMBERContract NumberCHAR13Mandatory
Real Estate Contract - DataVICNCNRECNTYPERECNCONTRACTTYPEContract TypeCHAR4Mandatory
Real Estate Contract - DataVICNCNRECNTXTRECNTXTContract DescriptionCHAR80Mandatory
Real Estate Contract - DataVICNCNRECNDATRECNDATDate of Contract ConclusionDATS8Conditional
Real Estate Contract - DataVICNCNRECN2DATRECN2DATDate of Second SignatureDATS8Optional
Real Estate Contract - DataVICNCNRECNBEGRECNCNBEGDate of contract startDATS8Mandatory
Real Estate Contract - DataVICNCNRECNEND1STRECNEND1STDate of First Contract EndDATS8Mandatory
Real Estate Contract - DataVICNCNAUTHGRPRECAAUTHGRPAuthorization GroupCHAR40Optional
Real Estate Contract - DataVICNCNRECNTLAWSMIETRTenancy lawCHAR5Optional
Real Estate Contract - DataVICNCNRECNTXTOLDRECNTXTOLDNumber of Old ContractCHAR20Optional
Real Estate Contract - DataVICNCNRECNBUKRSCOLLECTRECNBUKRSCOLLECTCompany Code of Main ContractCHAR4Conditional
Real Estate Contract - DataVICNCNRECNNRCOLLECTRECNNUMBERCOLLECTNumber of Real Estate Main ContractCHAR13Conditional
Real Estate Contract - DataVICNCNINDUSTRYBU_IND_SECTORIndustryCHAR10Optional
Real Estate Contract - DataVICNCNSRRELEVANTRECNSALESRENTRELEVANTIndicator: Relevant to SalesCHAR1Optional
Real Estate Contract - DataVICNCNRESPONSIBLERECARESPONSIBLEPerson ResponsibleCHAR12System
Real Estate Contract - DataVICNCNRECNDPORECDCFSTARTFROMCash Flow Generated Starting OnDATS8Conditional
Real Estate Contract - DataVICNCNCFPOSTINGFROMRECDCFPOSTINGFROMFirst Posting fromDATS8Optional
Real Estate Contract - DataVICNCNPOSSDATEFROMREBDPOSSDATEFROMDate From Which the Object Is Made Available for UseDATS8Optional
Real Estate Contract - DataVICNCNPOSSDATETOREBDPOSSDATETODate Up to Which the Object Is UsedDATS8Optional
Real Estate Contract - DataVICNCNRECNCNCURRRECNCNCURRCurrencyCHAR5Mandatory
Real Estate Contract - DataVICNCNRELEVANTEVALRELEVANTEVALValuation RelevanceCHAR10Mandatory
Real Estate Contract - DataVICNCNCustom Field 1TBD 1Icertis IDCHAR 8Optional
Real Estate Contract - DataVICNCNCustom Field 2 TBD 2Vendor Contract IDCHAR 20Optional
Real Estate Contract - DataVICNCNCustom Field 3 TBD 3PO NumberCHAR 10Optional
Real Estate Contract - DataVICNCNCustom Field 4 TBD 4PO Item NumberCHAR 5Optional

























































































































































































































































































































































































































































































































































Data Cleansing

IDCriticalityError Message/Report DescriptionRuleOutputSource System
1MediumDeactivated Lease Contracts

Terminated or concluded lease contracts must be closed and all related postings need to be posted and deactivated.

After cleansing, Lease contracts and associated ROU assets will have 'Deactivated' status.SAP ECC - PF2/WP2
2MediumLease Suspense GL Clearing

Lease Suspense account balances to be cleared: 

For Concluded contracts: Any contracts that have been terminated or concluded must have their balances to be cleared to Zero. 

For active contracts:  Open items are also to be cleared as much as possible for active lease contracts to ensure that remaining contract period balances are  consistent with the Lease suspense GL account

Lease suspense account IFRS 16 will be consistent with lease contract cash flow for any given date range.



SAP ECC - PF2/WP2
3MediumLease POs commitments match with IFRS 16 Active Lease Contracts Review all Lease POs against active IFRS 16 Lease Contracts that they match the commitments in source system. Otherwise, correct the incorrect values i.e., PO values, Qty, Lease dates and so on.The PO values are as per the commitment values for the IFRS 16 Lease Contracts, which align with the target Syway RE-FX design where each active lease contract must assign to the Lease POSAP ECC - PF2/WP2



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.

image-2025-6-10_15-39-25.png

Process

Activity

Extract

Extract involves collecting data from the source.

The source is a SAP system, Extract means to pull the required data from source systems into repository using Syniti ADMM.  There are 2 steps for this method:

  1. Perform full data extraction from relevant RE-FX tables in the source system(s).
  2. Apply Relevancy criteria for filtering the data that will be applicable according to Target Design.

Transform

There are 2 steps of Transform activities that can happen in ADMM:

  1. Perform mapping and data transformation rules.  Some data will need to be mapped to the to-be values and/or updated according to the rules as per design requirement in target system.
  2. Prepare load-ready data in the structure and format that is required for loading via SAP Data Migration Cockpit or any other standard tool.  This step also produces the load data ready for business to perform Pre-load Data Validation.

Load

This process includes:

  1. Execute the automated data load into target S4HANA system using load tool. 
  2. Once the data is loaded to target system, it will be extracted and prepared for Post Load Data Validation.

Data Privacy and Sensitivity

N/A


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

Apply relevancy rule/s before Extraction Run

Req #Requirement DescriptionTeam Responsible
1

Extract all active and released RE-FX Lease Contracts from table VICNCN in PF2 and WP2.

Syniti team
2

Extract Object data of RE-FX Lease Contracts from table VIBDOBJASS / VIBDCNSUBJECT in PF2 and WP2

Syniti team
3Extract Measurements data of RE-FX Lease Contracts from table VICNMEASCN in PF2 and WP2Syniti team
4Extract Organizational data of RE-FX Lease Contracts from table VITMOA in PF2 and WP2Syniti team
5

Extract Posting Terms data of RE-FX Lease Contracts from table VITMPY in PF2 and WP2

Syniti team
6

Extract Frequency Terms data of RE-FX Lease Contracts from table VITMRH in PF2 and WP2

Syniti team
7

Extract Business Partner (aka Vendors/Customers) data of RE-FX Lease Contracts from table VIBPOBJREL in PF2 and WP2

Syniti team
8

Extract Conditions data of RE-FX Lease Contracts from table VICDCOND in PF2 and WP2

Syniti team
9

Extract Valuation Rules data of RE-FX Lease Contracts from table VICERULE in PF2 and WP2

Syniti team


Selection Screen

Selection Ref ScreenParameter NameSelection TypeRequirementValue to be entered/set
N/A



Data Collection Template (DCT)

Field NameField DescriptionRule
N/A

Extraction Dependencies

Item #Step DescriptionTeam Responsible
1

Contracts which are already concluded and no longer valuated shall not be migrated

Data Team
2

Data cleansing of legacy RE-FX lease contracts where contracts that are no longer active will be concluded / deactivated 

Business 
3

The Purchase Orders relating to RE-FX Lease Contracts shall be reviewed to ensure the values match contracts data 

Business


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 Syniti Migrate ADMM 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

Item #Step DescriptionTeam Responsible

1 

Define the target load structure

Data team

2      

Map the target fields to the source fields as per the transformation rules

Data team

3      

Apply transformation rules

Data team

4      

Execute ETL job

Data team

5      

Generate Error reports

Data team

6      

Log and resolve defects

Data team

7

Generate Pre-load reports

Data team

8      

Generate load file

Data team

9

Generate post load reports

Data team


Transformation Rules

Rule #Source systemSource TableSource FieldSource DescriptionTarget SystemTarget TableTarget FieldTarget DescriptionTransformation Logic









































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

Transformation Mapping

List of mapping tables where the legacy values will have to be transformed to SyWay values.
Mapping Table NameMapping Table Description

Company code

Mapping of legacy company code to SyWay company code

Lease Contract Type

Mapping of legacy contract type to SyWay contract type

Object Type

Mapping of legacy Object type to SyWay Object type

Account Determination Value

Mapping of legacy Account Determination Value to SyWay Account Determination Value

Cost center

Mapping of legacy cost centre to SyWay cost centre

Profit center

Mapping of legacy profit centre to SyWay profit centre

Measurement TypeMapping of legacy Measurement type to SyWay Measurement type
Condition FormulaMapping of legacy Condition Formulae to SyWay Condition Formula
Business PartnerMapping of legacy Business Partner to SyWay Business Partner
Condition TypeMapping of legacy Condition type to SyWay Condition type
Valuation RulesMapping of legacy Valuation Rules to SyWay Valuation Rules

Transformation Dependencies

List the steps that need to occur before transformation can commence
Item #Step DescriptionTeam Responsible
1Profit center master data needed for assignment in the cost center and subsequently assigned to the lease contract during migrationR2R Data Team
2Cost Center master data is assigned to the lease contract master data during migrationR2R Data Team
3Business Master (Vendor & Customer) must be extended with the BP Roles TR0604 & TR0603R2R Data Team
4Purchase Orders relating to the Lease contracts must be migrated before the migration of the Lease contracts as the new PO numbers needs to be assigned to the contract templateS2F Data Team


Pre-Load Validation

Project Team

Completeness

TaskAction
Pre-load reportsCheck that the number of lease contracts in the upload file are the same as the number of contracts in the ETL file
Pre-load reportsCheck that all the lease contracts with lease POs have been updated with their respective PO numbers in the ETL file
Pre-load reportsReconciliation of record count: Total number of Lease contracts in the extraction is compared against the total number of lease contracts in the legacy system.

Accuracy

TaskAction
Conversion Accuracy

R2R Data Team to ensure that all fields listed below pass the checks:

  1. Mandatory Fields
  2. Field and Value Mapping Correctness
  3. Null Checks
  4. Filed Length Checks
  5. All necessary config values
  6. Custom fields 
Review Error ReportsReview and correct the errors.  Achieve a zero-error record count as much as possible. Raise defects for data remediated and requiring a correction in the ETL.

Business

Completeness

TaskAction
Verify record countBusiness Data Owner/s to verify that the total number of relevant records from the source is equal to the total number of records in the Preload and Load Sheets. 

Accuracy

TaskAction
Conversion accuracy

Business Data Owner/s to verify that all the Lease contracts are transformed accurately as per endorsed ETL rules. 

Review List of Error reports for any mismatch or missing transformed values.


Load

RE-FX Lease Contracts will be migrated using the SAP tool 'Migration Cockpit' and 'Object: Real Estate Contract-NEW' used for this specific import. Migration template is attached as a reference.

1076 RE-FX_Source data for Real Estate Contract - NEW.xml

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

Item #Step DescriptionTeam Responsible

1

Ensure Pre-load sign-offs are obtained

R2R Data team

2

Ensure the load tools are transported into the correct tool instance

R2R Data team

3

Go to <Load tool>

R2R Data team

4

Load 1 or 2 records for "Lease Contracts" to validate if data is loaded successfully without errors. If errors, log defects and obtain resolution 

R2R Data team

5

Proceed with full load if step 4 is successful and validated

R2R Data team

6

Validate few records loaded by accessing standard transactions or tables from S/4HNA E.g. RECISCN or FIORI: Contracts Management

R2R Data team

7

Generate post load report if step 7 is validated

R2R Data team


Load Phase and Dependencies

Configuration


Item #Configuration Item
1Company Code
2Contract Types
3Valuation Rules
4Conditions and Condition Purpose
5Contract Object Types
6Tax Type and Tax Group
7Valuation Relevance
8ROU Asset Classes
9Fixed Asset - Legacy Transfer Date
10ROU Assets Number Ranges
11Contract Number Ranges
12Business Partners with specific Role
13GL Accounts
14Cost Centres, Profit Centres and Functional Area
15Discounted Interest Rates

Conversion Objects

Object #Preceding Object Conversion Approach

list the exact title of the conversion object of only the immediate predecessor – this will then confirm the DDD (Data Dependency Diagram)




Error Handling

Error TypeError DescriptionAction Taken










Post-Load Validation

Project Team

Completeness

TaskAction







Accuracy

TaskAction





Business

Completeness

TaskAction
Record Count CheckBusiness Data Owner/s to verify that the total number of relevant records from the source is equal to the total number of records in the Preload validations. 

Accuracy

TaskAction
Spot checksBusiness should choose some Lease contracts and perform comprehensive checks of the fields in S/4 HANA. Recommended to verify sample data couple per company code and contract type combination.
Conversion AccuracyVerify that the Lease Contracts in target S/4 HANA are loaded correctly via load program and validate post load reports using standard t.code REISCN / RECEISASSETCN or FIORI - Contract Management from S/4 HANA.


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

Version Published Changed By Comment
CURRENT (v. 36) Apr 08, 2026 15:45 PARA-ext, Anil
v. 118 Mar 30, 2026 17:52 PARA-ext, Anil
v. 117 Feb 13, 2026 15:17 PARA-ext, Anil
v. 116 Feb 11, 2026 12:35 PARA-ext, Anil
v. 115 Dec 08, 2025 12:23 PARA-ext, Anil
v. 114 Dec 08, 2025 09:00 PARA-ext, Anil
v. 113 Dec 05, 2025 19:28 PARA-ext, Anil
v. 112 Dec 05, 2025 16:02 PARA-ext, Anil
v. 111 Dec 05, 2025 15:59 PARA-ext, Anil
v. 110 Dec 05, 2025 12:07 PARA-ext, Anil

Go to Page History

  • No labels