Sanity Check for Op. Statements

After you click Print on the Operating Statement Filter, the system performs an automatic check of your data files to look for the most common possible errors in your data.

WHAT THE SANITY CHECK DOES

Checks DOI file to make sure all status percents total to 100%.

Verifies that all owners and units exist in the DOI file, in the Owner/Customer and Unit/Well files.

Checks the beginning suspense date for owners that are currently in suspense.

Checks if specified units and owners have already been updated for the specified transaction dates. Prevents duplicate updates.

If the sanity check fails, you will receive a printout of failure codes and the necessary corrective action. Be sure to read the failure code carefully and perform the suggested corrective action.

FAILURE CODES and CORRECTIVE ACTION:

1. The owner has just been released from suspense, but does not have a beginning suspense date in the DOI file. I cannot print the Released Suspense Detail report, since it recaps all transactions from beginning suspense date to the ending suspense date. To correct, use ‘Owners on Suspense' from the Tools for Operating Statements program under JIB menu on your tool bar and enter a beginning suspense date. Suspense dates are cleared after printing the report to avoid conflict with future suspense dates, therefore, to reprint the report a second time, you will need to re-enter the dates.

2. The owner is coded as being on suspense in the DOI file, but has no beginning suspense date entered there. I cannot print the 'Non-Release Suspense Detail’ report, since it recaps all transaction from beginning suspense date to the ending suspense date. To correct, use ‘Owners on Suspense' from the Tools for Operating Statements program under JIB on your tool bar and enter a beginning suspense date. Suspense dates are cleared after printing the report to avoid conflict with future suspense dates, therefore, to reprint the report a second time, you will need to re-enter the dates.

3. WARNING…OWNER FOUND IN DOI FILE BUT NOT FOUND IN OWNER/CUSTOMER FILE. You must add the owner to the Owner/Customer file. Be sure to check the company number, because you may have the owner assigned to an incorrect company number.

4. WARNING…UNIT FOUND IN DOI FILE BUT NOT FOUND IN UNIT/WELL FILE. If the unit is not used on this set of Operating Statements, you may ignore the warning. Otherwise, you must add the unit to the Unit/Well File. Be sure to check the company number, because you may have the owner assigned to an incorrect company number.

5. WARNING…DOUBLE UPDATE. Expenses have already been updated for the beginning transaction date, owner and unit range specified in the filter. This beginning transaction date must be greater than the ending date of the last update (expenses) shown above for this owner & unit range. You should not continue unless you're trying to make an adjustment to the last update.

6. WARNING…DOUBLE UPDATE. Revenue has already been updated for the beginning transaction date, owner and unit range specified in the filter. This beginning transaction date must be greater than the ending date of the last update (revenue) shown above for this owner & unit range. You should not continue unless you're trying to make an adjustment to the last update.

7. WARNING…DOUBLE UPDATE. Revenue and expenses have already been updated for the beginning transaction date, owner and unit range specified in the filter. This beginning transaction date must be greater than the ending date of the last update (revenue & expenses) shown above for this owner & unit range. You should not continue unless you're trying to make an adjustment to the last update.

Created with the Personal Edition of HelpNDoc: Easily create Web Help sites