Status	20%
Owner	Prasad Naidu
Stakeholders

Purpose

The Business Partner role UKM000 is used to manage Credit Management data within the FSCM framework. It replaces the old ECC transaction FD32, centralizing credit limits, risk categories, and credit exposure at the Business Partner level. 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 conversion scope covers BP role assignment (UKM000), credit control area replacement with credit segments, migration of credit master data and exposures, and system configuration alignment to ensure smooth credit checks in S/4HANA.

1. Business Partner Conversion
- All customers/vendors must be converted into Business Partners.
- Credit-relevant customers in ECC must have the UKM000 role assigned in S/4HANA.

2. Credit Control Area → Credit Segment Mapping
- ECC’s Credit Control Areas (CCA) are no longer used.
- These must be mapped to Credit Segments in S/4HANA.

3. Credit Master Data Migration
- Credit limits, risk categories, and other credit parameters maintained in FD32 must be transferred to the BP’s UKM000 role.
- Use report UKM_TRANSFER_CUST (or migration cockpit) to migrate existing credit data.

4. Credit Exposure Migration
- Open sales orders, deliveries, billing documents, and FI-AR open items from ECC must be migrated so that credit exposure is correctly reflected in S/4HANA.

5. Configuration & Integration
- Set up credit segments and assign them to company codes.
- Enable integration of credit checks with SD, FI-AR, and FSCM.
- Replace obsolete transactions (like FD32) with BP maintenance in UKM000.

List of source systems and approximate number of records

Source	Scope	Source Approx No. of Records	Target System	Target Approx No. of Records
PF2			S4
WP2
PI2

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

Data Cleansing

ID	Criticality	Error Message/Report Description	Rule	Output	Source System
		No legacy cleansing	Relevancy

Conversion Process

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

Data Privacy and Sensitivity

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 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 Description	Team Responsible
1	Refresh KNB1 tables via Syniti (Customer data)	Data

Selection Screen

Selection Ref Screen	Parameter Name	Selection Type	Requirement	Value 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.

DCT Rules

Field Name	Field Description	Rule

Extraction Dependencies

Item #	Step Description	Team Responsible
1	Ensure Syniti has the necessary connection and access to legacy servers	Data
2	Ensure that the necessary cleansing activities in legacy sources are complete	Data / Business
3	Ensure that create, change and deletion of master data is freeze in legacy Production system	Legacy IT

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
1	KNA1 relevancy execution in Syniti	Data
2	KNB1 relevancy execution in Syniti	Data
3	BP relevancy execution in Syniti	Data
4	Business partner FI Customer execution in Syniti	Data

Transformation Rules

Rule #	Source system	Source Table	Source Field	Source Description	Target System	Target Table	Target Field	Target Description
1	PF2/PI2/WP2	KNB1	KUNNR	Customer Account Number	S/4HANA	BP000	PARTNER	Business Partner Number
2	PF2/PI2/WP2	KNB1	BUKRS	Company Code	S/4HANA	BP001	BUKRS	Company Code
3	PF2/PI2/WP2	KNB1	AKONT	Reconciliation Account	S/4HANA	BP001	AKONT	Reconciliation Account
4	PF2/PI2/WP2	KNB1	ZTERM	Payment Terms	S/4HANA	BP001	ZTERM	Payment Terms
5	PF2/PI2/WP2	KNB1	ZWELS	Payment Methods	S/4HANA	BP001	ZWELS	Payment Methods
6	PF2/PI2/WP2	KNB1	VZSKZ	Payment Block	S/4HANA	BP001	VZSKZ	Payment Block Indicator
7	PF2/PI2/WP2	KNB1	XPORE	Individual Payment	S/4HANA	BP001	XPORE	Individual Payment Indicator
8	PF2/PI2/WP2	KNB1	ZUAWA	Sort Key	S/4HANA	BP001	ZUAWA	Sort Key
9	PF2/PI2/WP2	KNB1	DTAWS	Instruction Key	S/4HANA	BP001	DTAWS	Instruction Key

Transformation Mapping

Mapping Table Name	Description
Legacy Customer-BP Master Mapping	Legacy to S4 Business Partner customer mapping
Business Partner deDupe mapping (Global Data)	dedupe Golden-child (Global) mapping
Company Code Mapping	Legacy to S4 Company Code Mapping
Payment Terms Mapping	Legacy to S4 Payment Terms Mapping
Payment Method Mapping	Payment Method Mapping
Tax Category Mapping	Legacy to S4 Tax Category Mapping
Reconciliation Account Mapping	Legacy to S4 Reconciliation Account Mapping
Sort Key Mapping	Legacy to S4 Sort Key Mapping
Planning Group Mapping	Legacy to S4 Planning Group Mapping
deDupe customer Company Code Nominations Mapping	Golden-Child Company Code data Mapping

Transformation Dependencies

List the steps that need to occur before transformation can commence

Item #	Step Description	Team Responsible
1	Extract PF2/PI2/WP2 source tables – KNB1	Data
2	Ensure that Business Partner – General is loaded	Data
2	Ensure all Customer master data collection templates, deduplication and cleansing completeness and no errors	Data
3	Ensure that all required Configurations are in S/4HANA	Data

Pre-Load Validation

Project Team

Completeness

Task	Action
Verify count	Verify that the record count in the pre-load file is the same as the record count based on the approved DCT records

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 and DCT contents
Mapping Error Reports	Verify that all necessary error reports have been validated, and that errors have been addressed.

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 and DCT contents
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	Incoterms Configuration
5	Plant Configuration
6	Confirmation Control Configuration
7	Payment Terms Configuration
8	Payment Method Configuration
9	Reconciliation Account Configuration
10	Withholding Tax Types Configuration

Conversion Objects

Object #	Preceding Object Conversion Approach
	Intercompany Business Partners
	Business Partner - Contact
	Business Partner – General
	GL Accounts

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 or if it’s mapped in DCT.

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
Verify full Count of Customers	Verify that the record count in the post-load file is the same as the record count based on the relevancy (including deduplication) results

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 and DCT contents
Error Reports	Verify that all necessary error reports have been validated, and that errors have been addressed.

Business

Completeness

Task	Action
Verify full Count of Customers	Verify that the record count in the post-load file is the same as the record count based on the relevancy (including deduplication) results
Validate Loaded Data	Validate, as per the loads files signed-off, that all records were created

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 and DCT contents
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. 5)	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