Status	20%
Owner	Prasad Naidu
Stakeholders	NG-ext, Bernard GARCIA-ext, Angel Luis PILLAY-ext, Lawrence

Purpose

The Business Partner role UKM000 is used to manage Credit Management data within the FSCM framework. With UKM000, credit data is maintained per credit segment (instead of credit control areas), ensuring accurate credit checks in sales and financial processes. Its purpose is to provide a unified, modern, and integrated way to control customer credit risk across the system.

Conversion Scope

The scope of this document covers the approach for converting active Customer Master Data from Legacy Source Systems into S/4HANA Business Partner Credit management UKM000 Master Data Design Standard.

The CNV-3007 Business Partners – General (Role 000000) relevancy criteria will also be used for this conversion document as below.

The relevance below is applicable for BP customers. Once the customers in scope are finalized and extracted, we need to check the credit management fields for those customers in the legacy system and apply the transformation rules as per the source-to-target mappings.

Customer Master Data - General Information

The data from legacy system includes:

1. Customer with AR Balance under the company codes within S4 Hana implementation scope (BSID-KUNNR).
2. or (Customer doesn't have central deletion indicator (KNA1-LOEVM="") AND Customer has active sales view data within the sales organizations in scope(KNVV-KUNNR)) and there is usage within 4 years. * modified on 16/Oct/2025
3. or (Customer doesn't have central deletion indicator and customer has active company code view within the company codes in scope) and there is usage within 4 years. * modified on 16/Oct/2025
4. or there is customer consignment stock and the plant for the consignment stock is within S4 Hana implementation scope.
5. or Customer is set as the credit account for other customers, and either the customer or credit account customer is not deleted. (if both customer or credit account is deleted, then not in migration scope)

6. Intercompany customer will be defined based on the Enterprise structure. (To identify Intercompany customer, trading partner will be used. In the meantime, Group field(KNA1-KONZS) from customer general data will be used. For WP2/PF2, Group value = 0000810135 (Syensqo) )

7. or the customer in the partner function is active, then the parent customer will also be migrated. * added on 16/Oct/2025

8. or the customer is active in Salesforce and there are activities within 48 months.* added on 16/Oct/2025

9. or there is an existing forecast for the customer in Kinaxis. * added on 16/Oct/2025

10. or there is active master data for the customer, such as active Pricing Condition records. * added on 16/Oct/2025

Criteria	Relevancy Rule	Technical Details
1	Customer with AR Balance under the company codes within S4 Hana implementation scope	Select KUNNR from BSID where BSID-BUKRS in (Company code in scope)
2	or (Customer doesn't have central deletion indicator AND Customer has active sales view data within the sales organizations in scope) and there is usage within 4 years.	Select KUNNR from KNA1 where KNA1-LOEVM="" and KNVV-KUNNR = KNA1-KUNNR AND KNVV-VKORG in (Sales Org in scope) and KNVV-LOEVM = "" and usage within 4 years. Accounting document (Select MAX(BSAD/BSID-CPUDT) where BSAD/BSID-KUNNR =KNA1-KUNNR and BSAD/BSID-BUKRS = (Company code in scope) ) Sales Document (Select MAX(VBAK-ERDAT) WHERE VBAK-VBELN=VBPA-VBELN AND VBPA-KUNNR = KNA1-KUNNR) Delivery Document (Select MAX(LIKP-ERDAT) WHERE LIKP-VBELN=VBPA-VBELN AND VBPA-KUNNR = KNA1-KUNNR) Billing (Select MAX(VBRK-ERDAT) WHERE VBRK-VBELN=VBPA-VBELN AND VBPA-KUNNR = KNA1-KUNNR)
3	or (Customer doesn't have central deletion indicator and customer has active company code view within the company codes in scope) and there is usage within 4 years	Select KUNNR from KNA1 where KNA1-LOEVM="" and KNB1-KUNNR = KNA1-KUNNR AND KNB1-BUKRS in (Company code in scope) and KNB1-LOVEM = "" and usage with 4 years Accounting document (Select MAX(BSAD/BSID-CPUDT) where BSAD/BSID-KUNNR =KNA1-KUNNR and BSAD/BSID-BUKRS = (Company code in scope) ) Sales Document (Select MAX(VBAK-ERDAT) WHERE VBAK-VBELN=VBPA-VBELN AND VBPA-KUNNR = KNA1-KUNNR) Delivery Document (Select MAX(LIKP-ERDAT) WHERE LIKP-VBELN=VBPA-VBELN AND VBPA-KUNNR = KNA1-KUNNR) Billing (Select MAX(VBRK-ERDAT) WHERE VBRK-VBELN=VBPA-VBELN AND VBPA-KUNNR = KNA1-KUNNR)
4	or there is customer consignment stock and the plant for the consignment stock is within S4 Hana implementation scope.	Select KUNNR from MSKU where MSKU-WERKS in (Plant in scope)
5	or Customer is used for Credit Limit Reference in Credit Management, only when the credit account is different from the customer, and at least credit account or customer is still active.	Select KNKLI from KNKK where KNKK-KKBER = T001CM-KKBER and T001CM-BUKRS in (Company Code in scope based on the sales organization) where KNKK-KUNNR<>KNKK-KNKLI AND (KNA1-LOEVM is initial where KNA1-KUNNR = KNKK-KUNNR or KNA1-LOEVM is initial where KNA1-KUNNR = KNKK-KNKLI)
6	Intercompany Customer is in migration scope, but it will be use Data Collection Template to collect the information	KNA1-VBUND <>"" or KNA1-KONZS
7	or the customer in the partner function is active and in migration scope, then the parent customer will also be migrated based on rule 2. * added on 16/Oct/2025	Select KNVP-KUNNR INNER JOIN KNA1 as a WHERE KNVP-KUNNR = a.kunnr and a.loevm = X and KNVP-VKORG in 'Sales Org in scope' inner join kna1 as b where knvp-kunn2 = b.kunnr and b.loevm = '' and kunn2 in rule 2
8	or the customer is active in Salesforce and there are activities within 48 months.	Two reports will be provided. iCare - If (there is value in field 'PRS Code (Account)' or 'RCS code (Account)') and 'Last Activity' is within 48 months and Type <> "Inactive Customer". then the account is in scope. 'PRS Code (Account)' is mapped to PF2 customer number, 'RCS code (Account)' is mapped to WP2 customer number. Core CRM - If (there is value in field 'PRS ID / RCS ID') and 'Last Activity' is within 48 months and 'Account Organization' = 'SCO' and 'Status'<>"Rejected", then the account is in scope. 'PRS ID / RCS ID' need to split using "/" to get the PRS/RCS code and 'GBU' in (Novecare, Technology Solutions).
9	or there is an existing forecast for the customer in Kinaxis.	This will be parked for now
10	or there is relevant Pricing Condition records maintained for the customer 4 years ago. a. The relevant condition table will be provided, which includes the customer field b. The price valid-from date is >= current date - 4 years c. Based on the selection criteria mentioned in a&b to select the condition header index table (KONH), then use it to match the customer number. If there is match, then the customer is taken into consideration.	Select KNA1-KUNNR from KONH where KONH-KOTABNR IN (List to be provided) and KONH-DATAB >= current date - 4 years and KONH-VAKEY CS KNA1-KUNNR

The data from legacy system excludes:

One time customer (Account group is Z004 or ZCPD)

1

One time customer (Account group is Z004)

KNA1-KTOKD = Z004 or ZCPD

List of source systems and approximate number of records

Source	Scope	Source Approx. No. of records	Target System	Target Approx. No. of records
PF2	Customer Master Data General Information	55371	S4	4200
WP2	Customer Master Data General Information	36983	S4	24000

Additional Information

Multi-language Requirement

Document Management

Legal Requirement

Special Requirements

Target Design

The technical design of the target for this conversion approach.

Table	Field	Data Element	Field Description	Data Type	Length	Requirement
KNA1	KUNNR	KUNNR	Business Partner Number	CHAR	10	Required
UKMBP_CMS	CHECK_RULE	CHECK_RULE	Rule for Credit Check	CHAR	10	Required
UKMBP_CMS	RISK_CLASS	RISK_CLASS	Risk Class	CHAR	3	Required
UKMBP_CMS	CREDIT_GROUP	CREDIT_GROUP	Customer Credit Group	NUMC	4	Conditional
UKMBP_CMS_SGM	CREDIT_SGMNT	CREDIT_SGMNT	Credit Segment	CHAR	10	Conditional
UKMBP_CMS_SGM	CREDIT_LIMIT	CREDIT_LIMIT	Credit Limit	CURR	15, 2	Conditional
UKMBP_CMS_SGM	XBLOCKED	SGMXBLOCKED	Blocked	CHAR	1	Conditional

Data Cleansing

This is not applicable for this Object

Conversion Process

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

The ETL (Extract, Transform, Load) process is a structured approach to data migration and management, ensuring high-quality data is seamlessly transferred across systems. Here’s a breakdown of its key components:

Extraction

Data will be extracted using Syniti ADMM from ECC

2. Transformation
Once extracted, the data undergoes cleansing, consolidation, and governance. This step ensures data integrity, consistency, and compliance with business rules. The transformation process includes:
- Data validation to remove inconsistencies.
- Standardization to align formats across datasets.
- Business rule application to refine data for operational use.

3. Loading
The transformed data is then loaded into the target S4 Hana system.

Data Privacy and Sensitivity

N/A

Extraction

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

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.

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 Description	Team Responsible
Extraction Scope Definition	- Identify the source systems and databases involved. - Define the data objects (tables, fields, records) to be extracted. - Establish business rules for data selection.	Syniti Syniti
Extraction Methodology	- Specify the extraction approach (full, incremental, or delta extraction). - Determine the tools and technologies used. - Define data filtering criteria to exclude irrelevant records.	Syniti
Extraction Execution Plan	- Establish execution timelines and batch processing schedules. - Assign responsibilities for extraction monitoring. - Document dependencies on other migration tasks.	Syniti
Data Quality and Validation	- Define error handling mechanisms for extraction failures.	Syniti

Selection Screen

Selection Ref Screen	Parameter Name	Selection Type	Requirement	Value to be entered/set
N/A

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.

DCT Rules - No DCT

Field Name	Field Description	Rule
N/A

Extraction Dependencies

Item #	Step Description	Team Responsible
1	Source System Availability Ensure that the source database or application is accessible. Confirm that necessary credentials and permissions are granted	Syensqo IT
2	Data Structure Identify relationships between tables, views, and stored procedures.	Syniti
3	Referential Integrity Ensure dependent records are extracted together.	Syniti
4	Extraction Methodology Define whether extraction is full, incremental, or delta-based. Establish batch processing schedules for large datasets.	Syniti
5	Performance and Scalability Considerations Optimize extraction queries to prevent system overload. Ensure network bandwidth supports data transfer volumes.	Syniti
6	Security and Compliance Adhere to regulatory standards for sensitive information if applicable	Syniti

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

NA

Transformation Rules

Rule #	Source system	Source Table	Source Field	Source Description	Target System	Target Table	Target Field	Target Description	Transformation Logic
1	ECC	KNA1	KUNNR	Customer Number	S/4HANA	KNA1	KUNNR	Business Partner Number	Map from source to target using Business Partner mapping table
2	ECC	UKMBP_CMS	CHECK_RULE	Rule for Credit Check	S/4HANA	UKMBP_CMS	CHECK_RULE	Rule for Credit Check	Legacy to target Mappings will be provided by business
3	ECC	KNKK	CTLPC	Risk category	S/4HANA	UKMBP_CMS	RISK_CLASS	Risk Class	Legacy to target Mappings will be provided by business
4	ECC	KNKK	GRUPP	Customer Credit Group	S/4HANA	UKMBP_CMS	CREDIT_GROUP	Customer Credit Group	Legacy to target Mappings will be provided by business
5	ECC	UKMBP_CMS_SGM	CREDIT_SGMNT	Credit Segment	S/4HANA	UKMBP_CMS_SGM	CREDIT_SGMNT	Credit Segment	Legacy to target Mappings will be provided by business
6	ECC	KNKK	KLIMK	Credit limit	S/4HANA	UKMBP_CMS_SGM	CREDIT_LIMIT	Credit Limit	Copy as-is
7	ECC	KNKK	CRBLB	Indicator: Blocked by credit management	S/4HANA	UKMBP_CMS_SGM	XBLOCKED	Blocked	Copy as-is

Transformation Mapping

Mapping Table Name	Description
Legacy Customer-BP Master Mapping	Legacy to S4 Business Partner customer mapping

Transformation Dependencies

List the steps that need to occur before transformation can commence

Item #	Step Description	Team Responsible
1	Source Data Integrity - Ensure extracted data is complete, accurate, and consistent. - Validate that data types and formats align with transformation requirements.	Syniti
2	Referential Integrity - Ensure dependent records are transformed together or in advance	Syniti
3	Transformation Logic and Mapping - Define data mapping rules between source and target schemas.	Data Team
4	Performance and Scalability Considerations - Optimize transformation processes for large datasets. - Ensure system resources can handle transformation workloads	Syniti
5	Logging and Error Handling - Maintain detailed logs of transformation activities. - Define error-handling procedures for failed transformations	Syniti

Pre-Load Validation

Project Team

Completeness

Task	Action
Verify count	Verify counts between source and target databases. Identify missing or duplicated records.
Validate the mandatory fields	Validate there is value for all the mandatory fields

Accuracy

Task	Action
Validate the transformation	Validate the fields which require transformation have the value after transformation instead of the original field value
Check Data Consistency	Compare field values across systems Validate data formats and structures

Business

Completeness

Task	Action
Verify Count for all customers	Verify that the record count in the pre-load file is the same as the record count based on the relevancy (including deduplication) results
Verify Relevancy Rules	Verify that the relevancy rules were correctly applied

Accuracy

Task	Action
Verify Data Accuracy	Verify that all the data in the load table/file is accurate as per signed-off transformation rules
Review Error Reports	Verify that all necessary error reports have been validated, and that errors have been addressed.
Verify Transformation Rules	Verify that the transformation rules are correct and have been carried out correctly

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
1	Load Sample Business Partners	Data
2	Validate sample Business Partners	Data
3	Load remaining Business Partners	Data
4	Validate data loaded for Business Partners	Data
5	Load Sample BP Type – Customer Contact Persons	Data
6	Validate sample BP Type – Customer Contact Persons	Data
7	Load remaining BP Type – Customer Contact Persons	Data
8	Validate data loaded for BP Type – Customer Contact Persons	Data
9	Load Sample BP Type – Vendor Contact Persons	Data
10	Validate sample BP Type – Vendor Contact Persons	Data
11	Load remaining BP Type – Vendor Contact Persons	Data
12	Validate data loaded for BP Type – Vendor Contact Persons	Data
13	Load Sample BP Type - Bank Contacts (First Name, Last Name)	Data
14	Validate sample BP Type - Bank Contacts (First Name, Last Name)	Data
15	Load remaining BP Type - Bank Contacts (First Name, Last Name)	Data
16	Validate data loaded for BP Type - Bank Contacts (First Name, Last Name)	Data
17	Load Sample BP Type – BP General, FI Customer, FI Vendor	Data
18	Validate sample BP Type – BP General, FI Customer, FI Vendor	Data
19	Load remaining BP Type – BP General, FI Customer, FI Vendor	Data
20	Validate data loaded for BP Type – BP General, FI Customer, FI Vendor	Data
21	Load Sample Vendors Default Partner	Data
22	Validate sample Vendors Default Partner	Data
23	Load remaining Vendors Default Partner	Data
24	Validate data loaded for Vendors Default Partner	Data
25	Load Sample BP - General for remaining customer roles	Data
26	Validate sample BP - General for remaining customer roles	Data
27	Load remaining BP - General for remaining customer roles	Data
28	Validate data loaded for BP - General for remaining customer roles	Data
29	Load Sample BP – Customers with Default Partner	Data
30	Validate sample BP – Customers with Default Partner	Data
31	Load remaining BP – Customers with Default Partner	Data
32	Validate data loaded BP – Customers with Default Partner	Data
33	Load Sample BP - Bank Role	Data
34	Validate sample BP - Bank Role	Data
35	Load remaining BP - Bank Role	Data
36	Validate data loaded BP - Bank Role	Data
37	Load Sample BP Relationship Contact Person to Organisation (Will create KNVK records)	Data
38	Validate sample BP Relationship Contact Person to Organisation (Will create KNVK records)	Data
39	Load remaining BP Relationship Contact Person to Organisation (Will create KNVK records)	Data
40	Validate data loaded for BP Relationship Contact Person to Organisation (Will create KNVK records)	Data
41	Load Sample BP - Carrier	Data
42	Validate sample BP - Carrier	Data
43	Load remaining BP - Carrier	Data
44	Validate data loaded BP - Carrier	Data
45	Load Sample BP - Credit Management	Data
46	Validate sample BP - Credit Management	Data
47	Load remaining BP - Credit Management	Data
48	Validate data loaded BP - Credit Management	Data
49	Load Sample BP Collections Management	Data
50	Validate sample BP Collections Management	Data
51	Load remaining BP Collections Management	Data
52	Validate data loaded BP Collections Management	Data

Load Phase and Dependencies

Configuration

Item #	Configuration Item
1	Obtain the approved upload USER ID’s to be used (e.g. Firefighter ID)
2	SAP USER profile (SU3) Date and Decimal Notation Formats are in sync with the load format
3	Company Code Configuration
4	BP Grouping
5	Customer Account Group
6	BP Number Range

Conversion Objects

Object #	Preceding Object Conversion Approach
N/A

Error Handling

Error Type

Error Description

Action Taken

Configuration

<configuration> is not valid/missing

If it is a missing configuration item then engage Functional team to expedite and fix the error in the system.

Invalid Data

<parameter> is not valid.

The parameter entry needs to be reviewed (ex. invalid payment terms).

If it is an invalid data, business needs to review and correct the source of the data either in PF2/PI2/WP2

Technical Setup

Interface / Connection issue within target system’s landscape

N/A – the data will be loaded directly to S/4HANA environment

Post-Load Validation

Project Team

Completeness

Task	Action
Perform Data Count	Validate that migrated data matches source records.
Perform Source-to-Target Comparisons	Validate all the mandatory fields are populated as per the loading file

Accuracy

Task	Action
Data Accuracy	Data team to verify that all the data in the load table/file is accurate as per signed-off transformation rules
Error Reports	Verify that all necessary error reports have been validated, and that errors have been addressed.

Business

Completeness

Task	Action
Perform Source-to-Target Comparisons	Validate that migrated data matches source records counts.
Conduct Post-Migration Reconciliation	Go through reports comparing pre- and post-migration data provided by Syniti.

Accuracy

Task	Action
Verify Data Accuracy	Data team to verify that all the data in the load table/file is accurate as per signed-off transformation rules
Review Error Reports	Verify that all necessary error reports have been validated, and that errors have been addressed.
Validate Loaded Data	Validate, as per the loads files signed-off, that all records were created

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
CURRENT (v. 25)	Apr 22, 2026 15:59	NAIDU-ext, Prasad
v. 33	Apr 22, 2026 13:43	NAIDU-ext, Prasad
v. 32	Mar 13, 2026 11:55	NAIDU-ext, Prasad
v. 31	Mar 13, 2026 11:13	NAIDU-ext, Prasad
v. 30	Nov 20, 2025 12:28	PILLAY-ext, Lawrence
v. 29	Nov 20, 2025 12:24	PILLAY-ext, Lawrence
v. 28	Nov 19, 2025 16:29	NAIDU-ext, Prasad
v. 27	Nov 18, 2025 15:38	NAIDU-ext, Prasad
v. 26	Nov 18, 2025 10:53	NAIDU-ext, Prasad
v. 25	Nov 17, 2025 11:06	NAIDU-ext, Prasad

Go to Page History

Workflow history

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

Apr 22, 2026	Actor	Type	Activity	Version
Update in progress	NAIDU-ext, Prasad	Edit	updated the page at 1:43 pm
Mar 18, 2026
	WENNINGER-ext, Sascha	State	changed state to Update in progress at 5:53 pm	v32
From Nov 20, 2025 to Mar 13, 2026
Edited following Tech Review	NAIDU-ext, Prasad and PILLAY-ext, Lawrence	Edit	multiple updates from NAIDU-ext, Prasad and PILLAY-ext, Lawrence
	PILLAY-ext, Lawrence	Comment	commented 12:25 pm GARCIA-ext, Angel Luis - I have updated the source field to the customer number
		Comment	commented 12:25 pm GARCIA-ext, Angel Luis - I have updated the source field to the customer number
		Edit	updated the page at 12:24 pm
		State	changed state to Edited following Tech Review at 11:24 am	v29
Lead Approval	GARCIA-ext, Angel Luis	State	changed expiry date to '27 Nov, 2025 09:10 am' at 9:10 am
Lead Approval	GARCIA-ext, Angel Luis	State	changed state to Lead Approval at 9:10 am	v28

Workflow history

Space shortcuts

Page tree

CNV-3019 Business Partners - Credit Management (UKM000)

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

Workflow history