Configure UME

Question

Hi All,
I have done implementation ESS+MSS using UME configured  ABAP system, it is working fine.
Now I have to change UME configuration  LDAP or JAVA stack database.
Case 1: IF I am going to use LDAP
I have to map employee personal number to the user in LDAP and I am goinng maintain same user ID in portal.
Case 2: If I am going to use JAVA Stack
I have to maintain same user id in JAVA and ABAP stack or user mapping.
But client don't want to create user in ABAP (Mapping the personal number same as  LDAP)
Could you please help me, best way to proceed and what are the things do I need to change in existing project.
Thanks in advance...
Regards
Ben

Answer 1

Hi Sunil,
Thank you very much.
Many to one scenario: (just imagination)
I will maintain user Id details in JAVA stack including employee personal number.
and fetch the data based on personal number.
I red some document regarding LDAP using as UME ...
Ex:
Data extraction in SAP HR
The extraction report in the appendix is based on the SAP report RPLDAP_MANAGER.
It uses the logical database PNP. The macro RP_PROVIDE_FROM_LAST is used to
retrieve the last entry of the current period in the table header entry from an internal
infotype table (here p0001 and p0002). The data is transmitted to the function module
SPLDAP_RECEIVE_ATTRIBUTES.
CALL FUNCTION 'SPLDAP_RECEIVE_ATTRIBUTES'
DESTINATION LDAPDEST
EXPORTING
LOGSYS = LOGSYS
SERVERID = LDAPSRV
ATTRIBUTES_S = attributes[]
INITIAL_RUN = LDAPINITIALRUN
IMPORTING
RETURN = ERRORS[].
The function module SPLDAP_RECEIVE_ATTRIBUTES is part of the ABAP stack in a
Web Application Server and is remote enabled. If the extraction report runs in a SAP HR
system having the release 4.6 or lower it can to be called remotely in separate SAP Web
Application Server that than acts as a LDAP Gateway.
The function module SPLDAP_RECEIVE_ATTRIBUTES needs the following input
parameters:
DESTINATION RFC destination that is configured to access the SAP Web
Application Server remotely where the LDAP connector is
configured. (Only needed for a SAP HR system having a release of
4.6 or lower)
LOGSYS Logical system name of the client where the extraction report runs.
This value is retrieved using the function module
'OWN_LOGICAL_SYSTEM_GET'
SERVERID Name of the LDAP server as it is configured in transaction LDAP in
the SAP Web Application Server
ATTRIBUTES_S Internal table that receives the name and values of the Logical SAP
Data Fields that are mapped in transaction LDAP against the
directory services attributes of the user object. The internal table
has the following fields:
PERNR
ATTR_TAB
6
ATTR_FIELD
VALUE
INITIAL_RUN If this flag is set the function module first tries to create a user. It will
try to update the user if the user already exists. If the flag is omitted
the function module will first try to update the user and will then try
to create the user if it does not exist
The logical SAP data fields can be represented by freely-definable names whereas the
name of the SAP data structure is fixed to EMPLOYEE. In our example we therefore
choose meaningful names such as FIRSTNAME and LASTNAME for the SAP data
fields. The SAP data fields are mapped to the directory services attributes using
transaction LDAPMAP in the SAP Web Application Server as described later.
If the first name and the last name of the two employees Bill Smith and Bob Smith are
extracted the table ATTRIBUTES_S will have the following content.
PERNR ATTR_TAB ATTR_FIELD VALUE
0000001 EMPLOYEE FIRSTNAME Bill
0000001 EMPLOYEE LASTNAME Smith
0000001 EMPLOYEE SAMACCOUNTNAME E00000001
0000002 EMPLOYEE FIRSTNAME Bob
0000002 EMPLOYEE LASTNAME Smith
0000002 EMPLOYEE SAMACCOUNTNAME E00000002
Because we have to maintain 60000 users..
Could you please  suggest me best way ?
Regards
Ben