This is an archive of the Maximo Yahoo Community. The content of this pages may be a sometimes obsolete so please check post dates.
Thanks to the community owner Christopher Wanko for providing the content.
When a user in your company has a name change (married, divorce, etc), do you also change their userid's in various applications - AD, Exchange, Maximo, ERP, etc?
We do...
.. in Maximo I usually then run a script to change the reference to the new username.
--- In MAXIMO@yahoogroups.com, "Jason Verly" <jason.verly@...> wrote:
>
> When a user in your company has a name change (married, divorce, etc), do you also change their userid's in various applications - AD, Exchange, Maximo, ERP, etc?
>
I do too. But I only deal in Maximo, not all the other apps you mention.
Travis Herron
--- In MAXIMO@yahoogroups.com, "kermitlong" <clowlong@...> wrote:
>
> We do...
> .. in Maximo I usually then run a script to change the reference to the new username.
>
> --- In MAXIMO@yahoogroups.com, "Jason Verly" <jason.verly@> wrote:
> >
> > When a user in your company has a name change (married, divorce, etc), do you also change their userid's in various applications - AD, Exchange, Maximo, ERP, etc?
> >
>
Anyone care to share their update scripts they use?
--- In MAXIMO@yahoogroups.com, "Travis Herron" <therron@...> wrote:
>
> I do too. But I only deal in Maximo, not all the other apps you mention.
>
> Travis Herron
>
>
>
> --- In MAXIMO@yahoogroups.com, "kermitlong" <clowlong@> wrote:
> >
> > We do...
> > .. in Maximo I usually then run a script to change the reference to the new username.
> >
> > --- In MAXIMO@yahoogroups.com, "Jason Verly" <jason.verly@> wrote:
> > >
> > > When a user in your company has a name change (married, divorce, etc), do you also change their userid's in various applications - AD, Exchange, Maximo, ERP, etc?
> > >
> >
>
HI,
We make the old userid, person and labor inactive with a comment that it was a name change.
Then create the new userid that is in our AD. We don't intgrate to the AD we just keep them in synch manually.
Going directly to the database and changing records that use the userid and person like POs and invoices can cause issues if you ever have to provide data to prove who did what and when. We audit the security tables for just this reason. But if you update through sql scripts you have no audit trail.
Dave Bone
--- In MAXIMO@yahoogroups.com, "Jason Verly" <jason.verly@...> wrote:
>
> Anyone care to share their update scripts they use?
>
> --- In MAXIMO@yahoogroups.com, "Travis Herron" <therron@> wrote:
> >
> > I do too. But I only deal in Maximo, not all the other apps you mention.
> >
> > Travis Herron
> >
> >
> >
> > --- In MAXIMO@yahoogroups.com, "kermitlong" <clowlong@> wrote:
> > >
> > > We do...
> > > .. in Maximo I usually then run a script to change the reference to the new username.
> > >
> > > --- In MAXIMO@yahoogroups.com, "Jason Verly" <jason.verly@> wrote:
> > > >
> > > > When a user in your company has a name change (married, divorce, etc), do you also change their userid's in various applications - AD, Exchange, Maximo, ERP, etc?
> > > >
> > >
> >
>
Same here, we do it manually through the Maximo UI, not through scripts. It doesn't happen frequently enough for it to bother me.
Travis Herron
--- In MAXIMO@yahoogroups.com, "in2data" <in2data@...> wrote:
>
> HI,
>
> We make the old userid, person and labor inactive with a comment that it was a name change.
>
> Then create the new userid that is in our AD. We don't intgrate to the AD we just keep them in synch manually.
>
> Going directly to the database and changing records that use the userid and person like POs and invoices can cause issues if you ever have to provide data to prove who did what and when. We audit the security tables for just this reason. But if you update through sql scripts you have no audit trail.
>
> Dave Bone
>
> --- In MAXIMO@yahoogroups.com, "Jason Verly" <jason.verly@> wrote:
> >
> > Anyone care to share their update scripts they use?
> >
> > --- In MAXIMO@yahoogroups.com, "Travis Herron" <therron@> wrote:
> > >
> > > I do too. But I only deal in Maximo, not all the other apps you mention.
> > >
> > > Travis Herron
> > >
> > >
> > >
> > > --- In MAXIMO@yahoogroups.com, "kermitlong" <clowlong@> wrote:
> > > >
> > > > We do...
> > > > .. in Maximo I usually then run a script to change the reference to the new username.
> > > >
> > > > --- In MAXIMO@yahoogroups.com, "Jason Verly" <jason.verly@> wrote:
> > > > >
> > > > > When a user in your company has a name change (married, divorce, etc), do you also change their userid's in various applications - AD, Exchange, Maximo, ERP, etc?
> > > > >
> > > >
> > >
> >
>
Hi Dave,
How do you handle questions involving history? It would seem that you'd have to report on both the old and the new IDs to get a complete picture.
Boyd
--- In MAXIMO@yahoogroups.com, "in2data" <in2data@...> wrote:
>
> HI,
>
> We make the old userid, person and labor inactive with a comment that it was a name change.
>
> Then create the new userid that is in our AD. We don't intgrate to the AD we just keep them in synch manually.
>
> Going directly to the database and changing records that use the userid and person like POs and invoices can cause issues if you ever have to provide data to prove who did what and when. We audit the security tables for just this reason. But if you update through sql scripts you have no audit trail.
>
> Dave Bone
>
> --- In MAXIMO@yahoogroups.com, "Jason Verly" <jason.verly@> wrote:
> >
> > Anyone care to share their update scripts they use?
> >
> > --- In MAXIMO@yahoogroups.com, "Travis Herron" <therron@> wrote:
> > >
> > > I do too. But I only deal in Maximo, not all the other apps you mention.
> > >
> > > Travis Herron
> > >
> > >
> > >
> > > --- In MAXIMO@yahoogroups.com, "kermitlong" <clowlong@> wrote:
> > > >
> > > > We do...
> > > > .. in Maximo I usually then run a script to change the reference to the new username.
> > > >
> > > > --- In MAXIMO@yahoogroups.com, "Jason Verly" <jason.verly@> wrote:
> > > > >
> > > > > When a user in your company has a name change (married, divorce, etc), do you also change their userid's in various applications - AD, Exchange, Maximo, ERP, etc?
> > > > >
> > > >
> > >
> >
>
Hi,
The history is the reason we do not modify the user records using scripts. Say you have a user MENOTYOU and they have a name change to MENOTTHEM. MENOTYOU remains but inactive and MENOTTHEM is added. So all of the old transactions for MENOTYOU remain.
Since we have audit tables running on all of the security tables we can see when users were made active and inactive and the users that made those changes. The users (our IT security team) making those changes only have access to make security changes. They cannot make changes to things like auditing or security controls. In fact they cannot make changes to their own security or assign super security groups like maxadmin. They also do not have access to change data through SQL scripts.
Say after a couple of years with the name change above we need to know what MENOTTHEM has done the entire time they have had access to Maximo. The IT security team provides all of the active directory user IDs that user has been assigned while employed. We only use valid AD user IDs in Maximo. So then I search all of the data they need for purchasing or work orders including audit tables for the purchasing and invoicing. Depends on what the internal auditors are looking for. If they are looking at purchasing all of those tables are audited and since we audit all security changes we can show when that user had access to make say PO approvals or invoice approvals.
Not a perfect system but it's working for us. But I'll say it again. You should not use SQL scripts to change transaction records when names change. IBM can say you are out of support becuase you have done that. You also cannot provide a chain of custody for your data that will hold up to any sort of legal inspection. Say HR wants to fire someone over a derogatory statement in a work order and you have been changing user IDs recorded in those transactions. You've opened a huge door there.
Dave Bone
--- In MAXIMO@yahoogroups.com, "boyd_bradford" <bbradford@...> wrote:
>
>
>
> Hi Dave,
>
> How do you handle questions involving history? It would seem that you'd have to report on both the old and the new IDs to get a complete picture.
>
> Boyd
>
> --- In MAXIMO@yahoogroups.com, "in2data" <in2data@> wrote:
> >
> > HI,
> >
> > We make the old userid, person and labor inactive with a comment that it was a name change.
> >
> > Then create the new userid that is in our AD. We don't intgrate to the AD we just keep them in synch manually.
> >
> > Going directly to the database and changing records that use the userid and person like POs and invoices can cause issues if you ever have to provide data to prove who did what and when. We audit the security tables for just this reason. But if you update through sql scripts you have no audit trail.
> >
> > Dave Bone
> >
> > --- In MAXIMO@yahoogroups.com, "Jason Verly" <jason.verly@> wrote:
> > >
> > > Anyone care to share their update scripts they use?
> > >
> > > --- In MAXIMO@yahoogroups.com, "Travis Herron" <therron@> wrote:
> > > >
> > > > I do too. But I only deal in Maximo, not all the other apps you mention.
> > > >
> > > > Travis Herron
> > > >
> > > >
> > > >
> > > > --- In MAXIMO@yahoogroups.com, "kermitlong" <clowlong@> wrote:
> > > > >
> > > > > We do...
> > > > > .. in Maximo I usually then run a script to change the reference to the new username.
> > > > >
> > > > > --- In MAXIMO@yahoogroups.com, "Jason Verly" <jason.verly@> wrote:
> > > > > >
> > > > > > When a user in your company has a name change (married, divorce, etc), do you also change their userid's in various applications - AD, Exchange, Maximo, ERP, etc?
> > > > > >
> > > > >
> > > >
> > >
> >
>
For Maximo, we use an "employee id" rather than username as personid, userid. That way name changes don't affect the person/user records.
--- In MAXIMO@yahoogroups.com, "in2data" <in2data@...> wrote:
>
> Hi,
>
> The history is the reason we do not modify the user records using scripts. Say you have a user MENOTYOU and they have a name change to MENOTTHEM. MENOTYOU remains but inactive and MENOTTHEM is added. So all of the old transactions for MENOTYOU remain.
>
> Since we have audit tables running on all of the security tables we can see when users were made active and inactive and the users that made those changes. The users (our IT security team) making those changes only have access to make security changes. They cannot make changes to things like auditing or security controls. In fact they cannot make changes to their own security or assign super security groups like maxadmin. They also do not have access to change data through SQL scripts.
>
> Say after a couple of years with the name change above we need to know what MENOTTHEM has done the entire time they have had access to Maximo. The IT security team provides all of the active directory user IDs that user has been assigned while employed. We only use valid AD user IDs in Maximo. So then I search all of the data they need for purchasing or work orders including audit tables for the purchasing and invoicing. Depends on what the internal auditors are looking for. If they are looking at purchasing all of those tables are audited and since we audit all security changes we can show when that user had access to make say PO approvals or invoice approvals.
>
> Not a perfect system but it's working for us. But I'll say it again. You should not use SQL scripts to change transaction records when names change. IBM can say you are out of support becuase you have done that. You also cannot provide a chain of custody for your data that will hold up to any sort of legal inspection. Say HR wants to fire someone over a derogatory statement in a work order and you have been changing user IDs recorded in those transactions. You've opened a huge door there.
>
> Dave Bone
>
>
> --- In MAXIMO@yahoogroups.com, "boyd_bradford" <bbradford@> wrote:
> >
> >
> >
> > Hi Dave,
> >
> > How do you handle questions involving history? It would seem that you'd have to report on both the old and the new IDs to get a complete picture.
> >
> > Boyd
> >
> > --- In MAXIMO@yahoogroups.com, "in2data" <in2data@> wrote:
> > >
> > > HI,
> > >
> > > We make the old userid, person and labor inactive with a comment that it was a name change.
> > >
> > > Then create the new userid that is in our AD. We don't intgrate to the AD we just keep them in synch manually.
> > >
> > > Going directly to the database and changing records that use the userid and person like POs and invoices can cause issues if you ever have to provide data to prove who did what and when. We audit the security tables for just this reason. But if you update through sql scripts you have no audit trail.
> > >
> > > Dave Bone
> > >
> > > --- In MAXIMO@yahoogroups.com, "Jason Verly" <jason.verly@> wrote:
> > > >
> > > > Anyone care to share their update scripts they use?
> > > >
> > > > --- In MAXIMO@yahoogroups.com, "Travis Herron" <therron@> wrote:
> > > > >
> > > > > I do too. But I only deal in Maximo, not all the other apps you mention.
> > > > >
> > > > > Travis Herron
> > > > >
> > > > >
> > > > >
> > > > > --- In MAXIMO@yahoogroups.com, "kermitlong" <clowlong@> wrote:
> > > > > >
> > > > > > We do...
> > > > > > .. in Maximo I usually then run a script to change the reference to the new username.
> > > > > >
> > > > > > --- In MAXIMO@yahoogroups.com, "Jason Verly" <jason.verly@> wrote:
> > > > > > >
> > > > > > > When a user in your company has a name change (married, divorce, etc), do you also change their userid's in various applications - AD, Exchange, Maximo, ERP, etc?
> > > > > > >
> > > > > >
> > > > >
> > > >
> > >
> >
>
And you just spelled out every arguement I made to our IT Dept on why this was a bad idea. Thanks.
--- In MAXIMO@yahoogroups.com, "in2data" <in2data@...> wrote:
>
> Hi,
>
> The history is the reason we do not modify the user records using scripts. Say you have a user MENOTYOU and they have a name change to MENOTTHEM. MENOTYOU remains but inactive and MENOTTHEM is added. So all of the old transactions for MENOTYOU remain.
>
> Since we have audit tables running on all of the security tables we can see when users were made active and inactive and the users that made those changes. The users (our IT security team) making those changes only have access to make security changes. They cannot make changes to things like auditing or security controls. In fact they cannot make changes to their own security or assign super security groups like maxadmin. They also do not have access to change data through SQL scripts.
>
> Say after a couple of years with the name change above we need to know what MENOTTHEM has done the entire time they have had access to Maximo. The IT security team provides all of the active directory user IDs that user has been assigned while employed. We only use valid AD user IDs in Maximo. So then I search all of the data they need for purchasing or work orders including audit tables for the purchasing and invoicing. Depends on what the internal auditors are looking for. If they are looking at purchasing all of those tables are audited and since we audit all security changes we can show when that user had access to make say PO approvals or invoice approvals.
>
> Not a perfect system but it's working for us. But I'll say it again. You should not use SQL scripts to change transaction records when names change. IBM can say you are out of support becuase you have done that. You also cannot provide a chain of custody for your data that will hold up to any sort of legal inspection. Say HR wants to fire someone over a derogatory statement in a work order and you have been changing user IDs recorded in those transactions. You've opened a huge door there.
>
> Dave Bone
>
>
> --- In MAXIMO@yahoogroups.com, "boyd_bradford" <bbradford@> wrote:
> >
> >
> >
> > Hi Dave,
> >
> > How do you handle questions involving history? It would seem that you'd have to report on both the old and the new IDs to get a complete picture.
> >
> > Boyd
> >
> > --- In MAXIMO@yahoogroups.com, "in2data" <in2data@> wrote:
> > >
> > > HI,
> > >
> > > We make the old userid, person and labor inactive with a comment that it was a name change.
> > >
> > > Then create the new userid that is in our AD. We don't intgrate to the AD we just keep them in synch manually.
> > >
> > > Going directly to the database and changing records that use the userid and person like POs and invoices can cause issues if you ever have to provide data to prove who did what and when. We audit the security tables for just this reason. But if you update through sql scripts you have no audit trail.
> > >
> > > Dave Bone
> > >
> > > --- In MAXIMO@yahoogroups.com, "Jason Verly" <jason.verly@> wrote:
> > > >
> > > > Anyone care to share their update scripts they use?
> > > >
> > > > --- In MAXIMO@yahoogroups.com, "Travis Herron" <therron@> wrote:
> > > > >
> > > > > I do too. But I only deal in Maximo, not all the other apps you mention.
> > > > >
> > > > > Travis Herron
> > > > >
> > > > >
> > > > >
> > > > > --- In MAXIMO@yahoogroups.com, "kermitlong" <clowlong@> wrote:
> > > > > >
> > > > > > We do...
> > > > > > .. in Maximo I usually then run a script to change the reference to the new username.
> > > > > >
> > > > > > --- In MAXIMO@yahoogroups.com, "Jason Verly" <jason.verly@> wrote:
> > > > > > >
> > > > > > > When a user in your company has a name change (married, divorce, etc), do you also change their userid's in various applications - AD, Exchange, Maximo, ERP, etc?
> > > > > > >
> > > > > >
> > > > >
> > > >
> > >
> >
>
Thanks for the idea.
--- In MAXIMO@yahoogroups.com, "Mary" <mmangier@...> wrote:
>
> For Maximo, we use an "employee id" rather than username as personid, userid. That way name changes don't affect the person/user records.
>
> --- In MAXIMO@yahoogroups.com, "in2data" <in2data@> wrote:
> >
> > Hi,
> >
> > The history is the reason we do not modify the user records using scripts. Say you have a user MENOTYOU and they have a name change to MENOTTHEM. MENOTYOU remains but inactive and MENOTTHEM is added. So all of the old transactions for MENOTYOU remain.
> >
> > Since we have audit tables running on all of the security tables we can see when users were made active and inactive and the users that made those changes. The users (our IT security team) making those changes only have access to make security changes. They cannot make changes to things like auditing or security controls. In fact they cannot make changes to their own security or assign super security groups like maxadmin. They also do not have access to change data through SQL scripts.
> >
> > Say after a couple of years with the name change above we need to know what MENOTTHEM has done the entire time they have had access to Maximo. The IT security team provides all of the active directory user IDs that user has been assigned while employed. We only use valid AD user IDs in Maximo. So then I search all of the data they need for purchasing or work orders including audit tables for the purchasing and invoicing. Depends on what the internal auditors are looking for. If they are looking at purchasing all of those tables are audited and since we audit all security changes we can show when that user had access to make say PO approvals or invoice approvals.
> >
> > Not a perfect system but it's working for us. But I'll say it again. You should not use SQL scripts to change transaction records when names change. IBM can say you are out of support becuase you have done that. You also cannot provide a chain of custody for your data that will hold up to any sort of legal inspection. Say HR wants to fire someone over a derogatory statement in a work order and you have been changing user IDs recorded in those transactions. You've opened a huge door there.
> >
> > Dave Bone
> >
> >
> > --- In MAXIMO@yahoogroups.com, "boyd_bradford" <bbradford@> wrote:
> > >
> > >
> > >
> > > Hi Dave,
> > >
> > > How do you handle questions involving history? It would seem that you'd have to report on both the old and the new IDs to get a complete picture.
> > >
> > > Boyd
> > >
> > > --- In MAXIMO@yahoogroups.com, "in2data" <in2data@> wrote:
> > > >
> > > > HI,
> > > >
> > > > We make the old userid, person and labor inactive with a comment that it was a name change.
> > > >
> > > > Then create the new userid that is in our AD. We don't intgrate to the AD we just keep them in synch manually.
> > > >
> > > > Going directly to the database and changing records that use the userid and person like POs and invoices can cause issues if you ever have to provide data to prove who did what and when. We audit the security tables for just this reason. But if you update through sql scripts you have no audit trail.
> > > >
> > > > Dave Bone
> > > >
> > > > --- In MAXIMO@yahoogroups.com, "Jason Verly" <jason.verly@> wrote:
> > > > >
> > > > > Anyone care to share their update scripts they use?
> > > > >
> > > > > --- In MAXIMO@yahoogroups.com, "Travis Herron" <therron@> wrote:
> > > > > >
> > > > > > I do too. But I only deal in Maximo, not all the other apps you mention.
> > > > > >
> > > > > > Travis Herron
> > > > > >
> > > > > >
> > > > > >
> > > > > > --- In MAXIMO@yahoogroups.com, "kermitlong" <clowlong@> wrote:
> > > > > > >
> > > > > > > We do...
> > > > > > > .. in Maximo I usually then run a script to change the reference to the new username.
> > > > > > >
> > > > > > > --- In MAXIMO@yahoogroups.com, "Jason Verly" <jason.verly@> wrote:
> > > > > > > >
> > > > > > > > When a user in your company has a name change (married, divorce, etc), do you also change their userid's in various applications - AD, Exchange, Maximo, ERP, etc?
> > > > > > > >
> > > > > > >
> > > > > >
> > > > >
> > > >
> > >
> >
>
Using an EmmployeeID is certainly the way to go . . .it keeps the database "normal" (by not using one field -- the PersonID -- to store two pieces of information), and as Mary says you don't have to worry about it changing.
However, in our case:
1). When we started with Maximo, we didn't have EmployeeIDs. Everything ran off people's Social Security Numbers. I wasn't going there.
2). Still today there are times we need to enter a PersonID for someone who is not an employee.
3). When assigning a work order, my users would not have tolerated having to do a lookup everytime they want to fill in the LEAD field. They'd much rather just type BILL or JIM or whatever and it (at least almost) fill in the rest. So including names in our PersonIDs was the happiest compromise I could come up with. Having to deal with the occasional name change was a good trade-off to have the masses a little happier when working with the computer system.
Travis Herron
--- In MAXIMO@yahoogroups.com, "Mary" <mmangier@...> wrote:
>
> For Maximo, we use an "employee id" rather than username as personid, userid. That way name changes don't affect the person/user records.
>
> --- In MAXIMO@yahoogroups.com, "in2data" <in2data@> wrote:
> >
> > Hi,
> >
> > The history is the reason we do not modify the user records using scripts. Say you have a user MENOTYOU and they have a name change to MENOTTHEM. MENOTYOU remains but inactive and MENOTTHEM is added. So all of the old transactions for MENOTYOU remain.
> >
> > Since we have audit tables running on all of the security tables we can see when users were made active and inactive and the users that made those changes. The users (our IT security team) making those changes only have access to make security changes. They cannot make changes to things like auditing or security controls. In fact they cannot make changes to their own security or assign super security groups like maxadmin. They also do not have access to change data through SQL scripts.
> >
> > Say after a couple of years with the name change above we need to know what MENOTTHEM has done the entire time they have had access to Maximo. The IT security team provides all of the active directory user IDs that user has been assigned while employed. We only use valid AD user IDs in Maximo. So then I search all of the data they need for purchasing or work orders including audit tables for the purchasing and invoicing. Depends on what the internal auditors are looking for. If they are looking at purchasing all of those tables are audited and since we audit all security changes we can show when that user had access to make say PO approvals or invoice approvals.
> >
> > Not a perfect system but it's working for us. But I'll say it again. You should not use SQL scripts to change transaction records when names change. IBM can say you are out of support becuase you have done that. You also cannot provide a chain of custody for your data that will hold up to any sort of legal inspection. Say HR wants to fire someone over a derogatory statement in a work order and you have been changing user IDs recorded in those transactions. You've opened a huge door there.
> >
> > Dave Bone
> >
> >
> > --- In MAXIMO@yahoogroups.com, "boyd_bradford" <bbradford@> wrote:
> > >
> > >
> > >
> > > Hi Dave,
> > >
> > > How do you handle questions involving history? It would seem that you'd have to report on both the old and the new IDs to get a complete picture.
> > >
> > > Boyd
> > >
> > > --- In MAXIMO@yahoogroups.com, "in2data" <in2data@> wrote:
> > > >
> > > > HI,
> > > >
> > > > We make the old userid, person and labor inactive with a comment that it was a name change.
> > > >
> > > > Then create the new userid that is in our AD. We don't intgrate to the AD we just keep them in synch manually.
> > > >
> > > > Going directly to the database and changing records that use the userid and person like POs and invoices can cause issues if you ever have to provide data to prove who did what and when. We audit the security tables for just this reason. But if you update through sql scripts you have no audit trail.
> > > >
> > > > Dave Bone
> > > >
> > > > --- In MAXIMO@yahoogroups.com, "Jason Verly" <jason.verly@> wrote:
> > > > >
> > > > > Anyone care to share their update scripts they use?
> > > > >
> > > > > --- In MAXIMO@yahoogroups.com, "Travis Herron" <therron@> wrote:
> > > > > >
> > > > > > I do too. But I only deal in Maximo, not all the other apps you mention.
> > > > > >
> > > > > > Travis Herron
> > > > > >
> > > > > >
> > > > > >
> > > > > > --- In MAXIMO@yahoogroups.com, "kermitlong" <clowlong@> wrote:
> > > > > > >
> > > > > > > We do...
> > > > > > > .. in Maximo I usually then run a script to change the reference to the new username.
> > > > > > >
> > > > > > > --- In MAXIMO@yahoogroups.com, "Jason Verly" <jason.verly@> wrote:
> > > > > > > >
> > > > > > > > When a user in your company has a name change (married, divorce, etc), do you also change their userid's in various applications - AD, Exchange, Maximo, ERP, etc?
> > > > > > > >
> > > > > > >
> > > > > >
> > > > >
> > > >
> > >
> >
>
I use the functions available in Maximo to maintain the history with handling the changes as they come along. In the users application you have both the userid and the user name. The user name is the login ID and is allow to change without changing the user ID and is the field used during direct login, AD or other authentication. By changing the User Name and Display Name you are able to have the user see the Name they expect to see. In the other resources application the Laobrid, Personid, etc cannot be modified but the actual name displayed is able to be modified. The entire history string is preserved for all applications while allowing the user to see any Name changes required by life.
Roy Cline
From: MAXIMO@yahoogroups.com [mailto:MAXIMO@yahoogroups.com] On Behalf Of Jason Verly
Sent: Tuesday, January 31, 2012 4:31 PM
To: MAXIMO@yahoogroups.com
Subject: [MAXIMO List] Re: Quick Poll - Modify UserID for Name Change
Thanks for the idea.
--- In MAXIMO@yahoogroups.com<mailto:MAXIMO%40yahoogroups.com>, "Mary" <mmangier@...> wrote:
>
> For Maximo, we use an "employee id" rather than username as personid, userid. That way name changes don't affect the person/user records.
>
> --- In MAXIMO@yahoogroups.com<mailto:MAXIMO%40yahoogroups.com>, "in2data" <in2data@> wrote:
> >
> > Hi,
> >
> > The history is the reason we do not modify the user records using scripts. Say you have a user MENOTYOU and they have a name change to MENOTTHEM. MENOTYOU remains but inactive and MENOTTHEM is added. So all of the old transactions for MENOTYOU remain.
> >
> > Since we have audit tables running on all of the security tables we can see when users were made active and inactive and the users that made those changes. The users (our IT security team) making those changes only have access to make security changes. They cannot make changes to things like auditing or security controls. In fact they cannot make changes to their own security or assign super security groups like maxadmin. They also do not have access to change data through SQL scripts.
> >
> > Say after a couple of years with the name change above we need to know what MENOTTHEM has done the entire time they have had access to Maximo. The IT security team provides all of the active directory user IDs that user has been assigned while employed. We only use valid AD user IDs in Maximo. So then I search all of the data they need for purchasing or work orders including audit tables for the purchasing and invoicing. Depends on what the internal auditors are looking for. If they are looking at purchasing all of those tables are audited and since we audit all security changes we can show when that user had access to make say PO approvals or invoice approvals.
> >
> > Not a perfect system but it's working for us. But I'll say it again. You should not use SQL scripts to change transaction records when names change. IBM can say you are out of support becuase you have done that. You also cannot provide a chain of custody for your data that will hold up to any sort of legal inspection. Say HR wants to fire someone over a derogatory statement in a work order and you have been changing user IDs recorded in those transactions. You've opened a huge door there.
> >
> > Dave Bone
> >
> >
> > --- In MAXIMO@yahoogroups.com<mailto:MAXIMO%40yahoogroups.com>, "boyd_bradford" <bbradford@> wrote:
> > >
> > >
> > >
> > > Hi Dave,
> > >
> > > How do you handle questions involving history? It would seem that you'd have to report on both the old and the new IDs to get a complete picture.
> > >
> > > Boyd
> > >
> > > --- In MAXIMO@yahoogroups.com<mailto:MAXIMO%40yahoogroups.com>, "in2data" <in2data@> wrote:
> > > >
> > > > HI,
> > > >
> > > > We make the old userid, person and labor inactive with a comment that it was a name change.
> > > >
> > > > Then create the new userid that is in our AD. We don't intgrate to the AD we just keep them in synch manually.
> > > >
> > > > Going directly to the database and changing records that use the userid and person like POs and invoices can cause issues if you ever have to provide data to prove who did what and when. We audit the security tables for just this reason. But if you update through sql scripts you have no audit trail.
> > > >
> > > > Dave Bone
> > > >
> > > > --- In MAXIMO@yahoogroups.com<mailto:MAXIMO%40yahoogroups.com>, "Jason Verly" <jason.verly@> wrote:
> > > > >
> > > > > Anyone care to share their update scripts they use?
> > > > >
> > > > > --- In MAXIMO@yahoogroups.com<mailto:MAXIMO%40yahoogroups.com>, "Travis Herron" <therron@> wrote:
> > > > > >
> > > > > > I do too. But I only deal in Maximo, not all the other apps you mention.
> > > > > >
> > > > > > Travis Herron
> > > > > >
> > > > > >
> > > > > >
> > > > > > --- In MAXIMO@yahoogroups.com<mailto:MAXIMO%40yahoogroups.com>, "kermitlong" <clowlong@> wrote:
> > > > > > >
> > > > > > > We do...
> > > > > > > .. in Maximo I usually then run a script to change the reference to the new username.
> > > > > > >
> > > > > > > --- In MAXIMO@yahoogroups.com<mailto:MAXIMO%40yahoogroups.com>, "Jason Verly" <jason.verly@> wrote:
> > > > > > > >
> > > > > > > > When a user in your company has a name change (married, divorce, etc), do you also change their userid's in various applications - AD, Exchange, Maximo, ERP, etc?
> > > > > > > >
> > > > > > >
> > > > > >
> > > > >
> > > >
> > >
> >
>