CVI Conversion issue

[Shekhard]

Hello All,

I am working on CVI Conversion activity. I am done with configuration part through BP_CVI_IMG_CHK and also performed CVI_COCKPIT. However those customer who are having the FD32 credit management data are not reflecting under UKM000 role. Could you please provide the detailed step to replicate FD32 data in to Business partner.

Thank you

[marcoiser]

Very interesting topic! I am currently facing exactly same problem. Did you already make some progress? Your help is much appreciated! Thanks, Marco

[Divyesh_Mistry]

Hi @Shekhard ,

FD32 → UKM000 data replication does not happen automatically during CVI.
You must migrate classic credit data using programs like UKM_TRANSFER_DATA or UKM_MIGRATION_CREDIT_MASTER_DATA after activating FSCM Credit Management.
Once done, the BP UKM000 role will reflect the migrated credit limits and segments.

Section	Details / Explanation
System Context	- SAP S/4HANA or S/4HANA Conversion Project (ECC → S/4HANA).- You have completed CVI configuration and CVI_COCKPIT processing.- Business Partner (BP) is created for customers, but UKM000 role is missing / not populated with FD32 data.
Root Cause	1️⃣ Classic credit management (transaction FD32) uses Credit Control Area (KNKK table).2️⃣ In S/4HANA, Credit Management is part of SAP Credit Management (FIN-FSCM-CR) and stores data in UKMBP_CMS / UKMBP_CMS_SGM tables.3️⃣ The conversion does not automatically migrate FD32 → UKM000 unless FSCM Credit Management is active and migration steps are executed.
Key Understanding	FD32 data = Classic Credit Management (FI-AR-CR).UKM000 role = New Credit Management (FSCM).➡️ The system treats them as different architectures. Simple CVI does not transfer FD32 data into UKM tables automatically.
Objective	To migrate FD32 (classic credit data) into Business Partner UKM000 (FSCM Credit Management) role data, so that converted BPs show corresponding credit master data in BP → UKM000 tab.
High-Level Solution Flow	Classic FD32 Data (KNKK) → Migration Program (UKM_TRANSFER / UKM_MIGRATION) → BP Role UKM000 / UKMBP_CMS Tables.
Detailed Step-by-Step Solution
Step 1 – Activate FSCM Credit Management	- Ensure FIN-FSCM-CR business function is active.- Transaction: SFW5 → Activate FIN_FSCM_CCD and FIN_FSCM_CCD_INTEGRATION.- Confirm configuration via node: SPRO → Financial Supply Chain Management → Credit Management → Integration with AR/AP.
Step 2 – Check BP Role Assignment	- Verify that BP role UKM000 (Credit Management) exists and is assigned to the correct BP grouping.- Transaction: BP → Change mode → add role UKM000 if not auto-assigned.
Step 3 – Migrate FD32 Data to FSCM	- Run migration program: UKM_TRANSFER_CUSTOMIZING (to transfer Credit Control Area customizing).- Then execute program: UKM_TRANSFER_DATA (or UKM_MIGRATION_CREDIT_MASTER_DATA) to transfer customer credit master data from KNKK (FD32) → UKM tables.- You can also use transaction UKM_MIGRATION (wizard for both customizing and data).
Step 4 – Verify Mapping of Company Code & Credit Control Area	- In S/4HANA, Credit Segment = Company Code (normally).- During migration, ensure credit control area (KNA1-KKBER) correctly maps to credit segment (UKM_SGMNT).- If 1:1 mapping not set, maintain in customizing: SPRO → FSCM → Credit Management → Integration with AR/AP → Define Relationship Between Company Code and Credit Segment.
Step 5 – Execute Migration Report	Program: UKM_MIGRATION_CREDIT_MASTER_DATAParameters:• Company code• Credit control area• Customer range• Test run (first execute in simulation).➡️ This program reads data from KNKK (FD32) and updates UKMBP_CMS/UKMBP_CMS_SGM.➡️ Automatically creates BP role UKM000 if BP exists.
Step 6 – Check BP After Migration	- Transaction: BP → Open the Business Partner.- Switch to Role: UKM000 (Credit Management).- Verify Credit Segment Data tab shows migrated credit limits, risk category, currency, etc.
Step 7 – Validate via Tables / Reports	- Table UKMBP_CMS → BP header credit data.- Table UKMBP_CMS_SGM → BP segment data (limit, currency, risk class).- Compare with KNKK (classic).
Step 8 – Reconcile & Activate	- Run consistency check report: UKM_CHECK_CREDIT_ACCOUNT.- If needed, assign Credit Segment BP via UKM_BP_CMS_ASSIGN.
Step 9 – Optional Enhancements	- If special mapping logic is needed (e.g., multiple credit control areas), enhance BAdI UKM_CREDIT_ACCOUNT_ASSIGNMENT to control how migration maps credit accounts to segments.
Key Transactions	- FD32 → Classic credit master.- UKM_BP → BP Credit Management (UKM000 role).- UKM_TRANSFER_DATA / UKM_MIGRATION → Data migration.- UKM_CHECK_CREDIT_ACCOUNT → Validation.- BP → Business Partner maintenance.
Post-Migration Testing	✅ Create a sales order → system should pick credit data from BP UKM000.✅ Run report FDM_COLL_SEND_CUSTOMER if credit data should flow to collections management.
Common Issues	Issue
UKM000 role missing	Add manually or re-run UKM_MIGRATION with correct BP mapping.
Credit limit not transferred	Check credit segment mapping (Company Code ↔ Credit Control Area).
Risk class missing	Verify customizing transfer via UKM_TRANSFER_CUSTOMIZING.
Multiple Credit Control Areas in source	Handle via manual assignment or enhancement BAdI.
FD32 data not visible after migration	Ensure FIN-FSCM-CR active and UKM_BP roles generated correctly.
SAP Notes & References	- SAP Note 2691534 – Migration of Credit Management Data to UKM_BP.- SAP Note 2603674 – UKM_MIGRATION report usage.- SAP Note 2777273 – Credit Segment mapping guidance.- SAP Help: CVI Conversion with FSCM Credit Management Migration.
Expected Outcome	✅ FD32 (Classic Credit Management) data migrated into UKM tables.✅ BP role UKM000 automatically updated/created.✅ Credit limits, risk class, control area appear correctly under BP → UKM000 tab.✅ Sales and AR processes use new Credit Management logic.

If you find my response helpful, kindly accept the answer and award a Kudos. This motivates me to serve you better.
Appreciate your feedback. Used GenAI
Thanks,
Divyesh

[marcoiser]

Pls. have a look at https://me.sap.com/notes/2713963/E . Here it says:

What roles should be created as part of the synchronization direction from Customer/Vendor to BP?

If the standard configuration is followed, the expected roles after running CVI are:

• For Suppliers: FLVN00, FLVN01
• For Customers: FLCU00, FLCU01

Any additional roles needed will be created directly in SAP S/4HANA after running SUM. For example:

• For Credit Management: The role UKM000 will be created during the execution of the FI post-conversion activities.

Hope it helps!