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_KZMRP |
| Short Description | Fill key figure with data from documents/stocks |
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 | Doc. KF |
| Medium | 15 | Document KF |
| Long | 20 | Document key figure |
| Heading | 5 | Do-KF |
Documentation
Definition
If you have key figures that are based on document data from other systems, set this indicator. The system then checks the information structure against transaction MC9V.
With transaction MC9V, you define the MRP elements of key figures that are based on document data. For example, you might define a key figure "original planned production" that is based on planned orders from MRP. You insert such a key figure in the planning table using either an actual data line in a planning type or user exit MCP20001 for external data.
If you do not have key figures that are based on document data, do not set this indicator. In this way, you improve system performance.
Dependencies
If you set this indicator, you must also define the checking group and the checking rule in the key figure parameters.
History
| Last changed by/on | SAP | 20130529 |
| SAP Release Created in |
