3 new To-Be Classes linked to Class Type 001 has been defined by the Business and the S2P Functional Team.  The new Classes will be captured in a DCT.

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

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

PF2: 5,167 (6 **)

** Linked to relevant materials for info purposes
** No Classes are linked to Service Materials 

28,005 (3,007 **)

** Linked to relevant materials for info purposes
** No Classes are linked to Service Materials 

Class Type

ANZUO

1

Extract data from source system based on records in the DCT that are marked for migration.

Syniti

Class Type

Default to 'EN'.

All Classes must have a description in at least 'EN'.  Allow the Description to be captured in multiple languages, with the following languages allowed: DE, EN, ES, FR, IT, PT, ZH.

Convert to internal code.

• Ensure no duplicate (With other Classes within Class Type 001) and language key.
• Ensure populated with Description as per specified Language.
• Approach if the description is more than 40 characters: Abbreviate to required length (40 Chars).
• Ensure that it does not include any of the below characters: 
  ;        Semi-colon
  :        Colon
  ::        Double Colon
  ?        Question Mark
  /        Forward Slash
  @        At sign
  &        Ampersand
  =        Equal Sign
  +        Plus Sign
  $        Dollar Sign
  %        Percent
  |        Vertical Bar
  []        Left or Right Square Bracket
  "        Double Quotes

The list of Classes will be provided by the Functional Team in the Configuration Document based on the To-Be design.

1

Verify that data is extracted from the DCT.

Syniti / S2P Data Team

2

Verify that data is extracted from both source systems.

Syniti / S2P Data Team

3

Transformation jobs are ready for execution.

Syniti

4

Review and Validate Error and Preload Reports

Syniti

5

Generate Load Files

Syniti

1

Data has been extracted from sources systems

Syniti

2

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

3

Value mapping and XREF tables are ready

Verify Record Count

The number of records presented after relevancy checks and validation needs to be correct between the DCT and the preload tables in Syniti Migrate.

Completeness check

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

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 Migrate standard reports.

Count and Completeness check

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

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 Migrate reports/SAP reports.

1

Verify data extracted

Data Specialist/Functional - S2P

2

Verify data combined from both source systems

Data Specialist/Functional - S2P

3

Stage data for transformations

Syniti

4

Run transforms

Syniti

5

Execute pre-load report

Syniti

6

Validate preload report - release

Data Specialist/Functional - S2P

7

Prepare and simulate

Syniti

8

Pre-load verification and approval to load

Functional/Data Owner - S2P

9

Load to S4

Syniti

10

Complete Jira steps, Volumes and Timings

All - where applicable

11

Execute post-load report

Syniti

12

Post-load report verification/validation

Data Specialist/Functional/Data Owner - S2P

13

Object load completion approval

Data Owner - S2P

1

TCLA-Class Types

2

TCLG-Class Groups

3

TCLU-Class Status

Data

Incorrect Language

Fix 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

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.

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

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.

Conversion Accuracy

Verify that the data in S/4 HANA was loaded correctly via Syniti Migrate post-load reports.