Activation of Data Model

[adnanmaqbool]

Dear All

I have activated the following business function in S/4 1610 system.

1. MDG_ERP_CUSTOMER_1 to MDG_ERP_CUSTOMER_5
2. MDG_ERP_CUSTOMER_HD
3. MDG_ERP_SUPPLIER to MDG_ERP_SUPPLIER_6
4. MDG_ERP_SUPPLIER_HD
5. MDG_ERP_FINANCIALS_3 to MDG_ERP_FINANCIALS_7
6. MDG_FOUNDATION to MDG_FOUNDATION_7
7. MDG_MATERIAL to MDG_MATERIAL_6

After activation above mentioned functions, I am trying to activate standard Data Model ( Chart of Accounts , Financials, Business Partner and Material ) but getting dump CL_MDG_MDF_FIELDNAME==========CP and IF_MDG_MDF_FIELDNAME~GET_FPROP.

. I am missing some step or any solution ?

Dump.

A RAISE statement in program "CL_MDG_MDF_FIELDNAME==========CP" has raised exception condition "FAILURE".

If the error occurs in a non-modfied SAP program, you might be able to find a solution in the SAP Notes system. If you have access to the SAP Notes system, check there first using the following keywords: "RAISE_EXCEPTION" "CL_MDG_MDF_FIELDNAME==========CP" bzw. CL_MDG_MDF_FIELDNAME==========CM01Q "IF_MDG_MDF_FIELDNAME~GET_FPROP" or "CL_MDG_MDF_FIELDNAME==========CP" FAILURE or "USMD_ADJUST_STAGING" "FAILURE"

[adnanmaqbool · Accepted solution]

Issue resolved by dropping an inactive table from database and activating it through SE11

[former_member720912 · Accepted solution]

Dear Adnan.

It is good to solve your problem.

How did you drop your inactive table? and what is inactive table?

[adnanmaqbool · Accepted solution]

Following response of OSS resolved the issue

• 
  After analyzing the issue, I noticed that the table ‘/SMD/MD_____000V’ has the following syntax error in SE11:
  DA 431 2 A table called /SMD/MD_____000V exists in the database
DA 300 2 E No active nametab exists for /SMD/MD_____000V
DA 432 2 E Termination due to inconsistencies
DT 066 2 E Table /SMD/MD_____000V (Statements could not be generated)

  
  The error message DA300 means that the table exists in the database (date/time created: 12.10.2016 18:52:38) but not in the data dictionary. Table ‘/SMD/MD_____000V’ has an old inconsistency and it causes DDIC activation failure (this inconsistency has been existed from 2016, you could find it in report RADPROTA, log name: MDG_MDFES410020161012213635). Unfortunately, I couldn't find the root cause how this inconsistency was occurred.

  
  >>To fix table ‘/SMD/MD_____000V’ inconsistency, there are 2 options:

  *** Please do NEVER use such a workaround unless it was explicitly advised by SAP in a note or in an incident. It could cause damage to the system which could not be recovered***

  
  Option 1: If the database table is empty or the data/records for table are not needed, you can use database means or execute the function module DB_DROP_TABLE in SE37 (you need only to specify parameter TABNAME, other parameters should remain unchanged) to delete the table on the database. once it's done, please check the consistency of the table in SE11 (it should be consistent)

  
  Option 2: If data/records for table ‘/SMD/MD_____000V’ are needed, you could follow instructions below:
  Rename the table ‘/SMD/MD_____000V’ in the database as a copy using database tools or function module DB_RENAME_TABLE in test mode (you should only fill TABNAME_NEW and TABNAME_OLD). Regenerate or activate the table. Then delete the newly created empty table on database level. Rename the table back to original table name again.

  
  As I checked, table ‘/SMD/MD_____000V’ is currently empty in S16, you could run the following statement in t-code DB02:
  select COUNT (*) from "/SMD/MD_____000V"

  
  So, you can follow option 1. Then, please try to activate the table in SE11.

[partha_kar2]

Have you tried generating the data model structures

[adnanmaqbool]

How to generate structures, any idea.

[adnanmaqbool]

I have tried to execute this report but it is also generating same dump.

[varun_jain3]

try running report USMD_ADJUST_STAGING" and see