PLAN Cloud Info: Common Input Template Error Messages

Summary:

This article details some common input (planning) template error messages and how to resolve them. 

Article Sections:

• More Information
  • An error occurred while saving data. Couldn't Store all Entries
  • Storing Failed. Cannot insert the value NULL into column
  • Storing Failed. The merge statement conflicted with the Foreign Key...
  • Storing failed. The merge statement attempted to update or delete the same row more than once
  • CreatedBy, UpdatedBy, CreatedOn, UpdatedOn are not getting updated
• Properties

More Information:

"An error occurred while saving data. Couldn't Store all Entries"

• Make sure that all dimensions being stored back in this template exist in their respective dimensions. 
• Make sure that your budget settings are unique enough. 

Typically this error indicates that your budget settings are not detailed enough and our Save Data routine is not finding unique enough transactions. For example, below is a diagram of a potential setup in the CorpDemo:

• Row 2 already exists in your database
• Row 3 gets added via a budget template, your budget template is not storing to currency
• Row 3 successfully saved the first time because its a unique transaction (not storing to currency)
• When you attempt to store again, it fails. This is because without currency, the application does not know whether to update row 2 or row 3. 

Resolution: Review your budget settings and make sure they include all dimensions that are relevant to existing data in your Module. These dimensions need to be in the Mandatory Fields section. 

"Storing Failed. Cannot insert the value NULL into column"

Users will receive this error message because a value they are storing does not exist in the respective dimension. Certain modules have required dimensions. As an example, the General Ledger module has Account, Entity, Scenario and TimePeriod as mandatory dimensions. If in your budget template, you provide an account code that does not exist in your Account dimension, users will receive this error. 

Resolution: Ensure that all dimension codes being stored back in the template are valid and exist in their respective dimension.

"Storing Failed. The merge statement conflicted with the Foreign Key..."

Similar to the above, users are getting this error message because a value being stored back does not exist for a mandatory dimension. 

Resolution: Ensure that all dimension codes being stored back in the template are valid and exist in their respective dimension.

"Storing failed. The merge statement attempted to update or delete the same row more than once"

Users will receive this error message due to their input template having the same data twice. 

Resolution: Ensure all dimension codes being stored back in the template exist in their respective dimension. Then review your input template to make sure that no duplicates are being stored. A duplicate is determined by those dimensions that are part of the mandatory dimensions in your budget settings. 

"CreatedBy, UpdatedBy, CreatedOn, UpdatedOn Are Not Getting Updated"

By default, the application will add information about who created/updated a transaction and when.

Resolution: If these fields do not appear updated in your SolverDW database, update your integration package to the latest version. 

Properties:

Cloud