Kevin_Gray
Active Member
Hi Everyone,
I was wondering if anyone has made any changes to the SECUSR field for adding the system user from the default 10 characters to another value. We have a naming convention for our network and JDE users. It used to be 6 characters and now it has changed to 7. What we decided years ago was to create the system users for each OneWorld user on the SQL side to have a prefix of JDE_ then the same 6 character OneWorld user ID. This made for easier traceability on the SQL server. Since that decision to have the prefix we have changed our naming convention to 7 characters. So now when we create the system user we either have to change the prefix or change the 10 character restriction for the SECUSR field. Has anyone done this? I opened a call with Oracle and they told me that it works as designed and if we wanted it changed we would have to put in a request to Development.
Maybe we should just change the naming convention but I'm just wondering if we could change the restriction.
Has anyone done this?
Kevin
ERP8 SQL 2000 SP3
I was wondering if anyone has made any changes to the SECUSR field for adding the system user from the default 10 characters to another value. We have a naming convention for our network and JDE users. It used to be 6 characters and now it has changed to 7. What we decided years ago was to create the system users for each OneWorld user on the SQL side to have a prefix of JDE_ then the same 6 character OneWorld user ID. This made for easier traceability on the SQL server. Since that decision to have the prefix we have changed our naming convention to 7 characters. So now when we create the system user we either have to change the prefix or change the 10 character restriction for the SECUSR field. Has anyone done this? I opened a call with Oracle and they told me that it works as designed and if we wanted it changed we would have to put in a request to Development.
Maybe we should just change the naming convention but I'm just wondering if we could change the restriction.
Has anyone done this?
Kevin
ERP8 SQL 2000 SP3