MDS_LOAD_COCKPIT; GUID Assigned but BP not Created.

[chris_bowling]

Hello. We are using MDS_LOAD_COCKPIT to convert a Vendor Account Group to Business Partners (BP). Out of 22,228 records, the process had 42 errors where the BP was not created. For example Vendor 5015555 should have corresponding BP 5015555 created but MDS_PPO2 has these messages:

Warning Partner data processed with key PartnerGUID 0050569A06B81EEAA3F8099C047D6054

Error Business partner with GUID 0050569A06B81EEAA3F8099C047D6054 does not exist

Transaction MDS_LINKS verifies that BP 5015555 was not created and returns these messages:

For Vendor-> BP->5015555: Business Partner mapped to the Vendor 0005015555 does not exist.

For BP->Vendor->5015555: Business Partner with the number 0005015555 does not exist.

We tried using FLBPC1 to create the BP from the vendor, it comes back with this message:

Vendor 5015555 is already assigned to business partner 0050569A06B81EEAA3F8099C047D6054.

The SAP CVI Cookbook (SAP S/4HANA Cookbook, Customer/Vendor Integration 2019/Q4, page 31) refers to the above MDS_PPO2 error, but we do not have the case of the Internal Standard Grouping sharing a number range with any other Business Partner Groupings.

Has anyone else run into a similar issue? If so, were you able to resolve this and create a BP? Thank you.

[former_member337627]

Hi Chris,

I' am facing the same issue but with Customer. Did you manage to solve this issue? if yes then could you please share me the solution.

Regards,

Mrinal

[chris_bowling]

Hi Mrinal,

We never solved this issue but it only happened in our Development environment. We have a weekly copy of Production that never ran into this issue during testing (we ran the conversion at least 10 times in this system, never an issue.) Our Development client has data synced from Production using EPIUse and it takes a designated time slice of data. I assumed that had something to do with it. We went forward to Production and never ran into the issue again. Sorry I don't have better news for you.

Chris

[chris_bowling]

So we ran into a similar issue again where a Business Partner (BP) was not created when a vendor was. This was due to a "Tax number category XXX does not exist” error. Below is how we fixed the error and created a corresponding BP for a vendor. Hope it helps someone.

1. Implemented SAP note # 2923695 .
2. Execute transaction BPVENDCHECK
   1. First in test mode, a list of vendor numbers will be displayed.
   2. Then unchecked test indicator and run again.
   3. Run again in test mode to verify the list was cleared.
3. Added the missing tax number category – Add entry to table V_TFKTAXNUMTYPE via SM30 (Note this is a modification)
   1. Tax Categ.: (whatever code is giving you the error)
   2. Name: Country:
   3. Funct.Name: BUPA_TAX_NUMBER_CHECK
4. Create BP via FK02 - Change Vendor (Accounting) for existing vendor.
5. Execute transaction BP to verify the BP was created