Status
Owner	PUN-ext, Eddy
Stakeholders	WELENSKY-ext, DaveERGUIZA-ext, Pinky Love TEE-ext, Paul  JOSHI-ext, Aditya VILARES, ines LEIGHTON-ext, Dean Betty Yue; STEFANESCU-ext, Aurelia MOUSSA-ext, Eva [Syniti Consultant]

Purpose

The purpose of this document is to define the conversion approach to create Catalog Profile in S/4 HANA.

A Catalog Profile is used to determine which catalogs and code groups from the individual catalogs are to be accessed by the system for maintenance notifications.

Syensqo utilizes Catalog Profile within the SAP S/4 HANA system to define and manage its technical object catalogs (Object Type, Cause, Action, Failure mode and Task).

Conversion Scope

The scope of this document covers the approach for migrating active Catalog Profile into S/4 HANA following the Catalog Profile Master Data Design Standard.

The conversion of Catalog Profile follows the endorsed EAM Core Data Design describing the Asset Identification Methodology.

Catalog Profile Data from legacy will be consolidated based on the S/4 HANA design and will be constructed via a common DCT which is target ready. This also means multiple GBU could be using the same Catalog Profile based on the Asset Identification Methodology.

There will not be a direct conversion from legacy to S/4 HANA, however there will be a mapping to ensure the valid and active legacy Catalog Profiles are considered for data migration. 

The data from legacy system includes:

1. All Catalog Profiles defined in the source systems

The data from legacy system excludes:

1. Not applicable since all Catalog Profiles defined in the source systems are considered valid

For reference, the Catalog Profiles in S/4 HANA are not transformed based on the legacy mapping, but they are derived based on the logic of the Asset Identification Methodology.

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	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.	500	S/4 HANA	500

Additional Information

Multi-language Requirement

Catalog Profile description will be made available in English.

Multi language is supported for Catalog Profile. Login via a different language will have its description displayed in the logon language if the language key is maintained in the Catalog Profile.

Document Management

Not Applicable

Legal Requirement

Not Applicable

Special Requirements

Not Applicable

Target Design

With Functional input, document the technical design of the target fields that are in the scope of this document.

The technical design of the target for this conversion approach.

1. Catalog Profile:

Table	Field	Data Element	Field Description	Data Type	Length	Requirement
T352C	RBNR	RBNR	Catalog Profile	CHAR	9	Mandatory
T352C	QKATART	QKATART	Catalog	CHAR	1	Mandatory
T352C	QCODEGRP	QCODEGRPSEARCHPATTERN	Search Pattern for Code Group/Selected Set	CHAR	8	Mandatory

Note: One Catalog Profile can have multiple Catalog and Search Pattern for Code Group / Selected Set.

2. Catalog Profile Text:

Table	Field	Data Element	Field Description	Data Type	Length	Requirement
T352C	RBNR	RBNR	Catalog Profile	CHAR	9	Mandatory
T352B_T	SPRAS	SPRAS	Language Key	LANG	1	Mandatory
T352B_T	RBNRX	RBNRX	Catalog Profile Text	CHAR	30	Mandatory

Note: Each Catalog Profile must have 1 entry for each language in scope: English,French, Italian, Mandarin, Brazilian, Portuguese, German and Spanish

Catalog Profile Data strictly adheres to the Master Data Standard. The complete information of the key fields that hold the Catalog Profile information follows the Master Data Standard document that is located here.

Data Cleansing

No data cleansing is required for Catalog Profile in the legacy system. If any cleansing is deemed necessary, it will be performed outside of the system.

As a result, the cleansed Catalog Profile data will be populated directly in the Data Collection Template (DCT).

ID	Criticality	Error Message/Report Description	Rule	Output	Source System
		Not Applicable

Conversion Process

Summarize High-Level Process. Include diagrams, where applicable. Include information supporting details of Extract, Transform and Load specific to the Data Object

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

 Collection will be done manually in the Data Collection Template for the following scenarios:

• For sites not on SAP-PF2 or WP2 systems
• For new Catalog Profiles that need to be created to support the to-be design

Data Privacy and Sensitivity

Not Applicable

Extraction

Extract data from a source into Syniti Migrate. There are 2 possibilities:

1. The data exists. Syniti Migrate connects to the source and loads the data into Syniti Migrate. There are 3 methods:
   1. Perform full data extraction from relevant tables in the source system(s).
   2. Perform extraction through the application layer.
   3. Only if Syniti Migrate; cannot connect to the source, data is loaded to the repository from the provided source system extract/report.
2. The data does not exist (or cannot be converted from its current state). The data is manually collected by the business directly in Syniti Migrate. This is to be conducted using DCT (Data Collection Template) in Syniti Migrate

The agreed Relevancy criteria is applied to the extracted records as reference point to identify the records that are applicable for the data construction in the DCT

Extraction Run Sheet

