Unifier: Why Is a System Error Being Thrown, or Functionality Not Working, Against One Data Object and Not Others in A Non-Production Environment?
(Doc ID 1908728.1)
Last updated on JANUARY 04, 2024
Applies to:
Primavera Unifier - Version 9.9.1 and laterPrimavera Unifier Cloud Service - Version 9.9.1 and later
Information in this document applies to any platform.
Goal
Why is a system error being thrown, or functionality not working, against one data object and not others in a non-production environment?
Examples:
A Business Process (BP) used to work and now it doesn't. This can include a system error, Alert or Notification suddenly being thrown or functionality within, or dependent on, the BP suddenly stops working.
Functionality used to work in in one type of Project/Shell and now it doesn't, or no longer working in historical data objects. This can include the auto-population of data, the rolling up of values/entries through various modules within the system, required entries not being populated, formulas not calculating as expected, or other.
Old/historic design/configuration is being observed in historical data objects but not new data objects.
Solution
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
Goal |
Solution |