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 Purchasing Categories into S/4 HANA as part of the Procurement Data Migration.

In S/4HANA, Purchasing Categories are a new concept used to classify the goods and services a company procures from its suppliers.  One or more Material Groups can be assigned to a single Purchasing Category (the relationship between material group and Purchasing Category is n:1, not n:n).  Suppliers may also be linked to multiple Purchasing Categories.

For example, a Purchasing Category such as “IT Services” may include Material Groups like "Software Licenses" and "Consulting Services".  A supplier providing both software and consulting could therefore be connected to this Purchasing Category.

Supplier Segmentation and Preferred Supplier are captured per Purchasing Category, therefore they will be assigned in the purchasing category.

Supplier Segmentation, also referred to as supplier tiering, is the process of grouping suppliers into distinct categories. These categories are determined using a balanced assessment of how critical the supplier is to the organization, how much risk the relationship entails, and how the supplier has performed historically.

Creating and maintaining Purchasing Categories in S/4 HANA will be via the FIORI app "Manage Purchasing categories".

Link to MDS: DD-FUN- 050 Master Data Standard_1096-Category Strategies

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 capturing data from Legacy Source Systems into S/4HANA following the Master Data Design Standard.

This object is migrated after Business Partner - General, therefore only suppliers in scope for the object "3007 - Business Business Partner - General" are in scope for this object.  Click here to go to the Conversion Spec for 3007 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
DCT	All suppliers that meet the relevancy rules for 3007 Business Partner - General are in scope	182 Purchasing Categories	S4H	182 Purchasing Categories

Additional Information

Multi-language Requirement

The Purchasing Categories will be created in English, but multiple languages are supported.  The following languages are allowed:

• Core languages:  EN-English, FR-French, IT-Italian and ZH-Mandarin.
• Additional languages:  PT-Portuguese, DE-German and ES-Spanish.

Not Applicable.  Only EN-English is now supported.

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.

