Can the Duplicate Invoice Number Check in the AP Project be Moved to the UserExitInvoiceNumberValidate Event as to set the InvoiceNumber Field to Invalid when Validating that Field instead of Document Validation? (Doc ID 2335262.1)

Last updated on SEPTEMBER 29, 2022

Applies to:

Goal

In the AP 1007G project, the duplicate invoice number check has been implemented and it works.  To change the behavior, the code to call the duplicate invoice number check has been moved from the UserExitDocumentValidate event to the UserExitInvoiceNumberValidate event in order to perform the duplicate check whenever the InvoiceNumber field is validated - instead of when all fields have been validated.  However when validating the InvoiceNumber field remains valid even after throwing an error message.  How can the duplicate Invoice Number check be moved in the code so that the check will leave the Invoice Number field as invalid after the check finds a duplicate record?
 

Solution

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.