Scope is Material and Service Master records that have been identified as part of Basic Data. 

STXL

TDOBJECT

Texts: application object

CHAR

10

Required

STXL

TDNAME

Name

CHAR

70

Required

STXL

TDID

Text ID

CHAR

4

Required

STXL

TDSPRAS

SPRAS

Language Key

LANG

1

Required

STXL

CLUSTD

SAPscript: LONG RAW field for table STXL

LRAW

7902

Required

1

High

TDSPARS Not In Allowed List

The following language are allowed as being either core, or additional or the language of the supplier: BG, DE, EN, ES, FI, FR, IT, JA, KO, NL, PL, PT, RU, TH, ZF, ZH.

MATNR and Text messages that are not in the allowed list

PF2 & WP2

2

High

TDSPRAS = Z9

(There is 1 record with this.  Country is TW-Taiwan.)

Change Z9 to ZH.

TDSPRAS = ZH

PF2 & WP2

3

Medium

Text Message Rules

1. No special characters.
2. Use line breaks.
3. Capitalise first letter of sentence & major words capitalised.

MATNR and Text messages that don’t follow this

PF2 & WP2

4

Medium

No Long Text for the Material

MATNR and MAKT-MAKTX (Material Short Description) for MAKT-SPRAS either EN, FR, IT or CH

PF2 & WP2

1

Extract data from PF2 and WP2 using Function Module “READ_TEXT”

Syniti Team

Materials and Services in scope to be loaded as Material Master Basic Data must be identified before the extraction of Text data, so that we can limit the extraction to this sub-set of data.

1

Verify that data is extracted from both source systems and includes both Materials and Services Long Text.

Syniti/Data Team(S2P)

2

Transformation jobs are ready for execution.

Syniti

1

PF2 & WP2

STXL

TDOBJECT

S4H

STXL

TDOBJECT

Default to MATERIAL

PF2 & WP2

STXL

TDNAME

S4H

STXL

TDNAME

Map from Old MARA-MATNR or Old ASMD-ASNUM to New MARA-MATRN

PF2 & WP2

STXL

TDID

S4H

STXL

TDID

Default to BEST

PF2 & WP2

STXL

TDSPRAS

S4H

STXL

TDSPRAS

Copy As-Is

PF2 & WP2

Long Text

S4H

Long Text

Copy As-Is

Syniti

Syniti & Data Team (S2P)

Syniti & Data Team (S2P)

Syniti & Data Team (S2P)

Verify Record Count

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

Completeness check

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

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.

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.

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

1

Verify data extracted

Data Specialist/Functional - S2P

2

Verify data combined from both source systems and from Materials and Services

Data Specialist/Functional - S2P

3

Verify Material XREF is ready

Data Specialist/Functional - S2P

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

8

Stage data for transformations

Syniti

9

Run transforms

Syniti

10

Execute pre-load report

Syniti

11

Validate preload report - release

Data Specialist/Functional - S2P

12

Prepare and simulate

Syniti

13

Pre-load verification and approval to load

Functional/Data Owner - S2P

14

Load to S4

Syniti

15

Complete Jira steps, Volumes and Timings

All - where applicable

16

Execute post-load report

Syniti

17

Post-load report verification/validation

Data Specialist/Functional/Data Owner - S2P

18

Object load completion approval

Data Owner - S2P

1

Material Master - Basic View (2019)

2

Materials - Additional data (2021)

3

Materials Purchasing View (2020)

Data

Incorrect Language

Fix incorrect data

Data

Duplicate

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 preload needs to be compared to the post-load. – Syniti report

Field by field check

Compare source data to target data.

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

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