problem saving Role in CUP

[former_member211575]

Dear Experts,

im having problems saving a role after trying to change a bussiness process and Sub-BP.

the bp and sub-bp were all created in erm and cup, sucha as functional area associated.

when i try to save it says : Action FAiled:

the log gives this message:

2012-06-18 17:38:22,325 [SAPEngine_Application_Thread[impl:3]_35] ERROR Error in Saving roles
com.virsa.ae.core.BOException: Error in saving the Role details
at com.virsa.ae.configuration.bo.RoleDetailsBO.saveRoleDetails(RoleDetailsBO.java:326)
at com.virsa.ae.configuration.actions.AdminSaveRoleAction.saveRoleDetails(AdminSaveRoleAction.java:521)
at com.virsa.ae.configuration.actions.AdminSaveRoleAction.execute(AdminSaveRoleAction.java:65)
at com.virsa.ae.commons.utils.framework.NavigationEngine.execute(NavigationEngine.java:295)
at com.virsa.ae.commons.utils.framework.servlet.AEFrameworkServlet.service(AEFrameworkServlet.java:431)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:401)
at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:266)
at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:386)
at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:364)
at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:1060)
at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:265)
at com.sap.engine.services.httpserver.server.Client.handle(Client.java:95)
at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:175)
at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
at java.security.AccessController.doPrivileged(Native Method)
at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:104)
at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:176)
Caused by: com.virsa.ae.dao.DAOException: Error in inserting into the Role details table
at com.virsa.ae.dao.sqlj.RoleDAO.updateWithReturnCount(RoleDAO.sqlj:4969)
at com.virsa.ae.dao.sqlj.RoleDAO.update(RoleDAO.sqlj:4814)
at com.virsa.ae.configuration.bo.RoleDetailsBO.saveRoleDetails(RoleDetailsBO.java:310)
... 19 more
Caused by: com.virsa.ae.dao.DAOException: Error in inserting into the Role details table
at com.virsa.ae.dao.sqlj.RoleDAO.insertRoleDetails(RoleDAO.sqlj:4538)
at com.virsa.ae.dao.sqlj.RoleDAO.updateWithReturnCount(RoleDAO.sqlj:4922)
... 21 more
Caused by: com.sap.sql.DuplicateKeyException: ORA-00001: unique constraint (SAPSR3DB.SYS_C004692) violated

at com.sap.sql.jdbc.common.CommonPreparedStatement.executeUpdate(CommonPreparedStatement.java:259)
at com.sap.sql.sqlj.runtime.profile.ref.RTStatementJDBCPrepared.executeUpdate(RTStatementJDBCPrepared.java:267)
at sqlj.runtime.ExecutionContext$StatementFrame.executeUpdate(ExecutionContext.java:1124)
at sqlj.runtime.ExecutionContext.executeUpdate(ExecutionContext.java:718)
at com.virsa.ae.dao.sqlj.RoleDAO.insertRoleDetails(RoleDAO.sqlj:4455)
... 22 more

can you please help.

TY

[Former Member · Accepted solution]

Hi,

I think this issue you are facing only with old roles.

The error that you are facing is coming due to the fact that there was a difference in table structures from the older support pack version and the later support pack.

There was a field in earlier support package field ROLEPROFNAME in table VIRSA_AE_ROLDTLS that contain the actual role name, but in the later support pack, these role names were moved to another field within the same table and replaced the contents of field ROLEPROFNAME with reference numbers.

So now when you try to edit the existing roles, it's possible that the record entry for those roles had an invalid value in the ROLEPROFNAME field and hence it throws error.

You can take help of your database team to help you in this issue.

Regards

Shaily

[former_member211575 · Accepted solution]

hi,

TY for your answer.

the problem e 50% solved....

if we delete the single role and the import them again, it is possible to chabe the bussiness process and subprocess.

however for composite roles, if we try to delete them it gives the following message:

Cannot delete because this is referenced by request.

can you help me solving this for composite roles.

tnks

Sofia

[Former Member · Accepted solution]

Hi Sofia,

The issue related to import of roles which throws error "Action failed" has been resolved in SP 19 of CUP 5.3.

For details kindly refer SAP Note 1168508

Best Regards,

Smriti

[Former Member]

Hi Sofia,

As per your logs, it's showing an 'unique constraint error' which means a primary key declared is having a duplicate value in table.

Please take help of your basis team and check with the table "VIRSA_AE_APPL_SEQ". with column "SEQ_VALUE".

Best Regards,

Akhil Chopra

[Former Member]

Hi all ,

I had this problem in SP18 patch 10.

After some checks on tables contents I found out that the table for locale dependent role details, which should be linked to Role details, had "orphaned" records (ROLEPROFNAME that did not exists anymore in mother table).

I ran this simple SQL to find out what are these records.

select * from vt_ae_roldtls_loc

where roleprofname not in (select roleprofname from virsa_ae_roldtls)

I didn't know exactly what caused the problem. I suspect of unsuccessful mass role import from backend or system delete (we had a backend removed)..

My solution was Export Initial System Data, check Roles12.xml (Role details - Mother) versus Roles13.xml  (Role details - locale dependent - Child).   Edited Roles13.xml and removed orphaned records.  Then imported Roles13.xml back with Clean and Insert.

Don't need to mention, after a full backup.

Regards,

Vaner

[Former Member]

Hi Sofia,

Please check that wether the table VIRSA_AE_APPL_SEQ is getting updated or not. If not then please update the following:

> Table: VIRSA_AE_APPL_SEQ
> Field: SEQ_NAME = CHANGE_LOG_CHG_ID
> Value: 110

**NOTE:-PLEASE TAKE A BACKUP OF THE DATABASE BEFORE UPDATING THE ABOVE FIELD.

I hope it helps.

Regards,

Yukti

[sharad_parasher]

Appears to be a Database inconsitency . You need to check with your DBA the tables that are getting updated during the action you are performing and look out for the discrepancy in one of these.You may require a change at the DB level directly to resolve the issue.

Regards

Sharad