Table	Field	Field Description	Data Type	Length	Requirement
General Screen Tab
/SRMSMC/D_PUC_RT	NAME	Purchasing Category Description	CHAR	60	Required
/SRMSMC/D_PUC_PY	USERID	Purchaser Responsible	CHAR	12	Required
/SRMSMC/D_PUC_RT	INACTIVE	Inactive Status	CHAR	1	Conditional
/SRMSMC/D_PUC_RT	PRIVATE	Private Status	CHAR	1	Conditional
/SRMSMC/D_PUC_RT	PURCATEG_VALID_TO	Purchasing category: Valid To	CHAR	8	Required
/SRMSMC/D_PUC_RT	PURCATEG_VALID_FROM	Purchasing category: Valid From	CHAR	8	Required
/SRMSMC/D_PUC_RT	CREA_UNAME	Created By	CHAR	12	Required
/SRMSMC/D_PUC_RT	CREA_DATE_TIME	Created On	DEC	21 (Decimals 7)	Required
Suppliers Screen Tab
/SRMSMC/D_PUC_PY	BUSINESSPARTNER	Business Partner	CHAR	10	Required
/SRMSMC/D_PUC_PY	SUPPLIERNAME	Name of Supplier	CHAR	80	System
/SRMSMC/D_PUC_PY	FORMATTEDADDRESS	Address	CHAR	200	System
/SRMSMC/D_PUC_PY	DOC_EMAIL	E-Mail	CHAR	241	System
/SRMSMC/D_PUC_PY	SUPPLIER_SEGMENTATION	Supplier Segmentation	CHAR	4	Required
/SRMSMC/D_PUC_PY	PREFERRED_SUPPL	Preferred Supplier	CHAR	1	Required
/SRMSMC/D_PUC_PY	MATKL	Material Group	CHAR	9	Required
/SRMSMC/D_PUCMG	MATERIALGROUPNAME	Description	CHAR	20	System
/SRMSMC/D_PUC_PY	GEO_AREA	Geographical Area	CHAR	4	Required
/SRMSMC/D_PUC_PY	PARTY_ROLE_CODE***	Role	CHAR	3	System
/SRMSMC/D_PUC_PY	PARTY_TYPE***		CHAR	1	System
Team Screen Tab
/SRMSMC/D_PUC_PY	PARTY_ID	ID	CHAR	32	Required
/SRMSMC/D_PUC_PY	FULLNAME	Name	CHAR	80	System
/SRMSMC/D_PUC_PY	DEPARTMENT	Department	CHAR	40	System
/SRMSMC/D_PUC_PY	PARTY_ROLE_CODE***	Role	CHAR	3	Required
/SRMSMC/D_PUC_PY	PARTY_TYPE***		CHAR	1	System
/SRMSMC/D_PUC_PD	TEXT	Role Description	CHAR	60	Conditional
Planned Spend Screen Tab
/SRMSMC/D_PUCPSP	VALID_FROM	Planned Spend: Valid From	DATE	8	Required
/SRMSMC/D_PUCPSP	VALID_TO	Planned Spend: Valid To	DATE	8	Required
/SRMSMC/D_PUCPSP	AMOUNT	Planned Spend: Amount	CURR	13 (Decimals 2)	Required
/SRMSMC/D_PUCPSP	CURRENCY	Currency	CUKY	5	Required
Attachments Screen Tab
/BOBF/D_ATF_DO	NAME	File Name	CHAR	255	Conditional
/BOBF/D_ATF_DO	DESCRIPTION	File Description	CHAR	64	Conditional
/BOBF/D_ATF_DO	MIMECODE	File Type	CHAR	128	System
/BOBF/D_ATF_DO	DATETIME_CR	Uploaded On/At	DEC	15	System
Language Screen Tab
/SRMSMC/D_PUCTRL	LANGUAGE_CODE	Language	LANG	1	Required
/SRMSMC/D_PUCTRL	TRANS_STATUS	Status of Translation	CHAR	2	Required
/SRMSMC/D_PUCNAM	NAME	Translated Description	CHAR	60	Required
Material Groups Screen Tab
/SRMSMC/D_PUCMG	MATKL	Material Group	CHAR	9	Required
/SRMSMC/D_PUCMG	MATERIALGROUPNAME	Description	CHAR	20	System
/SRMSMC/D_PUCMG	MATERIALGROUPTEXT	Long Description	CHAR	60	System

*** MDS updated based on technical findings of how Role works.

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	Syniti Report Required
1	High	Purchasing Category Does Not Have All Required Screen Tabs	A Purchasing Category must have at least 1 record in the following Screen Tabs:  Supplier, Team, Planned Spend Material Groups. A row will only be on the report if a Purchasing Category has 1 or more of the Screen Tabs with 0 records.	Purchasing Category Description (NAME), Count of Supplier, Count of Team, Count of Planned Spend Count of Material Groups	DCT	Yes
2	High	Material Group Assigned to multiple Purchasing Categories	A Material Group can only be assigned to 1 Purchasing Category.  (It is normal for the same Material Group to be assigned to several Suppliers in the same Purchasing Category) A row will only be on the report of a Material Group is assigned to 2 or more Purchasing Category.	Material Group (MATKL), Description (MATERIALGROUPNAME), List of Purchasing Category Description (NAME)	DCT	Yes
3		Planned Spend Periods Overlap  on Purchasing Category	Planned Spend Periods of A Purchasing Category Overlap. A row will only be on the report if: (For a Purchasing Category check each Planned Spend record against all the others) VALID_TO of record A >= VALID_FROM of record B AND VALID_FROM of record A <= VALID_TO of record B	Purchasing Category Description (NAME), VALID_FROM & VALID_TO of record A, VALID_FROM & VALID_TO of record B	DCT	Yes

Conversion Process

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

Data Privacy and Sensitivity

Not applicable.

Extraction

The data does not exist as a complete set.  It will be manually collected by the business directly in Syniti Migrate using DCT.

Extraction Run Sheet

Req #	Requirement Description	Team Responsible
1	Extract data from the DCTs.	Syniti

