d.shirtliff
Member
Hello smart JDE folks!
Currently on App 9.2 and Tools 9.2.5.6 running on RHEL and Oracle DB, and trying to put together some policies/strategies around object usage tracking in our production environment, and I figured some of y'all may have some excellent insight into what direction I should be leaning. We're currently running tracking on all objects (APP, UBE, BSFN) with a handful of UBEs and APPs excluded (e.g. I don't think I care to track how often P986162 "Printer selection before printing a UBE" is called).
1. Are many of you running Object Usage Tracking in production? We've tapped it to pull some time-of-day usage stats, and I've used it to monitor testing progress a couple times in PY, so I know there's going to be use cases for us where it provides value. I also understand you can use it as part of ESU installs for more insight into impact. Is this actually useful in your organization?
2. Are you running it wide open, or are you maintaining a list of excluded objects? Should I care that B1100007 "Decimals Trigger Get by CO CRCD" was called 274 million times in May 2023? Am I potentially going to be cursing my own name 1, 2 years down the road if I exclude it?
3. What kind of retention policy are you following for records in the F98902 Summary table? I don't believe there's a purge job for this table like there are for the two Detail tables, but I expect that it's going to end up being one of those big tables; not like F42199 or F0911 big, but probably top 20 in the DB. On the other hand, disk space is generally easily accessible in my org, so should I even care if it gets bigger? If it being big isn't going to harm performance, we can always chuck another data file at it and let it go.
4. If we end up landing on a policy to retain X years of usage, does it make the most sense to purge based on the OSOTYEAR column, or is there perhaps a better option?
Thanks kindly for any and all insight and guidance!
David
Currently on App 9.2 and Tools 9.2.5.6 running on RHEL and Oracle DB, and trying to put together some policies/strategies around object usage tracking in our production environment, and I figured some of y'all may have some excellent insight into what direction I should be leaning. We're currently running tracking on all objects (APP, UBE, BSFN) with a handful of UBEs and APPs excluded (e.g. I don't think I care to track how often P986162 "Printer selection before printing a UBE" is called).
1. Are many of you running Object Usage Tracking in production? We've tapped it to pull some time-of-day usage stats, and I've used it to monitor testing progress a couple times in PY, so I know there's going to be use cases for us where it provides value. I also understand you can use it as part of ESU installs for more insight into impact. Is this actually useful in your organization?
2. Are you running it wide open, or are you maintaining a list of excluded objects? Should I care that B1100007 "Decimals Trigger Get by CO CRCD" was called 274 million times in May 2023? Am I potentially going to be cursing my own name 1, 2 years down the road if I exclude it?
3. What kind of retention policy are you following for records in the F98902 Summary table? I don't believe there's a purge job for this table like there are for the two Detail tables, but I expect that it's going to end up being one of those big tables; not like F42199 or F0911 big, but probably top 20 in the DB. On the other hand, disk space is generally easily accessible in my org, so should I even care if it gets bigger? If it being big isn't going to harm performance, we can always chuck another data file at it and let it go.
4. If we end up landing on a policy to retain X years of usage, does it make the most sense to purge based on the OSOTYEAR column, or is there perhaps a better option?
Thanks kindly for any and all insight and guidance!
David