FICO S/4HANA Conversion Part 1: Customer-Vendor Integration and the Business Partner

📌 KEY POINTS
✅ In S/4HANA, the business partner is the single entry point for customers and vendors.
✅ Before conversion, all customers and vendors must be synchronised to business partners through CVI.
✅ Data quality problems (addresses, tax numbers, bank data, duplicates) block synchronisation.
✅ Number assignment and BP grouping decisions are hard to change later.
⚠️ Starting CVI cleanup late is one of the most common causes of conversion delays.

━━━━━━━━━━━━━━━━━━━━
▶ WHERE WE ARE
This series covers finance in brownfield conversions. Part 1 covers the first and often longest task.

━━━━━━━━━━━━━━━━━━━━
▶ 1. WHY BUSINESS PARTNER
S/4HANA uses the business partner as the master record for customers, vendors and other roles. Customer and vendor data still exist as roles of the BP, but they are maintained through BP. Systems must therefore create a BP for every customer and vendor before or during conversion.

━━━━━━━━━━━━━━━━━━━━
▶ 2. HOW CVI WORKS
Customer-vendor integration synchronises customers and vendors with business partners using mappings for account groups to BP groupings, roles and number ranges. Synchronisation runs as mass processing, and errors are logged per record. After conversion, BP maintenance creates customer and vendor data automatically.

━━━━━━━━━━━━━━━━━━━━
▶ 3. DATA ERRORS
Typical blockers are missing or invalid postal codes, tax numbers in the wrong format, inconsistent bank data, missing mandatory fields under BP rules, and duplicates. Each must be fixed in the source data, which requires business owners to decide on merges and archiving of old records.

━━━━━━━━━━━━━━━━━━━━
▶ 4. KEY DECISIONS
Should BP numbers equal customer and vendor numbers? How are customers that are also vendors handled — one BP with both roles? Which records are archived instead of converted? These decisions affect reporting and interfaces, so finance, sales and procurement must agree early.

━━━━━━━━━━━━━━━━━━━━
▶ 5. OWNERSHIP
Finance often leads because customers and vendors carry receivables, payables and tax data. A cleanup plan with owners, weekly error counts and deadlines keeps CVI from becoming the critical path of the conversion.

━━━━━━━━━━━━━━━━━━━━
▶ STEP BY STEP

1. Count customers and vendors and identify inactive ones to archive.
2. Run a CVI synchronisation check in a sandbox and categorise errors.
3. Decide number assignment and BP grouping with stakeholders.
4. Create a weekly cleanup tracker with owners.

✅ CHECKPOINT: every active customer and vendor synchronises to a business partner without errors.

A conversion project discovered three months before cutover that 18% of vendors failed synchronisation due to invalid tax numbers and missing postal codes, many for vendors unused for years. Archiving inactive vendors and a focused cleanup sprint resolved it, but the project lost six weeks.

• Starting CVI cleanup late.
• Converting inactive records instead of archiving.
• Number decisions made by IT alone.
• Ignoring customers that are also vendors.

• Early synchronisation tests and error categories.
• Archive inactive partners.
• Joint finance-sales-procurement decisions.
• Weekly tracking with owners.

Interviewers ask what customer-vendor integration is, why the business partner is mandatory in S/4HANA, and how you run the data cleanup in a conversion.