You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 12 Next »

Status

  Approved

Owner

PUN-ext, Eddy 

Stakeholders

Purpose

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


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 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 all the valid and active legacy Catalog Profiles are considered for data migration. 

The data from legacy system includes:

  1. All Catalog Profiles that are mapped to S/4 HANA Catalog Profiles

The data from legacy system excludes:

  1. All Catalog Profiles that are not mapped to S/4 HANA Catalog Profiles


List of source systems and approximate number of records
SourceScope

Source Approx No. of Records

Target SystemTarget Approx

No. of Records

PF2, WP2Valid Catalog Profile500S/4 HANA500















Additional Information

Multi-language Requirement

TBC

Document Management

N/A

Legal Requirement

N/A

Special Requirements






Target Design

The technical design of the target for this conversion approach.

TableFieldData ElementField DescriptionData TypeLengthRequirement
T352CRBNR
Catalog ProfileCHAR9Mandatory
T352B_TSPRAS
Language KeyLANG1Mandatory
T352B_TRBNRX
Catalog Profile TextCHAR30Mandatory
T352CQKATART
CatalogCHAR1Mandatory
T352CQCODEGRP
Search Pattern for Code Group/Selected SetCHAR8Mandatory
T352BMSGTP
Message TypeCHAR1Optional


Data Cleansing

IDCriticalityError Message/Report DescriptionRuleOutputSource System
1008-001C1Invalid or Inactive Catalog Code Groups & Codes linked to Catalog ProfileCatalog Profile as per Relevancy Criteria assigned with a Catalog Code Groups & Codes which does not belong below:
1. Catalog Code Groups & Codes as per Relevancy Criteria		All key fieldsPF2, WP2
1008-002C3Duplicate Catalog Profile by DescriptionCatalog Profile as per Relevancy Criteria where the Catalog Profile Description is used by more than one Catalog Profile.All key fieldsPF2, WP2
1008-003C1Missing Catalog Profile DescriptionsCatalog Profile as per Relevancy Criteria where there are blank Catalog Profile Descriptions.All key fieldsPF2, WP2
1008-004C2Catalog Profile Descriptions with Informal WordsCatalog Profile as per Relevancy Criteria which contain [Informal Words] in the Catalog Profile DescriptionAll key fieldsPF2, WP2
1008-005C1Company Code incorrect.Catalog Profile as per Relevancy Criteria with Invalid Company Code (T001)All key fieldsPF2, WP2
1008-006C1Plant incorrect.Catalog Profile as per Relevancy Criteria with Invalid Plant (T001W)All key fieldsPF2, WP2
1008-007C1Incorrect Company Code / Plant CombinationCatalog Profile as per Relevancy Criteria with Invalid ompany Code / Plant Combination (T001K)All key fieldsPF2, WP2
1008-008C1Inspection catalog type ind incorrect.Catalog Profile as per Relevancy Criteria with Invalid Inspection catalog type ind (TQ15)All key fieldsPF2, WP2
1008-009C1Legacy Catalog Profile which are not mappedLegacy Catalog Profile which does not have a mapped S/4 HANA Catalog ProfileAll key fieldsPF2, WP2



Conversion Process

The following represents the high-level process for DCT:

Data Privacy and Sensitivity


Extraction

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

  1. The data exists. connects to the source and loads the data into . 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 ; 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 . This is to be conducted using DCT (Data Collection Template) in

The agreed Relevancy criteria is applied to the extracted records to identify the records that are applicable for the Target loads

Extraction Run Sheet

Req #Requirement DescriptionTeam Responsible













Selection Screen

Selection Ref ScreenParameter NameSelection TypeRequirementValue to be entered/set





















Data Collection Template (DCT)

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

Catalog Profile DCT Rules

Field NameField DescriptionRule
RBNRCatalog Profile
SPRASLanguage Key
RBNRXCatalog Profile Text
QKATARTCatalog
QCODEGRPSearch Pattern for Code Group/Selected Set
MSGTPMessage Type

Extraction Dependencies

Item #Step DescriptionTeam Responsible













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 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
  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 DescriptionTeam Responsible
NA











Transformation Rules

Rule #Source systemSource TableSource FieldSource DescriptionTarget SystemTarget TableTarget FieldTarget DescriptionTransformation Logic









































Transformation Mapping

Mapping Table NameMapping Table Description

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







Transformation Dependencies

List the steps that need to occur before transformation can commence
Item #Step DescriptionTeam Responsible













Pre-Load Validation

Project Team

Completeness

TaskAction

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

TaskAction

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

Completeness

TaskAction

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

TaskAction

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













Load Phase and Dependencies

Configuration

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

Error TypeError DescriptionAction Taken










Post-Load Validation

Project Team

Completeness

TaskAction

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

TaskAction

Conversion Accuracy

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






Business

Completeness

TaskAction

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

TaskAction

Conversion Accuracy

Verify that the Measuring Point 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.
  • Catalog Profile is in scope based on data design and any exception requested by business.


See also

Change log

Version Published Changed By Comment
CURRENT (v. 12) Nov 05, 2025 07:58 PUN-ext, Eddy Updated MDS link to checked in link
v. 85 Oct 15, 2025 13:33 PUN-ext, Eddy
v. 84 Oct 15, 2025 13:29 PUN-ext, Eddy
v. 83 Oct 15, 2025 13:21 PUN-ext, Eddy
v. 82 Oct 08, 2025 11:58 PUN-ext, Eddy
v. 81 Oct 08, 2025 11:52 PUN-ext, Eddy
v. 80 Oct 08, 2025 11:21 PUN-ext, Eddy
v. 79 Oct 03, 2025 13:56 PUN-ext, Eddy
v. 78 Oct 03, 2025 13:56 PUN-ext, Eddy
v. 77 Oct 03, 2025 13:49 PUN-ext, Eddy

Go to Page History

Workflow history

Title Last Updated By Updated Status  
There are no pages at the moment.

  • No labels