Status

Percentage Progress | Vectors (Formerly: SP Percentage progress bar)

backgroundColor	0052CC
percentage	20100

Owner

Prasad Naidu

Stakeholders

KUMAR-ext, Kamal GARCIA-ext, Angel Luis

Purpose

The purpose of this document is to define the conversion approach to create Business Partners - FI Customer Collection Management (FLCU00) in S/4 HANA.UDM00)

Business Partner - FI Customer Role captures the Customer’s FI data attributes such as Reconciliation Account, Tax Code, etc. at the Company Code level.

Conversion Scope

The conversion scope of this document covers the approach for converting active from Legacy Source Systems Customer Master Data from legacy source systems into S/4HANA following the Business Partner Collections Management (UDM000) master data, in line with the defined Master Data Design Standard.

The data from legacy system includes:

All Customer types

The data from legacy system excludes:

Blocked / marked for deletion

Customer relevancy has already been determined through CNV3007, and once the customers in scope are finalized and extracted, the Collections Management fields for those customers will be reviewed in the legacy system. The necessary transformation rules will then be applied according to the defined source-to-target mappings.

Currently, Collections Management is handled through a third-party system (PCM).

As part of the S/4HANA migration, two options have been identified. This conversion specification approval by Syniti team is valid only if Option 2 is used.

Option 1: Automated Derivation:

This will be achieved through the implementation of BADI UDM_CHNG_SGMT_DATA_C, which is triggered by program UDM_CHANGE_SEGMENT (transaction code UDM_BP_GRP).
Step 1:
- Transaction code - UDM_BP_PROF
- This mass update program can be used for the first 2 steps in separate runs:
  - Assign the Collection Management role
  - Assign Collection Profile
  - Image Added
Step 2:
- Transaction Code - UDM_BP_GRP
- Can be used for the last 2 steps:
  - Assign Collection Group
  - Assign Collection Specialist
  - Image Added

Option 2: Static Load via Data Collection Template (DCT):

The required Business Partner (BP) role for Collections Management must first exist in the S/4HANA system, after which the existing Business Partner (customer) will be extended with the Collections Management role.

Step 1:
- Transaction code - UDM_BP_PROF
- This mass update program can be used for the first 2 steps in separate runs:
  - Assign the Collection Management role
  - Assign Collection Profile
  - Image Added

Step 2:
- The required Collections Management data will be collected using a Data Collection Template (DCT) and subsequently loaded into S/4HANA

The preferred option is Option 1: Automated Derivation, where all Collections Management migration elements are automated and logic is implemented to automate the assignment of the :

Collection Management Role
Collection Profile
Collection Segment
Collection Group
Collection Specialist

If full automation is not feasible for any reason, the alternative option is Option 2: Static Load via Data Collection Template (DCT).

Inactive customers without transactions within 2 years

List of source systems and approximate number of records:

Source	Scope	Source Approx. No. of

Records

records	Target System	Target Approx

. No. of

Records

records
PF2

/PI2/WP2

Extract from KNA1,KNB1 and as determined as active based on the relevancy criteria.

	Customer Master Data General Information	55371	S4	4200
WP2	Customer Master Data General Information	36983	S4	24000

S4

Additional Information

Multi-language Requirement

NA

Document Management

NA

Legal Requirement

NA

Special Requirements

NA

Target Design

The technical design of the target for this conversion approach.Below is the target design relevant to Option 2: Static Load via Data Collection Template (DCT)

Table

Field

field	Data Element	Field Description	Data Type	Length	Requirement

Data Cleansing

UDMBPSEGMENTS

ID

PARTNER

CriticalityError Message/Report DescriptionRuleOutputSource SystemNo legacy cleansingRelevancy

Conversion Process

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

Image Removed

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

BU_PARTNER	Business Partner	CHAR	10	System generates the value.
UDMBPSEGMENTS	COLL_SEGMENT	COLL_SEGMENT	Collection Segment	CHAR	10	System generates the value.
UDMBPSEGMENTS	COLL_GROUP	COLL_GROUP	Collection Group	CHAR	10	System generates the value.
UDMBPSEGMENTS	COLL_SPECIALIST	COLL_SPECIALIST	Collection Specialist	CHAR	12	System generates the value.
UDMBPSEGMENTS	VALID_FROM	VALID_FROM	Valid From	DATS	8	System generates the value.
UDMBPSEGMENTS	VALID_TO	VALID_TO	Valid to	DATS	8	Conditional
UDMBPSEGMENTS	LAST_CONTACT	LAST_CONTACT	Main Contact Person	CHAR	10	System generates the value.
BUT100	RLTYP	BU_PARTNERROLE	BP Role	CHAR	6	Mandatory

Data Cleansing

NA

Conversion Process

NA

Data Privacy and Sensitivity

NA

Extraction

NA

Extraction Run Sheet

NA

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 Responsible1Refresh KNB1 tables via Syniti (Customer data)Data

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

Below is the DCT is relevant to Option 2: Static Load via Data Collection Template (DCT)

Field

Field Name

	Field Description	Rule

Extraction Dependencies

Item #Step DescriptionTeam Responsible1Ensure Syniti has the necessary connection and access to legacy serversData2Ensure that the necessary cleansing activities in legacy sources are completeData / Business3Ensure that create, change and deletion of master data is freeze in legacy Production systemLegacy IT

