Status	`` In Progress
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 IT---

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.

---Process Flow---

1) Legacy systems
2) Extraction methods and file types
3) Scope relevancy criteria
4) Target structure/ Rules
5) MDS links
6) Cleansing rules
- 6a) Cleansing reports with technical information
- 6b) Profiling
- 6c) Deduplication (with technical details of Table-Fields, Conditions)
- 6d) Frequency of running reports
7) Transformation - and for this DOMD template must be populate and final version of DOMD template should be copied to Transformation section in CSpecs
8) Configuration/Value mapping file link
9) Value Mappings
10) Load template link
11) Loading method
12) Loading sequence or dependency
13) Pre load validation
14) Post load validation
15) any Exceptions
16) Signoff

--- 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:

Materials created as Services – Material Master records with service-related material types (PF2 = DIEN, Z710, Z720, Z732, ZB10, ZB20, ZESE, ZFS1, ZPSE, ZU10, ZU20 or WP2 = DIEN, ZDIE) ==> main table = MARA
Service Master Data – Maintained in SAP ECC ==> main table = ASMD

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 (ASMD) and Materials-as-Services records (MARA).
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 - 020

The Service Master Records (ASMD) and the Material Master Records created as Services (MARA with Service Material Types such as DIEN or equivalent) will be extracted and collected via the Data Collection Template (DCT).

An initial extract of the relevant data will be provided in Google Sheet format to support the business in reviewing and deciding which records should be included in scope for migration from the Source Systems.

Any additional Service data required to support the Lean Services design may also be added directly in the DCT by the business.

A data review, harmonization, and standardization exercise will be carried out across both Service Master and Service-as-Material records. This includes:

-Consolidation of overlapping entries.-Standardization of descriptions, units of measure, and language usage.
- Identification and removal of obsolete or redundant Services.
- Ensuring consistency in classification and purchasing-related fields.
- The final, validated dataset will represent the merged and standardized Services to be migrated into SAP S/4HANA Lean Services.

924 Materials (MARA)

34.756 Services (ASMD)

S4H

924 Materials (MARA)

34.756 Services (ASMD)

WP2 - 400

355 Materials (MARA)

624 Services(ASMD)

S4H

355 Materials (MARA)

624 Services(ASMD)

WPX

This WPX system (US base) is out of scope for this functional specification.

Relevancy Rules

***SERVICES AS MATERIALS (MARA TABLE) - System PF2/WP2

Relevant Tables for the Extraction

Groups	Table	Purpose	Key fields (core)	Link to MARA	Typical filters / notes
Group A	MARA	Central Material Master (type, base UoM, dimensions, weights, creation date, status flags).	MANDT, MATNR	--- Root Table	Filter by client (MANDT), material type (MTART), deletion flag (LVORM), etc. In ECC MATNR is 18-char (leading zeros); in S/4 it’s up to 40.
	MAKT	Language-dependent short descriptions (MAKTX).	MANDT, MATNR, SPRAS	MAKT.MATNR = MARA.MATNR	Filter SPRAS (e.g., ‘E’, ‘F’…), or pick “best language”. MARA → MAKT: MAKT.MANDT = MARA.MANDT and MAKT.MATNR = MARA.MATNR (1 material : many language texts).
	MARM	Alternative UoMs and conversion factors.	MANDT, MATNR, MEINH	MARM.MATNR = MARA.MATNR	Base UoM is MARA.MEINS; conversions via UMREZ/UMREN. MARA → MARM: MARM.MANDT = MARA.MANDT and MARM.MATNR = MARA.MATNR (1 : many UoMs).
	MEAN	EAN/UPC/GTINs for a material (often per UoM).	MANDT, MATNR, EAN11 (+ MEINH)	MEAN.MATNR = MARA.MATNR	Join to MARM on MATNR+MEINH when you need UoM-specific GTINs. MARA → MEAN: MEAN.MANDT = MARA.MANDT and MEAN.MATNR = MARA.MATNR (1 : many GTINs). Optional: if MEAN.MEINH is populated, it also corresponds to MARM.MEINH for that material.
	STXH	SAPscript long-text header for material texts.	TDOBJECT, TDNAME, TDID, TDSPRAS	TDOBJECT='MATERIAL' and TDNAME = MATNR (padded)	Typical TDIDs: ‘GRUN’ (Basic Data), ‘SALES’, ‘PURCH’. MARA ↔ STXH/STXL (long texts): STXH.TDOBJECT = 'MATERIAL' and STXH.TDNAME = MARA.MATNR (padded); STXL holds the lines for the same (TDOBJECT, TDNAME, TDID, TDSPRAS) key. Common TDIDs for Basic Data: GRUN (basic), SALES, PURCH.
	STXL	SAPscript long-text lines (content).	(cluster key matching STXH)	via STXH keys	Read/display via text functions; storage is clustered. MARA ↔ STXH/STXL (long texts): STXH.TDOBJECT = 'MATERIAL' and STXH.TDNAME = MARA.MATNR (padded); STXL holds the lines for the same (TDOBJECT, TDNAME, TDID, TDSPRAS) key. Common TDIDs for Basic Data: GRUN (basic), SALES, PURCH.
Group B	CABN	Characteristic definitions (metadata: name ATNAM, data type, length, value domain).	ATINN (internal), ATNAM	via ATINN (through KSML/AUSP)	Use to resolve internal ATINN → external ATNAM. KSML → CABN (characteristic catalog): KSML.ATINN = CABN.ATINN (characteristic technical definition).
	CABNT	Characteristic texts (language-dependent).	ATINN, SPRAS	via CABN.ATINN	Bring characteristic descriptions by language. CABN → CABNT (characteristic texts): CABNT.ATINN = CABN.ATINN (language-dependent).
	CAWN	Predefined values for a characteristic (for value-lists).	ATINN, ATZHL (+ ATWRT)	via CABN.ATINN	One row per allowed value; position ATZHL is the value key. CABN → CAWN → CAWNT (value lists and texts): CAWN.ATINN = CABN.ATINN; each allowed value is keyed by ATZHL. CAWNT provides texts per (ATINN, ATZHL, SPRAS).
	CAWNT	Texts for the predefined values.	ATINN, ATZHL, SPRAS	via CAWN(ATINN,ATZHL)	Language-dependent value labels. Use the same logic of CAWN
	KLAH	Class header (e.g., class type 001 for material classes).	CLINT (internal), KLART, CLASS	via CLINT (to KSML/KSSK)	Filter KLART='001' for material classification. KSSK → KLAH (class header): KSSK.CLINT = KLAH.CLINT and KLAH.KLART = '001'.
	KLAT	Class texts (language-dependent).	CLINT, SPRAS	via KLAH.CLINT	Get the class description. KLAH → KLAT (class texts): KLAT.CLINT = KLAH.CLINT (language-dependent class names).
	KSML	Class ↔ Characteristic assignments.	CLINT, ATINN	via KLAH.CLINT & CABN.ATINN	Which characteristics belong to a class. KLAH → KSML (class ↔ characteristic): KSML.CLINT = KLAH.CLINT (which characteristics the class contains).
	KSSK	Object (material) ↔ Class assignments.	OBJEK, CLINT, KLART	KSSK.OBJEK = MARA.MATNR(padded)	Filter OBTAB='MARA', KLART='001'. OBJEK = material number with leading zeros (ECC: 18 chars). MARA → KSSK (object ↔ class): KSSK.OBJEK = padded(MARA.MATNR) and KSSK.KLART = '001'; each row links a material to a class (KSSK.CLINT).
	AUSP	Assigned characteristic values for an object.	OBJEK, ATINN, KLART (+ ATWRT/ATFLV)	AUSP.OBJEK = MARA.MATNR(padded)	MARA → AUSP (assigned values): AUSP.OBJEK = padded(MARA.MATNR) and AUSP.KLART = '001'; AUSP.ATINN = CABN.ATINN; value stored in AUSP.ATWRT (char) or AUSP.ATFLV (numeric).

Execution Logic:

>>>========================================================================================

SINGLE

- All materials created in the previous 6 months will be included unless flagged for deletion.

GLOBAL
We will only include materials that are extended to the following:
- We will only include plants that are in-scope
- We will only include company codes that are in-scope
- We will only include purchasing orgs that are in-scope
- We will only include sales orgs that are in-scope

===========================================================================================

TO BE EXCLUDED

Evaluated in this exact order; first match wins:

Scope prerequisites

- Client: MANDT = (PF2 = '020' or WP2 = '400')
- Material types in scope (MARA-MTART): (PF2 = DIEN, Z710, Z720, Z732, ZB10, ZB20, ZESE, ZFS1, ZPSE, ZU10, ZU20 or WP2 = DIEN, ZDIE)
- Plant in scope (MARC-WERKS): Material must be extended to at least one plant in
- Exclusion indicator (MARA-MSTAE): exclude materials with the following status (PF2 = Z3/Z4/ZZ; WP2 = Z0).