Req #	Requirement Description	Team Responsible
1	Extract data from source system based on relevancy rule	SyWay Data Team
2	Google Sheet report pre-populated with PF2 and WP2 information to be generated based on relevancy criteria.	SyWay Data 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)

Target Ready Data Collection Template will be created for Catalog Profile data with exception of some fields which require transformation as mentioned in the transformation rule.

1. The extracted report will be loaded into the required structure using the DCT.
2. Standardization activities (including deduplication, standardization and additions)  will be carried out within the DCT.

Delta Data Management: Initial collection will be done via the report and one-time load to the DCT will be performed. Any delta after the initial collection within the DCT will require business to take due diligence to ensure any subsequent delta cleansing is verified and aligned within the DCT.

1. Catalog Profile DCT Rules

Field Name	Field Description	Rule
RBNR	Catalog Profile	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
QKATART	Catalog	Mandatory Allowed values from: TQ15-KATALOGART
QCODEGRP	Search Pattern for Code Group/Selected Set	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.

2. Catalog Profile Text DCT Rules

Field Name	Field Description	Rule
RBNR	Catalog Profile	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
SPRAS	Language Key	Mandatory For each Catalog Profile record, there must be a single record each for the following languages: English, French, Italian, Mandarin, Brazilian, Portuguese, German and Spanish
RBNRX	Catalog Profile Text	Mandatory Text must be translated according to the language key Cannot have duplicate records based on corresponding language text (eg 2 Catalog Profiles cannot have the same English language key Text, or 2 Catalog Profiles cannot have the same Spanish language key texts)

Extraction Dependencies

List the steps that need to occur before extraction can commence

Item #	Step Description	Team Responsible
	Not Applicable

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

Transformation Rules

1. Catalog Profile

Rule #	Source system	Source Table	Source Field	Source Description	Target System	Target Table	Target Field	Target Description	Transformation Logic
1	DCT	T352C	RBNR	Catalog Profile	S/4 Hana	T352C	RBNR	Catalog Profile	Direct Mapping A Global Value Mapping (Catalog Profile) is created to reference old Catalog Profiles.
2	DCT	T352C	QKATART	Catalog	S/4 Hana	T352C	QKATART	Catalog	Direct Mapping
3	DCT	T352C	QCODEGRP	Search Pattern for Code Group/Selected Set	S/4 Hana	T352C	QCODEGRP	Search Pattern for Code Group/Selected Set	Direct Mapping

2. Catalog Profile Text

Rule #	Source system	Source Table	Source Field	Source Description	Target System	Target Table	Target Field	Target Description	Transformation Logic
1	DCT	T352C	RBNR	Catalog Profile	S/4 Hana	T352C	RBNR	Catalog Profile	Direct Mapping A Global Value Mapping (Catalog Profile) is created to reference old Catalog Profiles.
2	DCT	T352B_T	SPRAS	Language Key	S/4 Hana	T352B_T	SPRAS	Language Key	Direct Mapping
3	DCT	T352B_T	RBNRX	Catalog Profile Text	S/4 Hana	T352B_T	RBNRX	Catalog Profile Text	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.

List of Custom Target Reports for this object is maintained here: Conversion Specification - Custom Reports Register.

Transformation Mapping

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

Mapping Table Name	Mapping Table Description
Catalog Profile	Mapping of legacy Catalog Profile to S/4 HANA Catalog Profile.
OTH_Informal Words	List of Informal Words and the words used to replace
OTH_Informal Characters	List of Informal Characters

Transformation Dependencies

List the steps that need to occur before transformation can commence

Item #	Step Description	Team Responsible
1	Ensure DCT tables completeness	SyWay Data Team
2	Ensure all Transformation mappings are up to date.	SyWay Data Team

Pre-Load

 Validation

Project Team

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

Completeness

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

Accuracy

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

Business

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

Completeness

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

Accuracy

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

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

Load Phase and Dependencies

Pre-Cutover

Configuration

List the Configurations required before loading can commence

Item #	Configuration Item
1	T002-Language Key
2	TQ15-Catalog

Conversion Objects

Object #	Preceding Object Conversion Approach
1007	Catalog Code Groups & Codes

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
Configuration	Invalid Language Key	Engage Functional team to expedite and fix the error in the system
Configuration	Invalid Catalog	Engage Functional team to expedite and fix the error in the system

Post-Load Validation

Project Team

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

Completeness

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

Accuracy

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

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 Catalog Profile 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.
• Data cleansing has met the required percentage threshold for the specified mock cycle and all preparation activities have been completed.
• Data entries in DCT are target-ready data unless a specific transformation rule is stated for that field in the transformation rules.
• All Catalog Profiles in the source systems are "active" as they are defined in configuration
• Not all legacy Catalog Profiles need to be mapped to S/4 HANA Catalog Profiles. If any of the successor objects is dependent on a Catalog Profile field with no mapped values, this will be an enrichment activity or manual transformation for the successor object to derive the Catalog Profile.

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