Validate Project Transactions
This page describes the Validate Project Transactions report in the Job Costing module.
---
The Validate Project Transactions report is a tool that you can use to check that all subsystem records (Time Sheets, Purchase Invoices, Expenses, Deliveries and Returned Goods, Activities and Stock Depreciation records) that are connected to Projects have corresponding Project Transactions, and that all Project Transactions have corresponding subsystem records.
- Period
- Paste Special
Reporting Periods setting, System module
- The report period.
- If you choose the Project Transaction exists option below, the report will check subsystem records from this period to ensure each one has a corresponding Project Transaction or Project Transactions.
- If you choose the Subsystem record exists option below, the report will check Project Transactions from this period to ensure each one has a corresponding subsystem record or row in a subsystem record.
- Project
- Paste Special
Project register, Job Costing module
- Range Reporting Alpha
- Enter a Project Code here if you need to check the Project Transactions for a particular Project. If this field is blank, Project Transactions from all Projects will be checked. You can also enter a range of Project Codes separated by a colon (:).
- Test if
- The report can include one or both of these two sections, as follows:
- Project Transaction exists
- The report will find subsystem records entered during the report period that you have connected to the Project(s) specified above. It will then check that a corresponding Project Transaction exists. If there is no such Project Transaction, the subsystem record will be listed in the report.
- If the report shows that a Project Transaction is missing, you will be able to re-create it by running the 'Restore Project Transactions' Maintenance function in the Database Maintenance module.
- Subsystem record exists
- The report will find Project Transactions belonging to the Project(s) specified above that were created during the report period. It will then check that a corresponding subsystem record exists. If there is no such record, the subsystem register and transaction number (e.g. Time Sheet Number, Purchase Invoice Number, etc) will be listed in the report, taken from the Project Transaction.
You must select at least one of these options, otherwise the report will be empty.
- Check Transactions from
- Use these options to choose which subsystem register(s) are to be checked.
- You must select at least one of these options, otherwise the report will be empty.
---
Reports in the Job Costing module:
Go back to:
Introduction to Reports in the Job Costing Module
