Demantra Forecast Publication To APCC For Reporting Taking Excessive Amount Of Time
(Doc ID 1486060.1)
Last updated on SEPTEMBER 08, 2016
Applies to:Oracle Demantra Demand Management - Version 7.3.1 to 12.2 [Release 7.3.0 to 12.2]
Oracle Advanced Supply Chain Planning - Version 12.1.3 to 12.2 [Release 12.1 to 12.2]
Information in this document applies to any platform.
Customer mentions that Publishing Demantra Consensus forecast at ITEM-ORG-SITE level to APCC is taking excessive amount of time on a production sized instance.
They are using Standard processes to publish Demantra forecast to APCC for reporting.
"Assign Plan Name" request takes 2 hours plus for publishing data from DENORM table to APCC's MSC table.
As per the TKPROF output there are some events that are taking a long time , as below
1. line 569 -->elapsed time 965.58---> SQL ID: gjwgd0rptq44g-->DELETE FROM MSD_DP_SCN_ENTRIES_DENORM ....
2. line 835 -->elapsed time 1913.35--->SQL ID: 3vj44rbtkuyxr -->UPDATE MSD_DP_SCN_ENTRIES_DENORM SET SCENARIO_ID = :B3...
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document