Employee locked in Time Registration thru "ESS in MSS"

[Former Member]

Hi,

we have a situation where some users experience that the session-handling is not working as expected when registering time (CATS) in the portal "ESS in MSS" - If anyone out there could guide me on how to correct this it would be greatly appreciated...

Example: The manager chooses person A from the list over employees and go to the time registration application, when done he closes the window and choose person B goes to the time reg dialogue, closes the window. When he tries to go back to person A he gets an error message stating that the emloyeenumber is locked.

If the user tries the application on another PC everything is working as expected.

Browser used IE 7.0

Were on ECC 6.0, Portal SAP Netweaver 7.0 Supportpackage 18, Business package for ESS/MSS version 1.31

Best regards

Joakim

[Former Member · Accepted solution]

Hi Joakim,

I guess that since you are using ESS 1.31 BP, this package would be an ITS version package. Since they might be BSP applications and BSP applications implicitly are stateless, meaning they themselves do not do any session management.

You can attempt the following to resolve this error

1. Go to SE80

2. Select BSP Application

3. Enter the name of the application

4. Double click on the root node

5. Select the properties tab

6. Check the checkboxes u201CStatefulu201D and u201CSupports Portal Integrationu201D

With the checkbox u201CSupports Portal Integrationu201D checked, the Session Management is handled by Portal "Distributed Session Management". Hence, whenever, you exit from a BSP application, the session is closed by DSM. Once a BSP application is closed, the application should not be listed in SM04 and no locks should be listed in SM12.

So please check the transactions SM04 and SM12 for any locks and applications.

Hope this helps,

Regards

Nikhil

[Former Member · Accepted solution]

Hi Nikhil,

thank you for your reply.

Actually we use the java-based iView for timereporting.

I´ve found out that the users affected were on IE6 and that the IE settings were not as they should be (regarding trusted sites).

Best regards

Joakim