richslaney
Member
Hi,
Were are on JDE EnterpriseOne 9.2 (9.2.6.3) on OCI and I have a Development issue and I wondered if anyone could help or has any ideas.
I've created a detailed 'User Password / Role / Object Inquiry' using multiple Power Forms and Subforms to provide a nice front end for CNC and Management to look at User related details and to also satisfy Auditor questions etc.
One of the elements of Information wanted to display in the Grid is the 'Last Logon Date and Time' and the 'Last Logoff Date and Time'to help decide if the user should be disabled etc.
I know F9312 has all the sign on history but this isn't a good fit to add into my Business View as there are many, many records per Action per day and I need the last Logon Time and the Last Logoff Time which are again spread over multiple records.
To be honest, I find it odd that JDE doesn't simply have a this info to the User in say the F0092, F00921 or F00922 or F98OWSEC.
So, I created a business function to get this at runtime of my Inquiry from F9312, but the performance was not acceptable when running though the Grid to load the forms. Also, we want it to be searchable so I wanted this to be in the Business View instead of fetching the value.
My solution was to create a new table which for a 'User' held a single record which contained the Users 'Last Logon Date and Time' and 'Last Logoff Date and Time' and therefore could be 'joined' into my business view. I created a UBE to also update my new table for all records at once, and then the Inquiry showed this info as required nicely, but I need the update of this data to be dynamic.
So, I then added Insert and Update Triggers on F9312 to call my new Business Function to get the info from F9312 and update / insert the details in my new table when F9312 is being updated.
Issue is that if I 'sign off' and 'sign on', and look in my new Table and there are no records created although F9312 has been updated to contain the information.
Therefore, I assume that F9312 is NOT being updated inside JDE and therefore the JDE triggers are not being executed.
Is this the case.. Is the logon Process outside of the JDE functionality and therefore Triggers in F9312 are pointless?
What about the F9312T as well? Does anyone know when that is created as that also seems to be updated with pretty much identical info a F9312 so wondering if it's created at the same time as F9312 or when inside JDE so maybe triggers may work?
I have turned on Debug logging and I don't see anything for 'F9312' or 'F9312T' in the logs again leading me to believe this is being done outside of the JDE infrastructure.
If there another function / process in JDE I could try to call my BSFN's to create my records when a user logs on instead of a Trigger on F9312?
I need something the User always does when logging on, as I want the load (tiny) of generating the Users 'Last Logon Date and Time' and 'Last Logoff Date and Time' to be on each user instead of having to process many thousands of records.
Open to suggestions (avoiding DB Triggers if I can) from you clever lot.
Many thanks,
Rich Slaney.
EnterpriseOne Developer
Were are on JDE EnterpriseOne 9.2 (9.2.6.3) on OCI and I have a Development issue and I wondered if anyone could help or has any ideas.
I've created a detailed 'User Password / Role / Object Inquiry' using multiple Power Forms and Subforms to provide a nice front end for CNC and Management to look at User related details and to also satisfy Auditor questions etc.
One of the elements of Information wanted to display in the Grid is the 'Last Logon Date and Time' and the 'Last Logoff Date and Time'to help decide if the user should be disabled etc.
I know F9312 has all the sign on history but this isn't a good fit to add into my Business View as there are many, many records per Action per day and I need the last Logon Time and the Last Logoff Time which are again spread over multiple records.
To be honest, I find it odd that JDE doesn't simply have a this info to the User in say the F0092, F00921 or F00922 or F98OWSEC.
So, I created a business function to get this at runtime of my Inquiry from F9312, but the performance was not acceptable when running though the Grid to load the forms. Also, we want it to be searchable so I wanted this to be in the Business View instead of fetching the value.
My solution was to create a new table which for a 'User' held a single record which contained the Users 'Last Logon Date and Time' and 'Last Logoff Date and Time' and therefore could be 'joined' into my business view. I created a UBE to also update my new table for all records at once, and then the Inquiry showed this info as required nicely, but I need the update of this data to be dynamic.
So, I then added Insert and Update Triggers on F9312 to call my new Business Function to get the info from F9312 and update / insert the details in my new table when F9312 is being updated.
Issue is that if I 'sign off' and 'sign on', and look in my new Table and there are no records created although F9312 has been updated to contain the information.
Therefore, I assume that F9312 is NOT being updated inside JDE and therefore the JDE triggers are not being executed.
Is this the case.. Is the logon Process outside of the JDE functionality and therefore Triggers in F9312 are pointless?
What about the F9312T as well? Does anyone know when that is created as that also seems to be updated with pretty much identical info a F9312 so wondering if it's created at the same time as F9312 or when inside JDE so maybe triggers may work?
I have turned on Debug logging and I don't see anything for 'F9312' or 'F9312T' in the logs again leading me to believe this is being done outside of the JDE infrastructure.
If there another function / process in JDE I could try to call my BSFN's to create my records when a user logs on instead of a Trigger on F9312?
I need something the User always does when logging on, as I want the load (tiny) of generating the Users 'Last Logon Date and Time' and 'Last Logoff Date and Time' to be on each user instead of having to process many thousands of records.
Open to suggestions (avoiding DB Triggers if I can) from you clever lot.
Many thanks,
Rich Slaney.
EnterpriseOne Developer