You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 48 Next »

Status

  Revision in Progress

Owner
Stakeholders

Purpose

The purpose of this document is to define the conversion approach to create Materials - Basic Data View in S/4 HANA.


Conversion Scope

The scope of this document covers the approach for converting active Materials - Basic Data 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. Material Types ZUNB, ZBOM, ZPRC will be included 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 (remove any records in EKKO/EKPO where LOEKZ = 'X') and use EKPO/AEDAT for previous 3 years filter
    2. For sales data use VBAK/VBAP tables
    3. For production data use AFKO/AFPO tables 
  6. Additionally, we can check material movements using MKPF/MSEG tables (and Transaction Types: IB,ID,IZ,RS,SI,WA,WE,WF,WH,WI,WL,WO,WQ,WR,WS,WV,WZ)
  7. 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
  8. Have current stock/open inventory
    1. For Open Inventory use the following tables:

      MARD

      MKOL (Consignment stock)

      MSKA (Sales Order stock)

      MSLB (Special stock)

      MSPR (Project stock)

  9. We will include all BOM data for materials in scope using tables: MAST/STKO/STPO
  10. 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
  11. Deletion Flags (Table/Field) are as follows: MARA/LVORM = 'X' MARA/MSTAE = Z3, Z4, ZZ (PF2 system) Z0 (WP2 system)
  12. 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















Additional Information

Multi-language Requirement

Material Master will have a default description available in English.
Multi language is supported for Materials. Login via a different language will show the description displayed in the logon language if the language key is maintained.

Document Management

Not Applicable

Legal Requirement

Not Applicable

Special Requirements




Target Design

The technical design of the target for this conversion approach.

TableFieldData ElementField DescriptionData TypeLengthRequirement
S_MARAMATNR
Material NumberText (CHAR)40Mandatory
S_MARAMTART
Material TypeText (CHAR)4Mandatory
S_MARAMATKL
Material GroupText (CHAR)9Mandatory
S_MARAMBRSH
Industry SectorText (CHAR)1    Mandatory
S_MARAMAKTX
DescriptionText (CHAR)40Mandatory
S_MARASPRAS
Language KeyText (CHAR)1  Mandatory
S_MARAMEINS
Base Unit of Measure (ISO Format)Text (CHAR)3   Mandatory
S_MARAAENNR
Change NumberText (CHAR)6Conditional
S_MARAREVLV
Revision LevelText (CHAR)2Conditional
S_MARAEAN11
GTINText (CHAR)18Conditional
S_MARANUMTP
GTIN CategoryText (CHAR)1Conditional
S_MARASPART
DivisionText (CHAR)2    Mandatory
S_MARABISMT
Old Material NumberText (CHAR)40Mandatory
S_MARAPRDHA
Product HierarchyText (CHAR)18   Conditional
S_MARAXCHPF
Batch Management Required Ind.Text (CHAR)1Conditional
S_MARAMLGUT
Has EmptiesText (CHAR)1Conditional
S_MARADATAB
Valid FromDate
Conditional
S_MARALIQDT
Deletion DateDate
Conditional
S_MARANORMT
Industry Standard DescriptionText (CHAR)18Conditional
S_MARAGROES
Size/DimensionsText (CHAR)32Conditional
S_MARALABOR
Laboratory / Design OfficeText (CHAR)4Conditional
S_MARAEXTWG
External Product GroupText (CHAR)18Conditional
S_MARAMTPOS_MARA
General Item Category GroupText (CHAR)4Conditional
S_MARABEGRU
Authorization GroupText (CHAR)4Conditional
S_MARAMSTAE
Cross-Plant Product StatusText (CHAR)2Conditional
S_MARAMSTDE
Valid-From DateDate
Conditional
S_MARAQMPUR
Quality Manag. in Procurement Is ActiveText (CHAR)1Conditional
S_MARAANP
ANP CodeNumber (NUMC)9Conditional
S_MARABRGEW
Gross WeightNumber (NUMC)

13

Decimals: 3

Conditional
S_MARANTGEW
Net WeightNumber (NUMC)

13

Decimals: 3

Conditional
S_MARAGEWEI
Unit of Weight (ISO Format)Text (CHAR)3Conditional
S_MARALAENG
LengthNumber (NUMC)

13

Decimals: 3

Conditional
S_MARABREIT
WidthNumber (NUMC)

13

Decimals: 3

Conditional
S_MARAHOEHE
HeightNumber (NUMC)

13

Decimals: 3

Conditional
S_MARAMEABM
Unit for Length/Width/Height(ISO Format)Text (CHAR)3Conditional
S_MARAVOLUM
VolumeNumber (NUMC)

13

Decimals: 3

