Status

Owner

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

StakeholdersThe business stakeholders involved in making, reviewing, and endorsing this decision. Type @ to mention people by name

Purpose

The purpose of this document is to define the conversion approach to upload Materials - Class Type 001 into S/4 HANA as part of the Material Data Migration.

Link to MDS: DD-FUN-050 Master Data Standard_2017-Material master - Class Type 001


Conversion Scope

The scope of this document covers the approach for converting active Class data linked to Class Type 001 from Legacy Source Systems into S/4HANA following the Material Master Data Design Standard.


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 here to go to the Conversion Spec for 2019 to see the full set of relevancy rules.


List of source systems and approximate number of records

SourceScope

Source Approx No. of Records

Target SystemTarget Approx

No. of Records

PF2,WP2

Scope is Classes that fall under CLASS TYPE 001 and are linked to Material records that have been identified as part of Basic Data.

Service Master records that will become Materials in the target are out of scope.  See the mail from Simran. Service Master Data Used in 2017 CLASS TYPE 001 in S4H.eml

WP2: 22,838 (3,000**)

PF2: 5,167 (6**)

** linked to relevant materials

S4H

28,005 (3,006**)

** linked to relevant materials


Jira Task to track the Classes that will be added to CLASS TYPE 001:

Configuration Document containing the above classes: <To Be Add>

Profiling

ZZZ

Legacy SystemTotal Relevant MaterialsRelevant Materials assigned to Classes
PF2104,4844,224
WP272,37825,866

Top 30 Classes by Legacy system

Legacy SystemCLASSMaterial Count
PF2Z_MAT_PL_ARCH3,202
SPARE_PARTS_TC989
Z_ORTEMS6
DANGEROUS_GOOD7
Z_SAD_MM7
Z68-421691
WP2Z_CM_MAT6,043
LIP00201483,447
M0012,898
Z_MAT_PL_ARCH2,088
MATERIAL_SEGMENTS935
LIP0034040842
Z_MAT_ADDITIONAL456
Z_MAT_CRIT418
LIP0008485343
CRIT_IND333
LIP0007716226
LIP0031355210
LIP0032812120
LIP003403094
LIP003248482
LIP000848481
LIP003248878
LIP003134569
LIP003457169
LIP000841168
LIP003456861
LIP000836760
LIP003405060
M002_H_05_AH57
LIP000825854
LIP003400054
M002_A_08_AT52
LIP003132451
LIP002016850
LIP000839446

Predecessor Objects

Material (Characteristics of CLASS TYPE -001) → Material - Class Type 001.

Additional Information

Multi-language Requirement

Multi language is supported for Materials - Class Type 001. 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

Not Applicable


Target Design

With Functional input, document the technical design of the target fields that are in the scope of this document.

The technical design of the target for this conversion approach.

TableFieldField DescriptionData TypeLengthRequirement
KLAHCLINTInternal Class NumberNUMC10Required
KLAHKLART

Class Type

CHAR3Required
KLAHCLASSClassCHAR18Required
KLAHSTATUStatusCHAR1System
KLAHLOCLALocal classCHAR1Conditional
KLAHVONDTValid fromDATS8System
KLAHBISDTValid toDATS8System
KLAHPRAUSSame classificationCHAR1System
KLAHANAMECreated ByCHAR12System
KLAHADATUCreated OnDATS8System
KLAH

ANZUO

No of AssignmentsCHAR1System
SWORCLINTInternal Class NumberNUMC10Required
SWORSPRASLanguage KeyLANG1Required
SWORKLPOSItem NumberNUMC2Required
SWORKSCHLClass DescriptionCHAR40Required
SWORKSCHGKeyword (Upper Case for Matchcode)CHAR40Required


Data Cleansing

All data cleansing should take place in the data source system as defined in this document, unless system limitations prevent it.

If data cleansing is managed outside of the source system (e.g. Syniti Migrate, 3rd Party Vendor, DCT), the necessary documentation must be produced and appended to this deliverable for sign-off.

IDCriticalityError Message/Report DescriptionRuleOutputSource System


























Conversion Process

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


Data Privacy and Sensitivity

Summarize Data Privacy and Sensitivity Requirements, if any


Extraction

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

  1. The data exists. Syniti Migrate connects to the source and loads the data into Syniti Migrate. 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 Syniti Migrate; 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 Syniti Migrate. This is to be conducted using DCT (Data Collection Template) in Syniti Migrate

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

If applicable, this section will give the details on any selection screen parameters, including the parameter type, that are required to be entered to ensure consistent data extracts.
Selection Ref ScreenParameter NameSelection TypeRequirementValue to be entered/set





















Data Collection Template (DCT)

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

<Object> DCT Rules

Field NameField DescriptionRule












Extraction Dependencies

List the steps that need to occur before extraction can commence

Item #Step DescriptionTeam Responsible













Transformation

The Target fields are mapped to the applicable Legacy field that will be its source, this is a 3-way activity involving the Business, Functional team and Data team. This identifies the transformation activity required to allow Syniti Migrate 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 Migrate
  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

Use the exact name and reference this section in the “Transformation rules” above
Mapping Table NameMapping Table Description








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

The following pre-load validations will be performed by the 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

The following pre-load validations will be performed by the 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

Identify the phase as to “when” the load for this object will occur. <Pre-Cutover, Cutover, Post Cutover> and list the steps that need to occur before the load can commence

Configuration

List the Configurations required before loading can commence

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

The table below depicts some possible system errors for this data object during data load. All data load error is to be logged as defect and managed within the Defect Management

Error TypeError DescriptionAction Taken










Post-Load Validation

Project Team

The following post-load validations will be performed by the 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

The following post-load validations will be performed by the 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 - Class Type 001 is in scope based on data design and any exception requested by business.

Any additional key assumptions.


See also

Insert links and references to other documents which are relevant when trying to understand this decision and its implications. Other decisions are often impacted, so it's good to list them here with links. Attachments are also possible but dangerous as they are static documents and not updated by their authors.

Change log

Workflow history