Versions Compared

Old Version 9

changes.mady.by.user HANCOCK-ext, John

Saved on

compared with

New Version Current

changes.mady.by.user CLARKE-ext, Steve

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Material Freight Group MARC-MFRGR is no longer needed
Status

Page Status

Owner

HANCOCK-ext, John CLARKE-ext, Steve BUOSI-ext, Angelo SLOAN-ext, Anthony 

Stakeholders

Purpose

The purpose of this document is to define the conversion approach to create upload Materials - Purchasing View in into S/4 HANA as part of the Material Data Migration.

Link to MDS: DD-FUN-050 Master Data Standard_2020-Material master-Purchasing data


Conversion Scope

The scope of this document covers the approach for converting active Materials - Purchasing View from Legacy Source Systems into S/4HANA following the Materials Master Data Design Standard.

From the current system landscape, Material data exists separately in the legacy systems (PF2 and WP2), with potential discrepancies in both organizations. Harmonization and validation are required to ensure accurate and consolidated data in S/4HANA. While PF2 and WP2 serve as source systems, extensive mapping and transformation logic will be necessary to produce properly formatted load templates in line with the target design.

Relevancy Rules

  1. All materials created in the previous 6 months will be included unless flagged for deletion
  2. These include Material Types ZUNB, ZBOM, ZPRC regardless of activity (unless flagged for deletion)
  3. We will only include materials that are extended to the following (excluding ZPRC material type as these do not require plant extension):
    1. Company Codes in scope
    2. Plants in scope
    3. Purchasing Orgs in scope
    4. Sales Orgs in scope
  4. Include only Material Types in scope
  5. We will include for migration all materials that have activity over the previous 3 years, to include:
    1. For procurement data use EKKO/EKPO tables
    2. For sales data use VBAK/VBAP tables
    3. For production data use AFKO/AFPO tables
  6. We will include for migration all materials that have open documents including the following:
    1. Open PO
    2. Open contracts
    3. Open STO
    4. Open SO
    5. Open WO
  7. Have current stock - refer to MARD table
  8. We will include all BOM data for materials in scope using tables: MAST/STKO/STPO
  9. Materials with Deletion Flags will be excluded unless appearing in the following open transactions:
    1. Open PO
    2. Open contracts
    3. Open STO
    4. Open SO
    5. Open WO
  10. Deletion Flags (Table/Field) are as follows: MARA/LVORM = 'X' MARA/MSTAE = Z3, Z4, ZZ (PF2 system) Z0 (WP2 system)
  11. Materials with the word 'OBSOLETE' or 'DELETED' contained within the Short Description will be excluded. Also excluded are Materials where Short Description contains '**OBS', '**OBS**', '**OBS***', '*OBS*', '*OBS**', '***OBS***'
List of source systems and approximate number of records
SourceScope

Source Approx No. of Records

Target SystemTarget Approx

No. of Records

PF2,WP2

The Material Master 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. 

700,000S4H204,000


This object is migrated after Material Basic Data and Material General Plant, therefore only materials in scope for the object "2019 - Materials Basic Data View" and have Plants in scope as per the object "2010 - Materials - General Plant Data / S.Loc Data", are in scope for this object.  Click here to go to the Conversion Spec for 2019 to see the full set of relevancy rules.  Furthermore, as per the MDS for 2019, materials with certain Material Types will not be extended to the Purchasing View, while all other Material Types will be.  Currently the Material Type not extended is the To-Be Material Type ZBAS, but this may change.  Therefore this MDS must be reviewed for changes to this rule as part of the preparation of a Syniti ADMM Transform run.

As an additional relevancy requirement Plant Extensions where MARC-MMSTA = Z0 for WP2 and either Z4 or ZZ for PF2 must be excluded from the migration.  Note that the existing rule of excluding a Plant Extension where MARC-LVORM = 'X' still applies.


The Service Master will be loaded as Materials in the Target.  The relevancy rules for this are also covered in the object "2019 - Materials Basic Data View".


List of source systems and approximate number of records
SourceScope

