Hierarchy
SAP_BW (Software Component) SAP Business Warehouse⤷
SCM-BAS (Application Component) SCM Basis⤷
/SAPAPO/SCMB_FORECAST (Package) Forecast
Basic Data
| Data Element | /SAPAPO/ALPROF |
| Short Description | Profile for Controlling Alert Monitor Output |
Data Type
| Category of Dictionary Type | D | Domain |
| Type of Object Referenced | No Information | |
| Domain / Name of Reference Type | /SAPAPO/ALPROF | |
| Data Type | CHAR | Character String |
| Length | 22 | |
| Decimal Places | 0 | |
| Output Length | 22 | |
| Value Table | /SAPAPO/DP_ALERT |
Further Characteristics
| Search Help: Name | ||
| Search Help: Parameters | ||
| Parameter ID | ||
| Default Component name | ||
| Change document | ||
| No Input History | ||
| Basic direction is set to LTR | ||
| No BIDI Filtering |
Field Label
| Length | Field Label | |
| Short | 10 | Profile |
| Medium | 15 | Alert Profile |
| Long | 20 | Alert Profile |
| Heading | 22 | Alert Profile |
Documentation
Definition
Restricts the situations for which alerts are issued in Demand Planning. The situation is defined by the planning area, key figure, version, and message type. An * in any of these fields in the alert constraint definition means that the profile is valid for all instances of that object: for example, an * in the field Planning area means that the profile is valid for all planning areas.
If you do not make any entries here, alerts are issued for all key figures, versions, and forecast models.
There are three message types:
- C
An alert is issued if the forecast was based on a composite profile.
- M
An alert is issued if the forecast was based on an MLR profile.
- U
An alert is issued if the forecast was based on a univariate profile.
Procedure
To define restrictions on demand alerts, choose Goto -> Alert restrictions in the master forecast profile.
Dependencies
You must also maintain a DP Alert Monitor profile.
History
| Last changed by/on | SAP | 20130604 |
| SAP Release Created in |