Conditional
S_MARAVOLEH
Volume UnitText (CHAR)3Conditional
S_MARACAPAUSE
Capacity UsageNumber15Conditional
S_MARACHML_CMPLNC_RLVNCE_IND
Compliance RelevantText (CHAR)1Conditional
S_MARAKZKFG
Product Is ConfigurableText (CHAR)1Conditional
S_MARABSTME
Order Unit of Measure (ISO Format)Text (CHAR)3Mandatory
S_MARAEKWSL
Purchasing Value KeyText (CHAR)2Mandatory
S_MARAVABME
State of Variable Purchase Order UnitText (CHAR)1Conditional
S_MARABMATN
Internal Product NumberText (CHAR)18Conditional
S_MARAMFRPN
Manufacturer Part NumberText (CHAR)40Conditional
S_MARAMFRNR
Manufacturer NumberText (CHAR)10Conditional
S_MARAMPROF
Manufacturer Part ProfileText (CHAR)4Conditional
S_MARATRAGR
Transportation GroupText (CHAR)4Conditional
S_MARAMSTAV
Cross-Distribution Chain Product StatusText (CHAR)2Conditional
S_MARAPROFL
DG Indicator ProfileText (CHAR)3Conditional
S_MARAKZUMW
Environmentally RelevantText (CHAR)1Conditional
S_MARAILOOS
In Bulk/LiquidText (CHAR)1Conditional
S_MARAIHIVI
Highly ViscousText (CHAR)1Conditional
S_MARAMSTDV
Valid From Date for StatusDate
Conditional
S_MARAATTYP
Material CategoryText (CHAR)2Conditional
S_MARAMAGRV
Product Group: Packaging MaterialsText (CHAR)80Conditional
S_MARAVHIART
Packaging Product TypeText (CHAR)80Conditional
S_MARAERGEW
Allowed Packaging WeightText (CHAR)13Conditional
S_MARAERGEI
Unit of Allowed Packaging WeightText (CHAR)80Conditional
S_MARAERVOL
Allowed Packaging VolumeText (CHAR)13Conditional
S_MARAERVOE
Unit of Allowed Packaging VolumeText (CHAR)80Conditional
S_MARAKZGVH
Packaging Product Is Closed PackagingText (CHAR)1Conditional
S_MARAVOLTO
Excess Volume Tolerance for HUNumber3Conditional
S_MARAIPRKZ
Period Indicator for Shelf LifeText (CHAR)80Conditional
S_MARARAUBE
Storage ConditionsText (CHAR)80Conditional
S_MARATEMPB
Temperature Conditions IndicatorText (CHAR)2Conditional
S_MARASTOFF
Hazardous Product NumberText (CHAR)40Conditional
S_MARAWESCH
Number of Goods Receipt/Issue SlipsNumber13Conditional
S_MARAXGCHP
Indicator: Approved Batch Rec. RequiredText (CHAR)1Conditional
S_MARAMHDHB
Total Shelf LifeNumber4Conditional
S_MARAMHDRZ
Minimum Remaining Shelf LifeNumber4Conditional
S_MARASLED_BBD
Indi. for the Shelf Life Expiration DateText (CHAR)80Conditional
S_MARAMHDLP
Storage PercentageNumber3Conditional
S_MARARDMHD
Rounding Rule for Calculation of SLEDText (CHAR)80Conditional
S_MARASERIAL
Serial Number ProfileText (CHAR)80Conditional
S_MARAHAZMAT
Relevant for Hazardous SubstancesText (CHAR)1Conditional
S_MARAMAABC
ABC IndicatorText (CHAR)1Conditional
S_MARAHERKL
Country/Region of OriginText (CHAR)3Optional
S_MARAEKGRP
Purchasing GroupText (CHAR)3Mandatory
S_MARATAKLV
Tax ClassificationText (CHAR)1Mandatory
S_MARALADGR
Loading GroupText (CHAR)4Conditional
S_MARAPSTATQ
Indicator: QualityText (CHAR)1Automatic
S_MARAPSTATV
Indicator: SalesText (CHAR)1Automatic
S_MARAPSTATL
Indicator: StorageText (CHAR)1Automatic
S_MARAPSTATE
Indicator: PurchasingText (CHAR)1Automatic


Data Cleansing

IDCriticalityError Message/Report DescriptionRuleOutputSource System

2019-001

C1

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.


PF2/WP2

2019-002

C1

Description format

Material descriptions must adhere to S4 standardization so no special characters etc and must not exceed character limit


PF2/WP2

2019-003

C1

UoM alignment

All material UoMs to adhere to S4 standardization. Confirmation regarding EA/PC format.


PF2/WP2

2019-004

C1

Check Gross and Net Weights

Check for missing weights and that Gross Weight >= Net


PF2/WP2

2019-005