1) EXCLUDED (No activity, when >= 6m and <=3y) ← targeted recency rule

2) EXCLUDED (Obsolete text)
If MAKT-MAKTX indicates obsolescence:
- contains word OBSOLETE or DELETED, or
- after removing * and spaces, contains OBS.

3) EXCLUDED (MSTAE)
System-specific status code (PF2: Z3/Z4/ZZ; WP2: Z0).

4) EXCLUDED (LVORM)
If LVORM = 'X' and there is no open order within the last 3 years across SO/PO/PP:
HasOpenSO3Y = 0 AND HasOpenPO3Y = 0 AND HasOpenPP3Y = 0 exclude entry

5) EXCLUDED (No plant in scope)
If HasInScopePlant = 0 (and @RequirePlantExtension = 1).

6) EXCLUDED (No activity, 6m-3y) ← targeted recency rule
Exclude when all are true:
- Created window: ERSDA_date <= @From6Months and ERSDA_date >= @From3Years, and
- No 3y activity: HasSO3Y = 0 AND HasPO3Y = 0 AND HasPP3Y = 0.

7) EXCLUDED Material Group Mapping (ZZM_GPS_MATKL)
Match MARA‑MATKL to ZZM_GPS_MATKL‑MATKL with ZZMGOODSER='S'. If a match exists and LOEVM is not initial, the record is excluded.

If none of the above exclusions apply, the material is included (see topic 4 for more details).

===========================================================================================

TO BE INCLUDED

Scope prerequisites

- Client: MANDT = (PF2 = '020' or WP2 = '400')
- Material types in scope (MARA-MTART): (PF2 = DIEN, Z710, Z720, Z732, ZB10, ZB20, ZESE, ZFS1, ZPSE, ZU10, ZU20 or WP2 = DIEN, ZDIE)
- Plant in scope (MARC-WERKS): Material must be extended to at least one plant in
- Exclusion indicator (MARA-MSTAE): exclude materials with the following status (PF2 = Z3/Z4/ZZ; WP2 = Z0).

2) Time windows (used everywhere)

- Materials with <= 6 month since its creation, don't need to have any activity (PurchOrder, SalesOrder, Production)
- Newness: @Today – 6 months

3) Activity & Open definitions (last 3 years)

Sales Orders (SO)
- Activity (HasSO3Y): exists VBAP line joined to VBAK with VBAK.ERDAT >= @From3Years.
- Open (HasOpenSO): line is open if any:
- VBUK.GBSTK NOT IN ('C','D'), or
- VBUP.GBSTA NOT IN ('C','D'), or
- no VBUP and VBAP.ABGRU = '' (blank).
- Open within 3y (LVORM override): same open condition AND VBAK.ERDAT >= @From3Years >>> HasOpenSO3Y.

Purchase Orders (PO)
- Activity (HasPO3Y): EKKO header date COALESCE(AEDAT,BEDAT) >= @From3Years on a matching EKPO.
- Open (HasOpenPO): EKPO.ELIKZ <> 'X' AND EKPO.LOEKZ <> 'X'.
- Open within 3y (LVORM override): open AND COALESCE(AEDAT,BEDAT) >= @From3Years >>> HasOpenPO3Y.

Production Orders (PP)
- Activity (HasPP3Y): COALESCE(AUFK.ERDAT, AFKO.GLTRP) >= @From3Years on a matching AFPO.
- Open (HasOpenPP): AUFK.LOEKZ <> 'X' AND (AFKO.GLTRP IS NULL OR AFKO.GLTRP >= @Today).
- Open within 3y (LVORM override): open AND COALESCE(AUFK.ERDAT, AFKO.GLTRP) >= @From3Years >>> HasOpenPP3Y.

4) Inclusion triggers (exceptional list)

- An exception list should be available, and if the material is in the manual table, it must be included.

~~5) Available Stock (note this migration regards SERVICES, therefore this rule should be treated as an exceptional situation)~~

If any of the below table-fields are greater than 0 and the material has current stock, it should be included for migration, even if other activity rules (PO, SO, PP) are not met. This has priority over all other rules.

~~- Check if Storage Location Stock (MARD) <> 0~~
MARD-LABST = Unrestricted stock
MARD-INSME = Stock in quality inspection
MARD-SPEME = Blocked stock
MARD-UMLME = Stock in transfer (to another storage location)

~~- Special Stocks (as needed in migration scope)~~
~~MKOL-KALAB = Consignment stock (vendor consignment)~~
~~MSLB-LABST = Special stock with customer (sales order stock)~~
~~MSKA-LABST = Sales order stock~~
~~MSPR-LABST = Project stock~~

6) Final filters before output

Even if a row/material has an INCLUDED reason, it must still pass all of these steps:

- IsObsoleteText = 0
- ExcludeByMSTAE = 0
- Not (LVORM='X' AND HasOpenSO3Y=0 AND HasOpenPO3Y=0 AND HasOpenPP3Y=0)
- And (IsForceIncluded = 1 OR EligibilityReason LIKE 'INCLUDED%')

========================================================================================<<<

***SERVICES MASTER DATA (ASMD TABLE) - System PF2/WP2

Relevant Tables for the Extraction

Groups	Table	Purpose	Key fields (core)	Link to ASMD	Typical filters / notes
Group A	ASMD	Core Service Master under evaluation (creation date, deletion flag, basic attributes).	MANDT, ASNUM, ERDAT (ERSDA), AEDAT, LVORM (LOEKZ), MATKL, MEINS	— Root table	Filter by client (MANDT); deletion flag is later overridden if there is open activity within 3 years.
Group A	ASMDT	Language-dependent short descriptions (used for “obsolete/deleted” text heuristic).	MANDT, ASNUM, SPRAS, KTEXT	ASMDT.ASNUM = ASMD.ASNUM	Choose “best language” (e.g., E). Detect “OBSOLETE/DELETED/OBS” (case-insensitive; trim spaces/asterisks).
Group B	EKKO	Purchase Order header (dates; organizational scope: BUKRS, EKORG).	MANDT, EBELN, BUKRS, EKORG, AEDAT/BEDAT	Via EKPO → ESLL to reach ASMD	Filter by client. Dates used for “last 3 years” window. Org scope checked against in-scope BUKRS/EKORG lists.
	EKPO	PO item lines (service items, open/closed flags, optional plant).	MANDT, EBELN/EBELP, PSTYP, ELIKZ, LOEKZ, WERKS, PACKNO	EKPO.PACKNO → ESLL.PACKNO → ESLL.SRVPOS = ASMD.ASNUM	PSTYP = ‘9’ (service). Open item = ELIKZ ≠ ‘X’ and LOEKZ ≠ ‘X’. WERKS used only if plant scoping is enforced.
	ESLL	Service package lines; bridges PO/SES packages to ASMD (service number).	MANDT, PACKNO, SRVPOS (service number)	ESLL.SRVPOS = ASMD.ASNUM; ESLL.PACKNO links to EKPO/ESSR	Essential link table; no direct date filters here.
	ESSR	Service Entry Sheet header (evidence of recent/open SES activity).	MANDT, PACKNO, BUDAT, LOEKZ, EBELN, EBELP	ESSR.PACKNO → ESLL.PACKNO → ESLL.SRVPOS = ASMD.ASNUM	“Recent” if BUDAT ≥ Today − 3 years. Open if LOEKZ ≠ ‘X’. Org scope derived via EKKO/EKPO on EBELN/EBELP (LEFT JOIN).

Execution Logic:

>>>========================================================================================

SINGLE

- All materials created in the previous 6 months will be included unless flagged for deletion.

GLOBAL
We will only include materials that are extended to the following:
- We will only include plants that are in-scope (is possible that field WERKS is empty, and this is in scope)
- We will only include company codes that are in-scope
- We will only include purchasing orgs that are in-scope
- We will only include sales orgs that are in-scope

===========================================================================================

SINGLE

- All services created in the previous 6 months (ASMD-ERDAT >= @From6Months) are included unless excluded by LVORM/MSTAE/text rules. (Services are client-level; no plant extension applies.)

GLOBAL

- Client: MANDT IN (PF2-020, WP2-400)

- Company codes / purchasing orgs in scope: restrict via your in-scope lists, applied through the documents that reference the service (POs/Entry Sheets).

- Purchasing Organization in scope: restrict via your in-scope lists, applied through the documents that reference the service (POs/SOs/Entry Sheets).

===========================================================================================

TO BE EXCLUDED

Evaluated in this exact order; first match wins:

1) EXCLUDED (No activity, when >= 6m and <=3y) ← targeted recency rule

2) EXCLUDED (Obsolete text)
Obsolete text detected in ASMDT (OBSOLETE / DELETED / (OBS) / “ obs ”).

