SAP ABAP Data Element FLGPRDB (Indicator: Do not save in forecast database)
Hierarchy
☛
BBPCRM (Software Component) BBPCRM
⤷
CRM (Application Component) Customer Relationship Management
⤷
CRM_APPLICATION (Package) All CRM Components Without Special Structure Packages
⤷ MCP2 (Package) R/3 application development: Sales & Operations Planning
BBPCRM (Software Component) BBPCRM⤷
CRM (Application Component) Customer Relationship Management⤷
CRM_APPLICATION (Package) All CRM Components Without Special Structure Packages⤷
MCP2 (Package) R/3 application development: Sales & Operations Planning
Basic Data
| Data Element | FLGPRDB |
| Short Description | Indicator: Do not save in forecast database |
Data Type
| Category of Dictionary Type | D | Domain |
| Type of Object Referenced | No Information | |
| Domain / Name of Reference Type | CHAR1 | |
| Data Type | CHAR | Character String |
| Length | 1 | |
| Decimal Places | 0 | |
| Output Length | 1 | |
| Value Table |
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 | No FODB |
| Medium | 20 | Do not save in FODB |
| Long | 36 | Do not save in forecast database |
| Heading | 4 | FODB |
Documentation
Definition
If you do not intend to work with forecast versions, you can switch off the use of them by setting this indicator. The forecast results are then saved in the information structure but not in the forecast database. Therefore, if you run the forecast and copy the results to the planning table, any previous forecast results are lost. The advantage of setting this indicator is that you achieve performance improvements.
History
| Last changed by/on | SAP | 19971002 |
| SAP Release Created in |
