Hierarchy
SAP_BW (Software Component) SAP Business Warehouse⤷
SCM-BAS (Application Component) SCM Basis⤷
/SAPAPO/SCMB_FORECAST (Package) Forecast
Basic Data
| Data Element | /SAPAPO/INFOCUBE |
| Short Description | InfoCube |
Data Type
| Category of Dictionary Type | D | Domain |
| Type of Object Referenced | No Information | |
| Domain / Name of Reference Type | CHAR30 | |
| Data Type | CHAR | Character String |
| Length | 30 | |
| Decimal Places | 0 | |
| Output Length | 30 | |
| Value Table |
Further Characteristics
| Search Help: Name | ||
| Search Help: Parameters | ||
| Parameter ID | /SAPAPO/ICUBE | |
| Default Component name | ||
| Change document | ||
| No Input History | ||
| Basic direction is set to LTR | ||
| No BIDI Filtering |
Field Label
| Length | Field Label | |
| Short | 10 | InfoCube |
| Medium | 15 | InfoCube |
| Long | 20 | InfoCube |
| Heading | 30 | InfoCube |
Documentation
Business Definition
The central data container as used in the SAP Business Information Warehouse. It is used in Demand Planning for storing historical data. It contains two types of data: key figures and characteristics.
A key figure is a criterion for forecasting future demand or evaluating past performance. It takes the form of a value or quantity; for example, sales revenue, sales quantity, or price.
A characteristic is an organizational unit or object in your company; for example, region, sales organization, brand, product, or customer. You create demand plans for one or more characteristics.
Note that you store forecasts themselves in liveCache, in planning books. You use InfoCubes for back-ups and reporting purposes.
Technical Definition
An InfoCube consists of a number of relational tables that are arranged according to the star schema: a large fact table in the center, currounded by several dimension tables. Dimension tables are independent of one another. The fact table connects the dimensions with the key figures.
Supplementary Documentation - /SAPAPO/INFOCUBE0001
Procedure
Enter the InfoCube for which you want to maintain Demand Planning master data.
Supplementary Documentation - /SAPAPO/INFOCUBE0002
Procedure
This is the InfoCube for which you wish to generate characteristic combinations that can be planned in Demand Planning.
Supplementary Documentation - /SAPAPO/INFOCUBE0003
Procedure
This is the InfoCube you are currently planning. To switch to a different InfoCube, go to a different planning book by choosing Planning -> Other Planning Book.
Supplementary Documentation - /SAPAPO/INFOCUBE0004
Procedure
Enter the InfoCube you want to display alerts for.
Dependencies
This InfoCube has to be one of the InfoCubes in the alert profile configuration of the master forecast profile.
Supplementary Documentation - /SAPAPO/INFOCUBE0005
Procedure
Enter the InfoCube with the demand plan you want to release.
Examples
Dependencies
Supplementary Documentation - /SAPAPO/INFOCUBE0006
Procedure
Specify the name of the InfoCube (in which the demand plan was generated) you want to release.
Supplementary Documentation - /SAPAPO/INFOCUBE0007
Procedure
Enter the InfoCube from which you want to transfer the demand plan to the R/3 system.
Supplementary Documentation - /SAPAPO/INFOCUBE0008
Procedure
In this screen, you create a time buckets profile for Demand Planning and Supply Network Planning. If you are creating a time buckets profile for Demand Planning, enter an InfoCube that you want to use it for. If you want to use the time buckets profile for Supply Network Planning, do not enter an InfoCube.
Examples
Dependencies
Im Demand Planning ist ein Periodenraster vom InfoCube abhängig.
Supplementary Documentation - /SAPAPO/INFOCUBE0100
Use
Enter the name of the InfoCube you want this key figure to be stored in.
You can store old planning data as well as actual data in InfoCubes.
Supplementary Documentation - /SAPAPO/INFOCUBE0110
Use
Demand Planning alerts always refer to a specific infoCube. By specifying this infoCube, the accompanying alerts are displayed.
If you make no entry in this field, Demand Planning alerts about this profile are not displayed. When calling the Alert Monitor, only the alerts for the objects that are derived from the respective environment (for example, a planning book that was just edited in the interactive planning for Demand Planning) are displayed.
Procedure
Examples
Dependencies
History
| Last changed by/on | SAP | 20130604 |
| SAP Release Created in |
