Quality Management RM traceability report issue
We have a problem running Quality Management (QM) requirement traceability reports in our distributed v.4.0.4 CLM environment. There is no value (requirement project) to select from in the Project* parameter box. If we try to run the report without this value, we get the obvious error - Missing Required Parameter: Project . Other types of reports run just fine.
We see the same behaviour with other lifecycle projects in the same distributed v.4.0.4 environment and also on our all-in one v.4.0.6 test server
The following have been verified:
The data warehouse jobs for all applications run successfully
No errors reported in the ETL log files
The project area associations are properly configured
The DBA has also verified and confirmed that the RM projects are listed in both the RIODS.PROJECT and RIDW.VW_REQUIREMENT tables
Are there pre-conditions or something missing in our projects configuration in order to make these Requirements Traceability reports work?
Thank you,
Pierre
Accepted answer
Could you please ask your DBA to verify the view RIDW.VW_REQUIREMENT_TESTPLAN_LOOKUP? If no records show up, you may want to verify the links between the Requirements <-> Requirement Collections <-> Test Plans.
If there are records, but the Projects linked to those requirements don't appear on the parameter list on the report, then please contact IBM support so they can take a closer look at your application.
Thank you,
Clara Forero
Comments
Hello Clara,
Your suggestion resolved the issue.
We configured and verified the links between the requirements - requirements collections - test plans
We forced the data warehouse jobs for all applications
We ran a Quality Mangement requirement traceability reports
The requirements project is now available from the Project* parameter box
Thank you for your assistance
Pierre Friend
Comments
Kevin Ramer
Nov 07 '14, 2:15 p.m.How many warehouse db are in play ? There will be (should be) 1 for each jts you have. Which is another way of saying that unless QM/RM are managed in same JTS it's likely there are different data warehouse db.