Loading a Business Partner (Customer) with IDOC DEBMAS06

[former_member298052]

SAP delivers the following explanation

"With IDOCs DEBMAS and CREMAS you can replicate customer and supplier master data. In SAP S/4HANA, when IDOCs are processed, Business Partner (BP) is being created first, then CVI (Customer/Supplier Integration) is triggered which leads to the creation of customer and supplier master data."

I posted the DEBMAS06 IDOC using Data Services while transmitting only KNA1 data. As desired, the system automatically creates a customer- and business partner number and assignes several roles to the bp, i.e. it fills the BUT000 and BUT100 tables and not only the KNA1.

The DEBMAS06 Idoc only includes Customer segments. So how is it possible to influence how the BUT tables are populated?

Looking forward to your replies!

Thanks

Andrzej

[paul_gendreau]

This is part of your Business Partner Master Data design.

Because it's possible to configure CVI in both directions, it's possible in some circumstances to integrate from ECC 6.0 to S/4HANA using standard IDocs and ALE.

There are many constrains, of course. Not the least of which include your design of BP Groupings and alignment with Customer and Vendor Account Groups, and number ranges across the board.

What's more, I've found CVI to be quite robust in the direction of BP to Customer and BP to Vendor, but no so mature in the opposite direction.

This is manifested by the number of relevant SAP Notes (as of S/4HANA 1809). Examples include ...

• SAP Note 2606809 - DEBMAS/CREMAS : BP existing role validity changed during idoc processing
• SAP Note 2607014 - DEBMAS/CREMAS : Coding improvements and CVI contact person issue changes
• SAP Note 2623693 - CREMAS : IDOC code refactoring
• SAP Note 2624196 - DEBMAS : Code refactoring (DEBMAS idoc processing)
• SAP Note 2643518 - Required field check also takes place for unchanged customer and vendor datasets in transaction BP
• SAP Note 2722848 - Error with the determination of the business partner grouping; assignment to business partner role is deleted
• SAP Note 2735050 - Business Partner creation via DEBMAS/CREMAS fails with error R11 555
• SAP Note 2743767 - CVI_VAL: Tax number is a required entry field
• SAP Note 2748536 - DEBMAS/CREMAS: Filter BP roles based on customer/supplier account group
• SAP Note 2751067 - CVI_VAL: "Language Key: Is a required entry field" when running migration of customer/supplier in test mode
• SAP Note 2753226 - CVI_VAL: Tax Juris.: Is a required entry field
• SAP Note 2801181 - DEBMAS CREMAS: create master data with partner function fails with 'Invalid value (foreign key check failed)' error

Be aware of Legal Entity Checks:

• SAP Note 2617001 - DETERMINE_BP Method in DEBMAS/CREMAS_IDOC_EXTENSION BADI for Legal Entity Checks
• SAP Note 2617002 - Legal Entity Check Implementation in DEBMAS/CREMAS Idocs

And beware of constraints:

• IDOCs integration in S/4 for creation of Customer/Supplier with same number as BP (Customizing configured as BP Internal numbering and Customer/Supplier External numbering with same number) will not be supported.
• Creating a BP per Customer and a BP per Vendor is the simple case. Merging related Customer and Vendor into a single BP is more complex and constrained (e.g. SAP Note 2617002 - Legal Entity Check).

Here are the key configuration points for this direction:

SPRO > Cross-Application Components > Master Data Synchronization > Customer/Vendor Integration > Business Partner Settings > Settings for Customer Integration

•> Field Assignment for Customer Integration > Assign Keys > Define Number Assignment for Direction BP to Customer •> Define BP Role for Direction Customer to BP

SPRO > Cross-Application Components > Master Data Synchronization > Customer/Vendor Integration > Business Partner Settings > Settings for Vendor Integration

•> Field Assignment for Vendor Integration > Assign Keys > Define Number Assignment for Direction Vendor to BP•> Define BP Role for Direction Vendor to BP

Of course, again, this is predicated not only on this configuration, but on your overall Business Partner Master Data design.