UDMBPPROFILE - PARTNER	Business Partner	Map from source to target using Business Partner mapping table.
UDMBPPROFILE - COLL_PROFILE	Collection Profile	One collection profile and will be provided by functional team
UDMBPSEGMENTS- COLL_SEGMENT	Collection Segment	This will be provided by functional team
UDMBPSEGMENTS-COLL_GROUP	Collection Group	This will be provided by functional team
UDMBPSEGMENTS-COLL_SPECIALIST	Collection Specialist	Details in attached spreadsheet

Extraction Dependencies

NA

Transformation

Below is the transformation is relevant to Option 2: Static Load via Data Collection Template (DCT)

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 ADMM 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 Syniti ADMM
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 Responsible1KNA1 relevancy execution in SynitiData2KNB1 relevancy execution in SynitiData3BP relevancy execution in SynitiData4Business partner FI Customer execution in SynitiData

NA

Transformation Rules

PF2PI2WP2Customer Account NumberBP000 NumberPF2PI2/WP2BP001Payment MethodsBP001Individual Payment8PI2/Instruction Key

Rule #	Source system	Source Table	Source Field	Source Description	Target System	Target Table	Target Field	Target Description	Transformation Logic
1	DCT
N/
A	N/
KNB1	KUNNR
A	N/A	S/4HANA
UDMBPSEGMENTS	PARTNER	Business Partner	Map from source to target using Business Partner
mapping table.
2	DCT
N/
KNB1	BUKRS	Company Code	S/4HANA	BP001	BUKRS	Company Code	3	PF2/PI2/WP2	KNB1	AKONT	Reconciliation Account
A	N/A	N/A
S/4HANA
UDMBPSEGMENTS
AKONT	Reconciliation Account
4	PF2/PI2/WP2	KNB1	ZTERM	Payment Terms	S/4HANA	BP001	ZTERM	Payment Terms
5	PF2/PI2/WP2	KNB1	ZWELS
COLL_SEGMENT	Collection Segment	Copy from DCT
3	DCT	N/A	N/A	N/A	S/4HANA
UDMBPSEGMENTS
ZWELS	Payment Methods
6	PF2/PI2/WP2	KNB1	VZSKZ	Payment Block	S/4HANA	BP001	VZSKZ	Payment Block Indicator
7	PF2/PI2/WP2	KNB1	XPORE
COLL_GROUP	Collection Group	Copy from DCT
4	DCT	N/A	N/A	N/A	S/4HANA	UDMBPSEGMENTS
BP001	XPORE	Individual Payment Indicator
COLL_SPECIALIST	Collection Specialist	Copy from DCT
5	PF2/
WP2
KNB1	ZUAWA	Sort Key	S/4HANA	BP001	ZUAWA	Sort Key	9	PF2/PI2/WP2	KNB1	DTAWS	Instruction Key	S/4HANA	BP001	DTAWS
N/A	N/A	N/A	S4HANA	BUT100	RLTYP	BP Role	Default to UDM000

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
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	3	Ensure that all required Configurations are in S/4HANA	Data

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

A custom program will be built to load the Collection Profile, Collection Group, and Collection Agent in one go through Syniti ADMM.

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
4Incoterms Configuration	BP Grouping
5Plant Configuration	Customer Account Group
6	Confirmation Control Configuration
7	Payment Terms Configuration
8	Payment Method Configuration
9	Reconciliation Account Configuration
10	Withholding Tax Types Configuration
BP Number Range

Conversion Objects

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

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.

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

Verify full

Perform Data 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 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 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
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.	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 contentsrules
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

Change History

limit	10

Workflow history

Workflow Report

parent	@self
hideheader	true
type	approvals

Mar 27, 2026	Actor	Type	Activity	Version
Approved	GARCIA-ext, Angel Luis	State	changed state to Approved at 9:24 am	v38
Revision under Review	GARCIA-ext, Angel Luis	State	gave Minor change approval at 9:24 am
Revision under Review	GARCIA-ext, Angel Luis	State	changed state to Revision under Review at 9:24 am	v38
Mar 24, 2026
Revision in Progress	NAIDU-ext, Prasad	Edit	updated the page at 5:32 pm
Mar 18, 2026
	WENNINGER-ext, Sascha	State	changed state to Revision in Progress at 5:49 pm	v37
Mar 13, 2026
Edited following Approval	PILLAY-ext, Lawrence	Comment	commented 7:45 pm GARCIA-ext, Angel Luisand KUMAR-ext, Kamal - please see the changes made to the conversion scope section relating to 2 options for migration and the preferred options. The DCT option is a fallback option.

Workflow history

Space shortcuts

Page tree

Page History

Versions Compared

Old Version 2

New Version Current

Key

Purpose

Conversion Scope

Additional Information

Multi-language Requirement

Document Management

Legal Requirement

Special Requirements

Target Design

Conversion Process

Data Privacy and Sensitivity

Extraction

Data Cleansing

Conversion Process

Data Privacy and Sensitivity

Extraction

Extraction Run Sheet

Extraction Run Sheet

Data Collection Template (DCT)

Extraction Dependencies

Extraction Dependencies

Transformation

Transformation Run Sheet

Transformation Mapping

Transformation Dependencies

Pre-Load Validation

Project Team

Completeness

Accuracy

Business

Completeness

Accuracy

Load

Configuration

Conversion Objects

Error Handling

Post-Load Validation

Project Team

Completeness

Accuracy

Business

Completeness

Accuracy

Key Assumptions

See also

Change log

Workflow history