Last updated on JUNE 06, 2016
Applies to:Oracle Demantra Demand Management - Version 7.1.1 and later
Information in this document applies to any platform.
Users are trying to publish the Demantra forecast back to the MSD (Old Oracle Demand Planning) in order to be able to use if for an ASCP plan run. However the forecast is not getting populated into table MSD_DP_SCN_ENTRIES_DENORM, so the forecast will not be seen in the list of values for ASCP to choose from. In debugging the program MSD_DEM_UPLOAD_FORECAST (msddemufs.pls , msddemufb.pls) we found this program is expecting the VALIDATION_ORG_ID field in the MSC_APPS_INSTANCES table to be populated. This field can not be setup at the front end when defining the instances. In the user's case the column VALIDATION_ORG_ID field in the MSC_APPS_INSTANCES table is null.
Users updated this field on the back end to see if the forecast upload works. The upload worked. But when they ran the ASCP collection next time, the VALIDATION_ORG_ID field became NULL.
1. Generate the forecast via the Demantra Analytical Engine
2. Try to upload the forecast with workflow MSD_DEM_UPLOAD_FORECAST
3. Review table MSD_DP_SCN_ENTRIES_DENORM and no demantra forecast records are found
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
Million Knowledge Articles and hundreds of Community platforms