3) EXCLUDED (MSTAE)
System-specific status code (PF2: Z3/Z4/ZZ; WP2: Z0).

4) EXCLUDED (LVORM)
Deletion flag (LVORM=X) and no open PO/SES in the last 3 years.

5) EXCLUDED No activity and AEDAT between 6 months and 3 years ago.

6) EXCLUDED Material Group Mapping (ZZM_GPS_MATKL)

Match ASMD‑MATKL to ZZM_GPS_MATKL‑MATKL with ZZMGOODSER='S'. If a match exists and LOEVM is not initial, the record is excluded. The solution publishes MAPPED/UNMAPPED reports for governance visibility.

If none of the above exclusions apply, the material is included (see topic 4 for more details).

===========================================================================================

TO BE INCLUDED

1) INCLUDED Any material available in an OPEN PO/SES (even in case the material is marked as deletion)

2) INCLUDED AEDAT (last change) within the last 6 months.

3) INCLUDED Any PO/SES activity within 3 years.

4) INCLUDED Default pass (no negatives matched).

========================================================================================<<<

*** Canonical Key & Duplication Detection

Deduplication of records from Material as Service (MARA) and Service Master (ASMD) tables. Evaluated in this exact order; first match wins:

	Table - MARA Oriented	International Version	Description
Sequency	Table	International Version	Description
1	ASMD	Text/Description Matching	Compare ASMD-KTEXT (service description) vs. MAKT-MAKTX (material description).
2	ASMD	Unit of Measure Harmonization	ASMD-MEINS vs. MARA-MEINS (ensure consistency).
3	ASMD	Language-Dependent Texts	Check for alignment in key languages (EN, FR, DE, PT, etc.).
4	ASMD	Fuzzy/Exact Match Rules	Normalize description strings (remove stop-words, punctuation, upper/lowercase). Apply fuzzy matching thresholds (e.g., 90%) to detect duplicates between ASMD & MARA.
1	MARA	Canonical Key & Core Attributes	Use MATNR (normalized/padded), MTART=DIEN, MEINS, MATKL, BISMT (old material no.). Build canonical keys and compare base UoM, material group, and legacy numbers across systems.
2	MAKT	Text/Description Matching	Compare short descriptions across languages; pick best language (e.g., EN > FR > DE > …), normalize text (case, punctuation, stop-words), and apply fuzzy/exact thresholds to detect duplicates.
3	STXH/STXL	Long-Text Alignment	Retrieve material long texts (TDOBJECT=‘MATERIAL’, TDNAME=MATNR padded). Normalize and compare paragraphs to consolidate duplicates with different short texts but same detailed content.
4	MARM	Unit-of-Measure Harmonization	Align base/alternate UoMs and conversion factors; deduplicate only if UoM sets are compatible (UMREZ/UMREN); flag conflicts for review. The verification of this table must be combined with
5	MEAN	GTIN/EAN Cross-Check	Use EAN11/GTIN as high-confidence match key (often per UoM). Detect 1:n GTIN-to-material issues and reconcile where GTINs collide across systems.
8	AUSP / INOB / CABN / CAWN / CAWNT(if used)	Classification Fingerprint	If classification is used, compare class/characteristic values as a strong dedup signal (same class & equal value set ⇒ higher confidence). Helps separate near-synonyms.
9	EINA / EINE	Vendor Catalog Signals	Vendor material numbers/descriptions in Info Records can corroborate duplicates (same vendor ref across systems).
10	MVKE	Sales View Consistency	If sales data exists, use product hierarchy and status as soft features; avoid merging items intentionally separated for commercial reasons.
11	MARC	Plant Extension Overlap	Plant assignments can be used as a weak feature (same service used in same plants) and for post-merge impact checks.

	Table - ASMD Oriented	International Version	Description
1	ASMD	Canonical Key & Core Attributes	Use ASNUM (normalized), MEINS, MATKL, ERDAT/AEDAT, LVORM. Build canonical keys and compare base UoM and service group across systems. Compare ASMD-KTEXT (service description) vs. MAKT-MAKTX (material description).
2	ASMDT	Text/Description Matching	Compare language-dependent short descriptions (KTEXT) across locales; pick a “best language” (e.g., EN ), normalize text (case, punctuation, stop-words), then run exact/fuzzy thresholds to detect duplicates.
3	STXH / STXL	Long-Text Alignment	Retrieve service long texts (SAPscript TDOBJECT = 'SERV'; typical TDIDs like GRUN). Normalize and compare paragraphs to catch duplicates with similar detailed content but differing short texts.
6	AUSP / INOB / CABN / CAWN / CAWNT (if used)	Classification Fingerprint	When services are classified, compare class/characteristic values (class type for services per your template) as a strong dedup signal—same class & equal value set ⇒ higher confidence.
7	EINA / EINE (optional)	Vendor Catalog Signals	Vendor service numbers/descriptions in Info Records can corroborate duplicates across systems when texts differ or UoMs are inconsistent.

...

Additional Information

Extraction Methods and File Types

Data is Extracted and Transformed by Syniti ADM, the stagging area of the Migration Cockpit is updated.

Multi-language Requirement

For all Lean Services in the target S/4HANA system, the default description will be maintained 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 supports all ISO languages, ensure that all standard languages are considered in scope.

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

N/A.

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.
- The decided loading tool is called 'Service Product' and is available on the migration cockpit

Deduplication Rules

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 mentioned below 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.

