Use Checkout to search the Backflow Management database for errors.

Step 1: Run Checkout

Search the database for errors.

Do this...

1. Open Connect Backflow Management > Organization > Checkout.

2. Set up the Selection Criteria.

The processing time to complete Checkout depends on the number of assembly IDs and the number of Checkout options that have been selected. 

4. Click GO (CTRL+G).

The routine runs. It may take a few minutes depending on how many options you have selected.

Step 2: Review the Checkout report

Use the instructions on the Checkout report to fix the errors in the database.  Click on the link to learn more.

1. Duplicate action codes
2. Missing action code
3. Missing index
4. There are x notifications older than MM/DD/YYYY
5. There are x assembly activities older than MM/DD/YYYY
6. There are x inactive assemblies
7. Locations without an active customer
8. Duplicate assembly sequence numbers at a location
9. Testing months that do not match the install month
10. Backflow testing activity with the same test year
11. Backflow testing activity without a test year
12. Backflow non-testing activity with a test year
    
    

Step 3: Rerun the Checkout report

When you're done fixing the errors listed on the Checkout report, rerun the Checkout report to make sure all of the errors have been resolved. When the Checkout reports that the database is error free, then you're done.

Checkout Options

Verify an active customer exists at each location

Do you want to verify an active customer exists at each location?

• Yes, I want to search for active customers at locations with an active assembly. Select the option to Verify an Active Customer Exists at Each Location.

• No, I want to skip this search. Clear the option to Verify an Active Customer Exists at Each Location.

How do I fix this error?

• If the customer is active but the system reports an active customer is missing, use Customers > Modify Existing Customers to change the customer's status to active.

• If the wrong customer is tied to the location, use Customers > Modify Existing Customers to update the customer's service address. .

Check for duplicate assembly sequence numbers at a location

Do you want to check for duplicate assembly sequence numbers at a location?

• Yes, I want to search for locations with assemblies that have been assigned to the same sequence number. Select the option to Check for Duplicate Assembly Sequence Numbers at a Location.

• No, I want to skip this search. Clear the option to Check for Duplicate Assembly Sequence Numbers at a Location.

How do I fix this error?

• Use Assemblies > Modify Existing Assemblies to assign a unique sequence number to the assembly that has been assigned to the duplicate sequence.

Verify the testing month matches the install month

Note: This check is optional. If the testing month can be adjusted from the original installation date, then run this check.

Do you want to verify that the testing month matches the install month?

• Yes, I want to verify the testing month matches the install month. Select the option to Verify the Testing Month Matches the Install Month.

• No, I want to skip this search. Clear the option to Verify the Testing Month Matches the Install Month.

How do I fix this error?

• Use Assemblies > Modify Existing Assemblies to change the Testing Month or Original Installation Date to the correct month.

Check for backflow testing activity with the same test year

Do you want to check for backflow testing activity with the same testing year?

• Yes, I want to search each year for multiple backflow testing activity. Select the option to Check for Backflow Testing Activity with the Same Testing Year.

• No, I want to skip this search. Clear the option to Check for Backflow Testing Activity with the Same Testing Year.

• If one of the testing activities is for a different test year, use Assemblies > Modify Existing Assembly Test Results to modify the test year for the testing results.

• If the testing activity is for the same testing year than the testing results does not need to be adjusted.

Check for backflow testing activity without a test year

Do you want to check for backflow testing activity without a testing year?

• Yes, I want to verify there are no blank testing years for the backflow testing activity. Click to select the option to Check for Backflow Testing Activity Without a Testing Year.

• No, I want to skip this search. Clear the option to Check for Backflow Testing Activity Without a Testing Year.

• If the testing activity is recorded without a year, then use Assemblies > Modify Existing Assembly Test Results. You can assign the test year after the appropriate testing results have been selected.  

Check for backflow non-testing activity with a test year

Do you want to check for backflow non-testing activity with a testing year?

• Yes, I want to search records where non-testing activity has been recorded with a testing year. Select the option to Check for Backflow Non-testing Activity with a Testing Year.

• No, I want to skip this search. Clear the option to Check for Backflow Non-testing Activity with a Testing Year.

• If the testing year is missing on a non-testing activity, please contact customer service for assistance to modify data.

Checkout Report Errors

Duplicate action codes

There should only be one action code for each action code type. The following action codes should not have the same action code type. To fix this error, change the action code type so the action code is assigned to an action code type that is not assigned to another action code.

Missing action code

The application is missing a required application code type. The following code types must exist to be able to perform all possible assembly activities. To fix this error, add the action type that's listed on the report.

Missing index

The following tables are missing at least one index.

There are x notifications older than MM/DD/YYYY

It's a good idea to keep notifications for 60 months. However, you should delete notifications that are older than 60 months to improve application performance. To delete old notifications, run Delete History.

There are x assembly activities older than MM/DD/YYYY

It's also a good idea to keep assembly activities for 60 months. Like notifications, you should delete assembly activities that are older than 60 months. To delete old assembly activities, run Delete History.

There are x inactive assemblies

These assemblies have a removal date and no related assembly activity or notification history. To fix this error, run Delete Inactive Assemblies to remove the inactive assemblies.

Locations without an active customer

This is a list of locations with a backflow assembly that do not have an active customer. You cannot send notifications without an active customer.

Duplicate assembly sequence numbers at a location

Each assembly at a location should have a unique sequence number. This is a list of assemblies at the same location with the same assembly sequence number. The assembly and activity for the assembly need to be corrected.

Testing months that do not match the install month

The testing month on the assembly does not match the month from the original installation date. If your organization requires the same testing month as the original installation date, use Modify Existing Assemblies to correct it.

Backflow testing activity with the same test year

An assembly should only be tested once each year. The assemblies in the list have multiple tests recorded in the same year. To fix the error, use Modify Existing Assembly Test Results to correct the test year.

Backflow testing activity without a test year

Testing activity should have a test year. This is a list of assemblies that should have a test year. To fix the error, use Modify Existing Assembly Test Results to add a test year.

Backflow non-testing activity with a test year

Non-testing activity should not have a test year. This is a list of assembly activities that should not have a test year.