Selection Screen

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 Purchasing Categories data with exception of some fields which require transformation as mentioned in the transformation rule.

DCT Rules for the General Screen Tab: DCT-General

Field Name	Field Description	Rule	Tool Tip	zComment	zDelete
NAME	Purchasing Category Description	Mandatory	This field is the description of the purchasing category. For the Raw Materials category, it corresponds to the name of the Material Group Cluster (MGC). For all other categories it corresponds to the segment name.
USERID	Purchaser Responsible	Mandatory	This field is populated with the SAP user ID of the user responsible for the current purchasing category.
INACTIVE	Inactive Status	Check Box.  Default to Blank	This field is ticked when a purchasing category is inactive.
PRIVATE	Private Status	Check Box.	This field is ticked when a purchasing category is private.
PURCATEG_VALID_FROM	Purchasing category: Valid From	Mandatory.  Default to 0001.01.01	Indicates the start of the validity period for the purchasing category.
PURCATEG_VALID_TO	Purchasing category: Valid To	Mandatory.  Default to 9999.12.31	Indicates the end of the validity period for the purchasing category.
CREA_UNAME	Created By	Mandatory.	This field contains the SAP user ID of the purchasing category creator from the legacy system (Convergence).
CREA_DATE_TIME	Created On	Mandatory.	This field contains the creation date of the purchasing category from the legacy system (Convergence).

DCT Rules for the General Screen Tab: DCT-Suppliers

Field Name	Field Description	Rule	Tool Tip	zComment	zDelete
Purchasing Category Name	Purchasing Category Description	Mandatory	Linking the suppliers to the purchasing category. One or many suppliers must be assigned to a purchasing category.
BUSINESSPARTNER	Business Partner	Mandatory.  Use Check Table BUT00	This field is populated with the suppliers that are assigned to this purchasing category.
SUPPLIERNAME	Name of Supplier	Auto-populated	The supplier’s registered name
FORMATTEDADDRESS	Address	Auto-populated from table ADRC	The supplier’s registered address
DOC_EMAIL	E-Mail	Auto-populated if it is maintained in the partner function CP of the business partner.	The supplier’s registered email
SUPPLIER_SEGMENTATION	Supplier Segmentation	Mandatory.  Dropdown containing: 0001-Critical Supplier 0002-Regular Supplier 0003-Tail-End Supplier	Indicates the supplier tiering. This field is based on the value of the Supplier Nature field from Convergence: Partner  --> 0001-Critical Supplier Regular --> 0002-Regular Supplier Blank    --> 0003-Tail-End Supplier
PREFERRED_SUPPL	Preferred Supplier	Mandatory.  Dropdown containing: X-Yes <Blank>-No	Indicates if the Supplier is a preferred supplier for the current purchasing category.
MATKL	Material Group	Mandatory.  Use Check Table T023.	The Material Group Code (MGC) for this Supplier.
MATERIALGROUPNAME	Description	Auto-populated	Material Group Description
GEO_AREA	Geographical Area	Mandatory.  Use Check Table T024E (Purchase Organisation)	Indicates whether the maintained supplier is a preferred supplier for the purchasing category within the specified geographical area.
PARTY_ROLE_CODE	Role	Auto-populated

  

DCT Rules for the General Screen Tab: DCT-Team

Field Name	Field Description	Rule	Tool Tip	zComment	zDelete
Purchasing Category Name	Purchasing Category Description	Mandatory	Linking the team to the purchasing category. One or many team members must be assigned to a purchasing category. A team member can belong to multiple purchasing category.
PARTY_ID	ID	Mandatory	This field contains the SAP user ID of the team member.
FULLNAME	Name	Auto-populated based on PARTY_ID. Concat of first and last names.	Based on the user ID identified in ID.  It's a concatenation of the first and last names mentioned in the SAP user profile.
DEPARTMENT	Department	Auto-populated based on PARTY_ID.	Based on the user ID identified in ID.  It is maintained in the SAP user profile.
PARTY_TYPE*** PARTY_ROLE_CODE	Role	Mandatory.  Dropdown containing: 190-Member 100-Internal Stakeholder	Contain either the value "Member" or  "Internal Stakeholder".
TEXT	Role Description		Enter a description or any other comments that may be useful regarding the team member entered.

