Your client requires that their A/P department not pay duplicate supplier Invoices. Which action will prevent users from entering duplicate invoice numbers?

In Oracle JD Edwards EnterpriseOne Accounts Payable, global system controls regarding invoice data integrity are configured within the A/P Constants setup. To enforce strict business rules that prevent duplicate payments, administrators set the "Duplicate Invoice Number Edit" field on the A/P Constants form to issue a hard error (disallow duplicate invoice numbers). When configured to disallow duplicates, the system actively checks incoming voucher entries against existing invoice numbers for the specified supplier across the system. If a duplicate invoice number is detected during entry, the system blocks transaction submission and forces the user to correct the invoice entry before saving the voucher.

Option A: Adding a check digit validates account/invoice formatting rules but does not verify against existing duplicate invoice records.
Option B: Issuing a warning alerts users but still permits them to save and process duplicate invoice entries.
Option D: Duplicate invoice validation is controlled globally via A/P Constants, not through standard voucher entry processing options.

- Oracle Documentation: JD Edwards EnterpriseOne Applications Accounts Payable Implementation Guide, Release 9.2, "Setting Up A/P Constants," Section: Setting Up Duplicate Invoice Number Editing.

- Oracle Documentation: JD Edwards EnterpriseOne Accounts Payable User Guide, Chapter 3: System Constants Setup.