Hi Mark,
Rights for clearing invalid transactions depends on the type of error encountered - some of them are:
- Invalid Entity (usually a missing location on project properties/financials page)
- Project Inactive
- Resource Inactive
- Rate not found
- Invalid Resource code
So, one will need rights for
- editing projects/project financials and resources (temporarily reactivate, let transactions post, then deactivate
- editing rate matrix (create new entries edit existing entries)
If you are using other investment objects, such as Products, Applications...will need edit access to those, as well. If the resource or project is missing a department or location because the correct department or location is not yet in CA PPM, then department and location navigate/create/edit rights will be needed.
The 'invalid resource code' message might be cleared by temporarily assigning a resource to a different department/location, then setting them back to their correct department/location - this sometimes clears orphaned content in PAC_MNT_RESOURCES table. If these doesn't do it, you may need to run SQL updates directly on the table - means you need access to the database or a DBA with access. This is a rare error - have only seen it a couple times in many years of using CA PPM/Clarity/Niku..
In order to view invalid transactions, try adding the global right "Financial Maintenance - Financial Organizational Structure." For editing matrix, try "Financial Maintenance - Define Matrix."
The other thing you'll find is that the "Invalid Transactions" list view has very limited filtering capabilities - for one, can't filter by OBS. Also, the list view doesn't display info that would be helpful to resolve certain types of errors. For these reasons, we developed our own portlet using filters like OBS, project manager, resource manager, et cetera, and columns including project department, resource department, et cetera.
An invalid transactions may have more than one error - the Invalid Transaction list view (and our custom portlet) only detects one error at a time. So, a transactions may show up as "Rate not found" - then when you fix this error, the same transactions may show again as "Project Closed" - once fixed, it may then show as "Resource Inactive." So, an iterative correction process is needed.
Don't let the invalid transaction error count get too high - very time consuming to correct, later.