Status
Owner	BUOSI-ext, Angelo HANCOCK-ext, John
Stakeholders

Purpose

The purpose of this document is to define the conversion approach to create Service Master records in S/4HANA. It follows the Procurement Master Data Design Standard and is based on data being migrated from legacy SAP ECC systems (PF2, WP2) into SAP S/4HANA.

The purpose of this document is to define the conversion approach to upload data in S/4 HANA.

This file is aligned with the Conversion Specification Guidelines

---CHECKLIST---

• Logical Source and Target Systems are identified. 
• Processing Type is specified (i.e. Direct Input, BAPI, IDoc, Web Service, OData API, etc.)
• Standard or custom load program name/BAPI/IDoc is specified to support this functionality.
• Data Mapping is provided for mappings which are not obvious to a suitably-skilled and experienced developer
• All translation requirements are clearly defined (including data validation rules, data derivation/calculation and default values, if applicable)Input and/or Output file layouts are provided for all record types possible
• Transaction volume is specified Execution frequency is specified Restart/Recovery requirements havee been defined
• Error handling requirements are specified, including alerting requirement and expected action on failure.
• Application log requirement if applicable to be specified. 

--- Additional topics to check---

• Rules for Data Merging (all systems) - DEDUPLICATION RULES

Conversion Scope

The migration will consolidate two existing legacy object types into a single Lean Service model in S/4HANA:

1. Materials created as Services – Material Master records with service-related material types (e.g., DIEN or equivalent).
2. Service Master Data – Maintained in SAP ECC as ASMD objects.

Both object types are currently used in parallel to support service procurement. While they may sometimes represent similar business needs, they are maintained and processed independently in the legacy systems.

In the target system (S/4HANA), all services will be represented exclusively as Lean Services within the Material Master (Material Type = SERV or ZSER), in line with the Procurement Master Data Design Standard. This approach eliminates the need for separate Service Master objects and service material types, providing:

• A single master data object for all services.

• Standardized naming, classification, and valuation.

• Harmonized Material Groups for enterprise-wide reporting and spend analysis.

The conversion scope includes:

• Extracting both Service Master and Materials-as-Services records.

• Cleansing, harmonizing, and deduplicating entries across both object types.

• Mapping legacy keys to new Lean Service material numbers for traceability.

• Excluding obsolete, incomplete, or unused records.

List of source systems and approximate number of records

Source	Scope	Source Approx No. of Records	Target System	Target Approx No. of Records
PF2	The Purchasing Info Records will be extracted/collected via DCT. An initial extract of the relevant data will be provided in Google Sheet format to assist business in decision making on including any relevant data from Source Systems. Any additional data that need to be created to support the new design may be added in the DCT. A data review and standardization will be done across all Info Records in the DCT.	38.594	S4H	16.000 (50% -)
WP2		883	S4H	440 (50% -)

Additional Information

Multi-language Requirement

For all Lean Services in the target S/4HANA system, the default description will be maintaineed in English.

Where available in the source systems (PF2, WP2), additional language-dependent descriptions will also be migrated. This applies to both:

• Service Master records (ASMD).

• Materials-as-Services (Material Type DIEN or equivalent).

Migration rules:

• Only languages available and supported in the target S/4HANA system will be migrated.

• If a description exists in a custom or unsupported language key in the source, that language entry will be skipped.

• The migration will preserve the link between the Lean Service material number and each language-specific description.

• Where the same service exists in multiple languages in the source, all valid language versions will be migrated together with the default English text.

This approach ensures that Lean Services are available in multiple languages for purchasing, reporting, and user interaction, while maintaining compliance with the target system’s supported language set.

Languages to be extracted (available on Source Systems)

SAP standard provides support for all ISO languages. The following list is illustrative and not exhaustive.

International Version	Description
AF	Afrikaans
AR	Arabic
BG	Bulgarian
CS	Czech
DE	German
EL	Greek
EN	English
ES	Spanish
FI	Finnish
FR	French
IT	Italian
JA	Japanese
KO	Korean
NL	Dutch
PL	Polish
PT	Portuguese
RU	Russian
SK	Slovak
TH	Thai
TR	Turkish
ZF	Chinese (Traditional)
ZH	Chinese (Simplified)

Languages to don't be extracted

