When opening a data form in Oracle | Hyperion Planning, you may experience that Planning returns one of the following error messages:
“Data form x is invalid.”
“The form [xxxxx] is invalid. Check log for details.”
There are a million different ways a Hyperion Planning form can go kaput. We’ve outlined a few potential causes of this error below.
Invalid Member Formulas
In many cases, the data form x is invalid error is caused by member formula errors for members that are referenced in the data form. A member in a form has an invalid member formula and returns the following error in the Essbase Application Log:
Local*Planning*Budget*admin@Native Directory*976*Error*(1012703)*Unknown calculation type ** during the dynamic calculation. Only default agg/formula/time balance operations are handled.
Correct the member formula, and the error will be resolved.
Another potential cause is the use of restricted characters. In one instance, the error was thrown by the data form name containing a “/” between “Revenue” and “Expense”. Once removed and replaced with “&”, the form rendered without error. Lesson learned! For more information on restricted characters in Planning, see: http://docs.oracle.com/cd/E57185_01/AGOHP/apas02.html
A third potential cause is a set limit for the number of blocks that can be requested. The QRYGOVEXECBLK setting in essbase limits the # of blocks a form can pull, and can be increased as needed. For more information, see: https://docs.oracle.com/cd/E12032_01/doc/epm.921/html_techref/config/qrygovexecblk.htm
Another example we’ve seen is the data form referencing substitution variables that are not properly defined. Confirm any variable used in the data form is properly set in Essbase.
The data form x is invalid error can also be caused if the underlying Essbase database is locked up and/or unreachable. Check to confirm Essbase is online and reachable.
If Location Aliases are used, confirm any referenced in the form are appropriately setup and defined. Incorrect location aliases can also cause this error.
Limited data cache settings can also cause this behavior. Increase the application’s data cache in Essbase to test whether data cache limitations are causing the issue.
And one final potential cause of this error, if members referenced in the data form have changed in Hyperion Planning, but have not been refreshed with Essbase. Refresh the application database and try again.
Here are some recommended troubleshooting steps:
- Perform initial fact finding to support root cause analysis:
- Identify any recent changes to application artifacts, such as metadata or data forms, since those may be culprits
- Attempt to run additional data forms to see whether the issue is widespread or isolated
- Recreate the issue and obtain an exact timestamp of when the error occured.
- Check the Planning logs and see if there is an error during that exact timestamp:
- Check the Essbase Application Log in EAS and see if there is an error during that exact timestamp
- Create an Essbase Ad Hoc Analysis grid, duplicating the design of the data form
- Make a copy of the data form in planning. In the copy, try to isolate the source of the issue by deleting rows and columns little by little, and running the form, to see at what point if/when it runs successfully
Still not working? Give us a call. 1-800-EPM-PROS