Some little tips about Manual test Plans
There was a migration of info types during the transition of GRC support packages to enable multilingual test steps in the test plan.
I started the scenario using a system with the following configuration:
- GRC 10.1 SP level 06.
The test steps are stored in table HRP5327:
The manual test Plan is stored like any other object in HRP1000:
A system upgrade was performed. Now my system configuration is like below:
- GRC 10.1 SP level 09.
In NWBC, the test plan is created:
However, my test steps are not there anymore:
If I create manually a new test step, it will show up in the grid.
New test step added:
Checking again in table HRP5327, the object is not there. However, the object was stored in table HRP5355.
Do not add any new items manually before executing the program.
In this case, a copy from the old database must be performed to copy all existing test steps to the new database.
The program GRPC_UPLOAD_HRP5327_TO_HRP5355 must be executed.
The second step is to choose a language. You can run in simulation mode for the first time.
Execution was successful:
After the execution, the record was moved to table HRP5355.
The test steps are shown in the front-end again:
The steps mentioned above can be found in SAP note 1949265 - GRC PC: How to enable multilingual test steps in test plan.
Summary:
After the GRC 10.0 SP-14 / 10.1 SP-07 implementation, the program GRPC_UPLOAD_HRP5327_TO_HRP5355 must be executed only once to copy all existing test steps from old database table HRP5327 to new database table HRP5355.
MDUG is uploading the objects into table HRP5327.
To resolve it, implement the note below:
- 2124607 to use MDUG to upload test step data after 10.0 SP-14 / 10.1 SP-07 upgrade.