[go: up one dir, main page]
Scribd
Upload
158 views2 pages

Function Module To Retrieve Forecast Results

This document describes a function module that can be called to retrieve forecast results from external systems. The function module takes input parameters like a diagnostics ID, time series source, logical system, and product-location and forecast horizon details. It returns forecast results, variance, and DIF effect for each product-location and date. Any invalid input parameters will return a message. Results are aggregated at the product-location-day level if there are multiple records for a day.

Uploaded by

koyalp
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
158 views2 pages

Function Module To Retrieve Forecast Results

This document describes a function module that can be called to retrieve forecast results from external systems. The function module takes input parameters like a diagnostics ID, time series source, logical system, and product-location and forecast horizon details. It returns forecast results, variance, and DIF effect for each product-location and date. Any invalid input parameters will return a message. Results are aggregated at the product-location-day level if there are multiple records for a day.

Uploaded by

koyalp
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 2

Function Module to retrieve Forecast Results

Objective:

Make forecast results available for external systems/applications.

Function Module:

Forecast results can be retrieved cross-system by calling the remote enabled function module ("RFC"):

/DMF/UFC_RETRIEVE_RESULTS

Interface:

Input parameters:

Parameter name Meaning Default Description


value

IV_DIAG_ID Diagnostics blank UDF can store model/forecast results for a defined diagnostics ID. Production forecast will create
Identifier results for DIAG_ID blank (or 4 whitespaces)

IV_TS_SOURCE Timeseries POS_TS UDF supports four types of timeseries: POS_TS (Point-Of-Sales data), CONS_TS (Consumption sales
Source data), POS_VDM and SO_VDM

IV_SENDER Logical system - DDF supports using data from several logical systems.

IT_PL_FC_HORIZON Product-location - The content of this table defines for which product-locations and for which foecast horizon results are
specific retrieved.
forecast horizon
The product-locations have to be specified in the external representation (not GUIDS) and the location
type code has to be specified as well.

The forecast time granularity is 'day' hence the horizon time format (start date and end date) is date -
without time information.

Output parameters

Paramter name Meaning Description

ET_FC_RESULTS Forecast A forecast value, forecast variance and DIF effect per (external) product-location and date
results
Note (1): As there is currently no way to read the DIF effect, this values is constantly 0.0

Note (2): If the variance value is -1.0 there is no variance available. The variance is a result from the
modeling. It is possible to have forecasts for a product without having it modeled before. Forecasting a newly
listed product with hierarchical priors would lead to this situation.

ET_MSG Messages Invalid input parameters are indicated by a message of type /DMF/MSG_HL

Note:

The key of the output table is product–location–location_type_code–date.


However, UDF knows more keys:

product-location and multichannel keys


regular sales and offer sales at one day

If there is more than one record at a day due to regular sales and offer sales or as there are sales for more than one channel, results are
aggregated on the product–location–day level.

You might also like