Last updated on SEPTEMBER 08, 2016
Applies to:Oracle Demantra Real-Time Sales and Operations Planning - Version 22.214.171.124 and later
Information in this document applies to any platform.
Case 1 Org
In in a Global EBS instance of parent company, the organizations are grouped into one collection group 'A1' & 'A2'. Our org will become part of 'A2' collection group.
When we run Demantra 'Shipment collection' we will have to use A2.
Is there a way to only bring the shipment history of 'PP' Org and stop the data of other Orgs in 'EUR' collection group to flow into Demantra.
Case 2 Site
When running the workflow ‘Download Plan Scenario Data’ in our production environment,
I noticed that the LEVEL4 column (which contains site data) is not being populated for all items in DM.BIIO_OTHER_PLAN_DATA.
When I run the same workflow in a non-production environment, LEVEL4 is populated for all items in DM.BIIO_OTHER_PLAN_DATA
The trading partner data and Demantra data in the non-production environment have been refreshed so that it essentially matches the production database.
Watching the DM.BIIO_OTHER_PLAN_DATA table populate as the workflow runs has narrowed the issue to the CollectData step which executes the stored procedure APPS.MSD_DEM_SOP.LOAD_PLAN_DATA.
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