Validation failed
This topic describes scenarios that can cause the validation to fail. After the issue has been corrected, you should run the validation process again to verify that all issues have been corrected.
Missing configuration data company in target environment
The package to be deployed contains data of one or more Infor LN companies in the source environment. A failure message is displayed if one or more companies of the package are not available in the target environment. The exact message can be found in logfile log.dcm for the LN tenant in the $BSE_APPDATA/log folder. The message will look like this: “Configuration data of company '51' cannot be imported because the company is not defined as configuration data company on the target environment and also no company mapping exists."
The solution is to add the company as a configuration data company in the target environment, or to add a company mapping from the source company to the target company.
Configuration data package too new
A configuration data package is created in a specific Infor LN version. A failure message is displayed if a newer package is deployed in an older Infor LN version. The exact message can be found in logfile log.dcm for the LN tenant in the $BSE_APPDATA/log folder. The message will look like this: “Configuration data package cannot be imported in target environment 'ce01068' because it is created in a newer environment 'ce01069'.”
The solution is to upgrade the target environment to the newer version, or to clear the Validate Version Compatibility check box in the Configuration Data Management Parameters (ttdcm0100m000) session (if you are absolutely sure).