SYSTEM	Rule ID	Semantic Rule
PF2	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
	SR02	Deduplication of Services Materials (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.
	SR03	Deduplication of Services between Material Master - Service (MARA oriented) X Service Master (ASMD oriented) In order to proceed with this step, apply the selection criteria below: If same service exists in both tables (MARA and ASMD): Keep one representation (normally the Material as Lean Service) and retire ASMD. Check using the fields MAKTX and MEINS If service exists only in MARA: Retain and convert as Lean Service (if material type = in-scope). If service exists only in ASMD: Assess usage — migrate as Lean Service Material or exclude if obsolete. If neither is used in recent years: Exclude.

Target Design

The technical design of the target for this conversion approach.

To be decided what to do with the Z Fields below:

Source System	Source Table	Source Field	Long Description	Expectation
PF2	ASMD	ZZMBISMT	This fields regards the Old Service Number	To be decided what to do with the source field

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.

Source Field Information

Transform Rules

Target Field Information

Sequence

Technical Source Table

Field Name

Technical Source Field

Field Format

Field Length

Comments

Mapping Type

Transform Rule or Default Value

Validation Rule

Comments

Dataload Template

Sheet Name

Group

Field Description

Business Description

Check Table

Business Mandatory
Y/N/C

System Mandatory
Y/N/C

Type

Length

Decimal

Sap Table Name

Sap Field Name

MARA - Material Basic Data

MAKT - Material Descriptions

MARA

MATNR

Product Number

Text (CHAR)

18

Product Number

Material Number

YES

Text (CHAR)

18

S_MARA

MATNR

MARA

MTART

Product Type

Text (CHAR)

80

Mandatory

Fixed Value

Default Value = 'ZSER'

Product Type

YES

Text (CHAR)

80

S_MARA

MTART

MARA

ATTYP

Product Category

Text (CHAR)

80

Mandatory

Product Category

YES

Text (CHAR)

80

S_MARA

ATTYP

MARA

SATNR

Configuration Product for Retail Variant

Text (CHAR)

80

Configuration Product for Retail Variant

YES

Text (CHAR)

80

S_MARA

SATNR

MARA

MATKL

Product Group (material group)

Text (CHAR)

80

Mandatory

Conversion

Use the mapping table to apply the proper data conversion

Product Group

YES

Text (CHAR)

80

S_MARA

MATKL

MARA

MBRSH

Industry Sector

Text (CHAR)

80

Mandatory

Fixed Value

Default Value = 'M'

Industry Sector

YES

Text (CHAR)

80

S_MARA

MBRSH

MARA

MAKTX

Description

Text (CHAR)

40

Mandatory

Description

YES

Text (CHAR)

40

S_MARA

MAKTX

MARA

SPRAS

Language Key

Text (CHAR)

80

Mandatory

Language Key

YES

Text (CHAR)

80

S_MARA

SPRAS

MARA

MEINS

Base Unit of Measure (ISO Format)

Text (CHAR)

80

Mandatory

Conversion

Use the mapping table to apply the proper data conversion

Base Unit of Measure (ISO Format)

YES

Text (CHAR)

80

S_MARA

MEINS

MARA

AENNR

Change Number

Text (CHAR)

80

Change Number

NO

Text (CHAR)

80

S_MARA

AENNR

MARA

REVLV

Revision Level

Text (CHAR)

80

Revision Level

NO

Text (CHAR)

80

S_MARA

REVLV

MARA

EAN11

GTIN

Text (CHAR)

18

GTIN

NO

Text (CHAR)

18

S_MARA

EAN11

MARA

NUMTP

GTIN Category

Text (CHAR)

80

GTIN Category

NO

Text (CHAR)

80

S_MARA

NUMTP

MARA

SPART

Division

Text (CHAR)

80

Division

NO

Text (CHAR)

80

S_MARA

SPART

MARA

BISMT

Old Product Number

Text (CHAR)

40

Old Product Number

NO

Text (CHAR)

40

S_MARA

BISMT

MARA

PRDHA

Product Hierarchy

Text (CHAR)

80

Product Hierarchy

NO

Text (CHAR)

80

S_MARA

PRDHA

MARA

BRAND_ID

Brand

Text (CHAR)

80

Brand

NO

Text (CHAR)

80

S_MARA

BRAND_ID

MARA

XCHPF

Batch Management Required Ind.

Text (CHAR)

1

Batch Management Required Ind.

NO

Text (CHAR)

1

S_MARA

XCHPF

MARA

MLGUT

Has Empties

Text (CHAR)

1

Has Empties

NO

Text (CHAR)

1

S_MARA

MLGUT

MARA

DATAB

Valid From

Date

10

Valid From

NO

Date

10

S_MARA

DATAB

MARA

LIQDT

Deletion Date

Date

10

Deletion Date

NO

Date

10

S_MARA

LIQDT

MARA

KUNNR

Competitor

Text (CHAR)

80

Competitor

NO

Text (CHAR)

80

S_MARA

KUNNR

MARA

NORMT

Industry Standard Description

Text (CHAR)

18

Industry Standard Description

NO

Text (CHAR)

18

S_MARA

NORMT

MARA

GROES

Size/Dimensions

Text (CHAR)

32

Size/Dimensions

NO

Text (CHAR)

32

S_MARA

GROES

MARA

LABOR

Laboratory / Design Office

Text (CHAR)

80

Laboratory / Design Office

NO

Text (CHAR)

80

S_MARA

LABOR

MARA

INHAL

Net Contents

Number (NUMC)

13

Net Contents

NO

Number (NUMC)

13

S_MARA

INHAL

MARA

INHME

Net Contents Unit (ISO Format)

Text (CHAR)

80

Net Contents Unit (ISO Format)

NO

Text (CHAR)

80

S_MARA

INHME

MARA

INHBR

Gross Contens

Number (NUMC)

13

Gross Contens

NO

Number (NUMC)

13

S_MARA

INHBR

MARA

VPREH

Comparison Price Unit

Number (NUMC)

5

Comparison Price Unit

NO

Number (NUMC)

5

S_MARA

VPREH

MARA

EXTWG

External Product Group

Text (CHAR)

80

External Product Group

NO

Text (CHAR)

80

S_MARA

EXTWG

MARA

MTPOS_MARA

General Item Category Group

Text (CHAR)

80

General Item Category Group

NO

Text (CHAR)

80

S_MARA

MTPOS_MARA

MARA

BEGRU

Authorization Group

Text (CHAR)

4

Authorization Group

NO

Text (CHAR)

4

S_MARA

BEGRU

MARA

MSTAE

Cross-Plant Product Status

Text (CHAR)

80

Cross-Plant Product Status

NO

Text (CHAR)

80

S_MARA

MSTAE

MARA

MSTDE

Valid-From Date

Date

Valid-From Date

NO

Date

10

S_MARA

MSTDE

MARA

SERLV

Level of Explicitness for Serial Number

Text (CHAR)

80

Level of Explicitness for Serial Number

NO

Text (CHAR)

80

S_MARA

SERLV

MARA

QMPUR

Quality Manag. in Procurement Is Active

Text (CHAR)

1

Quality Manag. in Procurement Is Active

NO

Text (CHAR)

1

S_MARA

QMPUR

MARA

ANIMAL_ORIGIN

Animal Origin

Text (CHAR)

1

Animal Origin

NO

Text (CHAR)

1

S_MARA

ANIMAL_ORIGIN

MARA

ANP

ANP Code

Text (CHAR)

80

ANP Code

NO

Text (CHAR)

80

S_MARA

ANP

MARA

BRGEW

Gross Weight

Number (NUMC)

13

Gross Weight

NO

Number (NUMC)

13

S_MARA

BRGEW

MARA

NTGEW

Net Weight

Number (NUMC)

13

Net Weight

NO

Number (NUMC)

13

S_MARA

NTGEW

MARA

GEWEI

Unit of Weight (ISO Format)

Text

80

Unit of Weight (ISO Format)

NO

Text

80

S_MARA

GEWEI

MARA

LAENG

Length

Number (NUMC)

13

Length

NO

Number (NUMC)

13

S_MARA

LAENG

MARA

BREIT

Width

Number (NUMC)

13

Width

NO

Number (NUMC)

13

S_MARA

BREIT

MARA

HOEHE

Height

Number (NUMC)

13

Height

NO

Number (NUMC)

13

S_MARA

HOEHE

MARA

MEABM

Unit for Length/Width/Height(ISO Format)

Text (CHAR)

80

Unit for Length/Width/Height(ISO Format)

NO

Text (CHAR)

80

S_MARA

MEABM

MARA

VOLUM

Volume

Number (NUMC)

13

Volume

NO

Number (NUMC)

13

S_MARA

VOLUM

MARA

VOLEH

Volume Unit

Text (CHAR)

80

Volume Unit

NO

Text (CHAR)

80

S_MARA

VOLEH

MARA

CAPAUSE

Capacity Usage

Number (NUMC)

15

Capacity Usage

NO

Number (NUMC)

15

S_MARA

CAPAUSE

MARA

CHML_CMPLNC_RLVNCE_IND

Compliance Relevant

Text (CHAR)

80

Compliance Relevant

NO

Text (CHAR)

80

S_MARA

CHML_CMPLNC_RLVNCE_IND

MARA

KZKFG

Product Is Configurable

Text (CHAR)

1

Product Is Configurable

NO

Text (CHAR)

1

S_MARA

KZKFG

MARA

BSTME

Order Unit of Measure (ISO Format)

Text (CHAR)

80

Order Unit of Measure (ISO Format)

NO

Text (CHAR)

80

S_MARA

BSTME

MARA

EKWSL

Purchasing Value Key

Text (CHAR)

80

Purchasing Value Key

NO

Text (CHAR)

80

S_MARA

EKWSL

MARA

VABME

State of Variable Purchase Order Unit

Text (CHAR)

80

State of Variable Purchase Order Unit

NO

Text (CHAR)

80

S_MARA

VABME

MARA

BMATN

Internal Product Number

Text (CHAR)

80

Internal Product Number

NO

Text (CHAR)

80

S_MARA

BMATN

MARA

MFRPN

Manufacturer Part Number

Text (CHAR)

40

Manufacturer Part Number

NO

Text (CHAR)

40

S_MARA

MFRPN

MARA

MFRNR

Manufacturer Number

Text (CHAR)

80

Manufacturer Number

NO

Text (CHAR)

80

S_MARA

MFRNR

MARA

MPROF

Manufacturer Part Profile

Text (CHAR)

80

Manufacturer Part Profile

NO

Text (CHAR)

80

S_MARA

MPROF

MARA

TRAGR

Transportation Group

Text (CHAR)

80

Transportation Group

NO

Text (CHAR)

80

S_MARA

TRAGR

MARA

MSTAV

Cross-Distribution Chain Product Status

Text (CHAR)

80

Cross-Distribution Chain Product Status

NO

Text (CHAR)

80

S_MARA

MSTAV

MARA

MSTDV

Valid From Date for Status

Date

10

Valid From Date for Status

NO

Date

10

S_MARA

MSTDV

MARA

PMATA

Pricing Reference Product

Text (CHAR)

80

Pricing Reference Product

NO

Text (CHAR)

80

S_MARA

PMATA

MARA

SPROF

Pricing Profile for Variants

Text (CHAR)

80

Pricing Profile for Variants

NO

Text (CHAR)

80

S_MARA

SPROF

MARA

ALLOW_PMAT_IGNO

Variant Price Allowed

Text (CHAR)

1

Variant Price Allowed

NO

Text (CHAR)

1

S_MARA

ALLOW_PMAT_IGNO

MARA

SOM_CYCLE

Billing Cycle

Text (CHAR)

80

Billing Cycle

NO

Text (CHAR)

80

S_MARA

SOM_CYCLE

MARA

SOM_CYCLE_RULE

Billing Cycle Determination Rule

Text (CHAR)

80

Billing Cycle Determination Rule

NO

Text (CHAR)

80

S_MARA

SOM_CYCLE_RULE

MARA

SOM_TC_SCHEMA

Assignment Schema

Text (CHAR)

80

Assignment Schema

NO

Text (CHAR)

80

S_MARA

SOM_TC_SCHEMA

MARA

BBTYP

Assortment List Type

Text (CHAR)

80

Assortment List Type

NO

Text (CHAR)

80

S_MARA

BBTYP

MARA

SERVV

Service Agreement

Text (CHAR)

80

Service Agreement

NO

Text (CHAR)

80

S_MARA

SERVV

MARA

MAGRV

Product Group: Packaging Materials

Text (CHAR)

80

Product Group: Packaging Materials

NO

Text (CHAR)

80

S_MARA

MAGRV

MARA

VHIART

Packaging Product Type

Text (CHAR)

80

Packaging Product Type

NO

Text (CHAR)

80

S_MARA

VHIART

MARA

ERGEW

Allowed Packaging Weight

Number (NUMC)

13

Allowed Packaging Weight

NO

Number (NUMC)

13

S_MARA

ERGEW

MARA

ERGEI

Unit of Allowed Packaging Weight

Text (CHAR)

80

Unit of Allowed Packaging Weight

NO

Text (CHAR)

80

S_MARA

ERGEI

MARA

GEWTO

Excess Weight Tolerance for HU

Number (NUMC)

3

Excess Weight Tolerance for HU

NO

Number (NUMC)

3

S_MARA

GEWTO

MARA

ERVOL

Allowed Packaging Volume

Number (NUMC)

13

Allowed Packaging Volume

NO

Number (NUMC)

13

S_MARA

ERVOL

MARA

ERVOE

Unit of Allowed Packaging Volume

Text (CHAR)

80

Unit of Allowed Packaging Volume

NO

Text (CHAR)

80

S_MARA

ERVOE

MARA

KZGVH

Packaging Product Is Closed Packaging

Text (CHAR)

1

Packaging Product Is Closed Packaging

NO

Text (CHAR)

1

S_MARA

KZGVH

MARA

VOLTO

Excess Volume Tolerance for HU

Number (NUMC)

3

Excess Volume Tolerance for HU

NO

Number (NUMC)

3

S_MARA

VOLTO

MARA

IPRKZ

Period Indicator for Shelf Life

Text (CHAR)

80

Period Indicator for Shelf Life

NO

Text (CHAR)

80

S_MARA

IPRKZ

MARA

RAUBE

Storage Conditions

Text (CHAR)

80

Storage Conditions

NO

Text (CHAR)

80

S_MARA

RAUBE

MARA

TEMPB

Temperature Conditions Indicator

Text (CHAR)

80

Temperature Conditions Indicator

NO

Text (CHAR)

80

S_MARA

TEMPB

MARA

BEHVO

Container Requirements

Text (CHAR)

80

Container Requirements

NO

Text (CHAR)

80

S_MARA

BEHVO

MARA

STOFF

Hazardous Product Number

Text (CHAR)

40

Hazardous Product Number

NO

Text (CHAR)

40

S_MARA

STOFF

MARA

ETIAR

Label Type

Text (CHAR)

80

Label Type

NO

Text (CHAR)

80

S_MARA

ETIAR

MARA

ETIFO

Label Form

Text (CHAR)

80

Label Form

NO

Text (CHAR)

80

S_MARA

ETIFO

MARA

WESCH

Number of Goods Receipt/Issue Slips

Number (NUMC)

13

Number of Goods Receipt/Issue Slips

NO

Number (NUMC)

13

S_MARA

WESCH

MARA

XGCHP

Indicator: Approved Batch Rec. Required

Text (CHAR)

1

Indicator: Approved Batch Rec. Required

NO

Text (CHAR)

1

S_MARA

XGCHP

MARA

MHDHB

Total Shelf Life

Number (NUMC)

4

Total Shelf Life

NO

Number (NUMC)

4

S_MARA

MHDHB

MARA

MHDRZ

Minimum Remaining Shelf Life

Number (NUMC)

4

Minimum Remaining Shelf Life

NO

Number (NUMC)

4

S_MARA

MHDRZ

MARA

SLED_BBD

Indi. for the Shelf Life Expiration Date

Text (CHAR)

80

Indi. for the Shelf Life Expiration Date

NO

Text (CHAR)

80

S_MARA

SLED_BBD

MARA

MHDLP

Storage Percentage

Number (NUMC)

3

Storage Percentage

NO

Number (NUMC)

3

S_MARA

MHDLP

MARA

RDMHD

Rounding Rule for Calculation of SLED

Text (CHAR)

80

Rounding Rule for Calculation of SLED

NO

Text (CHAR)

80

S_MARA

RDMHD

MARA

HNDLCODE

Handling Indicator

Text (CHAR)

80

Handling Indicator

NO

Text (CHAR)

80

S_MARA

HNDLCODE

MARA

WHMATGR

Warehouse Product Group

Text (CHAR)

80

Warehouse Product Group

NO

Text (CHAR)

80

S_MARA

WHMATGR

MARA

WHSTC

Warehouse Storage Condition

Text (CHAR)

80

Warehouse Storage Condition

NO

Text (CHAR)

80

S_MARA

WHSTC

MARA

HUTYP_DFLT

Standard Handling Unit Type

Text (CHAR)

80

Standard Handling Unit Type

NO

Text (CHAR)

80

S_MARA

HUTYP_DFLT

MARA

SERIAL

Serial Number Profile

Text (CHAR)

80

Serial Number Profile

NO

Text (CHAR)

80

S_MARA

SERIAL

MARA

PILFERABLE

Pilferable

Text (CHAR)

1

Pilferable

NO

Text (CHAR)

1

S_MARA

PILFERABLE

MARA

HAZMAT

Relevant for Hazardous Substances

Text (CHAR)

1

Relevant for Hazardous Substances

NO

Text (CHAR)

1

S_MARA

HAZMAT

MARA

QQTIME

Quarantine Period

Number (NUMC)

3

Quarantine Period

NO

Number (NUMC)

3

S_MARA

QQTIME

MARA

QQTIMEUOM

Time Unit for Quarantine Period

Text (CHAR)

80

Time Unit for Quarantine Period

NO

Text (CHAR)

80

S_MARA

QQTIMEUOM

MARA

QGRP

Quality Inspection Group

Text (CHAR)

80

Quality Inspection Group

NO

Text (CHAR)

80

S_MARA

QGRP

MARA

HUTYP

Handling Unit Type

Text (CHAR)

80

Handling Unit Type

NO

Text (CHAR)

80

S_MARA

HUTYP

MARA

MAXC

Maximum Capacity

Number (NUMC)

15

Maximum Capacity

NO

Number (NUMC)

15

S_MARA

MAXC

MARA

MAXC_TOL

Overcapacity Tolerance

Number (NUMC)

3

Overcapacity Tolerance

NO

Number (NUMC)

3

S_MARA

MAXC_TOL

MARA

TARE_VAR

Variable Tare Weight

Text (CHAR)

1

Variable Tare Weight

NO

Text (CHAR)

1

S_MARA

TARE_VAR

MARA

MAXL

Max. Pack. Length

Number (NUMC)

15

Max. Pack. Length

NO

Number (NUMC)

15

S_MARA

MAXL

MARA

MAXDIM_UOM

UoM for Max. Pack. Length (ISO Format)

Text (CHAR)

80

UoM for Max. Pack. Length (ISO Format)

NO

Text (CHAR)

80

S_MARA

MAXDIM_UOM

MARA

MAXB

Max. Pack. Width

Number (NUMC)

15

Max. Pack. Width

NO

Number (NUMC)

15

S_MARA

MAXB

MARA

MAXH

Max. Pack. Height

Number (NUMC)

15

Max. Pack. Height

NO

Number (NUMC)

15

S_MARA

MAXH

MARA

RBNRM

Catalog Profile

Text (CHAR)

80

Catalog Profile

NO

Text (CHAR)

80

S_MARA

RBNRM

MARA

SSTUF

Assortment Grade

Text (CHAR)

80

Assortment Grade

NO

Text (CHAR)

80

S_MARA

SSTUF

MARA

LSTVZ

Listing Procedure

Text (CHAR)

80

Listing Procedure

NO

Text (CHAR)

80

S_MARA

LSTVZ

MARA

LDVZL

Listing Period Start Date

Date

10

Listing Period Start Date

NO

Date

10

S_MARA

LDVZL

MARA

LDBZL

Listing Period End Date

Date

10

Listing Period End Date

NO

Date

10

S_MARA

LDBZL

MARA

LSTFL

Listing Procedure

Text (CHAR)

80

Listing Procedure

NO

Text (CHAR)

80

S_MARA

LSTFL

MARA

LDVFL

Listing Period Start Date

Date

10

Listing Period Start Date

NO

Date

10

S_MARA

LDVFL

MARA

LDBFL

Listing Period End Date

Date

10

Listing Period End Date

NO

Date

10

S_MARA

LDBFL

MARA

VDVZL

Sales Period Start Date

Date

10

Sales Period Start Date

NO

Date

10

S_MARA

VDVZL

MARA

VDBZL

Sales Period End Date

Date

10

Sales Period End Date

NO

Date

10

S_MARA

VDBZL

MARA

VDVFL

Sales Period Start Date

Date

10

Sales Period Start Date

NO

Date

10

S_MARA

VDVFL

MARA

VDBFL

Sales Period End Date

Date

10

Sales Period End Date

NO

Date

10

S_MARA

VDBFL

MARA

WAUSM

Delivery Unit of Measure (ISO Format)

Text (CHAR)

80

Delivery Unit of Measure (ISO Format)

NO

Text (CHAR)

80

S_MARA

WAUSM

MARA

WVRKM

Sales Unit of Measure (ISO Format)

Text (CHAR)

80

Sales Unit of Measure (ISO Format)

NO

Text (CHAR)

80

S_MARA

WVRKM

MARA

WMAAB

ABC Indicator

Text (CHAR)

80

ABC Indicator

NO

Text (CHAR)

80

S_MARA

WMAAB

MARA

WBKLA

Valuation Class

Text (CHAR)

80

Valuation Class

NO

Text (CHAR)

80

S_MARA

WBKLA

MARA

WHERL

Country/Region of Origin

Text (CHAR)

80

Country/Region of Origin

NO

Text (CHAR)

80

S_MARA

WHERL

MARA

WHERR

Region of Origin

Text (CHAR)

80

Region of Origin

NO

Text (CHAR)

80

S_MARA

WHERR

MARA

WEKGR

Purchasing Group

Text (CHAR)

80

Purchasing Group

NO

Text (CHAR)

80

S_MARA

WEKGR

MARA

BWSCL

Source of Supply

Text (CHAR)

80

Source of Supply

NO

Text (CHAR)

80

S_MARA

BWSCL

MARA

TAKLV

Tax Classification

Text (CHAR)

80

Tax Classification

NO

Text (CHAR)

80

S_MARA

TAKLV

MARA

WLADG

Loading Group

Text (CHAR)

80

Loading Group

NO

Text (CHAR)

80

S_MARA

WLADG

MARA

WBWSP

Valuation Margin

Number (NUMC)

6

Valuation Margin

NO

Number (NUMC)

6

S_MARA

WBWSP

MARA

PSTATQ

Indicator: Quality

Text (CHAR)

1

Indicator: Quality

NO

Text (CHAR)

1

S_MARA

PSTATQ

MARA

PSTATV

Indicator: Sales

Text (CHAR)

1

Indicator: Sales

NO

Text (CHAR)

1

S_MARA

PSTATV

MARA

PSTATL

Indicator: Storage

Text (CHAR)

1

Indicator: Storage

NO

Text (CHAR)

1

S_MARA

PSTATL

MARA

PSTATE

Indicator: Purchasing

Text (CHAR)

1

Indicator: Purchasing

NO

Text (CHAR)

1

S_MARA

PSTATE

MAKT - Material Descriptions

MAKT - Material Descriptions

MAKT

MATNR

Product Number

Text (CHAR)

18

Mandatory

Product Number

Material Number

YES

Text (CHAR)

18

S_MAKT

MATNR

MAKT

SPRAS

Language Key

Text (CHAR)

2

Mandatory

Language Key

YES

Text (CHAR)

2

S_MAKT

SPRAS

MAKT

MAKTX

Product Description

Text (CHAR)

40

Mandatory

Product Description

YES

Text (CHAR)

40

S_MAKT

MAKTX

MARM - Units of Measure for Material

MARM - Units of Measure for Material

MARM

PRODUCT

Product Number

Text (CHAR)

80

Mandatory

Product Number

Material Number

YES

Text (CHAR)

80

S_MARM

MATNR

MARM

MEINH

Alternative Unit of Measure (ISO Format)

Text (CHAR)

80

Mandatory

Alternative Unit of Measure (ISO Format)

YES

Text (CHAR)

80

S_MARM

MEINH

MARM

UMREN

Denominator for Conversion to Base Unit

Number (NUMC)

5

Mandatory

Denominator for Conversion to Base Unit

YES

Number (NUMC)

5

S_MARM

UMREN

MARM

UMREZ

Numerator for Conversion to Base Unit

Number (NUMC)

5

Mandatory

Numerator for Conversion to Base Unit

YES

Number (NUMC)

5

S_MARM

UMREZ

MARM

EAN11

GTIN

Text (CHAR)

18

GTIN

NO

Text (CHAR)

18

S_MARM

EAN11

MARM

NUMTP

GTIN Category

Text (CHAR)

80

GTIN Category

NO

Text (CHAR)

80

S_MARM

NUMTP

MARM

LAENG

Length

Number (NUMC)

13

Length

NO

Number (NUMC)

13

S_MARM

LAENG

MARM

BREIT

Width

Number (NUMC)

13

Width

NO

Number (NUMC)

13

S_MARM

BREIT

MARM

HOEHE

Height

Number (NUMC)

13

Height

NO

Number (NUMC)

13

S_MARM

HOEHE

MARM

MEABM

Unit for Length/Width/Height(ISO Format)

Text (CHAR)

80

Unit for Length/Width/Height(ISO Format)

NO

Text (CHAR)

80

S_MARM

MEABM

MARM

BRGEW

Gross Weight

Number (NUMC)

13

Gross Weight

NO

Number (NUMC)

13

S_MARM

BRGEW

MARM

GEWEI

Unit of Weight (ISO Format)

Text (CHAR)

80

Unit of Weight (ISO Format)

NO

Text (CHAR)

80

S_MARM

GEWEI

MARM

VOLUM

Volume

Number (NUMC)

13

Volume

NO

Number (NUMC)

13

S_MARM

VOLUM

MARM

VOLEH

Volume Unit (ISO Format)

Text (CHAR)

80

Volume Unit (ISO Format)

NO

Text (CHAR)

80

S_MARM

VOLEH

MARM

CAPAUSE

Capacity Usage

Number (NUMC)

15

Capacity Usage

NO

Number (NUMC)

15

S_MARM

CAPAUSE

MLAN - Tax Classification for Material

S_MLAN - Tax Classification for Material

MLAN

PRODUCT

Product Number

Text (CHAR)

80

Mandatory

Product Number

Material Number

YES

Text (CHAR)

80

S_MLAN

MATNR

MLAN

ALAND

Country/Region

Text (CHAR)

80

Mandatory

Country/Region

YES

Text (CHAR)

80

S_MLAN

ALAND

MLAN

TATYP1

Tax Category 1

Text (CHAR)

80

Mandatory

Tax Category 1

YES

Text (CHAR)

80

S_MLAN

TATYP1

MLAN

TAXM1

Tax Classification 1

Text (CHAR)

80

Mandatory

Tax Classification 1

YES

Text (CHAR)

80

S_MLAN

TAXM1

MLAN

TATYP2

Tax Category 2

Text (CHAR)

80

Tax Category 2

NO

Text (CHAR)

80

S_MLAN

TATYP2

MLAN

TAXM2

Tax Classification 2

Text (CHAR)

80

Tax Classification 2

NO

Text (CHAR)

80

S_MLAN

TAXM2

MLAN

TATYP3

Tax Category 3

Text (CHAR)

80

Tax Category 3

NO

Text (CHAR)

80

S_MLAN

TATYP3

MLAN

TAXM3

Tax Classification 3

Text (CHAR)

80

Tax Classification 3

NO

Text (CHAR)

80

S_MLAN

TAXM3

MLAN

TATYP4

Tax Category 4

Text (CHAR)

80

Tax Category 4

NO

Text (CHAR)

80

S_MLAN

TATYP4

MLAN

TAXM4

Tax Classification 4

Text (CHAR)

80

Tax Classification 4

NO

Text (CHAR)

80

S_MLAN

TAXM4

MLAN

TATYP5

Tax Category 5

Text (CHAR)

80

Tax Category 5

NO

Text (CHAR)

80

S_MLAN

TATYP5

MLAN

TAXM5

Tax Classification 5

Text (CHAR)

80

Tax Classification 5

NO

Text (CHAR)

80

S_MLAN

TAXM5

MLAN

TATYP6

Tax Category 6

Text (CHAR)

80

Tax Category 6

NO

Text (CHAR)

80

S_MLAN

TATYP6

MLAN

TAXM6

Tax Classification 6

Text (CHAR)

80

Tax Classification 6

NO

Text (CHAR)

80

S_MLAN

TAXM6

MLAN

TATYP7

Tax Category 7

Text (CHAR)

80

Tax Category 7

NO

Text (CHAR)

80

S_MLAN

TATYP7

MLAN

TAXM7

Tax Classification 7

Text (CHAR)

80

Tax Classification 7

NO

Text (CHAR)

80

S_MLAN

TAXM7

MLAN

TATYP8

Tax Category 8

Text (CHAR)

80

Tax Category 8

NO

Text (CHAR)

80

S_MLAN

TATYP8

MLAN

TAXM8

Tax Classification 8

Text (CHAR)

80

Tax Classification 8

NO

Text (CHAR)

80

S_MLAN

TAXM8

MLAN

TATYP9

Tax Category 9

Text (CHAR)

80

Tax Category 9

NO

Text (CHAR)

80

S_MLAN

TATYP9

MLAN

TAXM9

Tax Classification 9

Text (CHAR)

80

Tax Classification 9

NO

Text (CHAR)

80

S_MLAN

TAXM9

CLASS - Class Header Data (KLAH)

CLASS - Class Header Data (KLAH)

CLASS

PRODUCT

Product Number

Text (CHAR)

18

Mandatory

Product Number

Material Number

YES

Text (CHAR)

18

S_CLASS

MATNR

CLASS

Class

Text (CHAR)

80

Mandatory

Class

YES

Text (CHAR)

80

S_CLASS

CLASS

CLASSTYPE

Class Type

Text (CHAR)

80

Mandatory

Class Type

YES

Text (CHAR)

80

S_CLASS

CLASSTYPE

CHARACT - Characteristic (CABN)

S_CHARACT - Characteristic (CABN)

CHARACT

PRODUCT

Product Number

Text (CHAR)

80

Mandatory

Product Number

Material Number

YES

Text (CHAR)

80

S_CHARACT

MATNR

CHARACT

CLASS

Class

Text (CHAR)

80

Mandatory

Class

YES

Text (CHAR)

80

S_CHARACT

CLASS

CHARACT

CLASSTYPE

Class Type

Text (CHAR)

80

Mandatory

Class Type

YES

Text (CHAR)

80

S_CHARACT

CLASSTYPE

CHARACT

ATNAM

Characteristic Name

Text (CHAR)

80

Mandatory

Characteristic Name

YES

Text (CHAR)

80

S_CHARACT

ATNAM

CHARACT

POSNR

Item

Text (CHAR)

3

Item

NO

Text (CHAR)

3

S_CHARACT

POSNR

CHARACT

VALUE_CHAR

Character Value

Text (CHAR)

70

Character Value

NO

Text (CHAR)

70

S_CHARACT

VALUE_CHAR

CHARACT

VALUE_NUMC

Numeric Value

Number (NUMC)

16

Numeric Value

NO

Number (NUMC)

16

S_CHARACT

VALUE_NUMC

CHARACT

VALUE_DATE

Date

NO

Date

10

S_CHARACT

VALUE_DATE

CHARACT

VALUE_TIME

Time

NO

Time

8

S_CHARACT

VALUE_TIME

CHARACT

VALUE_CURR

Currency Value

Number (NUMC)

23

Currency Value

NO

Number (NUMC)

23

S_CHARACT

VALUE_CURR

STXH - SAPscript Text Header

STXH - SAPscript Text Header

STXH

TDOBJECT

Text Object (e.g., MATERIAL, VENDOR, etc.)

CHAR

10

Mandatory

Text Object (e.g., MATERIAL, VENDOR, etc.)

NO

CHAR

10

STXH

TDOBJECT

STXH

TDNAME

Text Name (object key, e.g., material number, PO number)

CHAR

70

Mandatory

Text Name (object key, e.g., material number, PO number)

NO

CHAR

70

STXH

TDNAME

STXH

TDID

Text ID (text type, e.g., F01 = Header Text, L01 = Item Text)

CHAR

4

Mandatory

Text ID (text type, e.g., F01 = Header Text, L01 = Item Text)

NO

CHAR

4

STXH

TDID

STXH

TDSPRAS

Language Key

LANG

1

Mandatory

Language Key

NO

LANG

1

STXH

TDSPRAS

STXH

TDTITLE

Title of the text (optional short description)

CHAR

60

Mandatory

Title of the text (optional short description)

NO

CHAR

60

STXH

TDTITLE

STXH

TDFUSER

Last Changed by (user)

CHAR

12

Last Changed by (user)

NO

CHAR

12

STXH

TDFUSER

STXH

TDFDATE

Date of Last Change

DATS

8

Date of Last Change

NO

DATS

8

STXH

TDFDATE

STXH

TDFTIME

Time of Last Change

TIMS

6

Time of Last Change

NO

TIMS

6

STXH

TDFTIME

STXH

TDVERSION

Version Number of Text

NUMC

4

Version Number of Text

NO

NUMC

4

STXH

TDVERSION

STXH

TDLOCK

Lock Indicator

CHAR

1

Lock Indicator

NO

CHAR

1

STXH

TDLOCK

STXH

TDTRANSTAT

Translation Status

CHAR

1

Translation Status

NO

CHAR

1

STXH

TDTRANSTAT

STXH

TDOSPRAS

Original Language

LANG

1

Original Language

NO

LANG

1

STXH

TDOSPRAS

STXL - SAPscript Text File (Cluster)

STXL - SAPscript Text File (Cluster)

STXL

RELID

Cluster Area (ID of cluster; for texts usually "TX")

Text (CHAR)

2

Mandatory

Cluster Area (ID of cluster; for texts usually "TX")

NO

Text (CHAR)

2

STXL

RELID

STXL

TDOBJECT

Text Object (e.g., MATERIAL, VENDOR, etc.)

Text (CHAR)

10

Mandatory

Text Object (e.g., MATERIAL, VENDOR, etc.)

NO

Text (CHAR)

10

STXL

TDOBJECT

STXL

TDNAME

Text Name (object key, e.g., material number, purchase order)

Text (CHAR)

70

Mandatory

Text Name (object key, e.g., material number, purchase order)

NO

Text (CHAR)

70

STXL

TDNAME

STXL

TDID

Text ID (text type, e.g., F01 = header text, L01 = item text)

Text (CHAR)

4

Mandatory

Text ID (text type, e.g., F01 = header text, L01 = item text)

NO

Text (CHAR)

4

STXL

TDID

STXL

TDSPRAS

Language Key

Language (LANG)

1

Mandatory

Language Key

NO

Language (LANG)

1

STXL

TDSPRAS

STXL

SRTF2

Sort number (used to split large texts across several cluster entries)

Numeric (NUMC)

3

Sort number (used to split large texts across several cluster entries)

NO

Numeric (NUMC)

3

STXL

SRTF2

STXL

CLUSTR

Length field for cluster (internal, technical)

Integer (INT2)

5

Length field for cluster (internal, technical)

NO

Integer (INT2)

5

STXL

CLUSTR

STXL

CLUSTD

Length field for cluster (internal, technical)

Integer (INT2)

5

Length field for cluster (internal, technical)

NO

Integer (INT2)

5

STXL

CLUSTD

STXL

VARTEXT

Compressed text data (the actual long text, stored in cluster format)

(RAW)

255

Compressed text data (the actual long text, stored in cluster format)

NO

(RAW)

255

STXL

VARTEXT

Table / Staging Area	Field	Field Description	Data Type	Length	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

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	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.

eyJleHRTcnZJbnRlZ1R5cGUiOiIiLCJnQ2xpZW50SWQiOiIiLCJjcmVhdG9yTmFtZSI6IkJVT1NJLWV4dCwgQW5nZWxvIiwib3V0cHV0VHlwZSI6ImJsb2NrIiwibGFzdE1vZGlmaWVyTmFtZSI6IkJVT1NJLWV4dCwgQW5nZWxvIiwibGFuZ3VhZ2UiOiJlbiIsInVpQ29uZmlnIjoie30iLCJkaWFncmFtRGlzcGxheU5hbWUiOiIiLCJzRmlsZUlkIjoiIiwiYXR0SWQiOiI5NDUwMzY1MDIiLCJkaWFncmFtTmFtZSI6IkRhdGEgTWVyZ2luZyBlbmdpbmUiLCJhc3BlY3QiOiIiLCJsaW5rcyI6ImF1dG8iLCJjZW9OYW1lIjoiQ05WLTIwMTYgU2VydmljZSBNYXN0ZXIgcmVjb3JkIChMZWFuIFNlcnZpY2VzKSIsInRic3R5bGUiOiJ0b3AiLCJjYW5Db21tZW50IjpmYWxzZSwiZGlhZ3JhbVVybCI6IiIsImNzdkZpbGVVcmwiOiIiLCJib3JkZXIiOnRydWUsIm1heFNjYWxlIjoiMSIsIm93bmluZ1BhZ2VJZCI6OTM3MDExNjkwLCJlZGl0YWJsZSI6ZmFsc2UsImNlb0lkIjo5NDUwNTc4ODEsInBhZ2VJZCI6IiIsImxib3giOnRydWUsInNlcnZlckNvbmZpZyI6eyJlbWFpbHByZXZpZXciOiIxIn0sIm9kcml2ZUlkIjoiIiwicmV2aXNpb24iOjI4LCJtYWNyb0lkIjoiYjIxN2U4YjktNjVhMC00MzJjLTllNjctMWNjMmE4YjA0YzdjIiwicHJldmlld05hbWUiOiJEYXRhIE1lcmdpbmcgZW5naW5lLnBuZyIsImxpY2Vuc2VTdGF0dXMiOiJPSyIsInNlcnZpY2UiOiIiLCJpc1RlbXBsYXRlIjoiIiwid2lkdGgiOiIxMzY3Iiwic2ltcGxlVmlld2VyIjpmYWxzZSwibGFzdE1vZGlmaWVkIjoxNzYxMDQzNDE4ODc3LCJleGNlZWRQYWdlV2lkdGgiOmZhbHNlLCJvQ2xpZW50SWQiOiIifQ==

Extraction

Extract data from a source into . There are 2 possibilities:

The data exists. connects to the source and loads the data into . 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.
The data does not exist (or cannot be converted from its current state). The data is manually collected by the business directly in . This is to be conducted using DCT (Data Collection Template) in

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

Selection Screen

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 with exception of some fields which require transformation as mentioned in the transformation rule.

DCT Rules

Field Name	Field Description	Rule

Extraction Dependencies

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 to make the data Target ready:

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
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
3	Review and Validate Error and Preload Reports All Preload and Postload reports are available here:	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
001	PF2 - MATERIAL	MARA	MATNR	Product Number	S4/HANA	S_MARA	MATNR	Product Number	Generate a new material code and keep the mapping of Old Material and New Material in a dedicated table
002	PF2 - MATERIAL	MARA	ATTYP	Product Category	S4/HANA	S_MARA	ATTYP	Product Category	Apply Data Conversion from OLD to NEW value. The 1:1 relation is expected.
003	PF2 - MATERIAL	MARA	SATNR	Configuration Product for Retail Variant	S4/HANA	S_MARA	SATNR	Configuration Product for Retail Variant	Apply Data Conversion from OLD to NEW value. The 1:1 relation is expected.
004	PF2 - MATERIAL	MARA	MATKL	Product Group	S4/HANA	S_MARA	MATKL	Product Group	Apply Data Conversion from OLD to NEW value. The 1:1 relation is expected.
005	PF2 - MATERIAL	MARA	MBRSH	Industry Sector	S4/HANA	S_MARA	MBRSH	Industry Sector	Apply Data Conversion from OLD to NEW value. The 1:1 relation is expected.
006	PF2 - MATERIAL	MARA	SPRAS	Language Key	S4/HANA	S_MARA	SPRAS	Language Key	Apply Data Conversion from OLD to NEW value. The 1:1 relation is expected.
007	PF2 - MATERIAL	MARA	MEINS	Base Unit of Measure (ISO Format)	S4/HANA	S_MARA	MEINS	Base Unit of Measure (ISO Format)	Apply Data Conversion from OLD to NEW value. The 1:1 relation is expected.
008	PF2 - MATERIAL	MARA	NUMTP	GTIN Category	S4/HANA	S_MARA	NUMTP	GTIN Category	Apply Data Conversion from OLD to NEW value. The 1:1 relation is expected.
009	PF2 - MATERIAL	MARA	SPART	Division	S4/HANA	S_MARA	SPART	Division	Apply Data Conversion from OLD to NEW value. The 1:1 relation is expected.

Transformation Mapping

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
Language Key	Mapping of legacy Language Key to target system value
Unit of Measure	Mapping of legacy Unit of Measure 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

Data Mapping: Account Group

Account Group
Source System	OLD: Legacy Account Group	NEW: S4/Hana Account Group
PF2	DIEN	ZSER
PF2	Z710	ZSER
PF2	Z720	ZSER
PF2	Z732	ZSER
PF2	ZB10	ZSER
PF2	ZB20	ZSER
PF2	ZESE	ZSER
PF2	ZFS1	ZSER
PF2	ZPSE	ZSER
PF2	ZU10	ZSER
PF2	ZU20	ZSER

WP2	DIEN	ZSER
WP2	ZDIE	ZSER

* some materials were originally created under type ZNLA (e.g., electricity). However, these must be converted to type ZSER. An exception list table should be created to capture all relevant materials, ensuring they are flagged as in-scope for migration.

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

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
Description Multilanguage	Identify whether some examples are being properly loaded. Take few examples to be checked according to the data volume purchased.

Accuracy

Task	Action
Description	Check whether the description matches the with the same value from Legacy System
Legacy Code	Check whether the Legacy code is maintained as expected. The rule is valid for all legacy systems.
UOM Maintained	Check whether the Unit of Measure was respected

Business

Completeness

Task	Action

Accuracy

Task	Action

Load

The load process includes:

Execute the automated data load into target system using load tool or product the load file if the load must be done manually
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
001	The data is save into the staging areas of Migration Cockpit	Syniti Team
002	Data Load is executed by Migration Cockpit respecting the proper sequence	Syensqo Team

Load Phase and Dependencies

N/A

Configuration

List the Configurations required before loading can commence

Item #	Configuration Item
001	Company Codes (T001-BUKRS)
002	Plants (T024-WERKS)
003	Material Group (T023-MATKL)
004	EAN Category (MARA-NUMTP)
005	Unit of Measures (T006-MSEHI) Volume Unit Weight Unit
006	Division (MARA-SPART)
007	Lab / Office (MARA-LABOR)
008	Authorization Group (MARA-BEGRU)
009	Product Allocation (MARA-KOSCH)
010	Product Hierarchy (MARA-PRDHA)
012	Material Status (MARA-MSTAE)
013	General Item Category Group (MTPOS_MARA)
014	Dangerous Goods Indicator Profile (MARA-PROFL)
015	Dangerous Goods Packaging Status (MARA-DG_PACK_STATUS)
016	Packaging Code (MARA-PACKCODE)
017	ANP Code - Brazil (MARA-ANP)
018	Material Type (MARA-MTART)

Conversion Objects

Object #	Preceding Object Conversion Approach

Error Handling

Error Type	Error Description	Action Taken

Post-Load Validation

Project Team

Completeness

Task	Action
	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

Business

Completeness

Task	Action

Accuracy

Task	Action

Syniti Reports

#	Topic	Jira Ticket	Creation Date	Resolution Date
001
003
004
005
006
007

Open Questions

#	Topic	Jira Ticket	Creation Date	Resolution Date
001	Multiple Objects being consolidated
003
004
005
006
007

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.

Change log

Version	Published	Changed By
CURRENT (v. 251)	Nov 20, 2025 09:12	BUOSI-ext, Angelo
v. 368	Nov 18, 2025 15:25	BUOSI-ext, Angelo
v. 367	Nov 13, 2025 08:54	BUOSI-ext, Angelo
v. 366	Oct 30, 2025 09:18	BUOSI-ext, Angelo
v. 365	Oct 21, 2025 10:43	BUOSI-ext, Angelo
v. 364	Oct 21, 2025 10:43	BUOSI-ext, Angelo
v. 363	Oct 20, 2025 10:43	BUOSI-ext, Angelo
v. 362	Oct 20, 2025 10:42	BUOSI-ext, Angelo
v. 361	Oct 17, 2025 13:53	BUOSI-ext, Angelo
v. 360	Oct 17, 2025 13:36	BUOSI-ext, Angelo

Go to Page History

Workflow history

Title	Last Updated By	Updated	Status
There are no pages at the moment.

From Jun 20, 2025 to Nov 20, 2025	Actor	Type	Activity	Version
	BUOSI-ext, Angelo	Edit	updated the page at 11:14 am
	BUOSI-ext, Angelo	Edit	created the page at 10:23 am

Workflow history

Space shortcuts

Page tree

CNV-2016 Service Master record (Lean Services)

Purpose

Conversion Scope

Relevancy Rules

Relevant Tables for the Extraction

Execution Logic:

Execution Logic:

*** Canonical Key & Duplication Detection

Additional Information

Extraction Methods and File Types

Multi-language Requirement

Document Management

Legal Requirement

Special Requirements

Target Design

Data Cleansing

Conversion Process

Data Privacy and SensitivityN/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

Extraction Run Sheet

Selection Screen

Data Collection Template (DCT)

Extraction Dependencies

Transformation

Transformation Run Sheet

Transformation Mapping

Data Mapping: Account Group

Transformation Dependencies

Pre-Load Validation

Project Team

Completeness

Accuracy

Business

Completeness

Accuracy

Load

Configuration

Conversion Objects

Error Handling

Post-Load Validation

Project Team

Completeness

Accuracy

Business

Completeness

Accuracy

Syniti Reports

Open Questions

Key Assumptions

See also

Change log

Workflow history

Data Privacy and Sensitivity
N/A