Status
Owner	CLARKE-ext, Steve
Stakeholders	The 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 - PO Text View into S/4 HANA as part of the Material Data Migration.

Link to MDS:

DD-FUN-050 Master Data Standard_2022-Material master-PO Text

Conversion Scope

The scope of this document covers the approach for converting active PO Text data on Materials and Services from Legacy Source Systems into S/4HANA following the 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

Source	Scope	Source Approx No. of Records	Target System	Target Approx No. of Records
PF2,WP2	Scope is Material and Service Master records that have been identified as part of Basic Data.	300,000	S4H	300,000

Predecessor Objects

Material Master - Basic View (2019) → Materials - Additional data (2021) → Materials Purchasing View (2020) → Materials – PO Text View.

Additional Information

Multi-language Requirement

Multi language is supported for Materials - PO Text. Login via a different language will show the description displayed in the logon language if the language key is maintained.

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, TH - Thai (descoped by CR0086).
• Supplier languages that are possible: FR - French, EN - English, ES - Spanish, DE - German, IT - Italian, NL - Dutch, PT - Brazil Portuguese, ZH - Mandarin, PL - Polish, JA - Japanese, KO - Korean, FI - Finnish, BG - Bulgarian, RU - Russian, TH- Thai, ZF - Chinese traditional.

Document Management

Not Applicable

Legal Requirement

Not Applicable

Special Requirements

Not Applicable

Target Design

The technical design of the target for this conversion approach.

Table	Field	Data Element	Field Description	Data Type	Length	Requirement
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

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.

ID	Criticality	Error Message/Report Description	Rule	Output	Source System
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	No special characters. Use line breaks. 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	List of Materials that do not have Long Text	MATNR and MAKT-MAKTX (Material Short Description) for MAKT-SPRAS either EN, FR, IT or CH	PF2 & WP2

Conversion Process

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

Field Governance Rules
These governance rules apply to the individual fields within the data record.
Rule #	Field Label	Rule Description	Validation Method	Conditional Logic	Cleansing Rule (Also see Data Cleansing section above)
1	MARA-MATNR	Material number governance rules will be defined in Basic data as these are copied over from Basic data to PO text view automatically & are not specific to this view.	Upfront Automated
2	Language	The following language are acceptable 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.	Upfront Automated		TDSPARS Not In Allowed List TDSPRAS = Z9
3	Long Text	1. No special characters. 2. Use line breaks. 3. Capitalise first letter of sentence & major words capitalised.			Text Message Rules No Long Text for the Material

Data Privacy and Sensitivity

Not Applicable

Extraction

Target Materials will come from both the Material Master and Service Master.

Text data in the table STXL is not readable and the Function Module “READ_TEXT” is used for this, using the following STXL fields: TDOBJECT, TDNAME, TDID and TDSPRAS.

TDOBJECT & TDID are used in the following combinations to get the data:

• Material Master: 'MATERIAL' and 'BEST'
• Service Master: 'ASMD' and 'LTXT'

TDNAME: this will contain MARA-MATNR or ASMD-ASNUM.

Extraction Run Sheet

Req #	Requirement Description	Team Responsible
1	Extract data from PF2 and WP2 using Function Module “READ_TEXT”	Syniti 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 Screen	Parameter Name	Selection Type	Requirement	Value to be entered/set
Not Applicable

Data Collection Template (DCT)

Not Applicable.

Extraction Dependencies

Item #	Step Description	Team Responsible
1	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.	Cutover

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 Description	Team Responsible
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

Transformation Rules

Rule #	Source system	Source Table	Source Field	Source Description	Target System	Target Table	Target Field	Target Description	Transformation Logic
1	PF2 & WP2	STXL	TDOBJECT		S4H	STXL	TDOBJECT		Default to MATERIAL
2	PF2 & WP2	STXL	TDNAME		S4H	STXL	TDNAME		Map from Old MARA-MATNR or Old ASMD-ASNUM to New MARA-MATRN
3	PF2 & WP2	STXL	TDID		S4H	STXL	TDID		Default to BEST
4	PF2 & WP2	STXL	TDSPRAS		S4H	STXL	TDSPRAS		Copy As-Is
5	PF2 & WP2		Long Text		S4H		Long Text		Copy As-Is

Transformation Mapping

Use the exact name and reference this section in the “Transformation rules” above

Mapping Table Name	Mapping Table Description	Link
Material	XREF

Transformation Dependencies

List the steps that need to occur before transformation can commence

Item #	Step Description	Team Responsible
1	Data has been extracted from sources systems	Syniti
2	Deduplication is completed	Syniti & Data Team (S2P)
3	Configuration should be completed - (Config documents should be complete)	Syniti & Data Team (S2P)
4	Value mapping and XREF tables are ready	Syniti & Data Team (S2P)

Pre-Load Validation

Project Team

The following pre-load validations will be performed by the Project Team.

Completeness

Task	Action
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.

Accuracy

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

The following pre-load validations will be performed by the business.

Completeness

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

Task	Action
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. The Long Text data field in STXL is not a normal field, therefore Syniti needs to determine if Migration Cockpit is the best option, or if another standard load method is available, otherwise a custom method must be developed.
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 Description	Team Responsible
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

Load Phase and Dependencies

Configuration

Item #	Configuration Item
1	Not Applicable.  This object is only dependent on Languages found in the table T002 and these are all SAP standard so nothing is required.

Conversion Objects

Object #	Preceding Object Conversion Approach
1	Material Master - Basic View (2019)
2	Materials - Additional data (2021)
3	Materials Purchasing View (2020)

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 Type	Error Description	Action Taken
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

Post-Load Validation

Project Team

Post-Load Step

Step Description	Team Responsible
Execute post-load report	Syniti
Post-load report verification/validation	Data Specialist/Functional/Data Owner - S2P
Object load completion approval	Data Owner - S2P

Completeness

Task	Action
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.

Accuracy

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

Task	Action
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.

Accuracy

Task	Action
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.

Key Assumptions

• Master Data Standard is up to date as on the date of documenting this conversion approach and data load.
• Materials - PO Text is in scope based on data design and any exception requested by business.

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