*** MDS updated based on technical findings of how Role works.

DCT Rules for the General Screen Tab: DCT-PlannedSpend

Field Name	Field Description	Rule	Tool Tip	zComment	zDelete
Purchasing Category Name	Purchasing Category Description	Mandatory	Linking the planned spend to the purchasing category. One or many planned spends must be assigned to a purchasing category, split by period.
VALID_FROM	Planned Spend: Valid From	Mandatory	The start date of the period during which the planned spend is valid.
VALID_TO	Planned Spend: Valid To	Mandatory	The end date of the period during which the planned spend is valid.
AMOUNT	Planned Spend: Amount	Mandatory	The planned amount to be spent during the defined validity period.
CURRENCY	Currency	Mandatory.  Dropdown using TCURT-WAERS, TCURT-LTEXT for SPRAS = E	The currency of planned amount to be spent.

DCT Rules for the General Screen Tab: DCT-Attachments

Field Name	Field Description	Rule	Tool Tip	zComment	zDelete
Purchasing Category Name	Purchasing Category Description	Mandatory	Linking the PDF documents to the purchasing category. Zero or many PDF documents can be attached to a purchasing category.
FILENAME	File Name	Mandatory	The file name of the uploaded PDF document.
DESCRIPTION	File Description		The description of the uploaded PDF document.
? FILE_LINK ?	? Uploaded File Link ?	? Mandatory ?	? The link to document attached to the purchasing category. ?
MIMECODE	File Type	Read only. Default to PDF	Set to PDF because only PDF documents are allowed.
DATETIME_CR	Uploaded On/At	Mandatory	The date and time of uploading the file.

DCT Rules for the General Screen Tab: DCT-Languages

Field Name	Field Description	Rule	Tool Tip	zComment	zDelete
DCT-General - NAME	Purchasing Category Description	Mandatory	Linking the Descriptions in other languages to the purchasing category. Zero or many Descriptions in other languages can be assigned to a purchasing category.
LANGUAGE_CODE	Language	Mandatory.  Dropdown using (T002-LAISO) and (T002T-SPTXT where SPRAS = E)	The language into which the original purchasing category description is translated into.
TRANS_STATUS	Status of Translation	Mandatory.  Dropdown containing: 01-To Be Translated 03-Translated Default to 03-Translated.	The status of the translation for the purchasing category description in the specified language.
NAME	Translated Description	Mandatory	The purchasing category description translated into the language specified in the field Language.  Each defined language requires its own translated description.

DCT Rules for the General Screen Tab: DCT-MaterialGroups

Field Name	Field Description	Rule	Tool Tip	zComment	zDelete
DCT-General - NAME	Purchasing Category Description	Mandatory	Linking the Material Groups to the purchasing category. One or many Material Groups must be assigned to a purchasing category.
MATKL	Material Group	Mandatory.  Dropdown using T023.	The Material Group Code (MGC) assigned to the purchasing category.  A MGC belongs to only one purchasing category.
MATERIALGROUPNAME	Description	Auto-populated with the Material Group Description.	The Material Group Description.
MATERIALGROUPTEXT	Long Description	Auto-populated with the Material Group Long Description.	The Material Group Long Description.

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	Verify that the Suppliers XREF has been updated	Syniti
2	Verify that the Material Groups XREF has been updated	Syniti

Transformation Rules

