Kontakt

Ansicht
Dokumentation

APO_SPP_PDEMCUST - Make General Settings for Demand History

APO_SPP_PDEMCUST - Make General Settings for Demand History

Addresses (Business Address Services)   ABAP Short Reference  
This documentation is copyright by SAP AG.
SAP E-Book

In this IMG activity, you can make general settings for the demand history.

SAP delivers default settings for all settings of this IMG activity.

We recommend that you use the default settings that SAP delivers. You should only change these settings if you have very good knowledge of Extended Service Parts Planning (eSPP)and of SAP NetWeaverusage type Business Intelligence.

You can make the following settings:

  • Fiscal Year Variant
If using Fiscal Year Periods, you must specify a fiscal year variant in the Fiscal Year Variant field. To do so, you choose a fiscal year variant that you have created under Maintain Fiscal Year Variants.
Note:
The fiscal year variant that you specify here must be identical to the fiscal year variant that you have specified under Determine Forecast Periodicity in the columnFV for posting period.
  • Scaling
Specify the scaling factors for the periods of the fiscal year variant, for weeks, and for months.
Since demand periods can have differing lengths and since the number of workdays within the demand periods can also differ, the forecasting service creates the forecast on the basis of scaled demands.
Example:
You have specified 21 as the scaling factor for months.
The raw demand in February 2005 is 40.
February 2005 has 20 workdays.
In this case, the scaled demand is 42 (40/20 = 2 and 2 * 21 = 42).

Assignment of Cancellation Reason Code/Update Indicator

You can define cancellation reason codes for sales orders. In this IMG activity, you can specify for each of these cancellation reason codes whether the system is to consider a sales order with one of these cancellation reason codes in the demand history and thus in the forecast.

If you want the system to consider sales orders with a certain cancellation reason code in the demand history, you specify the cancellation reason code in the Cnc Rsn Cd column and set the Keep Orig. Demand indicator.

If you do not want the system to consider sales orders with a certain cancellation reason code in the demand history, you specify the cancellation reason code in the Cnc Rsn Cd column but do not set the Keep Orig. Demand indicator.

In the standard system that SAP delivers, sales orders are considered in the demand history irrespective of their cancellation reason code.

SAP delivers the following demand categories that you must adopt:

  • ADJ_DEM (demands that you have adjusted manually)
  • FDO_DEM (demands for sales orders in the future)
  • NONE (all demands that do not fall in any of the other demand categories)
  • PROMO_DEM (promotion demands)

You can configure the message splitting mode using Parameter SOAP_SPLIT.

This Parameter allows for different values:

  • 1: No Message Split is applied. All Demand that is to be sent will be sent in a single message
  • 2: Messages are split by product. The Demand of each Product will be sent separately. In one message each. This is the default setting if no valid value is provided.
  • 3: Messages are split by product and location. The Demand of each Product and Location will be sent separately. In one message each.
  • 4: Messages are split by size. Each Sales Demand Notifications Message will contain a maximum number of demand entries. The number of demand entries can be defined using Parameter SOAP_SIZE. If SOAP_SIZE is not supplied the System will use the value '1000'.






Fill RESBD Structure from EBP Component Structure   CL_GUI_FRONTEND_SERVICES - Frontend Services  
This documentation is copyright by SAP AG.

Length: 4513 Date: 20240524 Time: 002158     sap01-206 ( 68 ms )