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.

Summarise how the data is currently utilized and set up in the legacy system/s and how object is intended to be represented in S/4, and any other relevant information

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 the Target MARA table can be included in the scope.  For completeness, the scope for Material Basic Data is given below.

The data from legacy system includes:

1. All materials with activity for last 2 years (direct materials). 3 years for spares.
2. All materials with stock

The data from legacy system excludes:

1. All materials flagged for deletion
2. Any blocked or obsolete materials
3. Inactive materials

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.	500,000	S4H	500,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.

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

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	LongText	1. No special characters. 2. Use line breaks. 3. Capitalise first letter of sentence & major words capitalised.			Text Message Rules

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-BEST
• Service Master: ASMD-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	Loading Material Master Basic Data is required before Text data is loaded	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 and merged.	Syniti/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
Material	XREF

Transformation Dependencies

List the steps that need to occur before transformation can commence

Item #	Step Description	Team Responsible
Not Applicable

Pre-Load Validation

Project Team

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

Completeness

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

Task	Action
Conversion Accuracy	SyWay S2P Data Team to verify that all fields below meet pass the checks: Mandatory Fields Field and Value Mapping Correctness Null Checks 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

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

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

Post-Load Validation

Project Team

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

Completeness

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

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

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

Completeness

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

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