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
Basic Data
| Data Element | FLG_UPD |
| Short Description | Switch off DB update restricted to planning type key figures |
Data Type
| Category of Dictionary Type | D | Domain |
| Type of Object Referenced | No Information | |
| Domain / Name of Reference Type | CHAR01 | |
| 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 | Update_off |
| Medium | 19 | Key fig update: off |
| Long | 36 | Key-figure-restricted DB update: off |
| Heading | 36 | Key-figure-restricted DB update: off |
Documentation
Definition
If you set this indicator, you improve performance. However, the system cannot save two planning types of an information structure simultaneously because ALL the key figures in the information structure are read when a planning type based on the information structure is saved.
If you do not set this indicator, the system automatically locks and saves only those key figures that are contained in one planning type. This means that two or more planning types of an information structure can be saved at the same time. Here is an example of where you would not set this indicator.
Example
Two planners are working on the same information structure, but in two planning types. They are planning the same periods and the same characteristic value combinations. They both save at the same time. One saves the key figure "sales." The other saves the key figure "production."
Use
If the situation described in the above example does not apply in your company, SAP recommends that you set this indicator.
History
| Last changed by/on | SAP | 20130529 |
| SAP Release Created in |