The Z9 language code represents “Multilingual / Other,” which is a generic placeholder rather than a specific language. It does not correspond to a standard ISO language code and therefore cannot be mapped reliably to a target language in the S/4HANA environment. Including Z9 would result in ambiguous or duplicate entries, making data validation, reporting, and translation maintenance inconsistent. To ensure data quality and consistency, records with Z9 will be excluded from the extraction scope.

International Version	Description
Z9	Multilingual / Other

Document Management

Summarize Document Management requirement, if any

Legal Requirement

Minor efforts with taxation are foreseen for some specific countries having specific taxations, the topic is limited to have the tax codes mapping (from Old to New tax code).

Special Requirements

Processing Type ETL: 

• Transformation (T): Syniti will be responsible for cleansing, transforming, and merging the data, as well as updating the staging areas of the SAP Migration Cockpit.

• Extraction (E): Data will be extracted from at least two source systems. This activity will be performed by Syniti.

• Loading (L): The final data load into the target SAP system will be carried out using the standard functionalities of the SAP Migration Cockpit.

Deduplication Rules

Rule ID	Semantic Rule	Purpose
SR01	Deduplication of Services Master (table ASMD) from PF2 & WP2:  - DEDUP 1: Exclude from the deduplication rule services where the Deletion Flag is set ASMD-LOEKZ <> "" (marked for deletion) - DEDUP 2: In case the Short Text (ASMD-KTEXT) + Language Key (ASMD-SPRAS) are identical, this is an indication of a duplicated entry - DEDUP 3: In case the Material Group (ASMD-MATKL) or two or more records are identical, this is an indication of a duplicated entry - DEDUP 4: In case the Base Unit of Measure (ASMD-MEINS) in combination of the Topics 2 & 3 are identical, this is an indication of a duplicated entry - DEDUP 5: In case the Long Text / Additional Descriptions (STXL/STXB) are exactly the same, this is an indication of a duplicated entry	To ensure that Lean Service Materials (stored in MARA and related tables) are unique and free of redundancies prior to migration into S/4HANA. The rules validate duplicates across standardized descriptions, language, material group, and units of measure, while also considering long texts for confirmation. Additionally, unsupported or custom languages (such as Z9) are excluded unless explicitly required, ensuring alignment with SAP standard language configurations. This prevents proliferation of redundant Lean Service materials and supports a harmonized catalog in the target system.
SR02	Deduplication of Services (table MARA) from PF2 & WP2: - DEDUP 1: Drop any record technically blocked or marked for deletion in source. Check field MARA-LOEKZ (or equivalent for Lean Services). - DEDUP 2: A duplicate exists if the following four attributes are exactly the same between two records (MAKT-MAKTX / MAKT-SPRAS / MARA-MATKL / MARM-MEINH) - DEDUP 3: A duplicate exists if the long texts (such as Purchase Order Texts or Basic Texts stored in STXL/STXB) are exactly the same (or at least 98% similar), then borderline duplicates can be promoted to confirmed duplicates. - DEDUP 4: Exclude any records that are only in custom or unsupported languages (e.g., Z9) unless explicitly required by the business.

Target Design

With Functional input, document the technical design of the target fields that are in the scope of this document.

The technical design of the target for this conversion approach.

Tables to be migrated as Basic Data:

Table	Description
MARA	General Material Data	Stores material master data that is valid for all organizational levels (client-level data such as base unit of measure, material type, industry sector).
MARM	Units of Measure	Holds all alternative units of measure and conversion factors for each material.
MAKT	Material Descriptions (multi language)	Contains the material short texts (descriptions) in different languages.
MANT	Text per UoM	Holds long texts for materials, used for extended descriptions.
MLAM	Tax Classification for Material)	Stores material tax data per country

Table / Staging Area	Field	Data Element	Field Description	Data Type	Length	Decimal	Importance
MARA - General Material Data
S_MARA	MATNR		Product Number	Text (CHAR)	18		Mandatory MDS: OK
S_MARA	MTART		Product Type	Text (CHAR)	80		Mandatory
S_MARA	ATTYP		Product Category	Text (CHAR)	80
S_MARA	SATNR		Configuration Product for Retail Variant	Text (CHAR)	80
S_MARA	MATKL		Product Group	Text (CHAR)	80		MDS: OK
S_MARA	MBRSH		Industry Sector	Text (CHAR)	80
S_MARA	MAKTX		Description	Text (CHAR)	40		Mandatory MDS: OK
S_MARA	SPRAS		Language Key	Text (CHAR)	80		Mandatory
S_MARA	MEINS		Base Unit of Measure (ISO Format)	Text (CHAR)	80		Mandatory MDS: OK
S_MARA	AENNR		Change Number	Text (CHAR)	80
S_MARA	REVLV		Revision Level	Text (CHAR)	80
S_MARA	EAN11		GTIN	Text (CHAR)	18
S_MARA	NUMTP		GTIN Category	Text (CHAR)	80
S_MARA	SPART		Division	Text (CHAR)	80		MDS: OK
S_MARA	BISMT		Old Product Number	Text (CHAR)	40		MDS: OK
S_MARA	PRDHA		Product Hierarchy	Text (CHAR)	80		MDS: OK
S_MARA	BRAND_ID		Brand	Text (CHAR)	80
S_MARA	XCHPF		Batch Management Required Ind.	Text (CHAR)	1
S_MARA	MLGUT		Has Empties	Text (CHAR)	1
S_MARA	DATAB		Valid From	Date
S_MARA	LIQDT		Deletion Date	Date
S_MARA	KUNNR		Competitor	Text (CHAR)	80
S_MARA	NORMT		Industry Standard Description	Text (CHAR)	18
S_MARA	GROES		Size/Dimensions	Text (CHAR)	32
S_MARA	LABOR		Laboratory / Design Office	Text (CHAR)	80
S_MARA	INHAL		Net Contents	Number (NUMC)	13	3
S_MARA	INHME		Net Contents Unit (ISO Format)	Text (CHAR)	80
S_MARA	INHBR		Gross Contens	Number (NUMC)	13	3
S_MARA	VPREH		Comparison Price Unit	Number (NUMC)	5
S_MARA	EXTWG		External Product Group	Text (CHAR)	80		MDS: OK
S_MARA	MTPOS_MARA		General Item Category Group	Text (CHAR)	80		MDS: OK
S_MARA	BEGRU		Authorization Group	Text (CHAR)	4		MDS: OK
S_MARA	MSTAE		Cross-Plant Product Status	Text (CHAR)	80
S_MARA	MSTDE		Valid-From Date	Date
S_MARA	SERLV		Level of Explicitness for Serial Number	Text (CHAR)	80
S_MARA	QMPUR		Quality Manag. in Procurement Is Active	Text (CHAR)	1
S_MARA	ANIMAL_ORIGIN		Animal Origin	Text (CHAR)	1
S_MARA	ANP		ANP Code	Text (CHAR)	80
S_MARA	BRGEW		Gross Weight	Number (NUMC)	13	3
S_MARA	NTGEW		Net Weight	Number (NUMC)	13	3
S_MARA	GEWEI		Unit of Weight (ISO Format)	Text	80
S_MARA	LAENG		Length	Number (NUMC)	13	3
S_MARA	BREIT		Width	Number (NUMC)	13	3
S_MARA	HOEHE		Height	Number (NUMC)	13	3
S_MARA	MEABM		Unit for Length/Width/Height(ISO Format)	Text (CHAR)	80
S_MARA	VOLUM		Volume	Number (NUMC)	13	3
S_MARA	VOLEH		Volume Unit	Text (CHAR)	80
S_MARA	CAPAUSE		Capacity Usage	Number (NUMC)	15	3
S_MARA	CHML_CMPLNC_RLVNCE_IND		Compliance Relevant	Text (CHAR)	80
S_MARA	KZKFG		Product Is Configurable	Text (CHAR)	1		MDS: OK
S_MARA	BSTME		Order Unit of Measure (ISO Format)	Text (CHAR)	80
S_MARA	EKWSL		Purchasing Value Key	Text (CHAR)	80
S_MARA	VABME		State of Variable Purchase Order Unit	Text (CHAR)	80
S_MARA	BMATN		Internal Product Number	Text (CHAR)	80
S_MARA	MFRPN		Manufacturer Part Number	Text (CHAR)	40
S_MARA	MFRNR		Manufacturer Number	Text (CHAR)	80
S_MARA	MPROF		Manufacturer Part Profile	Text (CHAR)	80
S_MARA	TRAGR		Transportation Group	Text (CHAR)	80
S_MARA	MSTAV		Cross-Distribution Chain Product Status	Text (CHAR)	80
S_MARA	MSTDV		Valid From Date for Status	Date
S_MARA	PMATA		Pricing Reference Product	Text (CHAR)	80
S_MARA	SPROF		Pricing Profile for Variants	Text (CHAR)	80
S_MARA	ALLOW_PMAT_IGNO		Variant Price Allowed	Text (CHAR)	1
S_MARA	SOM_CYCLE		Billing Cycle	Text (CHAR)	80
S_MARA	SOM_CYCLE_RULE		Billing Cycle Determination Rule	Text (CHAR)	80
S_MARA	SOM_TC_SCHEMA		Assignment Schema	Text (CHAR)	80
S_MARA	BBTYP		Assortment List Type	Text (CHAR)	80
S_MARA	SERVV		Service Agreement	Text (CHAR)	80
S_MARA	MAGRV		Product Group: Packaging Materials	Text (CHAR)	80
S_MARA	VHIART		Packaging Product Type	Text (CHAR)	80
S_MARA	ERGEW		Allowed Packaging Weight	Number (NUMC)	13	3
S_MARA	ERGEI		Unit of Allowed Packaging Weight	Text (CHAR)	80
S_MARA	GEWTO		Excess Weight Tolerance for HU	Number (NUMC)	3	1
S_MARA	ERVOL		Allowed Packaging Volume	Number (NUMC)	13	3
S_MARA	ERVOE		Unit of Allowed Packaging Volume	Text (CHAR)	80
S_MARA	KZGVH		Packaging Product Is Closed Packaging	Text (CHAR)	1
S_MARA	VOLTO		Excess Volume Tolerance for HU	Number (NUMC)	3	1
S_MARA	IPRKZ		Period Indicator for Shelf Life	Text (CHAR)	80
S_MARA	RAUBE		Storage Conditions	Text (CHAR)	80
S_MARA	TEMPB		Temperature Conditions Indicator	Text (CHAR)	80
S_MARA	BEHVO		Container Requirements	Text (CHAR)	80
S_MARA	STOFF		Hazardous Product Number	Text (CHAR)	40
S_MARA	ETIAR		Label Type	Text (CHAR)	80
S_MARA	ETIFO		Label Form	Text (CHAR)	80
S_MARA	WESCH		Number of Goods Receipt/Issue Slips	Number (NUMC)	13	3
S_MARA	XGCHP		Indicator: Approved Batch Rec. Required	Text (CHAR)	1
S_MARA	MHDHB		Total Shelf Life	Number (NUMC)	4
S_MARA	MHDRZ		Minimum Remaining Shelf Life	Number (NUMC)	4
S_MARA	SLED_BBD		Indi. for the Shelf Life Expiration Date	Text (CHAR)	80
S_MARA	MHDLP		Storage Percentage	Number (NUMC)	3
S_MARA	RDMHD		Rounding Rule for Calculation of SLED	Text (CHAR)	80
S_MARA	HNDLCODE		Handling Indicator	Text (CHAR)	80
S_MARA	WHMATGR		Warehouse Product Group	Text (CHAR)	80
S_MARA	WHSTC		Warehouse Storage Condition	Text (CHAR)	80
S_MARA	HUTYP_DFLT		Standard Handling Unit Type	Text (CHAR)	80
S_MARA	SERIAL		Serial Number Profile	Text (CHAR)	80
S_MARA	PILFERABLE		Pilferable	Text (CHAR)	1
S_MARA	HAZMAT		Relevant for Hazardous Substances	Text (CHAR)	1
S_MARA	QQTIME		Quarantine Period	Number (NUMC)	3
S_MARA	QQTIMEUOM		Time Unit for Quarantine Period	Text (CHAR)	80
S_MARA	QGRP		Quality Inspection Group	Text (CHAR)	80
S_MARA	HUTYP		Handling Unit Type	Text (CHAR)	80
S_MARA	MAXC		Maximum Capacity	Number (NUMC)	15	3
S_MARA	MAXC_TOL		Overcapacity Tolerance	Number (NUMC)	3	1
S_MARA	TARE_VAR		Variable Tare Weight	Text (CHAR)	1
S_MARA	MAXL		Max. Pack. Length	Number (NUMC)	15	3
S_MARA	MAXDIM_UOM		UoM for Max. Pack. Length (ISO Format)	Text (CHAR)	80
S_MARA	MAXB		Max. Pack. Width	Number (NUMC)	15	3
S_MARA	MAXH		Max. Pack. Height	Number (NUMC)	15	3
S_MARA	RBNRM		Catalog Profile	Text (CHAR)	80
S_MARA	SSTUF		Assortment Grade	Text (CHAR)	80
S_MARA	LSTVZ		Listing Procedure	Text (CHAR)	80
S_MARA	LDVZL		Listing Period Start Date	Date
S_MARA	LDBZL		Listing Period End Date	Date
S_MARA	LSTFL		Listing Procedure	Text (CHAR)	80
S_MARA	LDVFL		Listing Period Start Date	Date
S_MARA	LDBFL		Listing Period End Date	Date
S_MARA	VDVZL		Sales Period Start Date	Date
S_MARA	VDBZL		Sales Period End Date	Date
S_MARA	VDVFL		Sales Period Start Date	Date
S_MARA	VDBFL		Sales Period End Date	Date
S_MARA	WAUSM		Delivery Unit of Measure (ISO Format)	Text (CHAR)	80
S_MARA	WVRKM		Sales Unit of Measure (ISO Format)	Text (CHAR)	80
S_MARA	WMAAB		ABC Indicator	Text (CHAR)	80
S_MARA	WBKLA		Valuation Class	Text (CHAR)	80
S_MARA	WHERL		Country/Region of Origin	Text (CHAR)	80
S_MARA	WHERR		Region of Origin	Text (CHAR)	80
S_MARA	WEKGR		Purchasing Group	Text (CHAR)	80
S_MARA	BWSCL		Source of Supply	Text (CHAR)	80
S_MARA	TAKLV		Tax Classification	Text (CHAR)	80
S_MARA	WLADG		Loading Group	Text (CHAR)	80
S_MARA	WBWSP		Valuation Margin	Number (NUMC)	6	2
S_MARA	PSTATQ		Indicator: Quality	Text (CHAR)	1
S_MARA	PSTATV		Indicator: Sales	Text (CHAR)	1
S_MARA	PSTATL		Indicator: Storage	Text (CHAR)	1
S_MARA	PSTATE		Indicator: Purchasing	Text (CHAR)	1
MAKT - Material Descriptions
S_MAKT	MATNR		Product Number	Text (CHAR)	18		Mandatory
S_MAKT	SPRAS		Language Key	Text (CHAR)	2		Mandatory
S_MAKT	MAKTX		Product Description	Text (CHAR)	40		Mandatory
MARM - Units of Measure for Material
S_MARM	PRODUCT		Product Number	Text (CHAR)	80		Mandatory
S_MARM	MEINH		Alternative Unit of Measure (ISO Format)	Text (CHAR)	80		Mandatory
S_MARM	UMREN		Denominator for Conversion to Base Unit	Number (NUMC)	5		Mandatory
S_MARM	UMREZ		Numerator for Conversion to Base Unit	Number (NUMC)	5		Mandatory
S_MARM	EAN11		GTIN	Text (CHAR)	18
S_MARM	NUMTP		GTIN Category	Text (CHAR)	80
S_MARM	LAENG		Length	Number (NUMC)	13	3
S_MARM	BREIT		Width	Number (NUMC)	13	3
S_MARM	HOEHE		Height	Number (NUMC)	13	3
S_MARM	MEABM		Unit for Length/Width/Height(ISO Format)	Text (CHAR)	80
S_MARM	BRGEW		Gross Weight	Number (NUMC)	13	3
S_MARM	GEWEI		Unit of Weight (ISO Format)	Text (CHAR)	80
S_MARM	VOLUM		Volume	Number (NUMC)	13	3
S_MARM	VOLEH		Volume Unit (ISO Format)	Text (CHAR)	80
S_MARM	CAPAUSE		Capacity Usage	Number (NUMC)	15	3
CLASS - Class Header Data (KLAH)
S_CLASS	PRODUCT		Product Number	Text (CHAR)	18		Mandatory
S_CLASS	CLASS		Class	Text (CHAR)	80		Mandatory
S_CLASS	CLASSTYPE		Class Type	Text (CHAR)	80		Mandatory
S_CHARACT - Characteristic (CABN)
S_CHARACT	PRODUCT		Product Number	Text (CHAR)	80		Mandatory
S_CHARACT	CLASS		Class	Text (CHAR)	80		Mandatory
S_CHARACT	CLASSTYPE		Class Type	Text (CHAR)	80		Mandatory
S_CHARACT	ATNAM		Characteristic Name	Text (CHAR)	80		Mandatory
S_CHARACT	POSNR		Item	Text (CHAR)	3
S_CHARACT	VALUE_CHAR		Character Value	Text (CHAR)	70
S_CHARACT	VALUE_NUMC		Numeric Value	Number (NUMC)	16	16
S_CHARACT	VALUE_DATE		Date	Date
S_CHARACT	VALUE_TIME		Time	Time
S_CHARACT	VALUE_CURR		Currency Value	Number (NUMC)	23	2
S_MLAN - Tax Classification for Material
S_MLAN	PRODUCT		Product Number	Text (CHAR)	80		Mandatory
S_MLAN	ALAND		Country/Region	Text (CHAR)	80		Mandatory
S_MLAN	TATYP1		Tax Category 1	Text (CHAR)	80		Mandatory
S_MLAN	TAXM1		Tax Classification 1	Text (CHAR)	80		Mandatory
S_MLAN	TATYP2		Tax Category 2	Text (CHAR)	80
S_MLAN	TAXM2		Tax Classification 2	Text (CHAR)	80
S_MLAN	TATYP3		Tax Category 3	Text (CHAR)	80
S_MLAN	TAXM3		Tax Classification 3	Text (CHAR)	80
S_MLAN	TATYP4		Tax Category 4	Text (CHAR)	80
S_MLAN	TAXM4		Tax Classification 4	Text (CHAR)	80
S_MLAN	TATYP5		Tax Category 5	Text (CHAR)	80
S_MLAN	TAXM5		Tax Classification 5	Text (CHAR)	80
S_MLAN	TATYP6		Tax Category 6	Text (CHAR)	80
S_MLAN	TAXM6		Tax Classification 6	Text (CHAR)	80
S_MLAN	TATYP7		Tax Category 7	Text (CHAR)	80
S_MLAN	TAXM7		Tax Classification 7	Text (CHAR)	80
S_MLAN	TATYP8		Tax Category 8	Text (CHAR)	80
S_MLAN	TAXM8		Tax Classification 8	Text (CHAR)	80
S_MLAN	TATYP9		Tax Category 9	Text (CHAR)	80
S_MLAN	TAXM9		Tax Classification 9	Text (CHAR)	80
STXH - SAPscript Text Header
	TDOBJECT		Text Object (e.g., MATERIAL, VENDOR, etc.)	CHAR	10
