cancel
Showing results for 
Search instead for 
Did you mean: 

ME 6.0 Data Collection Maintenance Exception

former_member323997
Participant
0 Kudos

Hi,

I have a problem about the Data Collection maintenance, as long as I tried to maintain the Parameter Detail data, first time it is able to save, and then any change on this DC group and click Save button returns the part of error message as bellow:

javax.ejb.EJBException: ASJ.ejb.005044 (Failed in component: sap.com/me~ear) Exception raised from invocation of public com.sap.me.system.base.ApplicationVO com.sap.me.datacollection.DCMaintApplicationBean.update(com.sap.me.system.base.ApplicationVO) throws com.sap.me.frame.BasicBOBeanException method on bean instance com.sap.me.datacollection.DCMaintApplicationBean@7cbf6076 for bean sap.com/me~ear*xml|me.datacollection.ejb-6.0.4.0.jar*xml|DCMaintApplication in application sap.com/me~ear.; nested exception is: javax.ejb.TransactionRolledbackLocalException: ASJ.ejb.005044 (Failed in component: sap.com/me~ear) Exception raised from invocation of public com.sap.me.frame.Data com.sap.me.frame.BasicBOBean.dbUpdateAndRead(com.sap.me.frame.Data) throws com.sap.me.frame.BasicBOBeanException method on bean instance com.sap.me.datacollection.DcGroupBOBean@6d07567d for bean sap.com/me~ear*xml|me.datacollection.ejb-6.0.4.0.jar*xml|DcGroupBO in application sap.com/me~ear.; nested exception is: javax.ejb.EJBException: nested exception is: java.sql.SQLSyntaxErrorException: ORA-00904: "ERP_IS_QM_CRITICAL": invalid identifier

I looked into the database DC_PARAMETRIC table, I could not find there is a field named ERP_IS_QM_CRITICAL, but it seems the Save button from the maintenance page is generating the values for this field name and causing this issue.

Our SAP ME core version is:

Vendor:SAP AG
Customer:Base
Version:6.0.4.0
Counter:147
Build ID:149670

I tested same in another version ME Base 6.0.3.8 Counter 10, it works probably. Can anybody advice what happens to our new version?

Thanks a lot and best regards,

Leon

Accepted Solutions (1)

Accepted Solutions (1)

0 Kudos

Hi Leon,

This field is added by wip_alter_tables_6.0.3_6.0.4.sql. Looks like a missed upgrade step problem. Do not forget to run upgrade scripts for ODS database too.

Regards,

Alex.

former_member323997
Participant
0 Kudos

Thanks Alex. It works now after running those sql. Another question, I've seen there is another sql file WIP_migrate_6.0.3_to_6.0.4.sql, shall I run it as well?

Best regards,

Leon

0 Kudos

Hi Leon,

- AL_alter_tables_6.0.3_6.0.4.sql

- ARC_alter_tables_6.0.3_6.0.4.sql

- WIP_alter_tables_6.0.3_6.0.4.sql

mentioned in the guide enough to run. Scripts

ODS_migrate_6.0.3_to_6.0.4.sql and

WIP_migrate_6.0.3_to_6.0.4.sql

do not provide any additional SQL statements.

Regards,

Alex.

Answers (0)