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 Customer Master Data from

legacy source systems into S/4HANA Business Partner

Collections Management (

UDM000) master data, in line with the defined Master Data Design Standard.

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

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

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. 

1. Accounting document (Select MAX(BSAD/BSID-CPUDT) where BSAD/BSID-KUNNR =KNA1-KUNNR and BSAD/BSID-BUKRS = (Company code in scope) )
2. Sales Document (Select MAX(VBAK-ERDAT) WHERE VBAK-VBELN=VBPA-VBELN AND VBPA-KUNNR = KNA1-KUNNR)
3. Delivery Document (Select MAX(LIKP-ERDAT) WHERE LIKP-VBELN=VBPA-VBELN AND VBPA-KUNNR = KNA1-KUNNR)
4. Billing   (Select MAX(VBRK-ERDAT) WHERE VBRK-VBELN=VBPA-VBELN AND VBPA-KUNNR = KNA1-KUNNR)

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

1. Accounting document (Select MAX(BSAD/BSID-CPUDT) where BSAD/BSID-KUNNR =KNA1-KUNNR and BSAD/BSID-BUKRS = (Company code in scope) )
2. Sales Document (Select MAX(VBAK-ERDAT) WHERE VBAK-VBELN=VBPA-VBELN AND VBPA-KUNNR = KNA1-KUNNR)
3. Delivery Document (Select MAX(LIKP-ERDAT) WHERE LIKP-VBELN=VBPA-VBELN AND VBPA-KUNNR = KNA1-KUNNR)
4. Billing   (Select MAX(VBRK-ERDAT) WHERE VBRK-VBELN=VBPA-VBELN AND VBPA-KUNNR = KNA1-KUNNR)

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

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

• This will be parked for now

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

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

List of source systems and approximate number of records:

Additional Information

Multi-language Requirement

NA

Document Management

NA

Legal Requirement

NA

Special Requirements

NA

Target Design

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

Data Cleansing

NA

Conversion Process

NA

Data Privacy and Sensitivity

Extraction

NA

Extraction Run Sheet

NA

Selection Screen

Data Collection Template (DCT)

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

Extraction Dependencies

NA

Transformation

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

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:

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

NA

Transformation Rules

Transformation Mapping

Transformation Dependencies

The data from legacy system excludes:

1. One time customer (Account group is Z004 or ZCPD)

One time customer (Account group is Z004)

List of source systems and approximate number of records 

Additional Information

Multi-language Requirement

Document Management

Legal Requirement

Special Requirements

Target Design

The technical design of the target for this conversion approach.

Data Cleansing

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:

1. 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.
2. 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

Selection Screen

Data Collection Template (DCT)

DCT Rules

Extraction Dependencies

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:

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

Transformation Rules

Transformation Mapping

Transformation Dependencies

Pre-Load Validation

Project Team

Completeness

Accuracy

Business

Completeness

Accuracy

Load

The load process includes:

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

Load Phase and Dependencies

Configuration

Conversion Objects

Error Handling

Post-Load Validation

Project Team

Completeness

Accuracy

Business

Completeness

Accuracy

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.

See also

Change log

Workflow history