Source Approx. No. of Records

Target SystemTarget Approx. No. of Records
PF2, WP2

Materials: The Material Master Records will be extracted that meet the relevancy criteria of Material Basic Data.  Material Type will further refine this list to Materials relevant for the Purchasing View.

Materials:
PF2: 115,853**
WP2: 81,288**
** As per Material relevancy criteria

Plants (See CNV-2010):
2.4 Million, depending on Plant consolidation

S4H

Materials:
197,141 **
** This will change based on the Material Deduplication Process

Plants (See CNV-2010):
TBC, depending on Plant consolidation

DCT

Services: There is no Purchase View data, therefore a DCT will be required for the records that meet the relevancy criteria to be created as Materials and Material Type will further refine this list to records relevant for the Purchasing View.

Services:
PF2: 9,821**
WP2: 353**
** As per Material relevancy criteria

S4H

10,174 **
** This will change based on the Material Deduplication Process

Predecessor Object


Material Master - Basic View (2019) → Materials - Additional data (2021) → Materials - General Plant Data / S.Loc Data (2010) → Materials Purchasing View (2020).

Additional Information

Multi-language Requirement

Not Applicable

Document Management

Additional Information

Multi-language Requirement

Not Applicable

Document Management

Not Applicable

Legal Requirement

Not Applicable

Special Requirements

Not Applicable



Target Design

The technical design of the target for this conversion approach.

TableField
Data Element
Field DescriptionData TypeLengthRequirement
S_MARA

Updated in Predecessor / Other Object

MARCMATNRMaterial Number
Automatic
CHAR
   
18Required
Mandatory

2010

S_
MARCWERKSPlantCHAR4
Configured
Required
Mandatory
2010
S_ConfiguredMandatoryS_
MARAMEINSBase Unit of Measure
(ISO Format)
UNIT3Required2019
S_
MARABSTME **Order Unit
of Measure (ISO Format)ConfiguredMandatory
UNIT3Conditional2019 **
MARAVABME **
State of
Variable
Purchase
Order Unit
ConfiguredS_MARAMATKLMaterial GroupConfiguredMandatoryS_
CHAR
OptionalS_MARCEKGRPPurchasing GroupConfiguredMandatory
1Conditional2019 **
MARAMATKLMaterial GroupCHAR9Required2019
MARCEKGRPPurchasing GroupCHAR3Conditional
ConfiguredOptionalS_
MARCMMSTAMaterial Status (Plant-Specific
Material Status
)CHAR2Conditional
MARCMMSTDValid From
Date for Status
DATS8Conditional
MLAN
DateOptionalS_MARC
TAXIMTax Indicator for Material
ConfiguredS_
CHAR
OptionalS_MARANRFHGMaterial Disc In KdConfiguredOptional
1Required
MARCMFRGR***Material Freight
Grp
GroupCHAR
Configured
4
Optional
Not Required
S_

MARCKAUTBAutomatic
Purchase Oder AllowedText
PO allowedCHAR1
Optional
Required
S_

MARC
XCHPFBatch Management Req. Indicator
KZKRICritical PartCHAR
Text
1
Optional
Conditional
S_S_MARCWEBAZGR Processing TimeText2MandatoryS_MARA

MARA
EKWSLPurchasing Value KeyConfiguredMandatory
MFRPNManufacturer Part Number
Text
CHAR
80
40
Optional
Conditional
S_

MARAMFRNRManufacturer
Number
Configured
CHAR
Optional
10
S_MARA
Conditional
MPROF

MARC
Manufacturer Part ProfileConfiguredOptional
HERKLCountry of OriginCHAR3Conditional
MARCWEBAZGR Processing TimeDEC3Conditional2005

** BSTME and VABME are no longer in CNV_2019 so they must be included here.
*** MARC-MFRGR is no longer needed.


Data Cleansing

Data Cleansing

