Catalog Profile will be collected via DCT. An initial extract of the relevant Catalog Profiles will be provided in google sheet format to assist business in decision making on including any relevant Catalog Profiles from PF2 and WP2 as Catalog Profile in S/4 HANA.

Any additional Catalog Profiles that need to be created to support the new design may be added in the DCT.

A review and standardization will be done across all Catalog Profiles in the DCT. 

Please see an indication of what will be baselined from source systems below and what will be constructed in the DCT. 

Note: A full Data Construct will be created for Catalog Profile, as the SyWay design is changing and a complete standardization will be performed. While data may already exist, it cannot be easily transformed to align with the new SyWay data setup.

Extract data from source system based on relevancy rule

Google Sheet report pre-populated with PF2 and WP2 information to be generated based on relevancy criteria. 

Mandatory

Follow Naming Convention: NN(Technical Object Type)_NNN(Subdivide of Technical Object Type)_NN(Sequential Number)

The Technical Object Type and Subdivide of Technical Object Type must exist in the following mapping table:

OTH-Catalog Profile_Technical Object Type_Naming Convention

Mandatory

Allowed values from: TQ15-KATALOGART

Mandatory

Must not contain characters from mapping table: OTH_Informal Characters, except for asterisk *

If user select exist code group, need to check the value existence in QPCD-CODEGRUPPE based on the Catalog provided;

If user input value contains asterisk (*) in the code group field, the system should skip data validation for this field.  

Mandatory

Follow Naming Convention: NN(Technical Object Type)_NNN(Subdivide of Technical Object Type)_NN(Sequential Number)

The Technical Object Type and Subdivide of Technical Object Type must exist in the following mapping table:

OTH-Catalog Profile_Technical Object Type_Naming Convention

Mandatory

Text must be translated according to the language key

Cannot have duplicate records based on corresponding language text (2 Catalog Profiles cannot have the same English language key texts)

Mandatory

Text must be translated according to the language key

Cannot have duplicate records based on corresponding language text (2 Catalog Profiles cannot have the same French language key texts)

Mandatory

Text must be translated according to the language key

Cannot have duplicate records based on corresponding language text (2 Catalog Profiles cannot have the same Italian language key texts)

Mandatory

Text must be translated according to the language key

Cannot have duplicate records based on corresponding language text (2 Catalog Profiles cannot have the same Mandarin language key texts)

Mandatory

Text must be translated according to the language key

Cannot have duplicate records based on corresponding language text (2 Catalog Profiles cannot have the same Brazilian Portugese language key texts)

Mandatory

Text must be translated according to the language key

Cannot have duplicate records based on corresponding language text (2 Catalog Profiles cannot have the same German language key texts)

Mandatory

Text must be translated according to the language key

Cannot have duplicate records based on corresponding language text (2 Catalog Profiles cannot have the same Spanish language key texts)

1

Obtain DCT Sign-off from Business.

SyWay Data Team

2

In dspMigrate, select the wave – S4/HANA – Plant Maintenance

Syniti

3

Go to Process Area Launch and Process the Object – Catalog Profile

Syniti

4

Review and Validate Error and Preload Reports

Syniti

5

Execute the transformation to prepare the target tables

Syniti

6

Validate data from pre-load and error reports

Business/Data owner

7

Generate load files

Syniti

Direct Mapping 

Direct Mapping

Direct Mapping

Direct Mapping 

Default to "E"

Value Mapping: OTH_Informal Words and OTH_Informal Characters

Review the value mappings for the presence of informal words or invalid characters.If any are identified, replace them with the appropriate standardized values as specified in the mappings.

Direct Mapping 

Default to "F"

Value Mapping: OTH_Informal Words and OTH_Informal Characters

Review the value mappings for the presence of informal words or invalid characters.If any are identified, replace them with the appropriate standardized values as specified in the mappings.

Direct Mapping 

Default to "I"

Value Mapping: OTH_Informal Words and OTH_Informal Characters

Review the value mappings for the presence of informal words or invalid characters.If any are identified, replace them with the appropriate standardized values as specified in the mappings.

Direct Mapping 

Default to "1"

Value Mapping: OTH_Informal Words and OTH_Informal Characters

Review the value mappings for the presence of informal words or invalid characters.If any are identified, replace them with the appropriate standardized values as specified in the mappings.

Direct Mapping 

Default to "P"

Value Mapping: OTH_Informal Words and OTH_Informal Characters

Review the value mappings for the presence of informal words or invalid characters.If any are identified, replace them with the appropriate standardized values as specified in the mappings.

Direct Mapping 

Default to "D"

Value Mapping: OTH_Informal Words and OTH_Informal Characters

Review the value mappings for the presence of informal words or invalid characters.If any are identified, replace them with the appropriate standardized values as specified in the mappings.

Direct Mapping 

Default to "S"

Value Mapping: OTH_Informal Words and OTH_Informal Characters

Review the value mappings for the presence of informal words or invalid characters.If any are identified, replace them with the appropriate standardized values as specified in the mappings.

Mapping of legacy Catalog Profile to S/4 HANA Catalog Profile.

Ensure DCT tables completeness

SyWay Data Team

Ensure all Transformation mappings are up to date.

SyWay Data Team

Verify Record Count 

Data team to verify that the total number of relevant records from the source systems is equal to the total number of records in the Preload and Load Sheets.

Conversion Accuracy

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.

Verify Record Count 

Business team to verify that the total number of relevant records from the source systems is equal to the total number of records in the Preload and Load Sheets.

Conversion Accuracy

Business  to verify that all the data in the load table/file is accurate as per endorsed transformation/mapping rules (and signed-off data) 

1

Ensure Pre-load sign-offs are obtained.

SyWay Data team

2

Go to the load tool and select the correct load Program.

SyWay Data team

3

Proceed with Data load.

SyWay Data team

4

Validate few records loaded by accessing standard transactions.

SyWay Data team

5

Generate the post load reports in the tool.

SyWay Data team

6

Log errors as defects, if any and address resolutions. Close defects.

SyWay Data team

7

Resolve defects by re-upload and re-generate post load reports if necessary.

SyWay Data team

8

Business to validate the post load files as part of post-load validation, raise data defects or provide the post-load sign-off.

Business

9

Repeat steps 5 to 7 if necessary.

SyWay Data team

Verify Count

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.

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

Conversion Accuracy

Data team to verify that the Catalog Profile data in target S/4 HANA were loaded correctly via dspMigrate post load reports or standard reports from S/4 HANA. 

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.

Conversion Accuracy

Verify that the Catalog Profile data in target S/4 HANA were loaded correctly via dspMigrate post load reports or standard reports from S/4 HANA.