Deleting or Changing a user ID

gregglarkin

gregglarkin

Legendary Poster
Question:

We are in the middle of a project to implement single sign on between the LAN, JDE and other applications. Many of our users have the same ID for JDE and the LAN. The problem is that a large percentage of our users have an older style LAN ID that does not match the standard that we are using in JDE.

Has anyone deleted or attempted to change a user's JDE ID? What modules or tables are affected? If I change a user's ID in JDE, say from JOEUSER to USAJOEUSER, is all of the data previously associated with JOEUSER irrevocably lost or can I massage some tables to reassociate that data to the new user account?

We are having a tug of war with the LAN guys. The JDE camp is saying that the LAN guys should change the LAN accounts to be in synch with JDE. Our contention is that we are afraid of losing data. The LAN guys don't want to change LAN IDs and want us to make the change in JDE.

Has anyone out there wrestled with this issue and if so, what did you do?

Our system:
XE, Update 6, SP21, Windows 2000 Server, SQL Server, 15 Citrix XP terminal servers.

Gregg Larkin
North American CNC
Praxair, Inc.
 
Gregg...

When you consider all factors...IMHO changing the LAN ID is by far the
easiest. Usually you simply copy the existing ID, thus the new inherits
all the rights/groups of the old, and then usually it's just a
modification of the users' home directory.

Depending on the modules in use and how you use OneWorld, the process of
changing a user ID could be very simple or very complex. In the least
you need to delete the user ID, delete role definitions and
relationships, delete security workbench records, recreate the ID,
recreate the user password and system account, recreate the security (or
copy all the security records), reestablish roles, reestablish role
relationships....and then if you simply add in the use of work
center...then consider all of the records tagged with the old user ID for
reporting and troubleshooting purposes. And the list goes on and on and
on. Depending on your security model and use of roles/relationships,
this can become very intricate.

I always suggest changing the LAN ID unless there is a strong reason not
to, for instance the OneWorld user ID doesn't conform to corporate ID
standards. My measuring stick is always this...ask yourself, "which of
the two systems is more important from a business standpoint?" Usually
the answer is "the ERP system". I mean, if you have problems accessing
your LAN files, that could be problematic, but if you have problems
accessing AR/AP/Distribution...and the clincher for those clients running
it....PAYROLL...which will have a greater business impact??

Regards...

Jim

________________________________________________________________
The best thing to hit the internet in years - Juno SpeedBand!
Surf the web up to FIVE TIMES FASTER!
Only $14.95/ month - visit www.juno.com to sign up today!
 
Gregg -

I have changed user names in the database before. These are the tables I
needed to touch...

update sysb733.f0092
set uluser = v_newID
where uluser = v_oldID;
--
update sysb733.f00921
set uluser = v_newID
where uluser = v_oldID;
--
update sysb733.f00922
set uluser = v_newID
where uluser = v_oldID;
--
update sysb733.f0093
set lluser = v_newID
where lluser = v_oldID;
--
update sysb733.f00950
set fsuser = v_newID
where fsuser = v_oldID;
--
update sysb733.f98owsec
set scuser = v_newID
where scuser = v_oldID;
--
update sysb733.f98owsec
set scsecfrq = v_newfreq
where scuser = v_newID;
--

-- for each pathcode
update prodb733.F983051 set vruser = 'C90656T' where vruser = 'TESTBNT'
update prodb733.F983051 set vrusr0 = 'C90656T' where vrusr0 = 'TESTBNT'
update prodb733.f98950 set uouser = 'C90655S' where uouser = 'TNNELIPOV'
Commit;

I have not had any problems with the users afterwards.

Tony
 
Greg,
Don't even think of trying to "change" a jde profile. The profile's user stamp is in hundreds of tables. This would be an unbelievable amount of work to change the user name in all of those tables.
On top of that you would also have to re-do all the One World security.
Suggest you put up a strong fight on this one.
Good Luck !
Dave
 
Greg, I have a different opinion on this.
The username is saved in many tables but that is for audit only. It will
not break any process flow if you change the ID. I cannot see the need to
change a user´s name in all kind of transaction tables when that ID
ceases to exist.
If you *copy* user to newuser in P0092 you will maintain it´s AB number
and group. Therefore all workflow and workcenter setup will continue as
before.
Of course you would have to (re-)set newuser´s initial password.

Security should be set up by group, so it will be maintained as well. If
you have security set up for user, you can still copy all F00950 records
from user to newuser in P00950.

I would say it´s something that can be done.

My two centavos, Gerd
 
Hi Jim

The CNCs in our company agree with your opinion. We have over 2000 users on our system. The JDE IDs are in a uniform format with country code identifiers for each user. The format we use when creating a new JDE user is the same format that the LAN group uses when creating a new LAN user. It is the older LAN accounts that are the problem. Praxair changed over to a new naming convention several years ago, but did not go back and revise existing LAN accounts. The previous JDE security officer had the foresight to use the new naming convention even if the new JDE user's LAN account was in the older convention.

Thank you all for your opinons. Any additional opinions are appreciated.

Gregg Larkin
North American CNC and Security Guy
Praxair, Inc.
 
Re: RE: Deleting or Changing a user ID

If your users create report versions, I would also update the VRUSR0 field in the Versions file F983051.
 
Back
Top