IDCriticalityError Message/Report DescriptionRuleOutputSource System
2020-001
Syniti Report Required
1High
C1
Purchasing Group
Confirm all procured materials have Purchasing Data in place and confirm Purchasing Group mapping to S4 target valuePF2/WP22020-002C1PIR alignmentCheck that procured materials have PIR in placePF2/WP22020-003C1Purchasing Value KeyAll material Purchasing data requirements to be confirmedPF2/WP22020-004C1GR processing timeAll material Purchasing data requirements to be confirmedPF2/WP22020-004C1Manufacturer Part NoAll spares to have Manufacturer Part No populatedPF2/WP2

Conversion Process

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

Image Removed

Data Privacy and Sensitivity

Extraction

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

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

1

Extract data from source system based on relevancy rule

SyWay Data Team

2

Google Sheet report pre-populated with PF2 and WP2 information to be generated based on relevancy criteria. 

SyWay Data Team

Selection Screen

Selection Ref ScreenParameter NameSelection TypeRequirementValue to be entered/set

Data Collection Template (DCT)

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

Materials - Purchasing View DCT Rules

Field NameField DescriptionRule

Extraction Dependencies

Item #Step DescriptionTeam Responsible

1

Data cleansing of legacy Material data must be completed.
If standardization within the DCT begins using relevant data from PF2 and WP2 before the cleansing is finalized, it is understood that the business will take due diligence to ensure any subsequent delta cleansing is verified and aligned within the DCT.

Business

Transformation

The Target fields are mapped to the applicable Legacy field that will be its source, this is a 3-way activity involving the Business, Functional team and Data team. This identifies the transformation activity required to allow to make the data Target ready:

  1. Perform value mapping and data transformation rules.
    1. Legacy values are mapped to the to-be values (this could include a default value)
    2. Values are transformed according to the rules defined in
  2. Prepare target-ready data in the structure and format that is required for loading via prescribed Load Tool. This step also produces the load data ready for business to perform Pre-load Data Validation

Transformation Run Sheet

Item #Step DescriptionTeam Responsible

1

Obtain DCT Sign-off from Business

SyWay S2P Data Team

2

<Add steps from Syniti Migrate here>

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 systemSource TableSource FieldSource DescriptionTarget SystemTarget TableTarget FieldTarget DescriptionTransformation Logic

001

PF2/WG2

S_MARA

MATNR

Material Number

S/4HANA

S_MARA

MATNR

Material Number

Generate new Material number in Target System and maintain mapping in reference table

002

PF2/WG2

S_MARC

WERKS

Plant

S/4HANA

S_MARC

WERKS

Plant

Map from source to target

003

PF2/WG2

S_MARA

MEINS

Base Unit of Measure (ISO Format)

S/4HANA

S_MARA

MEINS

Base Unit of Measure (ISO Format)

Map from source to target in adherence to Data Standard

004

PF2/WG2

S_MARA

BSTME

Order Unit of Measure (ISO Format)

S/4HANA

S_MARA

BSTME

Order Unit of Measure (ISO Format)

Map from source to target in adherence to Data Standard

005

PF2/WG2

S_MARA

VABME

State of Variable Purchase Order Unit

S/4HANA

S_MARA

VABME

State of Variable Purchase Order Unit

Copy from source to target system

006

PF2/WG2

S_MARC

EKGRP

Purchasing Group

S/4HANA

S_MARC

EKGRP

Purchasing Group

Map from source to target using Purchasing Group mapping table

007

PF2/WG2

S_MARA

MATKL

Material Group

S/4HANA

S_MARA

MATKL

Material Group

Map from source to target using Material Group mapping table

008

PF2/WG2

S_MARC

MMSTA

Plant-Specific Material Status

S/4HANA

S_MARC

MMSTA

Plant-Specific Material Status

Copy from source to target system

009

PF2/WG2

S_MARC

MMSTD

Valid From Date for Status

S/4HANA

S_MARC

MMSTD

Valid From Date for Status

Copy from source to target system

010

PF2/WG2

S_MARC

TAXIM

Tax Indicator

S/4HANA

S_MARC

TAXIM

Tax Indicator

Copy from source to target system

011