Rule #	Source system	Source Table	Source Field	Source Description	Target System	Target Table	Target Field	Target Description	Transformation Logic
1	DCT	DCT-General	NAME	Purchasing Category Description	S4	/SRMSMC/D_PUC_RT	NAME	Purchasing Category Description	Copy As-Is
2	DCT	DCT-General	USERID	Purchaser Responsible	S4	/SRMSMC/D_PUC_PY	USERID	Purchaser Responsible	Copy As-Is
3	DCT	DCT-General	INACTIVE	Inactive Status	S4	/SRMSMC/D_PUC_RT	INACTIVE	Inactive Status	Default to Blank.
4	DCT	DCT-General	PRIVATE	Private Status	S4	/SRMSMC/D_PUC_RT	PRIVATE	Private Status	Tick = X else Blank
5	DCT	DCT-General	PURCATEG_VALID_TO	Purchasing category: Valid From	S4	/SRMSMC/D_PUC_RT	PURCATEG_VALID_TO	Purchasing category: Valid From	Copy As-Is
6	DCT	DCT-General	PURCATEG_VALID_FROM	Purchasing category: Valid To	S4	/SRMSMC/D_PUC_RT	PURCATEG_VALID_FROM	Purchasing category: Valid To	Copy As-Is
7	DCT	DCT-General	CREA_UNAME	Created By	S4	/SRMSMC/D_PUC_RT	CREA_UNAME	Created By	Possible User ID XREF Mapping
8	DCT	DCT-General	CREA_DATE_TIME	Created On	S4	/SRMSMC/D_PUC_RT	CREA_DATE_TIME	Created On	Copy As-Is

Rule #	Source system	Source Table	Source Field	Source Description	Target System	Target Table	Target Field	Target Description	Transformation Logic
1	DCT	DCT-Suppliers	DCT-General - NAME	Purchasing Category Description	S4				Link to Purchasing Category
2	DCT	DCT-Suppliers	BUSINESSPARTNER	Business Partner	S4	/SRMSMC/D_PUC_PY	BUSINESSPARTNER	Business Partner	Copy As-Is
3	DCT	DCT-Suppliers	SUPPLIERNAME	Name of Supplier	S4	/SRMSMC/D_PUC_PY	SUPPLIERNAME	Name of Supplier	Business Partner from table BUT00
4	DCT	DCT-Suppliers	FORMATTEDADDRESS	Address	S4	/SRMSMC/D_PUC_PY	FORMATTEDADDRESS	Address	Business Partner from table ADRC
5	DCT	DCT-Suppliers	DOC_EMAIL	E-Mail	S4	/SRMSMC/D_PUC_PY	DOC_EMAIL	E-Mail	If it is maintained in the partner function CP of the Business Partner.
6	DCT	DCT-Suppliers	SUPPLIER_SEGMENTATION	Supplier Segmentation	S4	/SRMSMC/D_PUC_PY	SUPPLIER_SEGMENTATION	Supplier Segmentation	Copy As-Is
7	DCT	DCT-Suppliers	PREFERRED_SUPPL	Preferred Supplier	S4	/SRMSMC/D_PUC_PY	PREFERRED_SUPPL	Preferred Supplier	Copy As-Is
8	DCT	DCT-Suppliers	MATKL	Material Group	S4	/SRMSMC/D_PUC_PY	MATKL	Material Group	Copy As-Is
9	DCT	DCT-Suppliers	MATERIALGROUPNAME	Description	S4	/SRMSMC/D_PUCMG	MATERIALGROUPNAME	Description	T023T-WGBEZ based on MATKL and SPRAS = 'E'.
10	DCT	DCT-Suppliers	GEO_AREA	Geographical Area	S4	/SRMSMC/D_PUC_PY	GEO_AREA	Geographical Area	Copy As-Is
11	DCT	DCT-Suppliers	PARTY_ROLE_CODE***	Role	S4	/SRMSMC/D_PUC_PY	PARTY_ROLE_CODE***	Role	Default to 2
12	DCT	DCT-Suppliers	PARTY_TYPE***		S4	/SRMSMC/D_PUC_PY	PARTY_TYPE***		Default to 'S'

*** MDS updated based on technical findings of how Role works.

