Versions Compared

Old Version 2

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

Saved on

compared with

New Version Current

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

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Status

Page Status

Owner

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

Stakeholders

Purpose

The purpose of this document is to define the conversion approach to create Material Master- Additional Data in S/4 HANA. 


Conversion Scope

The scope of this document covers the approach for converting active Materials - Additional Data 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.

The data from legacy system may include:

  1. Uncleansed data or duplicated records

The data from legacy system excludes:

  • All materials flagged for deletion
  • Any blocked or obsolete materials

    • Relevancy Rules

    This object is migrated after Material Basic Data, therefore only materials in scope for object '2019 - Materials Basic Data View' are in scope for this object.

    Click link below to go to the Conversion Spec for 2019 to see the full set of relevancy rules.

    https://wiki.syensqo.com/x/-Z7ZNw

    Any inactive materials that are out of scope


    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

    (Additional Data)

    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. 

    that meet the relevancy criteria of Material Basic Data.

    The Material Master Records will be extracted or collected via DCT.

    		700,000S4H260
    500,000S4H500
    ,000

    Additional Information

    Multi-language Requirement

    MDS Documents

    Google Drive Live Link
    urlhttps://docs.google.com/spreadsheets/d/1dx36Ge3n1WXycFmho2qXdVoBEiFsdJOj/edit?usp=sharing&ouid=114908176752927480470&rtpof=true&sd=true


    Multi-language Requirement

    Multi language is supported for Materials - Additional Data. Login via a different language will show the description Multi language is supported for Materials - Additional Data. 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

    Data Cleansing

    IDCriticalityError Message/Report DescriptionRuleOutputSource System

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

    DCT Rules

    Field NameField DescriptionRule

    Extraction Dependencies

    The following languages are allowed:

    • Core languages: EN - English, FR - French, IT - Italian and ZH - Mandarin.
    • Additional languages: PT - Brazilian Portuguese, DE - German, ES - Spanish
    • Additional Supplier languages that are possible: PL - Polish, JA - Japanese, KO - Korean, FI - Finnish, BG - Bulgarian, RU - Russian, TH- Thai, ZF - Chinese traditional, SK - Slovak, Z9 - Brazil Portuguese. 

    Document Management

    Not Applicable

    Legal Requirement

    Not Applicable

    Special Requirements

    Not Applicable


    Target Design

    The technical design of the target for this conversion approach.

    Sequence TableTechnical FieldField DescriptionField FormatField Length

    Requirement


    001MARAMATNRMaterialText (CHAR)40System
    002MAKTSPRASLanguageText (CHAR)1Required
    003MAKTMAKTXDescriptionText (CHAR)40Required
    004MARMMEINHAUnText (CHAR)3Conditional
    005MARMUMREZY (Numerator)DEC5Conditional
    006MARMUMRENX (Denominator)DEC5Conditional
    007MARMMEINSBUnText (CHAR)3Automatic
    008MARMEAN11EAN/UPCText (CHAR)18Conditional
    009MARMNUMTPCtText (CHAR)2Conditional
    010MARMLAENGLengthQUAN13,3Conditional
    011MARMBREITWidthQUAN13,3Conditional
    012MARMHOEHEHeightQUAN13,3Conditional
    013MARMMEABMUnit (Dimensions)UNIT3Conditional
    014MARMVOLUMVolumeQUAN13,3Conditional
    015MARMVOLEHVol. UnitUNIT3Conditional
    016MARMBRGEWGross WeightQUAN13,3Conditional
    017MARMNTGEWNet weight(derived)QUAN13,3Automatic
    018MARMGEWEIWeight UnitUNIT3Conditional
    019MARMNEST_FTR

    Rem. Vol. After Nesting

    		DEC3Not Required
    020MARMMAX_STACKMax. Stacking FactorQUAN3Not Required
    021MARMTOP_LOAD_FULLMaximum Top LoadQUAN13,3Not Required
    022MARMTOP_LOAD_FULL_UOMUoM of Maximum Top Load on Full PackageUNIT3Not Required
    023MARMCAPAUSECapacity UsageDEC15,3Not Required
    024MARMTY2TQCategory of Unit of MeasureText (CHAR)1Not Required
    025MARMMEINHAlternative Unit of Measure for stock keeping unit
    (Derived)    		Text (CHAR)3System
    026T006AMSEHTAlternative UOM description
    (Derived)    		Text (CHAR)10System
    027MEANHPEANMain indicator: EANText (CHAR)1Conditional
    028MEANEAN11EAN/UPCText (CHAR)18Conditional
    029MEAN

    EANTP

    		EAN CategoryText (CHAR)2Conditional
    030DRAWDOKARDocument TypeText (CHAR)3Not Required
    031DRAWDOKNRDocument NumberText (CHAR)25Not Required
    032DRAWDOKVRLast Document VersionText (CHAR)2Not Required
    033DRAWDOKTLDocument PartText (CHAR)3Not Required
    034DRAWDOKVRDocument VersionText (CHAR)2Not Required
    035DRAWDKTXTDocument DescriptionText (CHAR)40Not Required
    036DRAWSTATUStatus TextText (CHAR)3Not Required
    037DRAWOBJKYObject DescriptionText (CHAR)40Not Required
    038DRAWLOEKZDeletion IndicatorText (CHAR)1Not Required
    039DRAWAENNRChange NumberText (CHAR)12Not Required
    040DRAWDOKGRAuthorization GroupText (CHAR)4Not Required
    041DRAWHERKLOriginText (CHAR)3Not Required
    042DRAWMANDTClientText (CHAR)3Not Required
    043DRAW

    DRLID

    		Document Relationship indicatorText (CHAR)3Not Required
    044T002TSPTXTLanguage keyText (CHAR)2Conditional
    045STXLCLUSTDText, Text ID: GRUNText (CHAR)132Conditional
    046T002TSPTXTLanguage keyText (CHAR)2Not Required
    047STXLCLUSTDText, Text ID: PRUEText (CHAR)132Not Required
    048T002TSPTXTLanguage keyText (CHAR)2Conditional
    049STXLCLUSTDText, Text ID: IVERText (CHAR)132Conditional


    Data Cleansing

    IDCriticalityError Message/Report DescriptionRuleOutputSource System

    2021-001

    C1

    UoM alignment

    Check that all material AUoMs adhere to S4 standardization, refer to UoM mapping table:

     

    Google Drive Live Link
    urlhttps://docs.google.com/spreadsheets/d/1EW0XaNVb_oDk6Pm1ikpHoPdC0qYgc17Y/edit?usp=sharing&ouid=114908176752927480470&rtpof=true&sd=true


    		PF2/WP2
    2021-002C1UoM calculations

    Check that all UoM conversions are correct eg. 1 Ton = 1000 kg


    		PF2/WP2
    2021-003C1Additional Descriptions

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

    Refer to 'Informal Words' document (Special Characters tab):

    Google Drive Live Link
    urlhttps://docs.google.com/spreadsheets/d/1ltgenyM2Xn8bHC4pNlwv0QfkWEIXL1sZ/edit?usp=sharing&ouid=114908176752927480470&rtpof=true&sd=true


    		PF2/WP2
    2021-004C1Default DescriptionAll materials must have an EN description by default
    		PF2/WP2
    2021-006C1LanguageCheck that all Suppliers have their local language included in list
    		PF2/WP2
    2021-007C1EAN/GTINCheck if all EAN/GTIN codes are still valid
    		PF2/WP2
    2021-008C1EAN/GTINCheck that all AUoM have a unique EAN
    		PF2/WP2
    2021-009C1EAN/GTINCheck that no duplicates exist for EAN
    		PF2/WP2
    2021-010C1Additional Validation ReportsAdditional Validation Reports will be added in Validation_Reports_link
    		 PF2/WP2



    Conversion Process

    The high-level process 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

    Data Privacy and Sensitivity

    Not Applicable


    Extraction

    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

    Syniti


    Selection Screen

    Selection Ref ScreenParameter NameSelection TypeRequirementValue to be entered/set
    Not Applicable




    Data Collection Template (DCT)

    Materials & Service Master


    draw.io Diagram
    bordertrue
    diagramNameAdditional Data schema
    simpleViewerfalse
    width
    linksauto
    tbstyletop
    lboxtrue
    diagramWidth241
    height401
    revision3


    SAP StructureSAP FieldTypeLengthField DescriptionImportanceRules
    MARM - Alternative Unit of Measure 1:n
    MARMMATNRCHAR18Material Numbermandatory for sheetMaterial Number*

    A key that uniquely identifies the product.
    MARMBRGEWDEC15 (3 decimals)Gross Weight
    		Gross Weight

    Gross weight expressed in the unit of weight specified by you in the Unit of weight field.
    The system can use the gross weight at a later stage, depending on what kind of capacity check you run, to check storage bin capacity for warehouse management purposes.
    MARMGEWEIUNIT3Weight Unit
    		Unit of Weight (ISO Format)

    Unit referring to the gross weight or net weight of the product.
    If a product is created with sales data, the field unit of weight gets mandatory. Please provide an entry in this field or a default unit of weight is defined in product groups settings.
    MARMVOLUMDEC15 (3 decimals)Volume
    		Volume

    Space that the product occupies per unit of volume. The volume refers to the unit specified in the "Volume unit" field. The volume and its unit always refer to the base unit of measure.
    MARMVOLEHUNIT3Volume Unit
    		Volume Unit

    If you specify a volume, you have to enter the corresponding volume unit here.
    MARMEAN11CHAR18EAN/UPC

    Copy from source to target system

    Maintain EAN/UPC No available from the manufacturer and migrate if values exist in legacy.

    Any EAN currently in the system has to be either 8,12,13,14 digits long (as per GS1 standards)

    Not applicable for ZSER Materials.

    MARMNUMTPCHAR2EAN category

    Copy from source to target system

    If both the EAN field and the EAN category field contain values, the system assumes that you want to enter the EAN externally.

    For 8 digit EAN codes, category should be set as HK, otherwise default to HE.

    Not applicable for ZSER Materials.


    SAP StructureSAP FieldTypeLengthField DescriptionImportanceRules
    MEAN - Additional GTINs 1:n
    MEANMATNRCHAR18Material Numbermandatory for sheetMaterial Number*

    A key that uniquely identifies the product.
    MEANMEINHUNIT3Alternative Unit of Measuremandatory for sheetThere are multiple situations in which Alternative UOM should be maintained as list below -
    1.) For product compliance (SVT, DG quantity limit checks) and Sustainability (CSRD reporting), Sustainability team should be able to derive mass units for any product in our scope (based on compliance relevant indicators). It means the needed conversion will be available in the product master for products not created in mass units"
    Alternate UoM maintained in the material master for the materials (marked as compliance relevant) so the system is able to convert to mass units and utilize it for the compliance assessment checks in S2S.
    2.) For Material type = ZDIR(Direct materials - diluted chemical product), % concentration is specified as alternative UOM where Alt Un = KAI(Kilogram Active ingredient and the relevant conversion to Base unit KG will be maintained.
    eg: Sulphuric acid 98% concentrate will be maintained as 100 KG will be 98 KAI.
    2.) Alternative units of measure can also be defined to identify packages or lager containers for smaller units of measure such as cartons, boxes, bottles, barrels, pallets (storage unit types) and so on. A material can be stored, transported and sold in various units of measure.
    However, you only need to maintain the fields of the units of measure if they deviate from the base unit of measure. If no other fields with units of measure are maintained, the system automatically takes the base unit of measure as a basis for its calculations.
    MEANHPEANCHAR1Main Indicator (EAN)ConditionalSpecifies that the International Article Number (EAN) is the main EAN for the unit of measure.
    This will default to 'X' for the current migration
    Not Applicable for ZSER materials.
    MEANEAN11CHAR18GTIN (EAN/UPC)mandatory for sheet

    Copy from source to target system

    Maintain EAN/UPC No available from the manufacturer and migrate if values exist in legacy.

    Any EAN currently in the system has to be either 8,12,13,14 digits long (as per GS1 standards)

    Not applicable for ZSER Materials.

    MEANEANTPCHAR2GTIN Categorymandatory for sheet

    If both the EAN field and the EAN category field contain values, the system assumes that you want to enter the EAN externally.

    For 8 digit EAN codes, category should be set as HK, otherwise default to HE.

    Not applicable for ZSER Materials.


    SAP StructureSAP FieldTypeLengthField DescriptionImportance
    MAKT - Material Descriptions (short/long material text per language) 1:n
    MAKTMATNRCHAR18Material Numbermandatory for sheetMaterial Number*

    A key that uniquely identifies the product.
    MAKTSPRASCHAR2   Language Keymandatory for sheetLanguage Key*

    The language key indicates

    - the language in which texts are displayed,
    - the language in which you enter texts,
    - the language in which the system prints texts.
    MAKTMAKTXCHAR40    Material Descriptionmandatory for sheetMaterial Description*

    Text that describes the product in more detail.
    Note: You can maintain additional descriptions (for languages other than those provided on the 'Basic Data' sheet).


    SAP StructureSAP FieldTypeLengthField DescriptionImportance
    STXH / STXL - Long Text (Compressed Text Lines)
     STXH / STXLTDOBJECTCHAR10Text Objectmandatory for sheet

    Text object (e.g. MATERIAL, EINA, EKKO, LFA1, ASMD, etc.)

     STXH / STXLTDNAMECHAR70Text Name (technical key)mandatory for sheet

    Text name / key (material, vendor, info record key, document, etc.)

     STXH / STXLTDIDCHAR4Text IDmandatory for sheet

    For Basic Data Long Text TDID = GRUN, for Internal Comment TDID = IVER 

     STXH / STXLTDSPRASLANG1Language Keymandatory for sheet

    Language key (1-char SAP code: E, F, D, P, S, etc.)

     STXH / STXLTDLINECHAR132Text Line Contentmandatory for sheet

    Text line content

    CR0407 - date 16/03/26   CR0407-DCT.xlsx

    SAP StructureSAP FieldTypeLengthField DescriptionImportanceComments/ Tooltip
    MAKT - Material Descriptions (Different Languages

    		SystemCHAR Systemmandatory

    If Material/Lang_key in ECC then populate = 'ECC' else value = 'CONSTRUCT'

    System is for MATNR/SPRAS - Allowed values ECC/CONSTRUCT


    		SOURCE_SYSTEMCHAR Source mandatory

    Source System is for MATNR and allowed values are: SAPPF2/SAPWP2/Construct

    MAKTMATNRCHAR18Material Numbermandatory

    Material 

    MAKTSPRASLANG2Language Keymandatory

    Language key ( example EN/FR/DE..)

    MAKTMTARTCHAR4Legacy Material Type mandatory if in ECC

    Automatic population from ECC data based on Material Number

    MAKTMATKLCHAR9LegacyMaterial_Grpmandatory if in ECC

    Automatic population from ECC data based on Material Number

    MAKTMAKTXCHAR40Legacy_Material_Descriptionmandatory if in ECC

    Automatic population from ECC data based on Material Number

    MAKTMTARTCHAR4S4_ Mat Type(Derived)mandatory

    Populate S4 Material type based on Material Type mapping from Data team

    MAKTMATKLCHAR9S4_MAT_GRPmandatory

    Populate based on Material Group mapping from Project team

    MAKTMAKTXCHAR40S4-MAKTXmandatory

    1) Populate from Proposed descrip from Data team

    2) Business  input allowed


    		   Formatting_Statusoptional

    Populate from 'Proposed S4 descrip' from Data team

    Dropdown values - 

    • Copy
    • Fixed
    • Unknown

    		  1Relevancy_Flagmandatory if in ECC

    Automatic population from Deduplication Data (Including Relevancy rule)


    		  1Business_ApprovalConditional

    Business  input allowed


    		  1Re-Approval_RequiredConditional

    Automatic population: If S4 material type or S4 material group is changed then Re-Approval_Required Flag will change to 'Yes' and field 'Business_Approval' will be set to 'Blank'.


    		   Commentoptional

    Business  input allowed

    MAKT     

     


    Extraction Dependencies

    Item #Step DescriptionTeam 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

    2

    All data cleansing tasks have been completed

    S2P Data Team

    3

    All dedupe tasks have been completed

    Syniti/S2P Data Team

    4

    All description translations have been completed

    S2P Data Team



    Transformation

    The Target fields are mapped to the applicable Legacy field that will be its source, this is a 3-way activity involving the Business, Functional team and Data team. This identifies the transformation activity required to allow Syniti 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 Syniti ADMM
    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
    3. Use the Informal Words list to properly exclude records based on it's description (MAKT-MAKTX)
      1. List can be encountered here

    Transformation Run Sheet

    Item #Step DescriptionTeam Responsible

    1

    Verify that data is extracted and merged.

    S2P Data Team

    2

    Transformation jobs are ready for execution.

    Syniti


    Transformation Rules

    Rule #Source systemSource TableSource FieldSource DescriptionTarget SystemTarget TableTarget FieldTarget DescriptionTransformation Logic
    001PF2/WP2

    MARM

    		MATNRMaterial NumberS/4HANA

    MARM

    		MATNRMaterial Number

    Reference new Material number in Target System from mapping reference  (XREF) table

    002PF2/WP2MARMMEINHAlternative Unit of Measure (ISO Format)S/4HANAMARMMEINHAlternative Unit of Measure (ISO Format)

    Copy or map from source to target system in adherence to S4H ISO Data Standard using mapping table below

    Google Drive Live Link
    urlhttps://docs.google.com/spreadsheets/d/1EW0XaNVb_oDk6Pm1ikpHoPdC0qYgc17Y/edit?usp=sharing&ouid=114908176752927480470&rtpof=true&sd=true

    003PF2/WP2MARMUMRENDenominator for Conversion to Base UnitS/4HANAMARMUMRENDenominator for Conversion to Base UnitCopy from source to target system
    004PF2/WP2MARMUMREZNumerator for Conversion to Base UnitS/4HANAMARMUMREZNumerator for Conversion to Base UnitCopy from source to target system
    005PF2/WP2MARMEAN11EAN/GTINS/4HANAMARMEAN11EAN/GTIN

    Copy from source to target system

    Maintain EAN/UPC No available from the manufacturer and migrate if values exist in legacy.

    Not applicable for ZSER Materials.

    006PF2/WP2MARMNUMTPEAN/GTIN CategoryS/4HANAMARMNUMTPEAN/GTIN Category

    Copy from source to target system

    If both the EAN field and the EAN category field contain values, the system assumes that you want to enter the EAN externally.

    Any EAN currently in the system has to be either 8,12,13,14 digits long (as per GS1 standards)


    Not applicable for ZSER Materials.
    007PF2/WP2MEANHPEANMain Indicator (EAN)S/4HANAMEANHPEANMain Indicator (EAN)Only required if multiple vendors exist for material, with different EANS
    008PF2/WP2MEANEAN11EAN/GTINS/4HANAMEANEAN11EAN/GTIN

    Copy from source to target system

    If both the EAN field and the EAN category field contain values, the system assumes that you want to enter the EAN externally.

    Any EAN currently in the system has to be either 8,12,13,14 digits long (as per GS1 standards)

    Not applicable for ZSER Materials.

    009PF2/WP2MEANEANTPEAN/GTIN CategoryS/4HANAMEANEANTPEAN/GTIN Category

    Copy from source to target system

    If both the EAN field and the EAN category field contain values, the system assumes that you want to enter the EAN externally.

    For 8 digit EAN codes, category should be set as HK, otherwise default to HE.


    Not applicable for ZSER Materials.
    010PF2/WP2MARMLAENGLengthS/4HANAMARMLAENGLengthCopy from source to target system
    011PF2/WP2MARMBREITWidthS/4HANAMARMBREITWidthCopy from source to target system
    011PF2/WP2MARMHOEHEHeightS/4HANAMARMHOEHEHeightCopy from source to target system
    012PF2/WP2MARMMEABMUnit for Length/Width/Height(ISO Format)S/4HANAMARMMEABMUnit for Length/Width/Height(ISO Format)Copy or map from source to target system in adherence to S4H ISO Data Standard
    013PF2/WP2MARMBRGEWGross WeightS/4HANAMARMBRGEWGross WeightCopy from source to target system
    014PF2/WP2MARMGEWEIUnit of Weight (ISO Format)S/4HANAMARMGEWEIUnit of Weight (ISO Format)Copy or map from source to target system in adherence to S4H ISO Data Standard
    015PF2/WP2MARMVOLUMVolumeS/4HANAMARMVOLUMVolumeCopy from source to target system
    016PF2/WP2MARMVOLEHVolume Unit (ISO Format)S/4HANAMARMVOLEHVolume Unit (ISO Format)Copy or map from source to target system in adherence to S4H ISO Data Standard
    017PF2/WP2MARMMAKTXDescriptionS/4HANAMARMMAKTXDescriptionCopy additional descriptions in multiple languages from source to target system
    018PF2/WP2MARMSPRASLanguage KeyS/4HANAMARMSPRASLanguage Key

    Default language - English
    Based on employee language coverage - 
    The text should be maintained in 4 core languages – English (EN), French (FR), Italian (IT) & Mandarin (ZH). 
    Additional languages available in which text can be maintained are Portuguese (PT), German (DE), Spanish (ES).

    Alternative criteria for maintenance of text is to  support regulatory with Syway Suppliers about the Purchase order text, thereby Supplier languages should also be maintained basis languages maintained in Business partner - Suppliers master data.
    Based on current languages maintained for Suppliers - below languages are possible.
    FR - French
    EN - English
    ES - Spanish
    DE - German
    IT - Italian
    NL - Dutch
    PT - Portuguese
    ZH-Mandarin
    PL- Polish
    JA- Japanese
    KO- Korean
    FI- Finnish
    BG- Bulgarian
    RU-Russian
    TH- Thai
    ZF- Chinese traditional
    Z9 - Brazil Portuguese
    SK - Slovak

    019PF2/WP2STXLTDOBJECTText ObjectS/4HANASTXLTDOBJECTText Object

    Default To MATERIAL

    020PF2/WP2STXLTDNAMEText Name (technical key)S/4HANASTXLTDNAMEText Name (technical key)

    Map from ECC MARA-MATNR or ECC ASMD-ASNUM to S4 MARA-MATNR

    021PF2/WP2STXLTDIDText IDS/4HANASTXLTDIDText ID

    For Basic Data Long Text TDID = GRUN, for Internal Comment TDID = IVER 

    022PF2/WP2STXLTDSPRASLanguage KeyS/4HANASTXLTDSPRASLanguage Key

    Copy from source to target system

    023PF2/WP2STXLTDLINEText Line ContentS/4HANASTXLTDLINEText Line Content

    Copy from source to target system


    Transformation Mapping

    Mapping Table NameMapping Table Description
    MaterialXREFValue_Mapping_Link
    AUoMMapping of Alternate Unit Of Measure

    Google Drive Live Link
    urlhttps://docs.google.com/spreadsheets/d/1EW0XaNVb_oDk6Pm1ikpHoPdC0qYgc17Y/edit?usp=sharing&ouid=114908176752927480470&rtpof=true&sd=true

    Transformation Dependencies

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

    1

    Data has been extracted from source 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

    6

    All material description translations have been completed

    S2P Data Team

    Exclusion Table

    SAP StructureSAP FieldTypeLengthField DescriptionImportance
    MARM - Exclusions for Alt UoM
    MARMMATNRCHAR18Material Numbermandatory for sheet
    MARMUMRENNUMC5Denominator for Conversion to Base Unitmandatory for sheet
    MARMMEINHUNIT3Alternative Unit of Measuremandatory for sheet
    MARMUMREZNUMC5Numerator for Conversion to Base Unitmandatory for sheet
    MARAMEINSUNIT3Alternative Unit of Measuremandatory for sheet


    SAP StructureSAP FieldTypeLengthField DescriptionImportance
    MEAN - Exclusions for EAN/GTIN
    MEANMATNRCHAR18Material Numbermandatory for sheet
    MEANMEINHUNIT3Alternative Unit of Measuremandatory for sheet
    MEANLFNUMCHAR5Consecutive Numbermandatory for sheet
    MEANEAN11CHAR18GTIN (EAN/UPC)mandatory for sheet
    MEANEANTPCHAR2GTIN Categorymandatory for sheet


    SAP StructureSAP FieldTypeLengthField DescriptionImportanceRules
    STXH/STXL - Exclusions for Additional Descriptions
     STXH / STXLTDOBJECTCHAR10Text Objectmandatory for sheet
     STXH / STXLTDNAMECHAR70Text Name (technical key)mandatory for sheet
     STXH / STXLTDIDCHAR4Text IDmandatory for sheetFor Basic Data Long Text TDID = GRUN, for Internal Comment TDID = IVER 
     STXH / STXLTDSPRASLANG1Language Keymandatory for sheet


    Pre-Load Validation

    Project Team

    Completeness 

    TaskAction

    Verify Record Count

    The number of records presented after relevancy checks and validation needs to be correct compared to the staged data in Migrate.


    Accuracy

    TaskAction

    Conversion Accuracy

    Data 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 DSP reports.


    Business

    Completeness

    TaskAction

    Count and Completeness check

    All fields required as per mapping template rules must be completed.  Validity reports checking each field in ADMM must be built to help check.


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

    Verify data extracted

    Data Specialist

    2

    Verify data merged

    Data Specialist

    3

    Verify Material XREF is ready

    Data Specialist

    4

    Release - Load signoff and go-ahead by Functional/Data Owner

    Functional/Data Owner - S2P

    5

    Approval to stage/Pre-stage steps

    Functional/Data Owner - S2P

    6

    Extraction from source

    Syniti

    7

    Extraction from S4 where needed

    Syniti

    8

    Stage data for transformations

    Syniti

    9

    Run transforms

    Syniti

    10

    Execute pre-load report

    Syniti

    11

    Validate preload report - release

    Syniti

    12

    Prepare and simulate

    Data Specialist

    13

    Pre-load verification and approval to load

    Data Specialist/Data Owner - S2P

    14

    Load to S4

    Syniti

    15

    Complete Jira steps, Volumes and Timings

    All - where applicable

    16

    Execute post-load report

    Developer - Syniti or Data Specialist - S2P

    17

    Post-load report verification/validation

    Data Specialist/Functional/Data Owner - S2P

    18

    Object load completion approval

    Data Owner - S2P


    Load Phase and Dependencies

    Configuration

    Item #Configuration Item

    Google Drive Live Link
    urlhttps://docs.google.com/spreadsheets/d/1ycO3yrVqQufSK-M9IhUEGp9YQQ8wQP4A/edit?gid=87624989#gid=87624989

    Conversion Objects

    Object #Preceding Object Conversion Approach
    1Material Master - Basic View (2019)

    Error Handling

    Error TypeError DescriptionAction Taken
    DataLanguage errorsFix incorrect data
    DataDuplicatesFix incorrect data


    Post-Load Validation

    Project Team

    Post-Load Step

    Step Description

    Team Responsible

    Execute post-load report

    Developer - Syniti or Data Specialist - S2P

    Post-load report verification/validation

    Data Specialist/Functional/Data Owner - S2P

    Object load completion approval

    Data Owner - S2P

    Completeness

    Completeness

    TaskAction

    Execute post-load report

    Developer - Syniti or Data Specialist - S2P

    Post-load report verification/validation

    Data Specialist/Functional/Data Owner - S2P

    Object load completion approval

    Data Owner - S2P


    Accuracy

    TaskAction

    Verify count

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

    Field by field check

    Compare source data to target data

    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

    Transformation Mapping

    Mapping Table NameMapping Table Description

    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

    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 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 walkthroughsDownload 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 Business team to verify that the Material data in target S/4 HANA were loaded correctly via dspMigrate post load reports or standard reports from S/4 HANAstaged in the preload tables are correct in terms of the mapping rules. This will be done via Syniti/SAP reports.


    Key Assumptions

    • Master Data Standard is up to date as on the date of documenting this conversion approach and data load.
    • Materials - Additional Data is 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