PF2/WG2

S_MARC

KAUTB

Automatic Purchase Oder Allowed

S/4HANA

S_MARC

KAUTB

Automatic Purchase Oder Allowed

Copy from source to target system

012

PF2/WG2

S_MARC

XCHPF

Batch Management Req. Indicator

S/4HANA

S_MARC

XCHPF

Batch Management Req. Indicator

Copy from source to target system

013

PF2/WG2

S_MARA

EKWSL

Purchasing Value Key

S/4HANA

S_MARA

EKWSL

Purchasing Value Key

Copy from source to target system

014

PF2/WG2

S_MARC

WEBAZ

GR Processing Time

S/4HANA

S_MARC

WEBAZ

GR Processing Time

Copy from source to target system

Transformation Mapping

Purchasing Group

Mapping of legacy Purchasing Groups to target system value

Transformation Dependencies

List the steps that need to occur before transformation can commenceItem #Step DescriptionTeam 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

Pre-Load Validation

Project Team

Completeness

TaskAction

Verify Record Count

Business Data Owner/s to verify that the total number of relevant records from the the DCT is equal to the total number of records in the Preload and Load Sheets.

Accuracy

TaskAction

Conversion Accuracy

SyWay S2P Data Team to verify that all fields below meet pass the checks:

  1. Mandatory Fields
  2. Field and Value Mapping Correctness
  3. Null Checks
  4. Text Length Checks

Review Error Reports

Review and correct the errors.  Achieve a zero-error record count as much as possible. Raise defects for data remediated and requiring a correction in the source data.

Business

Completeness

TaskAction

Verify Record Count

Business Data Owner/s to verify that the total number of relevant records from the the DCT is equal to the total number of records in the Preload and Load Sheets.

Missing

If MARC-EKGRP is Blank then include in the report.

MARA-MATNR, MARC-WERKSPF2, WP2 & DCTYES
2MediumCountry Of Origin Missing **

if ( MARC-HERKL is Blank ) AND
( T001W-LAND1 = 'BR' ) AND
( ( To-Be Material Type IN ('ZDIR','ZIND') ) OR
( ( To-Be Material Type IN ('UNBW','NLAG') ) AND ( To-Be MARC-KZKRI = 'X' ) ) )
then include in the report **

MARA-MATNR, MARC-WERKSPF2 & WP2YES
3MediumGR Processing Time Missing****

If MARC-WEBAZ is Blank AND (To-Be Material Type = 'ZDIR' OR 'ZIND') then include in the report

MARA-MATNR, MARC-WERKS, MARA-MTARTPF2 & WP2YES

** This rule has been clarified by Dean Leighton in a Google Chat with Jasleen Madhok, John Hancock and Steve Clarke on Wednesday 12 November 2025.
**** This report is not required because the field is owned by MRP and they will have and manage a cleansing report if required.


Conversion Process

The high-level process for Materials, where the source is PF2 & WP2, is represented by the diagram below:

Image Added


The high-level process for Services, where there is no source data, is represented by the diagram below:

Image Added



Field Governance Rules

These governance rules apply to the individual fields within the data record.

Rule #

Field Label

Rule Description

Validation Method

Conditional Logic

Cleansing Rule (see above)

1

MARA-MATNR &

MARC-WERKS

Only records where the material or service has been loaded into the Target, i.e. it is relevant.

Upfront Automated

Fields in the Material & Plant XREFs


2

MARA-MTART

if To-Be Material Type = 'ZBAS' then DO NOT extend Material to Purchasing View
else extend Material to Purchasing View


Field in the Material Type XREF


3

MARC-HERKL

This field is only applicable for Plants in Brazil with Material types associated with ZDIR or Spares (ZIND) or
Capital Spares (UNBW, NLAG) and Critical Part = Active. **

Upfront Automated

( T001W-LAND1 = 'BR' ) AND
( ( To-Be Material Type IN ('ZDIR','ZIND') ) OR
( ( To-Be Material Type IN ('UNBW','NLAG') ) AND ( MARC-KZKRI = 'X' ) ) ) **