STXH	TDNAME		Text Name (object key, e.g., material number, PO number)	CHAR	70
STXH	TDID		Text ID (text type, e.g., F01 = Header Text, L01 = Item Text)	CHAR	4
STXH	TDSPRAS		Language Key	LANG	1
STXH	TDTITLE		Title of the text (optional short description)	CHAR	60
STXH	TDFUSER		Last Changed by (user)	CHAR	12
STXH	TDFDATE		Date of Last Change	DATS	8
STXH	TDFTIME		Time of Last Change	TIMS	6
STXH	TDVERSION		Version Number of Text	NUMC	4
STXH	TDLOCK		Lock Indicator	CHAR	1
STXH	TDTRANSTAT		Translation Status	CHAR	1
STXH	TDOSPRAS		Original Language	LANG	1
STXL - SAPscript Text File (Cluster)
STXL	RELID		Cluster Area (ID of cluster; for texts usually "TX")	Text (CHAR)	2
STXL	TDOBJECT		Text Object (e.g., MATERIAL, VENDOR, etc.)	Text (CHAR)	10
STXL	TDNAME		Text Name (object key, e.g., material number, purchase order)	Text (CHAR)	70
STXL	TDID		Text ID (text type, e.g., F01 = header text, L01 = item text)	Text (CHAR)	4
STXL	TDSPRAS		Language Key	Language (LANG)	1
STXL	SRTF2		Sort number (used to split large texts across several cluster entries)	Numeric (NUMC)	3
STXL	CLUSTR		Length field for cluster (internal, technical)	Integer (INT2)	5
STXL	CLUSTD		Length field for cluster (internal, technical)	Integer (INT2)	5
STXL	VARTEXT		Compressed text data (the actual long text, stored in cluster format)	(RAW)	255

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
001	High	Remove Duplicated Entries - Services	Remove duplicates based on Service Description + UoM + Service Group (?)		PF2 / WP2
002	High	Remove Duplicated Entries - Materials	Check for materials with same Long/Short Description Check Old Material Number field Check Materials with same Manufacturer Part Number Check Source List/PIR for identical set ups Check BOMs for identical components Where duplicates found, check if either has no activity		PF2 / WP2
003	Medium	Validation of Service Group, UoM, and active status in target config	Validate existence of Service Group, UoM, and active status in target config		PF2 / WP2
004	High	English description missing or EN description not English language	All materials require English description by default, so need to be provided if missing. Current EN descriptions not in English language need to be translated. The field details for description are the following: Field Name / Data Element / Domain: MAKTX		PF2 / WP2
005	High	Description format	Material descriptions must adhere to S4 standardization so no special characters, and must not exceed character limit		PF2 / WP2
006	High	UoM alignment	All material UoMs to adhere to S4 standardization. Confirmation regarding EA/PC format.		PF2 / WP2

