Hierarchy
FI-CA (Software Component) FI-CA⤷
IS-U-MD (Application Component) Master Data⤷
EMDGEN (Package) Master Data Generator - Generic Part
Basic Data
| Data Element | EPD_EVALTYPE |
| Short Description | Evaluation Category of Attribute |
Data Type
| Category of Dictionary Type | D | Domain |
| Type of Object Referenced | No Information | |
| Domain / Name of Reference Type | EPD_EVALTYPE | |
| 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 | EVALTYPE | |
| Change document | ||
| No Input History | ||
| Basic direction is set to LTR | ||
| No BIDI Filtering |
Field Label
| Length | Field Label | |
| Short | 10 | Eval. Cat. |
| Medium | 15 | Evaluation Cat. |
| Long | 20 | Evaluation Category |
| Heading | 10 | Eval. Cat. |
Documentation
Definition
The evaluation category defines:
- When an attribute is supplied with a value
- Where the value is supplied
- The meaning of the content of the Attribute value field in the definition of the master data template.
The following values can be applied to the combination of evaluation category and attribute value:
- Not defined
This evaluation category indicates attributes to which you currently do not want to allocate a value. If you use this evaluation category, you cannot make an entry in the attribute value field. As long as a master data template contains an attribute with this evaluation category, it is inconsistent and cannot be used.
- Not evaluated
You can only allocate identifying constants to this evaluation category.Although the system handles the not evaluated category in the same way as an identifying constant, it is not a product attribute but is evaluated in order to determine the data environment.
- Constant
This means that the attribute was allocated a fixed value when the master data template was defined. When you execute the master data template, the system allocated the contents of the attribute value field to the attribute. Use this evaluation category for attributes which must have the same value at all times.
- Identifying constant
The same applies here as to constants. In addition, the system handles this constant as an identifying characteristic during further processing of the master data template.This means that all the attributes are not given the same value; instead this value is used to specify any additional information (that is still to be determined) in the master data template environment.
- Parameter
The value of the attribute is not specified until the master data template is executed. If the parameter is not supplied with a values during runtime, and the paramter is a key field then the system generates a newkey. This means the system creates a new object in the master data.
- Virtual
The value of the attribute is determined during runtime by a function module that was stored for this purpose.
- Do not change
The attribute must not be assigned a value. Cannot be used for key fields.
- Key reference
Generally, this attribute is determined from the master data category. If this attribute is unique in the master data hierarchy then it cannot be allocated a different value. If the inheritance hierarchy of the master data template is not unique (meaning if more than one key parameters can define the attribute value) then you can use the input help to select and allocate the unique key attribute.
- Identifying Parameters
As for parameters, except that these parameters are used, in the case of multiple product assignments, to determine the product valid at the run time for the template. The valuation of the parameter at this attribute is used to determine the corresponding product. You can assign this evaluation category to more than one parameter. To determine the identifying parameter (CRMPips), however, you must then execute the valuation and assign the CRMPips to the individual products. The valuation of the CRMPips for the assigned products must be unique. This ensures that only one product can be assigned to the template at the run time (due to the current value of the CRMPips).
History
| Last changed by/on | SAP | 20050409 |
| SAP Release Created in |
