Status	Approved
Owner	CLARKE-ext, Steve
Stakeholders

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

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.

List of source systems and approximate number of records

Source	Scope	Source Approx No. of Records	Target System	Target Approx No. of Records

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.

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	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	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	PARTY_ROLE_CODE	Role	CHAR	3	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_TYPE	Role	CHAR	3	Required
/SRMSMC/D_PUC_PY	????????	Role Description	CHAR	60	Conditional
Planned Spend Screen Tab
/SRMSMC/D_PUCPSP	VALID_FROM	Planned Spend: Valid From	DATE	8	Conditional
/SRMSMC/D_PUCPSP	VALID_TO	Planned Spend: Valid To	DATE	8	Conditional
/SRMSMC/D_PUCPSP	AMOUNT	Planned Spend: Amount	CURR	13 (Decimals 2)	Conditional
/SRMSMC/D_PUCPSP	CURRENCY	Currency	CUKY	5	Conditional
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

Data Cleansing

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, Language, Material Groups. A row will only be on the report if a Purchasing Group has 1 or more of the Screen Tabs with 0 records.	Purchasing Category Description (NAME), Count of Supplier, Count of Team, 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. 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	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
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	Default to Blank	This field is ticked when a purchasing category is inactive.
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
DCT-General - 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.
PARTY_ROLE_CODE	Role	Default to 2-Supplier

DCT Rules for the General Screen Tab: DCT-Team

Field Name	Field Description	Rule	Tool Tip
DCT-General - 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	Role	Mandatory. Dropdown containing: 190-Member 100-Internal Stakeholder	Contain either the value "Member" or "Internal Stakeholder".
????????	Role Description		Enter a description or any other comments that may be useful regarding the team member entered.

DCT Rules for the General Screen Tab: DCT-PlannedSpend

Field Name	Field Description	Rule	Tool Tip
DCT-General - NAME	Purchasing Category Description	Mandatory	Linking the planned spend to the purchasing category. Zero or many planned spends can be assigned to a purchasing category, split by period.
VALID_FROM	Planned Spend: Valid From		The start date of the period during which the planned spend is valid.
VALID_TO	Planned Spend: Valid To		The end date of the period during which the planned spend is valid.
AMOUNT	Planned Spend: Amount		The planned amount to be spent during the defined validity period.
CURRENCY	Currency	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
DCT-General - 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.
NAME	File Name	C	The file name of the uploaded PDF document.
DESCRIPTION	File Description	C	The description of the uploaded PDF document.
? FILE_LINK ?	? Uploaded File Link ?	??	? 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
DCT-General - NAME	Purchasing Category Description	Mandatory	Linking the Descriptions in other languages to the purchasing category. One or many Descriptions in other languages must 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. XXXXX	XXXX
NAME	Translated Description	Mandatory. XXXXX	XXXX

DCT Rules for the General Screen Tab: DCT-MaterialGroups

Field Name	Field Description	Rule
DCT-General - NAME	Purchasing Category Description	Mandatory
MATKL	Material Group
MATERIALGROUPNAME	Description
MATERIALGROUPTEXT	Long Description

Extraction Dependencies

Item #	Step Description	Team 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:

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

Transformation Rules

Rule #	Source system	Source Table	Source Field	Source Description	Target System	Target Table	Target Field	Target Description	Transformation Logic

Transformation Mapping

Mapping Table Name	Mapping Table Description

Transformation Dependencies

List the steps that need to occur before transformation can commence

Item #	Step Description	Team Responsible

Pre-Load Validation

Project Team

Completeness

Task	Action

Accuracy

Task	Action

Business

Completeness

Task	Action

Accuracy

Task	Action

Load

The load process includes:

Execute the automated data load into target system using load tool or product the load file if the load must be done manually
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

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

Post-Load Validation

Project Team

Completeness

Task	Action

Accuracy

Task	Action

Business

Completeness

Task	Action

Accuracy

Task	Action

Key Assumptions

Master Data Standard is up to date as on the date of documenting this conversion approach and data load.
is in scope based on data design and any exception requested by business.

Change log

Version	Published	Changed By	Comment
CURRENT (v. 11)	Apr 15, 2026 10:53	CLARKE-ext, Steve	MDS updated based on technical findings of how Role works.
v. 31	Apr 14, 2026 12:14	CLARKE-ext, Steve	Changed requested by FC
v. 30	Apr 07, 2026 14:48	CLARKE-ext, Steve
v. 29	Apr 07, 2026 09:36	CLARKE-ext, Steve
v. 28	Mar 31, 2026 10:47	CLARKE-ext, Steve
v. 27	Mar 31, 2026 10:25	CLARKE-ext, Steve
v. 26	Mar 25, 2026 12:54	CLARKE-ext, Steve
v. 25	Mar 23, 2026 08:46	CLARKE-ext, Steve
v. 24	Mar 20, 2026 16:30	CLARKE-ext, Steve
v. 23	Mar 18, 2026 09:17	CLARKE-ext, Steve

Go to Page History

Apr 16, 2026	Actor	Type	Activity	Version
Approved	HOLMES-ext, Richard	State	changed state to Approved at 2:33 pm	v32
Lead Approval	HOLMES-ext, Richard	State	gave POD Lead Review approval at 2:33 pm
	JAIN-ext, Gaurav	State	changed expiry date to '23 Apr, 2026 11:17 am' at 11:17 am
	JAIN-ext, Gaurav	State	changed state to Lead Approval at 11:17 am	v32
Tech Review of Updates	JAIN-ext, Gaurav	State	gave Minor change approval at 11:17 am
Apr 15, 2026
	CLARKE-ext, Steve	State	changed state to Tech Review of Updates at 11:01 am MDS updated based on technical findings of how Role works.	v32

Workflow history

Space shortcuts

Page tree

CNV-1096 Category Strategies

Purpose

Conversion Scope

Additional Information

Multi-language Requirement

Document Management

Legal Requirement

Special Requirements

Target Design

Data Cleansing

Conversion Process

Data Privacy and Sensitivity

Extraction

Extraction Run Sheet

Selection Screen

Data Collection Template (DCT)

Extraction Dependencies

Transformation

Transformation Run Sheet

Transformation Mapping

Transformation Dependencies

Pre-Load Validation

Project Team

Completeness

Accuracy

Business

Completeness

Accuracy

Load

Load Run Sheet

Configuration

Conversion Objects

Error Handling

Post-Load Validation

Project Team

Completeness

Accuracy

Business

Completeness

Accuracy

Key Assumptions

See also

Change log