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:

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

Relevancy Rules

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

Relevant Tables for the Extraction

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

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 Plant is not Empty and in not in scope 

If WERKS = '' then there is no verification to be done.

Elseif Plant is in Scope

7) 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 AEDAT (last change) within the last 6 months.

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

3) INCLUDED Default pass (no negatives matched).

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

*** Canonical Key & Duplication Detection

Deduplication of records from Material as Service (MARA) and Service Master (ASMD) tables

...

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.

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.

Target Design

The technical design of the target for this conversion approach.

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

Tables to be migrated as Basic Data: