Demantra Solutions - EBS (MOSC)

MOSC Banner

Publish to ASCP performance

We have a forecast publish scheduled on 3 nights from demantra to ASCP.

The first night it runs successfully and completes in less than 15 mins while on the remaining nights it takes over 3 hours. Data volume is almost the same all the 3 nights and same series is being used for forecast publish.

Demantra version is 7.3.1.4 and the forecast publish workflow is triggered using a concurrent request from ASCP.

The collaborator log shows that the demantra workflow is being triggered immediately when the concurrent request passes the command to it.

The first step of the publish workflow is the standard export integration that creates the view BIEO_XXX and this step is completing within a second all the 3 days.

Howdy, Stranger!

Log In

To view full details, sign in to My Oracle Support Community.

Register

Don't have a My Oracle Support Community account? Click here to get started.

Category Leaderboard

Top contributors this month

EBS Demantra Tags

New to My Oracle Support Community? Visit our Welcome Center

MOSC Help Center