My Oracle Support Banner

Unable To Save Edited Risk Threshold Range Values When Using "Schedule Impact By Value" Type (Doc ID 2249016.1)

Last updated on APRIL 06, 2020

Applies to:

Primavera P6 Enterprise Project Portfolio Management Cloud Service - Version 16.2.4.0 and later
Primavera P6 Enterprise Project Portfolio Management - Version 16.2.4.0 and later
Information in this document applies to any platform.

Symptoms

ACTUAL BEHAVIOR
---------------
Unable to save Risk Threshold Data when using "schedule impact by value" type.

EXPECTED BEHAVIOR
-----------------------
The edited Risk Threshold Data should save.

STEPS
-----------------------

  1. Go to Administer, Enterprise Data, Risks, Risk Thresholds.
  2. Click to add a new threshold, change the type to 'Schedule Impact by Value'.
  3. Change the levels to '2' and save.
  4. Change the High value to '10'.
  5. Click 'Save'.
  6. The High value should save with the value of 10, but it reverts to the default value.

BUSINESS IMPACT
-----------------------
The issue has the following business impact:
Due to this issue, users cannot save Risk Threshold Data

Changes

 

Cause

To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!


In this Document
Symptoms
Changes
Cause
Solution
References


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.