Skip to Content
avatar image
Former Member

portal user issue - all users are viewing data of one particluar user...

Hi all,

we are implementing ess 1.0 on EP7.0 and using ecc6.0

Now, while creating Jco connection we had provided user id/pwd of a user in portal and assigned that user to an employee in backend r3 (say abc).(we followed the famous pdf available on sdn: Configuring the Business Package for Employee Self-Service (ESS) u2013 mySAP ERP 2004 by an HCL employee)

Now the Problem is:

whenever an xyz user logs in to portal with ess role, and views any data...say perosnal information, telephone no., address, etc than that xyz user sees all this data of the employee(abc) to whom we had mapped our user which was used while creating Jco connections.

infact if xyz tries to edit any data than it gets reflected to abc.

to genralise: any portal user with ess role logs in to portal is viewing/editing data of abc employee...which normally should not be the case.

plz try and help me resolve this issue...

Regards,

JJ

Add comment
10|10000 characters needed characters exceeded

  • Get RSS Feed

1 Answer

  • Best Answer
    avatar image
    Former Member
    Sep 02, 2008 at 11:08 AM

    Hi!

    You have to configre your JCo Destionations to use Portal SSO.

    Additionally in your HR Backend you have to maintain (I think it is) Info type 0105 (sub-type 001) and assign every personal number the appropriate UserID so that every user sees his own data.

    A technical user is only needed for the JCo destinations dealing with metadata. The "real" JCo destinations performing RFC calls to the HR Backend can be configured to use Portal SSO.

    For more details refer to http://help.sap.com/saphelp_nw70/helpdata/EN/44/45a04028f40160e10000000a1550b0/content.htm

    Hope this helps!

    Regards,

    Volker

    Add comment
    10|10000 characters needed characters exceeded

    • Former Member

      Thnxs for ur reply....issue is resolved....basically it was wrong authentication type used in creation of JCO connection.

      For Metada data we used Ticket method and for application data we used userid/pwd method to resolve the issue.

      Regards,

      JJ