C1

Country of Origin

Check Country of Origin exists for procured materials


PF2/WP2

2019-006

C1

Duplicate materials excluded

Check for materials with same Long/Short Description

Check Old Material Number field

Check Materials with same EAN

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



Conversion Process

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


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

Materials - Basic Data 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
1PF2/WQ2S_MARAMATNRMaterial NumberS/4HANAS_MARAMATNRMaterial NumberGenerate new Material number in Target System and maintain mapping in reference table
2PF2/WQ2S_MARAMBRSHIndustry SectorS/4HANAS_MARAMBRSHIndustry SectorCopy from source to target system
3PF2/WQ2S_MARAMTARTMaterial TypeS/4HANAS_MARAMTARTMaterial TypeMap from source to target using Material Type mapping table
4PF2/WQ2S_MARAMAKTXDescriptionS/4HANAS_MARAMAKTXDescriptionCopy from source to target system in adherence to S4H Data Standard (ie. descriptions to be cleansed so that non standard special characters are excluded)
5PF2/WQ2S_MARASPRASLanguage KeyS/4HANAS_MARASPRASLanguage KeyEN description to be created if not available. Copy local descriptions from source if required.
6PF2/WQ2S_MARAMEINSBase Unit of Measure (ISO Format)S/4HANAS_MARAMEINSBase Unit of Measure (ISO Format)Map from source to target in adherence to S4H Data Standard
7PF2/WQ2S_MARAMATKLMaterial GroupS/4HANAS_MARAMATKLMaterial GroupMap from source to target using Material Group mapping table
8PF2/WQ2S_MARASPARTDivisionS/4HANAS_MARASPARTDivisionMap from source to target in adherence to S4H Data Standard
9PF2/WQ2S_MARAPRDHAProduct HierarchyS/4HANAS_MARAPRDHAProduct HierarchyMap from source to target using Product Hierarchy mapping table
10PF2/WQ2S_MARAMTPOS_MARAGeneral Item Category GroupS/4HANAS_MARAMTPOS_MARAGeneral Item Category GroupCopy from source to target system
11PF2/WQ2S_MARABRGEWGross WeightS/4HANAS_MARABRGEWGross WeightCopy from source to target system
12PF2/WQ2S_MARANTGEWNet WeightS/4HANAS_MARANTGEWNet WeightCopy from source to target system
13PF2/WQ2S_MARAGEWEIUnit of Weight (ISO Format)S/4HANAS_MARAGEWEIUnit of Weight (ISO Format)Copy from source to target system in adherence to S4H Data Standard
14PF2/WQ2S_MARAPROFLDG Indicator ProfileS/4HANAS_MARA
Compliance Relevant IndicatorIf DG Ind Profile or Environmentally Rel is populated/ticked then set Compliance Relevant Indicator to X in S4H
15PF2/WQ2S_MARAKZUMWEnvironmentally RelevantS/4HANAS_MARA
Compliance Relevant IndicatorIf DG Ind Profile or Environmentally Rel is populated/ticked then set Compliance Relevant Indicator to X in S4H


Transformation Mapping

Mapping Table NameMapping Table Description

Material Type

Mapping of legacy Material Types to target system value

Material Group

Mapping of legacy Material Groups to target system value

Product HierarchyMapping of legacy Product Hierarchies to target system value
Lab/OfficeMapping of legacy Lab/Office values to target system value
DivisionMapping of legacy Division values to target system value
Authorization GroupMapping of legacy Authorization Group values to target system value

Transformation Dependencies

List the steps that need to occur before transformation can commence
Item #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

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.






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.






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 Approach

list the exact title of the conversion object of only the immediate predecessor – this will then confirm the DDD (Data Dependency Diagram)




Error Handling

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

Download 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 loaded correctly via dspMigrate 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 - Basic Data is in scope based on data design and any exception requested by business.


See also

Change log

Version Published Changed By Comment
CURRENT (v. 48) Apr 29, 2026 14:44 HANCOCK-ext, John
v. 313 Apr 28, 2026 13:55 HANCOCK-ext, John
v. 312 Apr 27, 2026 07:42 HANCOCK-ext, John
v. 311 Apr 21, 2026 08:04 HANCOCK-ext, John
v. 310 Apr 21, 2026 08:01 HANCOCK-ext, John
v. 309 Apr 21, 2026 07:51 HANCOCK-ext, John
v. 308 Apr 10, 2026 12:02 HANCOCK-ext, John
v. 307 Apr 09, 2026 14:07 HANCOCK-ext, John
v. 306 Mar 06, 2026 13:37 MADHOK-ext, Jasleen
v. 305 Mar 03, 2026 17:15 HANCOCK-ext, John

Go to Page History

Workflow history

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

  • No labels