A project can't be opened in OWB after creating a requisition on a role with 0% Default Allocation

Document ID : KB000096360
Last Modified Date : 16/05/2018
Show Technical Document Details
Issue:
After creating a requisition for a role that has 0% default allocation, the project cannot be opened in OWB.

Steps to Reproduce
  1. Create a new project 
  2. Go to Team tab and add a role. Make sure that the default allocation is set to 0% (as well as Average allocation, Allocation, ETC...) 
  3. Create a new task with ETC. Assign the role (so that the role ends with ETC for the assignment) 
  4. Go to Team tab and execute action "Allocate from Estimates" on the role 
  5. Execute action "Create Requisitions" on the role (Create and Open) 
  6. Go to Team > Requisitions and open the newly created Requisition. 
  7. On the Resources tab, add a resource 
  8. Book the requisition 
  9. Go to the Team tab and confirm that the resource has been added to the team. 
  10. Open the project in OWB 
Expected Results: OWB opens the project 
Actual Results: OWB shows the error "Unable to open project XXXX. Operation Disallowed: AllocCurve must be of type RATECURVE".
Environment:
This issue has been observed in CA PPM 15.2.
Cause:
This issue has been reported to Engineering as DE37207.
Resolution:
This issue has been fixed in CA PPM 15.4.1.

As a temporary workaround, the project can be opened in OWB after selecting all resources in the team tab, then choose the action "Set Allocation", then set "Default Allocation %" to "0" and check "Clear existing allocation segments", then Save.