Hi everyone,
I am currently investigating the problem of having to validate user data entry on Order Templates. We have investigated the use of Action Checks but Oracle has confirmed that Action Checks are not supported with Order Templates - which is really surprising and disappointing.
However, I have stumbled across a function called User Exit - apparently, the object persistence engine will refer to a package called pkg_user_exit to check if there is any problem persisting an object.
Configuration and Administration > System Administration > User Exit
Looking at the package, it looks like there is a way to validate data BEFORE the object is persisted - and throw custom error messages.
Has anyone used this functionality before? Any best practices for this functionality and what is the difference between User Exit and Action Checks?
Thanks!
Ian
I am currently investigating the problem of having to validate user data entry on Order Templates. We have investigated the use of Action Checks but Oracle has confirmed that Action Checks are not supported with Order Templates - which is really surprising and disappointing.
However, I have stumbled across a function called User Exit - apparently, the object persistence engine will refer to a package called pkg_user_exit to check if there is any problem persisting an object.
Configuration and Administration > System Administration > User Exit
Looking at the package, it looks like there is a way to validate data BEFORE the object is persisted - and throw custom error messages.
Has anyone used this functionality before? Any best practices for this functionality and what is the difference between User Exit and Action Checks?
Thanks!
Ian
Comment