cancel
Showing results for 
Search instead for 
Did you mean: 

Exception:- Changing own data in ESS

Former Member
0 Kudos

Hi Experts

I am getting this exception

com.sap.tc.webdynpro.services.exceptions.WDRuntimeException: failed to create or init instance of model 'com.sap.xss.hr.cod.model.CodModel' in scope APPLICATION_SCOPE with instanceId 'null'

in ESS Employee search (changing own data)

Thanks

Rishi.

Accepted Solutions (0)

Answers (3)

Answers (3)

srinivas_sistu
Active Contributor
0 Kudos

Hi,

Few Causes/Solutions are

1. Not Maintaining Communication Info type for the user in R3.

2. Differences between the patch levels of R3 and EP specially.. If you are using EP 7.0 better use ECC 6.0

3. Make sure that your XSS version on R3 matches with that of EP.

Mostly I got reply from SDN stating that there is a level miss match between the components and communication info type 1015 of employee in R3...

Some times after creating JCo if you restart both R3 and EP then also it woks(may be solution).

if you use a 7.0 portal and a ECC 5.0 backend, you need another J2EE instance to run your XSS services. This has to be a J2EE 640 version, because of the special setup (latest portal, not the latest ecc).

We have it at our client and it's a mess. I would like to see them upgrade to ECC 6.0, but the added value isn't very big in my opinion.

There is a note that describe the J2EE 640 story

Refer to SAP Note 1007341.

have a look at SAPNote 1129210, as may occurs due to mismatch of the front end and backend levels...

Have a look at this Thread

Check the entries of Message server in the service file in the j2ee server.

after making the entry of the message server in Service file restart the server.

example:

sapmsCED 3601/tcp #messagesever

Regards,

Srinivas.

Former Member
0 Kudos

Hi ,

Check below thread .

It may help you

Koti Reddy

Former Member
0 Kudos

Hi

Any updates on this

Thanks

Rishi

former_member193769
Active Contributor
0 Kudos

Hi,

Check if any authorization object missing.

T-Code ST01.

Enable trace and login to portal and generate the same error again.

And then look in the trace file for any missing authorization and info type.

Thanks and Regards,

gopal