Rule 2

** This rule has been clarified by Dean Leighton in a Google Chat with Jasleen Madhok, John Hancock and Steve Clarke on Wednesday 12 November 2025.

Data Privacy and Sensitivity

Not Applicable

Extraction

The source for Purchasing data for Materials is PF2 & WP2.  This will be extracted by Syniti and the Relevancy criteria, as specified in object "2019 - Materials Basic Data View" and Material Type relevant to the Purchasing View, applied to identify the records that are applicable for the Target load.

There is no source for Purchasing data for Services, therefore this data will be extracted by Syniti from a DCT (see below in the DCT section for more details).

Extraction Run Sheet

Req #

Requirement Description

Team Responsible

1

Extract data from source system based on relevancy rule

Syniti


Selection Screen

Selection Ref Screen

Parameter Name

Selection Type

Requirement

Value to be entered/set

Not Applicable






Data Collection Template (DCT)

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

There is no source for Purchasing data for Services, therefore this data will be extracted by Syniti from the DCT specified below.  It will be populated by Business for relevant services which they want to migrate.

Materials - Purchasing View DCT Rules

Field Name

Field Description

Rule

Tool Tip

zComment

zDelete

MARC-MATNR

Material Number

Required

The Service Master Number will be used to identify the corresponding Target Material Number.

MARC-WERKS

Plant

Exists in Plant XREF as a To-Be Plant and use dropdown.

Organizational unit where material is maintained/used (e.g., manufacturing site, storage location).



MARA-BSTME

Order Unit

Value in Check Table T006

The unit in which the material is ordered from vendors (may differ from Base UoM).



MARC-EKGRP

Purchasing Group

Value in Check Table T024

Buyer or group of buyers responsible for procurement activities of the material.



MARC-MMSTA***

Material Status (Plant-Specific)

Value in Check Table T141.  Default to Blank.

Controls whether a material can be procured, produced, or sold in a plant.



MARC-MMSTD***

Valid From

If MARC-MMSTA contains a value then MARC-MMSTD must have a value else Blank

Date from which the material status or conditions are effective.



MLAN-TAXIM

Tax Indicator for Material

Value in Check Table TMKM1

Defines if material is taxable, non-taxable, or exempt for purchasing.



MARC-MFRGR*****

Material Freight Group

Value in Check Table TMFG

Groups materials for freight calculation and logistics handling.



MARC-KAUTB***

Automatic PO allowed

X or Blank.  Default X.

Allows automatic generation of POs from requisitions without manual intervention.



MARC-KZKRI****

Critical Part

X or Blank  Default Blank.

Used if we consider this Material a critical part from a planning perspective and/or we want it to be part of every inventory Count while running Cycle Counting. This indicator will be sent to Maestro/kinaxis as part of the Material Master Interface.



MARA-MFRPN

Manufacturer Part Number


General part number assigned by the manufacturer.



MARA-MFRNR

Manufacturer


Vendor or producer of the material.



MARC-HERKL

Manufacturer Country

Value in Check Table T005

Country where the manufacturer is located.



MARC-WEBAZ**

GR Processing Time

Value >= 0

Time (in days) between goods receipt and availability for use.
Only capture a value here if the Material is for a Service (Material Type ZSER).  For other materials this field is captured in the MRP Views.



** MARC-WEBAZ is in the Conversion Spec for 2005, Material Master - MRP Views, however the DCT is for Services and Services will not get the MRP Views so the field has been included to capture this data if required.
*** The MRC fields MMSTA, MMSTD and KAUTB are now defaulted in the Transformation section so they must be removed from the DCT.
**** MARC-KZKRI has been updated with CR0445.  It now has default value which is done in the Transformation Rules.
***** MARC-MFRGR is no longer needed.

Extraction Dependencies

Item #

Step Description

Team Responsible

1

Materials and Plants in scope to be loaded must be identified so that we can limit the extraction to this sub-set of data.

