Cannot Activate Data Model BP in MDG 6.1

[Former Member]

Dear MDG guru,

I want to use SAP MDG-C in my system, and i activate the require business function (sfw5)

MDG_FOUNDATION, MDG_FOUNDATION_2, MDG_FOUNDATION_3, MDG_ERP_CUSTOMER_1, MDG_ERP_CUSTOMER_2

when i want to activate the data model BP in MDGIMG i got an error like below :

Data model BP, entity type AKONT, relat. CUS_AKONT:  Entity type AKONT does not exist

Data model BP, entity type BUSAB, relat. CDD_BUSAB:  Entity type BUSAB does not exist

Data model BP, entity type BUSAB, relat. CUS_BUSAB:  Entity type BUSAB does not exist

Data model BP, entity type COMPANY, relat. CESSION:  Entity type COMPANY does not exist

Data model BP, entity type COMPANY, relat. COMPANY:  Entity type COMPANY does not exist

Data model BP, entity type COMPANY, relat. LOCKB_CUS:  Entity type COMPANY does not exist

Data model BP, entity type HBKID, relat. CUS_HBKID:  Entity type HBKID does not exist

Data model BP, entity type KTOPL, relat. CUS_KTOPL:  Entity type KTOPL does not exist

Data model BP, entity type MABER, relat. CDD_MABER:  Entity type MABER does not exist

Data model BP, entity type MEGRU, relat. CSD_MEGRU:  Entity type MEGRU does not exist

Data model BP, entity type MEINS, relat. CSD_MEINS:  Entity type MEINS does not exist

Data model BP, entity type TOGRU, relat. CUS_TOGRU:  Entity type TOGRU does not exist

Data model BP, entity type WITHT, relat. CWT_WITHT:  Entity type WITHT does not exist

Data model BP, entity type WT_WITHCD, relat. CWT_WITHC:  Entity type WT_WITHCD does not exist

Data model BP: Define a "qualifying" relationship for entity type BP_CUSDUN

Data model BP: Define a "qualifying" relationship for entity type BP_CUSWHT

Data model BP: Define a "qualifying" relationship for entity type BP_CUS_CC

Data model BP, ent.type ADDRESS, attr. TYPE, data elem. AD_ADRTYPE: No change documents

Data model BP, ent.type AD_EMAIL, attr. E_SEARCH, data elem. AD_SMTPAD2: No change documents

Data model BP, ent.type AD_FAX, attr. F_NR_CALL, data elem. AD_FAXNRCL: No change documents

Data model BP, ent.type AD_FAX, attr. F_NR_LONG, data elem. AD_FXNRLNG: No change documents

Data model BP, ent.type AD_NAME_O, attr. MC_NAME1, data elem. AD_MC_NAME: No change documents

Data model BP, ent.type AD_NAME_O, attr. NAME_TEXT, data elem. AD_NAMETXT: No change documents

Data model BP, ent.type AD_NAME_P, attr. NAMETXT_P, data elem. AD_NAMTEXT: No change documents

Data model BP, ent.type AD_POSTAL, attr. FLAGGROUP, data elem. AD_FLGGP: No change documents

Data model BP, ent.type AD_POSTAL, attr. MC_CITY1, data elem. AD_MC_CITY: No change documents

Data model BP, ent.type AD_POSTAL, attr. MC_STREET, data elem. AD_MC_STRT: No change documents

Data model BP, ent.type AD_POSTAL, attr. PERS_ADDR, data elem. AD_PRSADDR: No change documents

Data model BP, ent.type AD_TEL, attr. T_NR_CALL, data elem. AD_TELNRCL: No change documents

Data model BP, ent.type AD_TEL, attr. T_NR_LONG, data elem. AD_TELNRLG: No change documents

Data model BP, ent.type AD_URL, attr. U_ADDRESS, data elem. AD_URISCR: No change documents

Data model BP, ent.type BP_ADDR, attr. ADDR_GUID, data elem. ADDR_UUID_CHAR: No change documents

Data model BP, ent.type BP_CENTRL, attr. MCNAME1, data elem. BU_MCNAME1: No change documents

Data model BP, ent.type BP_CENTRL, attr. MCNAME2, data elem. BU_MCNAME2: No change documents

Data model BP, ent.type BP_CENTRL, attr. NAME_GRP1, data elem. BU_GR_NAME1: No change documents

Data model BP, ent.type BP_CENTRL, attr. NAME_GRP2, data elem. BU_GR_NAME2: No change documents

Data model BP, ent.type BP_CENTRL, attr. NAME_ORG1, data elem. BU_ORG_NAME1: No change documents

Data model BP, ent.type BP_CENTRL, attr. NAME_ORG2, data elem. BU_ORG_NAME2: No change documents