Conversion Process

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

 

Data Privacy and Sensitivity
N/A

Data Merging / Data Consolidation

The data merging is restricted to the Materia Types Z720 / ZB20 / ZDIE being Deduplicated/Merged into ZSER in combination with the Service Master.

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
	All material status not defined as "EXCLUDED" should be included in scope, otherwise must be included in scope (independently of the status)
001	Do not extract records where ASMD-LVORM = X (record deleted)	Syniti Team
002	Do not extract records where ASMD-MATKL (Material Group) is set as out of scope	Syniti Team
003	Do not extract records where ASMD-MLANG (Main Language)  is set as out of scope	Syniti Team
004	Do not extract records where ASMD-BKLAS (Valuation Class)  is set as out of scope	Syniti Team
005	Service Group (ASMD-ASBGR) must exist in customizing table T023	Syniti Team
006	All Services and Materials (defined as services) that have been created on the last 36 months are relevant to be migrated	Syniti Team
007	All Services and Materials (defined as services) that have a Purchase Order created in the last 6 months or has a goods receipt on the last 6 months, must be included	Syniti Team
008	All Services and Materials that are marked for Deletion should be excluded	Syniti Team
009	All material status not defined as EXCLUDED should be included in scope, otherwise must be included in scope (independently of the status)	Syniti Team
	Inactive Materials

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
1	Obtain DCT Sign-off from Business	SyWay S2P Data Team
2	<OPEN TOPIC>	SyWay S2P Data Team
3	Review and Validate Error and Preload Reports	SyWay S2P Data Team
4	Generate Load Files	SyWay S2P Data Team

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
Material Number	Mapping of legacy Material Number to target system value
Material Type	Mapping of legacy Material Types to target system value
Material Group	Mapping of legacy Material Groups to target system value
Product Hierarchy	Mapping of legacy Product Hierarchies to target system value