Syniti


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

  1. Perform value mapping and data transformation rules.
    1. Legacy values are mapped to the to-be values (this could include a default value).
    2. Values are transformed according to the rules defined in ADMM.
  2. Prepare target-ready data in the structure and format that is required for loading via the prescribed Load Tool. This step also produces the load data ready for business to perform Pre-load Data Validation.

Transformation Run Sheet

Item #Step DescriptionTeam Responsible

1

Verify that Material data is extracted from both source systems.

Syniti / S2P Data Team

2

Verify that Services data is extracted from the DCT.

Syniti / S2P Data Team

3

Verify that the Material Number XREF has been updated for both material and service data.

Syniti

4

Review the MDS for 2019 to check what Material Types must not be extended to the Purchasing View and update the rule if required

S2P Data Team

5

Transformation jobs are ready for execution.

Syniti

6

Generate Load Files.

Syniti


Transformation Rules

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

1

PF2,WP2,DCT

MARC

MATNR

Material Number

S/4HANA

MARC

MATNR

Material Number

Map Source to Target using Material XREF

2

PF2,WP2,DCT

MARC

WERKS

Plant

S/4HANA

MARC

WERKS

Plant

Map Source to Target using Plant XREF


PF2,WP2,DCT

MARA

BSTME

Order Unit

S/4HANA

MARA

BSTME

Order Unit

Copy As-Is


PF2,WP2,DCT

MARA

VABME

Variable Order Unit

S/4HANA

MARA

VABME

Variable Order Unit

Default to Blank


PF2,WP2,DCT

MARCEKGRPPurchasing Group

S/4HANA

MARCEKGRPPurchasing Group

Map Source to Target using Purchasing Group XREF


PF2,WP2,DCT

MARCMMSTAMaterial Status (Plant-Specific)

S/4HANA

MARCMMSTAMaterial Status (Plant-Specific)

Default to Blank


PF2,WP2,DCT

MARCMMSTDValid From

S/4HANA

MARCMMSTDValid From

Default to '00000000'


PF2,WP2,DCT

MLANTAXIMTax Indicator for Material

S/4HANA

MLANTAXIMTax Indicator for Material

Copy As-Is
For ECC, use the following to go from MARC to MLAN:
MARC-WERKS = T001W-WERKS, MARC-MATNR = MLAN-MATNR AND T001W-LAND1 = MLAN-ALAND


PF2,WP2,DCT

MARCMFRGR****Material Freight Group

S/4HANA

MARCMFRGR****Material Freight Group

Copy As-Is


PF2,WP2,DCT

MARCKAUTBAutomatic PO allowed

S/4HANA

MARCKAUTBAutomatic PO allowed

Default to X.
This field may be updated as a follow-on activity during cut-over after the load.


PF2,WP2,DCT

MARCKZKRI***Critical Part

S/4HANA

MARCKZKRI***Critical Part

Default to: if MARA-MTART IN ('UNBW','NLAG') and PIR > EUR 15k then X else Blank

PIR > EUR 15K will have been calculated when determining MARA-MTART = UNBW or NLAG in Conversion Spec for 2019, therefore store the result of this calc in a table so it can be referenced here.

Here is a summary of how to calculate PIR value:
Use EINA:  EINA-MATNR = MARA-MATNR
Use EINE:  EINE-INFRA = EINA-INFRA
if EINE-WAERS <> 'EUR' then convert using TCURR
Use TCURR:  TCURR-FCURR = EINE-WAERS, TCURR-TCURR = 'EUR', GDATU = 99999999 - Migration_Conversion_Date (e.g. 99999999 - 20260420 = 79739579)
Migration_Conversion_Date:  Date set by Project to use for currency conversions, e.g. 20 April 2026.
Convert to EUR:  EINE-NETPR / TCURR-UKURS
PIR value: take MAX of ( NETPR_in_EUR / EINE-PEINH )


PF2,WP2,DCT

MARAMFRPNManufacturer Part Number

S/4HANA

MARAMFRPNManufacturer Part Number