Data model BP, ent.type BP_CENTRL, attr. NAME_ORG3, data elem. BU_ORG_NAME3: No change documents

Data model BP, ent.type BP_CENTRL, attr. NAME_ORG4, data elem. BU_ORG_NAME4: No change documents

Data model BP, ent.type BP_CUSFCN, attr. CPF_REFLX, data elem. MDG_BP_PFNC_REFLEXIVE: No change documents

Data model BP, ent.type BP_HEADER, attr. BP_GUID, data elem. CHAR32: No change documents

Data model BP, ent.type BP_MLT_AS, attr. STANDARD, data elem. FLAG: No change documents

Data model BP, ent.type BP_ROLE, attr. ROL_VFROM, data elem. BU_VALID_FROM_DATS: No change documents

Data model BP, ent.type BP_ROLE, attr. ROL_VTO, data elem. BU_VALID_TO_DATS: No change documents

Data model BP, ent.type WP_EMAIL, attr. E_SEARCH, data elem. AD_SMTPAD2: No change documents

Data model BP, ent.type WP_FAX, attr. F_NR_CALL, data elem. AD_FAXNRCL: No change documents

Data model BP, ent.type WP_FAX, attr. F_NR_LONG, data elem. AD_FXNRLNG: No change documents

Data model BP, ent.type WP_TEL, attr. T_NR_CALL, data elem. AD_TELNRCL: No change documents

Data model BP, ent.type WP_TEL, attr. T_NR_LONG, data elem. AD_TELNRLG: No change documents

Data model BP, ent.type WP_URL, attr. U_ADDRESS, data elem. AD_URISCR: No change documents

Data model BP: Business object type 147 is used in data model CP

Can someone tell me whats wrong with my data model? are threre something that i have to do before? or some pre requisites that i miss?

[former_member1359658]

I guess you are using standard package to activate the model. Please try using custom package and it should work.

[Former Member]

Hi Aditya,

I am also facing this same issue...

We are have ERP 6 and MDG 6.1 both are installed in the same system.

We want to implement MDG-C scenario and for which we have activated the required software components attached is a screenshot for reference :

1. I want to know whether is it mandatory to install MDG-C as Hub System before you install

MDG-C  on Client ERP because we don't have MDG as Hub System in our case and we are directly activating the BP model in client system.

2. Is because of this we are unable to activate BP model?

Please help as I am new to MDG and have less knowledge in this.

[former_member206605]

Hi

1. No its not required to activate hub related service. Only activate client services.

2. Please check whether you have activated supplier related business functions as well.

If still you can't activate BP data model then you have to activate few business sets in MDG. I will share the list later. First try and activate supplier business function.

Kiran

[Former Member]

Hi Kiran,

Thank you for your quick reply... I have activated services related to supplier as well but still not able to activate BP model and while I try activating it I am getting following errror :

Please help me with this

Regards,

PB

[former_member206605]

Hi

Try activating below sets and let me know if it works.

use the transaction SFW_BROWSER and then open any of the MDG

Business functions and then open the switches and then switch BC sets

then double click to open the new screen here you give the BC set

names below and activate them in the same order.

CA-MDG-APP-BP_DE_VC_USMD004_C_02

CA-MDG-APP-BP_DE_VC_USMD004_C_03

CA-MDG-APP-BP_VC_USMD004_C_04

CA-MDG-APP-CUS_VC_USMD004_C_01

CA-MDG-APP-CUS_VC_USMD004_C_02

CA-MDG-APP-SUP_VC_USMD004_C_01

CA-MDG-APP-SUP_VC_USMD004_C_02

CA-MDG-APP-SUP_VC_USMD004_C_03

[Former Member]

Hi Kiran,

I have checked all the above mentioned sets but were unable to found CA-MDG-APP-BP_VC_USMD004_C_04 .

All the other sets are already in active mode.

Regards,

PB

[former_member247064]

Hi SCN User,

See if the below SAP Note helps you in overcoming the error:

2058868 - Error message USMD1 079 when checking the model definition

Best Regards

Uday

[Former Member]

Hi Uday,

Thank you for your response.

I went through the note and it says we need to upgrade Support package.

For applying the correction instruction mentioned in the note our current EA-PS component level is not matching with the required component.

Our current system level :

EA-PS: 600 : 0026 : SAPKGPPD26

and

suggested EA-PS: 600 : 0023 : SAPKGPPD23

If we still want to continue with the correction instruction does this EA-PS component would affect anything?

Please suggest.

Regards,

PB

[former_member247064]

Hi PB,

From what you said seems like you are already on a higher patch level for the EA-PS component (EA-PS: 600 : 0026 : SAPKGPPD26).

So I believe it should be ok for you to continue with the correction instruction.

Regards

Uday