Demantra Solutions - EBS (MOSC)

MOSC Banner

What parameters should be set to shorten the run time on Shipping & Booking Collection?

in Demantra Solutions - EBS (MOSC) 2 commentsAnswered

Currently using EBS/ASCP/Demantra version 12.2.4. Due to sheer data volume, the Shipping and Booking Collection (run weekly on Sunday evenings) is taking 8-9 hours to complete, and appears to be pulling data as far back as 6 months for shipments (equating to over 3/4 million records). This run time is negatively impacting the availability of the planning data to start each week. The settings currently used are default, out-of-the box for Shipping & Booking Collection.

  1. How much history is truly needed for Demantra to establish the anchor week?
  2. Is this history used for Demantra forecasting calculations and metrics?

If the Demantra forecasting engines are not being employed for our operations, and the previous forecasts are archived weekly as part of the update process, what would be the optimal settings to pull only the data needed to establish the Demantra anchor week for planning and where would those settings be changed in the ASCP Shipping & Booking collection?

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

Instructions for posting

×

1. Select a discussion category from the picklist.


2. Enter a title that clearly identifies the subject of your question.


3. In the body, insert detailed information, including Oracle product and version.


Please abide by the Oracle Community guidelines and refrain from posting any customer or personally identifiable information (PI/CI).


Cloud / Fusion customers - Our Cloud community has moved! Please go to Cloud Customer Connect .


New to My Oracle Support Community? Visit our Welcome Center

MOSC Help Center