Duplicate Invoice Tests

From Opentaps Wiki

Jump to: navigation, search

Contents


Creating Invoice with Reference Number

Action 1 Log in to financials as demofinadmin and go to Receivables tab. Create a Sales Invoice to Demo Customer with no reference number.

Result 1 Invoice created successfully.

Action 2 Create another sales invoice to DemoCustomer with a reference number "test".

Result 2 Invoice created successfully

Action 3 Create another sales invoice to DemoCustomer with reference number "test".

Result 3 An error message appears "Warning: Invoice ${invoiceId} has the same reference number. Are you sure you want to use this reference number?". The invoiceId is the one created in the last action (2). The create button now reads Force Create.

Action 4 Click Force Create and when the popup confirmation appears, select OK.

Result 4 Invoice created with reference number "test".

Action 5 Create another sales invoice to DemoCustomer with reference number "TEST"

Result 5 Same warning appears. The reference numbers are checked ignoring case.

Action 6 Create a sales invoice to DemoAccount1 with reference number "test".

Result 6 Invoice created successfully without any force complete.

Action 7 Create another sales invoice to DemoAccount1 with reference number "test".

Result 7 An error message appears "Warning: Invoice ${invoiceId} has the same reference number. Are you sure you want to use this reference number?". The invoiceId is the one created in the last action (6). The create button now reads Force Create.

Action 8 Change the reference number to "test2", then click Force Create and when the popup confirmation appears, select OK.

Result 8 Invoice created with reference number "test2".

Action 9 Create another sales invoice to DemoAccount1 with reference number "test".

Result 9 An error message appears "Warning: Invoice ${invoiceId} has the same reference number. Are you sure you want to use this reference number?". The invoiceId is the one created before the last action (6). The create button now reads Force Create.

Action 10 Change the reference number to "test2", then click Force Create and when the popup confirmation appears, select OK.

Result 10 An error message appears again "Warning: Invoice ${invoiceId} has the same reference number. Are you sure you want to use this reference number?". The invoiceId is the one created in the last action (8). The create button now reads Force Create. The idea here is you can't sneak a different duplicate reference number when pressing [Force Update].

Action 11 Click Force Create and when the popup confirmation appears, select OK.

Result 11 Invoice created with reference number "test2".


Updating Invoice with Reference Number

Action 1 Pick a sales invoice with reference number "test" and erase it. Press Update.

Result 1 Update successful and invoice reference number removed.

Action 2 Change the reference number back to "test"

Result 2 Warning message about duplicate reference number appears and button changes to Force Update.

Action 3 Press Force Update.

Result 3 Invoice updated to reference number "test".

Action 4 Change some fields in the invoice header. Leave the reference number as "test", press Update.

Result 4 Invoice updates without force update warning. This is because the reference number has not changed.

Action 5 Change reference number to something else, "testing".

Result 5 Invoice updates without force update.

Action 6 Pick the sales invoice to DemoCustomer that has no reference number. Change the reference number to "testing". When the force update warning comes up, change the reference number to "test" and press Force Update.

Result 6 Warning about duplicate reference number comes up again. Invoice is not updated. The idea here is you can't sneak a different duplicate reference number when pressing Force Update.

Repeat Tests

Repeat tests for the following invoice types

  1. Commission Invoices
  2. Purchase Invoice
  3. Partner Invoice


© Open Source Strategies, Inc. Development of this documentation site is sponsored by Open Source Strategies, Inc.
Help support opentaps with a subscription to this documentation site.