w2vijay
Well Known Member
Hi All,
Scenario- At the sales point multiple salesmen create sales orders and they get some commission for each sales. When user "A" signed into JDE created sales order and moved away. User "B" comes and tries to create sales order in the already active session of user "A". In this case sales order is created with user A which should not.
To avoid this everytime when user access sales order entry application P4210, should ask for password again. So when user B provides his password. JDE should throw error and force him to logoff and login with his userid.
So can we authenticate the user at application level. Does the password present in the table F98OWSEC. How to match the password. Please let me know your thoughts on this.
Scenario- At the sales point multiple salesmen create sales orders and they get some commission for each sales. When user "A" signed into JDE created sales order and moved away. User "B" comes and tries to create sales order in the already active session of user "A". In this case sales order is created with user A which should not.
To avoid this everytime when user access sales order entry application P4210, should ask for password again. So when user B provides his password. JDE should throw error and force him to logoff and login with his userid.
So can we authenticate the user at application level. Does the password present in the table F98OWSEC. How to match the password. Please let me know your thoughts on this.