if S4H.MARA-MTART IN ('ZIND','UNBW','NLAG') and LEGACY.MARA-MFRPN is not Blank and LEGACY.MARA-MFRNR = LEGACY_LFA1-LIFNR and LEGACY.LFA1-LOEVM = '' then Copy As-Is else Blank


PF2,WP2,DCT

MARAMFRNRManufacturer

S/4HANA

MARAMFRNRManufacturer

if S4H.MARA-MTART IN ('ZIND','UNBW','NLAG') and LEGACY.MARA-MFRPN is not Blank and LEGACY.MARA-MFRNR = LEGACY_LFA1-LIFNR and LEGACY.LFA1-LOEVM = '' then Copy As-Is else Blank


PF2,WP2,DCT

MARCHERKLCountry of Origin

S/4HANA

MARCHERKLCountry of Origin

if S4H.MARA-MTART IN ('ZIND','UNBW','NLAG','ZDIR') then Copy As-Is else Blank


DCT only

MARC

WEBAZ**

GR Processing Time

S/4HANA

MARCWEBAZ**GR Processing Time

Copy As-Is
WHERE Source = DCT and S4H.MARA-MTART = 'ZSER'
ELSE ignore

** MARC-WEBAZ is in the Conversion Spec for 2005, Material Master - MRP Views, however Service Materials will not get this View, so it will be captured in the DCT, along with all the other data for Services.  If the DCT is used for Material Types other than ZSER then this value must be excluded.
*** MARC-KZKRI has been updated with CR0445.
**** MARC-MFRGR is no longer needed.

Transformation Mapping

Mapping Table Name

Mapping Table Description

Link

Material

XREF

Conversion Specification - Mappings

PlantXREFConversion Specification - Mappings
Purchasing GroupXREFConversion Specification - Mappings

Transformation Dependencies

List the steps that need to occur before transformation can commence
Item #Step DescriptionTeam Responsible

1

Data has been extracted from sources systems

Syniti

2

Deduplication is completed

Syniti & S2P Data Team

3

Configuration should be completed - (Config documents should be complete)

S2P Functional Team

4

Ensure DCT completeness

S2P Data Team

5

Value mapping and XREF tables are ready

Syniti & S2P Data Team


Pre-Load Validation

Project Team

Completeness

TaskAction

Verify Record Count

The number of records presented after relevancy checks and validation, as well as the number of records in the DCT, needs to be correct compared to the staged data in Syniti ADMM.

Completeness check

All fields required as per mapping template rules must be completed. Syniti ADMM standard validity reports checking each field in Syniti must be built.


Accuracy

TaskAction

Conversion Accuracy

Verify that the data staged in the preload tables are correct in terms of the mapping rules. This will be done via Syniti ADMM standard reports..

Review Error Reports

Review and correct the errors.  Achieve a zero-error record count as much as possible. Raise defects for data remediated and requiring a correction in the source data.


Business

Completeness

TaskAction

Completeness Check

Business should compare legacy record counts, taking into account the reduction from the relevancy and deduplication processes, against the record count in the preload table.


Accuracy

TaskAction

Conversion Accuracy

Business team to verify that the data staged in the preload tables are correct in terms of the mapping rules. This will be done via Syniti ADMM reports/SAP reports.


Load

The load process includes:

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

Load Run Sheet

Item #Step DescriptionTeam Responsible

1

Verify data extracted

Data Specialist/Functional - S2P

2

Verify data combined from both source systems and DCT

Data Specialist/Functional - S2P

3

Verify Material, Plant and Purchasing Group XREFs are ready

Data Specialist/Functional - S2P

4

Stage data for transformations

Syniti

5

Run transforms

Syniti

6

Execute pre-load report

Syniti

7

Validate preload report - release

Data Specialist/Functional - S2P

8

Prepare and simulate

Syniti

9

Pre-load verification and approval to load

Functional/Data Owner - S2P

10

Load to S4

Syniti

11

Complete Jira steps, Volumes and Timings

All - where applicable

12

Execute post-load report

Syniti

13

Post-load report verification/validation

