Status
Owner	PARA-ext, Anil
Stakeholders	PILLAY-ext, Lawrence KUMAR-ext, Kamal GARCIA-ext, Angel Luis

Purpose

The purpose of this document is to define the conversion approach for Right of Use (ROU) assets Master and Transactional data in SyWay S/4 HANA. In ROU Fixed Assets migration both the master and transactional data will be migrated in one step. There will be only one SAP standard template which will be used for both the migration of the Master and Transactional data.

ROU Asset master consists of the following information:

• General information: Asset description, asset class, account determination, capitalization date etc. 
• Time Dependent data: Cost Center, Plant, Location etc.,
• Depreciation terms data: Depreciation keys, Useful life and Depreciation areas

Conversion Scope

The scope of this document covers the approach for converting active ROU Assets from Legacy Source Systems into S/4HANA following the Master Data Design Standard DD-FUN-050 Master Data Standard_1070-Fixed Assets (incl. Sub Assets) 

There are 2 group go-live as below:

• Group 1 go-live is planned for 1 July 2028
• Group 2 go-live is planned for 1 Jan 2029

RE-FX Contracts will be migrated to respective group go live as described in Enterprise Structure Catalog - Google Sheets (worksheet 10. Company code).

The data from legacy system includes:

1. Relevancy Criteria 1
2. Relevancy Criteria 2
3. Relevancy Criteria n

The data from legacy system excludes:

1. Exclusion Criteria 1
2. Exclusion Criteria 2
3. Exclusion Criteria n

List of source systems and approximate number of records

Source	Scope	Source Approx No. of Records	Target System	Target Approx No. of Records
PF2	ROU Assets	3,270	S/4 HANA	Will be same as Source, unless any new Assets and/or deactivation of assets before Go-live
WP2	ROU Assets	1,044	S/4 HANA	Will be same as Source, unless any new Assets and/or deactivation of assets before Go-live

Additional Information

Multi-language Requirement

It was decided to apply approach below:

• Field “Description Line1” (ANLA-TXT50) = Migrate as it is from legacy system to S/4HANA. The description could be any languages (not only the 4 core languages but also any other non-core languages.
• Field “Description Line2” (ANLA-TXA50) = Migrate as it is from legacy system to S/4HANA. The description line 2 is used to add information on the description of the asset when the line 1 length is not enough.
• Field "Asset main no.text" (ANLH-ANLHTXT) must be in English 

Document Management

N/A

Legal Requirement

There are no legal requirements relevant to data migration of ROU Assets

Special Requirements

N/A

Target Design

The technical design of the target for this conversion approach.

Table	Field	Data Element	Field Description	Data Type	Length	Requirement
ANLA	BUKRS	BUKRS	Company Code	CHAR	4	Mandatory
ANLA	ANLN1	ANLN1	Main Asset number	CHAR	12	System generated number and mandatory
ANLA	ANLN2	ANLN2	Asset sub-number	CHAR	4	System generated number and mandatory
ANLA	ANLKL	ANLKL	Asset Class	CHAR	8	Mandatory
ANLA	ZUJHR	DZUJAHR	Fiscal year in which first acquisition was posted	NUMC	4	Optional
ANLA	ZUPER	DZUPER	Period in which first acquisition was posted	NUMC	3	Optional
ANLA	ZUGDT	DZUGDAT	Asset value date of the first posting	DATS	8	Optional
ANLA	AKTIV	AKTIVD	Asset capitalization date	DATS	8	Optional
ANLA	DEAKT	DEAKT	Deactivation on	DATS	8	Optional
ANLA	ORD41	ORD41	Evaluation group 1	CHAR	4	Optional
ANLA	ORD42	ORD42	Evaluation group 2	CHAR	4	Optional
ANLA	ORD43	ORD43	Evaluation group 3	CHAR	4	Optional
ANLA	ORD44	ORD44	Evaluation group 4	CHAR	4	Optional
ANLA	LIFNR	LIFNR	Account number of vendor (other key word)	CHAR	10	Optional
ANLA	HERST	HERST	Manufacturer of asset	CHAR	30	Conditional
ANLA	VMGLI	VMGLI	Property Classification Key	CHAR	4	Conditional
ANLA	AIBN1	AIBN1	Original asset number or Original Group Asset number	CHAR	12	Mandatory
ANLA	AIBN2	AIBN2	Original Sub-Asset	CHAR	4	Mandatory
ANLA	AIBDT	AIBDT	Original Acquisition Date of AuC/ Transferred Asset	DATS	8	Optional
ANLA	MENGE	AM_MENGE	Quantity	QUAN	13	Optional
ANLA	MEINS	MEINS	Base unit of measure	UNIT	3	Conditional
ANLA	INKEN	INKEN	Include asset in inventory list	CHAR	1	Mandatory
ANLA	IVDAT	IVDAT_ANLA	Last Inventory on	DATS	8	Optional
ANLA	INVZU	INVZU_ANLA	Inventory Note	CHAR	15	Optional
ANLA	INVNR	INVNR_ANLA	Inventory Number	CHAR	25	Conditional
ANLA	VBUND	RASSC	Company ID of Trading Partner	CHAR	6	Conditional
ANLA	TXT50	TXA50_ANLT	Asset description	CHAR	50	Mandatory
ANLA	TXA50	TXA50_MORE	Additional asset description	CHAR	50	Conditional
ANLA	GDLGRP	GDLGRP	Evaluation group 5	CHAR	8	Conditional
ANLA	SERNR	AM_SERNR	Serial number	CHAR	18	Conditional
ANLA	UMWKZ	AM_UMWKZ	Reason for Environmental Investment	CHAR	5	Conditional
ANLB	AFABE	AFABE_D	Depreciation area	NUMC	2	Mandatory
ANLB	AFABG	AFABG	Depreciation Start date	DATS	8	Optional
ANLB	AFASL	AFASL	Depreciation Key	CHAR	4	Mandatory
ANLB	NDJAR	NDJAR	Useful Life	NUMC	3	Optional
ANLB	NDPER	NDPER	Useful Life (Period)	NUMC	4	Optional
ANLB	SCHRW	SCHRW	Asset scrap value	CURR	13 with 2 decimals	Conditional
ANLB	SCHRW_PROZ	SCHRW_PROZ	Scrap value %	DEC	14	Conditional
ANLB	ANLGR	ANLGR	Group asset	CHAR	12	Not used
ANLZ	KOSTL	KOSTL	Cost Centre	CHAR	10	Mandatory
ANLZ	PRCTR	PRCTR	Profit Centre	CHAR	10	System generated
ANLZ	WERKS	WERKS_D	Plant	CHAR	4	Mandatory
ANLZ	STORT	STORT	Location	CHAR	10	Optional
ANLZ	RAUMN	RAUMNR	Room	CHAR	8	Optional
ANLZ	KFZKZ	AM_KFZKZ	License Plate No. of Vehicle	CHAR	15	Optional
ANLH	ANLHTXT	ANLHTXT	Asset main no. text	CHAR	50	Mandatory
ANLZ	XSTIL	XSTIL	Asset shutdown indicator	CHAR	1	Optional

Data Cleansing

All data cleansing should take place in the data source system as defined in this document, unless system limitations prevent it.

If data cleansing is managed outside of the source system (e.g. Syniti Migrate, 3rd Party Vendor, DCT), the necessary documentation must be produced and appended to this deliverable for sign-off.

ID	Criticality	Error Message/Report Description	Rule	Output	Source System

Conversion Process

The high-level process is represented by the diagram below:

Summarize High-Level Process. Include diagrams, where applicable. Include information supporting details of Extract, Transform and Load specific to the Data Object

Data Privacy and Sensitivity

Summarize Data Privacy and Sensitivity Requirements, if any

Extraction

Extract data from a source into 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 Syniti Migrate; 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

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

Extraction Run Sheet

Req #	Requirement Description	Team Responsible

Selection Screen

If applicable, this section will give the details on any selection screen parameters, including the parameter type, that are required to be entered to ensure consistent data extracts.

Selection Ref Screen	Parameter Name	Selection Type	Requirement	Value to be entered/set

Data Collection Template (DCT)

Target Ready Data Collection Template will be created for Data Object data with exception of some fields which require transformation as mentioned in the transformation rule.

<Object> DCT Rules

Field Name	Field Description	Rule

Extraction Dependencies

List the steps that need to occur before extraction can commence

Item #	Step Description	Team Responsible

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 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 Syniti Migrate
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 Description	Team Responsible

Transformation Rules

Rule #	Source system	Source Table	Source Field	Source Description	Target System	Target Table	Target Field	Target Description	Transformation Logic

Transformation Mapping

Use the exact name and reference this section in the “Transformation rules” above

Mapping Table Name	Mapping Table Description

Transformation Dependencies

List the steps that need to occur before transformation can commence

Item #	Step Description	Team Responsible

Pre-Load Validation

Project Team

The following pre-load validations will be performed by the Project Team.

Completeness

Task	Action
title	specific details of what and how the task needs to be performed e.g. which reports are being used etc.

Accuracy

Task	Action
title	specific details of what and how the task needs to be performed e.g. which reports are being used etc.

Business

The following pre-load validations will be performed by the business.

Completeness

Task	Action
title	specific details of what and how the task needs to be performed e.g. which reports are being used etc.

Accuracy

Task	Action
title	specific details of what and how the task needs to be performed e.g. which reports are being used etc.

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

Item #	Step Description	Team Responsible

Load Phase and Dependencies

Identify the phase as to “when” the load for this object will occur. <Pre-Cutover, Cutover, Post Cutover> and list the steps that need to occur before the load can commence

Configuration

List the Configurations required before loading can commence

Item #	Configuration Item

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

The table below depicts some possible system errors for this data object during data load. All data load error is to be logged as defect and managed within the Defect Management

Error Type	Error Description	Action Taken

Post-Load Validation

Project Team

The following post-load validations will be performed by the Project Team.

Completeness

Task	Action
title	specific details of what and how the task needs to be performed e.g. which reports are being used etc.

Accuracy

Task	Action
title	specific details of what and how the task needs to be performed e.g. which reports are being used etc.

Business

The following post-load validations will be performed by the business.

Completeness

Task	Action
title	specific details of what and how the task needs to be performed e.g. which reports are being used etc.

Accuracy

Task	Action
Spot checks	Business should choose some ROU Assets and perform comprehensive checks of the fields in S/4 HANA. Recommended to verify sample data per company code and Asset class combination.
Conversion Accuracy	Verify that the ROU Assets in target S/4 HANA are loaded correctly via load program and validate post load reports using standard t.code AR01 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.
• Data Object is in scope based on data design and any exception requested by business.

Any additional key assumptions.

See also

Insert links and references to other documents which are relevant when trying to understand this decision and its implications. Other decisions are often impacted, so it's good to list them here with links. Attachments are also possible but dangerous as they are static documents and not updated by their authors.

Change log