Configuring a "Pre-Alert" Hook in the Generate Forecast Process Using APPCUST.XML (Doc ID 1918851.1)

Last updated on SEPTEMBER 20, 2016

Applies to:

Oracle Retail Demand Forecasting - Version 14.0.1 and later
Oracle Retail Predictive Application Server - Version 14.0.1 and later
Information in this document applies to any platform.

Goal

When there is a mismatch between alerts and automatic forecast approval, the cause is typically due to timing. All the measures and alerts used to calculate the Master Alert (which determines approval) must be calculated before the Master Alert is calculated. Oftentimes, when there is a mismatch, measures and alerts are being calculated after the Master Alert. It is necessary to move the dependent measure and alert calculations earlier, either earlier in the batch or through configuration of a prealert hook. This Note discusses the prealert hook.

 

'Generate' is the RDF utility that executes the RDF batch. It performs such processes as generating profiles, generating source level and final level forecasts, and approving forecasts.  Often, some customized computation is needed during the various stages of generate's execution. RDF provides a number of “hooks” for running customized computation at certain points in the batch process; for a list of these hooks, please see <Document 1098558.1> - RDF: Using APPCUST.XML as a Hook into Generate Forecast and CurveBatch Profile Utilities.

This article addresses scenarios in which it may be needed to configure the appcust.xml for pre-alert customizations specifically.
 

Solution

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