cancel
Showing results for 
Search instead for 
Did you mean: 

ECM: JSP Fails With Multiple Users

Former Member
0 Kudos

Hi,

We just implemented ECM on our EP. We have a JSP for Compensation Planning. The JSP works just fine when there is only one user using the application. However, when more than one user enters the planning screen, it throws an exception error message.

An error occurred: com.sap.pct.hcm.ecm.ApplicationException

Our Basis team had checked out Thread values, but everything appears to be okay.

Any input or advise would be greatly appreciated.

Thanks,

Calvin

Accepted Solutions (0)

Answers (2)

Answers (2)

Former Member
0 Kudos

How did you get the par files? Was there an OSS note?

Former Member
0 Kudos

SAP emailed them to us directly from Palo Alto. Send an email to chewitt@rdg.boehringer-ingelheim.com and I will send you the zip file.

Former Member
0 Kudos

Hi Calvin and all who read this.

SAP has finally implemented an OSS note 923662 to help with this problem. I say only help because we had to massively tune our code to take care of the situation further.

The ECM planning sheet custom columns/function modules were not caching values, so the run-time was longer than the iView expected. Therefore, when people go impatient and clicked multiple times on links in the planning page, we still could recreate the java error. In reality, the iView should not allow multiple clicks.

Anyhow, we used STATICS in the function modules to cache the column values so that subsequent reads would not have to re-evaluate the entire data again. This helped tremendously. Although we could still reproduce the java error if we clicked like madmen on the links, this is hopefully not the behaviour of the users in production.

Former Member
0 Kudos

Hi,

We are getting the same problem. Any help would be appreciated. This message happens sporadically.

Former Member
0 Kudos

SAP sent us four of the latest PAR files for ECM:

com.sap.pct.hcm.ecmmain.par

com.sap.pct.hcm.util.par

com.sap.pct.hcm.objectanddataprovider.par

com.sap.pct.hcm.orgmanagementeventing.par

This resolved our problem. We had already downloaded what we thought were the most recent PAR files from SAP. Perhaps it was the latest that was causing the problems. In any case, we are happy now.

Regards,

Calvin