Data Specialist/Functional/Data Owner - S2P

14

Object load completion approval

Data Owner - S2P


Load Phase and Dependencies

Configuration

Item #Configuration Item

MM Config Values




Conversion Objects

Object #Preceding Object Conversion Approach
1Material Master - Basic View (2019)
2Materials - General Plant Data / S.Loc Data (2010)

Error Handling

Error TypeError DescriptionAction Taken
DataSource Material not linked to a Target Material in the XREFFix incorrect data
DataSource Plant not linked to a Target Plant in the XREFFix incorrect data
DataSource Purchasing Group not linked to a Target Purchasing Group in the XREFFix incorrect data

Data

Duplicates

Fix incorrect data

Load

Authorization errors

Apply for the applicable authorization permission and retry

Load

Technical load failures - If using MC - Simulation errors, etc

Investigate error and rectify. Retry simulation and/or load

Config

Configuration is missing in the Target System

Missing config added in the Target System


Post-Load Validation

Project Team

Post-Load Steps

Step Description

Team Responsible

Execute post-load report

Syniti

Post-load report verification/validation

Data Specialist/Functional/Data Owner - S2P

Object load completion approval

Data Owner - S2P

Completeness

TaskAction

Verify Count

The number of records presented in the post-load needs to be compared to the preload – Syniti report

Field by field check

Compare source data staged in the preload tables to target data in the load tables

Accuracy

TaskAction

Conversion Accuracy

Business Data Owner/s to verify that all the data in the load table/file is accurate as per endorsed transformation/mapping rules (and signed-off DCT data).

Load

The load process includes:

  1. Execute the automated data load into target system using load tool or product the load file if the load must be done manually
  2. Once the data is loaded to the target system, it will be extracted and prepared for Post Load Data Validation

Load Run Sheet

Item #Step DescriptionTeam Responsible

1

Go to <Load Tool>

SyWay S2P Data Team

2

Load 3 records for < > to validate if data is loaded successfully without errors

SyWay S2P Data Team

3

Load 3 records for < > to validate if data is loaded successfully without errors

SyWay S2P Data Team

4

Proceed with full load if steps 2 and 3 are validated

SyWay S2P Data Team

5

Validate few records loaded by accessing standard transactions from S/4HNA eg. MM03

SyWay S2P Data Team

6

Generate post load report if step 5 is validated

SyWay S2P Data Team

Load Phase and Dependencies

Configuration

Item #Configuration Item

Conversion Objects

Object #Preceding Object Conversion Approachlist the exact title of the conversion object of only the immediate predecessor – this will then confirm the DDD (Data Dependency Diagram)

Error Handling

Error TypeError DescriptionAction Taken

Post-Load Validation

Project Team

Completeness

TaskAction

Verify Count

SyWay S2P Data Team to verify the record count created in target S/4 HANA by accessing post load reports in dspMigrate or standard reports from S/4 HANA.


Accuracy

TaskAction

Verify Logs

Check if there is data that failed to load and perform the necessary actions (e.g. register as post load issue or attempt to load the record again, etc.).


Business

Completeness

TaskAction

Verify Count

The number of records presented in the preload needs to be compared to the post-load Syniti report.

Missing data

Check missing data which was supposed to be loaded.

Reconciliation

Participate in Post-load walkthroughs.

Field by field check

Perform random Field by Field checks by comparing source data staged in the preload tables to target data in the load tablesDownload Post Load Reports from dspMigrate and verify that the record count loaded in the target S/4 HANA is the same count as of the endorsed load file.


Accuracy

TaskAction

Conversion Accuracy

Verify that the Material data in target S/4 HANA were was loaded correctly via dspMigrate Syniti post-load reports or standard reports from S/4 HANA.


Key Assumptions

  • Master Data Standard is up to date as on the date of documenting this conversion approach and data load.
  • Materials - Purchasing Data is in scope based on data design and any exception requested by business.


See also

Change log

Change History
limit10

Workflow history

Workflow Report
parent@self
hideheadertrue
typeapprovals