Transformation - Special Requirements

Custom Fields - to be identified the usage of those and whether they will be moved into S4/Hana

Tables: MARA / MAKT

Custom Unit of Measures - to be identified the usage of those and whether they will be moved into S4/Hana

Transformation Dependencies

List the steps that need to occur before transformation can commence

Item #	Step Description	Team Responsible
1	Ensure DCT tables completeness	SyWay S2P Data Team
2	Value Mappings are according to the latest design - <List of Value Mappings>	SyWay S2P Data Team
3	Mapping Tables must be properly updated	Syensqo Data Team

Pre-Load Validation

Project Team

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

Completeness

Task	Action
Verify Record Count	SyWay S2P Data Team to verify that the total number of relevant records from the  DCT is equal to the total number of records in the Preload and Load Sheets.
Mandatory Fields	Check mandatory fields for completeness
Field Format	Validate field formats (text length, data types)
Service Group and UOM	Confirm Service Group and UoM exist in target system
Duplicated Records	Check for duplicates before load

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

The loading will be executed using LSMW with the BAPI BAPI_SERVICE_CREATE, as there is no standard object available in the SAP Migration Cockpit for Service Master data.

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

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	Check record count against DCT and load file.
	Verify random samples in S/4 using transaction AC03.
	Ensure data appears in standard search helps (e.g., ML81N).
	Log any mismatches or errors for remediation.

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
title	specific details of what and how the task needs to be performed e.g. which reports are being used etc.

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

Workflow history