Rule #	Source system	Source Table	Source Field	Source Description	Target System	Target Table	Target Field	Target Description	Transformation Logic
1	DCT	DCT-Team	DCT-General - NAME	Purchasing Category Description	S4				Link to Purchasing Category
2	DCT	DCT-Team	PARTY_ID	ID	S4	/SRMSMC/D_PUC_PY	PARTY_ID	ID	Possible User ID XREF Mapping
3	DCT	DCT-Team	FULLNAME	Name	S4	/SRMSMC/D_PUC_PY	FULLNAME	Name	Concat of first and last names of User ID in PARTY_ID.
4	DCT	DCT-Team	DEPARTMENT	Department	S4	/SRMSMC/D_PUC_PY	DEPARTMENT	Department	Based on User ID in PARTY_ID.
5	DCT	DCT-Team	PARTY_ROLE_CODE***	Role	S4	/SRMSMC/D_PUC_PY	PARTY_ROLE_CODE***	Role	Copy As-Is
6	DCT	DCT-Team	PARTY_TYPE***		S4	/SRMSMC/D_PUC_PY	PARTY_TYPE***		Default to 'E'
7	DCT	DCT-Team	TEXT	Role Description	S4	/SRMSMC/D_PUC_PD	TEXT	Role Description	Copy As-Is

*** MDS updated based on technical findings of how Role works.

Rule #	Source system	Source Table	Source Field	Source Description	Target System	Target Table	Target Field	Target Description	Transformation Logic
1	DCT	DCT-PlannedSpend	DCT-General - NAME	Purchasing Category Description	S4				Link to Purchasing Category
2	DCT	DCT-PlannedSpend	VALID_FROM	Planned Spend: Valid From	S4	/SRMSMC/D_PUCPSP	VALID_FROM	Planned Spend: Valid From	Copy As-Is
3	DCT	DCT-PlannedSpend	VALID_TO	Planned Spend: Valid To	S4	/SRMSMC/D_PUCPSP	VALID_TO	Planned Spend: Valid To	Copy As-Is
4	DCT	DCT-PlannedSpend	AMOUNT	Planned Spend: Amount	S4	/SRMSMC/D_PUCPSP	AMOUNT	Planned Spend: Amount	Copy As-Is
5	DCT	DCT-PlannedSpend	CURRENCY	Currency	S4	/SRMSMC/D_PUCPSP	CURRENCY	Currency	Copy As-Is

Rule #	Source system	Source Table	Source Field	Source Description	Target System	Target Table	Target Field	Target Description	Transformation Logic
1	DCT	DCT-Attachments	DCT-General - NAME	Purchasing Category Description	S4				Link to Purchasing Category
2	DCT	DCT-Attachments	NAME	File Name	S4	/BOBF/D_ATF_DO	NAME	File Name	Copy As-Is
3	DCT	DCT-Attachments	DESCRIPTION	File Description	S4	/BOBF/D_ATF_DO	DESCRIPTION	File Description	Copy As-Is
4	DCT	DCT-Attachments	? FILE_LINK ?	? Uploaded File Link ?	S4	? To be updated ?	? FILE_LINK ?	? Uploaded File Link ?	Copy As-Is
5	DCT	DCT-Attachments	MIMECODE	File Type	S4	/BOBF/D_ATF_DO	MIMECODE	File Type	Copy As-Is
6	DCT	DCT-Attachments	DATETIME_CR	Uploaded On/At	S4	/BOBF/D_ATF_DO	DATETIME_CR	Uploaded On/At	Copy As-Is

  

Rule #	Source system	Source Table	Source Field	Source Description	Target System	Target Table	Target Field	Target Description	Transformation Logic
1	DCT	DCT-Languages	DCT-General - NAME	Purchasing Category Description	S4				Link to Purchasing Category
2	DCT	DCT-Languages	LANGUAGE_CODE	Language	S4	/SRMSMC/D_PUCTRL	LANGUAGE_CODE	Language	Copy As-Is
3	DCT	DCT-Languages	TRANS_STATUS	Status of Translation	S4	/SRMSMC/D_PUCTRL	TRANS_STATUS	Status of Translation	Copy As-Is
4	DCT	DCT-Languages	NAME	Translated Description	S4	/SRMSMC/D_PUCNAM	NAME	Translated Description	Copy As-Is

  

