Last updated on SEPTEMBER 26, 2017
Applies to:Oracle Demantra Demand Management - Version 7.3.0 and later
Information in this document applies to any platform.
From many items that were forecasted, the customer needs to remove some. How it could be achieved? Are there any documents related to this?
The way demantra behaves is normally triggered by *_data tables but please take into consideration deletion process is not supported.
You will need to take a backup, remove corresponding sales_data rows, mdp_matrix should be removed consequently by the foreign key.
You should also review next update on normal maintenance operations after that. Please fully test your main operations after that, before migrating, and keep a backup for further reference
1. Recover from backup before loading is the safest way.
-- the following can only be run on TEST by consultants, not for production - Data Cleanup Script - ref Implementation Guide
2. all other methods are not supported: -- remove from sales_data, mdp_matrix
Always use Remove combination from worksheet environment, same for user passwords editing - always use either links for Admin from Collaborator Workbench, or Business Modeler definitions
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms