on 04-15-2007 9:03 AM
Dear All,
EP7.0 SP9, ECC5
We have an major issue in ESS, The problem is with single sign on.
Here are the scenario's we are using :-
1. We are using "training1" as EP login id and in PA30 in R/3 InfoType 105 and Sub Infotype 0001 The same ID "training1" (Same as EP log in), the portal is picking the data properly and working fine.
2. If we use training1 as EP loginID and in PA30 in R/3 InfoType 105 and Sub Infotype 0001 if we use exeibckk (R/3 ID created for each individual user as communication user),
we are getting error "User TRAINING1 does not exist in this period"
we need to go ahead with the Step2, since all the EP login users are LDAP configured and,it has more than 15 characters, we cannot use EP login ID in InfoType 105 and Sub Infotype 0001
since it is restricted to 12 Characters.
e.g:
EP user ID is - shivakumar_ks ( taken from LDAP)
where as his R/3 or ESS user ID is - P000000002
since the login ID and R/3 ID are different,The system is throwing the error mentioned above.
We map the Shivakumar_ks with P000000002 in the EP Personalize option. But it is
not picking up the mapping. It tried to find the Shivakumar_ks in R/3 and fails.
Even though we are giving the UIDPWD in the system Logon Method.
Can anyone please give me the solution on the above.
Thanks in advane
Ponnusamy P
I beleive you know how to map it ABAP UME - any how i enclose the details - may be useful to our friends
Update Host file on Portal server with information of ABAP IP & Host Name
Update Services file on Portal with entry sapms<SID> 36<NR>/tcp
Update Host file on ABAP server with information of Portal Server
Create User ABAP Client with SAP_ALL & record password
On Portal Server
============
Open Configtool from
<DRIVE>:\usr\sap\<SID>\JC<NR>\j2ee\configtool
Expand - Global Service Configuration
Expand - Services
Click - com.sap.security.core.ume.service
In Right Pane - Change the below things
==
1
==
UME_persistence.data_source_configuration
from : dataSourceConfiguration_database_only.xml (default)
to : dataSourceConfiguration_abap.xml
==
2
==
ume.logon.r3.master.adapterid
from : master
to : 001
==
3
==
ume.r3.connection.001.user
from : --
to : <ABAP SUPER USER CREATED>
==
4
==
ume.r3.connection.001.passwd
<PASSWORD OF ABAP USER>
==
5
==
ume.r3.connection.001.ashost
from : --
to : <ABAP SERVER HOSTNAME / FQDN>
==
6
==
ume.r3.connection.001.sysnr
from : --
to : <ABAP INSTANCE NUMBER>
==
7
==
ume.r3.connection.001.client
from : --
to : <ABAP CLIENT>
==
8
==
ume.r3.connection.001.group
from : --
to : <LOGON GROUP DEFAULT is SPACE or any You created >
==
9
==
ume.r3.connection.001.gwhost
from : --
to : <ABAP SERVER HOSTNAME / FQDN>
==
10
==
ume.r3.connection.001.gwserv
from : --
to : sapgw<NR>
==
11
==
ume.r3.connection.001.msghost
from : --
to : <ABAP SERVER HOSTNAME / FQDN>
==
12
==
ume.r3.connection.001.r3name
from : --
to : <ABAP SID>
====
Above Configs Cahnges done as per below link and Note
====
Useful Help Link :
com/saphelp_erp2005vp/helpdata/en/49/9dd53f779c4e21e10000000a1550b0/content.htm
Alos Look at Note : SAP Note 718383
Please mark the question answered
Good Luck - Cheers
PR
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
If you are using user mapping in ESS scenario.
For example :
if user accessing his slary slip - every ESS user wil see slary slip of user which you used for JCO Connections of application data.
we experienced the same problem and the only solution is LOGONTICKET for Application / user data of ESS JCO Connections
Regards
PR
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi,
The user mapping will work. You need to make changes in JCO also. There you need to select user ID option & enter the R/3 user ID & password.
If u face any further issue then mail me. I'll explain u. I think you know my ID.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Dear Ponnusamy P .
for ESS application usage you can use User mapping
read it as
Dear Ponnusamy P .
for ESS application usage you can not use User mapping
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Dear Ponnusamy P .
for ESS application usage you can use User mapping.
for ESS ther are METADATA & APPLICATION JCO Connections.
METADATA can be binded with single user id but
APPLICATION JCo connections must be with LOGONTICKET.
The Pre-Requisiste for single -sign on - The User ID should be same in PORTAL and R3.
as your names are different your solution will not at all work for ESS Solution.(id I am not wrong)
I strongly feel the easy one is map UME of portal to ABAP UME instead LDAP that users can have similar user names in portal as well in R3.
If i am not wrong the data is retreived from r3 system thru JCO Connections only
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
84 | |
10 | |
9 | |
8 | |
6 | |
6 | |
6 | |
5 | |
3 | |
3 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.