Rule #	Source system	Source Table	Source Field	Source Description	Target System	Target Table	Target Field	Target Description	Transformation Logic
1	DCT	DCT-MaterialGroups	DCT-General - NAME	Purchasing Category Description	S4				Link to Purchasing Category
2	DCT	DCT-MaterialGroups	MATKL	Material Group	S4	/SRMSMC/D_PUCMG	MATKL	Material Group	Copy As-Is
3	DCT	DCT-MaterialGroups	MATERIALGROUPNAME	Description	S4	/SRMSMC/D_PUCMG	MATERIALGROUPNAME	Description	T023T-WGBEZ based on MATKL and SPRAS = 'E'.
4	DCT	DCT-MaterialGroups	MATERIALGROUPTEXT	Long Description	S4	/SRMSMC/D_PUCMG	MATERIALGROUPTEXT	Long Description	T023T-WGBEZ60 based on MATKL and SPRAS = 'E'.

Transformation Mapping

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

Mapping Table Name	Mapping Table Description	Link
Material Group	XREF	Conversion Specification - Mappings
Supplier (Vendor Number)	XREF	Conversion Specification - Mappings
User ID	XREF	Conversion Specification - Mappings

Transformation Dependencies

List the steps that need to occur before transformation can commence

Item #	Step Description	Team Responsible
1	Ensure DCT completeness	S2P Data Team
2	Value mapping and XREF tables are ready	Syniti & S2P Data Team
3	We have dependency on HR migration and User ID setup for all users.  We may need XREF of Legacy to S4HANA users IDs	Syniti & S2P 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	The number of records in the DCT after validation needs to be correct compared to the staged data in Syniti ADMM.
Completeness check	All fields required as per mapping template rules must be completed. Syniti ADMM standard validity reports checking each field in Syniti must be built.

Accuracy

Task	Action
Conversion Accuracy	Verify that the data staged in the preload tables are correct in terms of the mapping rules. This will be done via Syniti ADMM standard reports.
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
Completeness Check	Business should compare legacy record counts, taking into account the reduction from the relevancy and deduplication processes, against the record count in the preload table.

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. Execute the automated data load into target system using the appropriate load tool.
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 Material Group and Suppliers XREFs are ready	Data Specialist/Functional - S2P
2	Stage data for transformations	Syniti
3	Run transforms	Syniti
4	Execute pre-load report	Syniti
5	Validate preload report - release	Data Specialist/Functional - S2P
6	Prepare and simulate	Syniti
7	Pre-load verification and approval to load	Functional/Data Owner - S2P
8	Load to S4	Syniti
9	Complete Jira steps, Volumes and Timings	All - where applicable
10	Execute post-load report	Syniti
11	Post-load report verification/validation	Data Specialist/Functional/Data Owner - S2P
12	Object load completion approval	Data Owner - S2P

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
1	DD - FUN - 030 Configuration Workbook - S2P - Purchasing - Supplier and Category Management.docx

Conversion Objects

Object #	Preceding Object Conversion Approach
1	Material Master - Basic View (2019)
2	Business Partner (Vendor) (3026)

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	Source Material Group not linked to a Target Material Group in the XREF	Fix incorrect data
Data	Source Supplier not linked to a Target Supplier in the XREF	Fix incorrect data
Data	Duplicates	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
Config	Configuration is missing in the Target System	Missing config added in the Target System

Post-Load Validation

Project Team

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

Post-Load Steps

Task	Action
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 post-load needs to be compared to the preload – Syniti report
Field by field check	Compare source data staged in the preload tables to target data in the load tables.

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	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.
Field by field check	Perform random Field by Field checks by comparing source data staged in the preload tables to target data in the load tables.

Accuracy

Task	Action
Conversion Accuracy	Verify that the data in S/4 HANA was loaded correctly via Syniti post-load reports.

Key Assumptions

• Master Data Standard is up to date as on the date of documenting this conversion approach and data load.
• Purchasing Categories (Category Strategies) 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