Hierarchy
ECC-DIMP (Software Component) DIMP⤷
IS-A-VMS (Application Component) Vehicle Management System⤷
ISAUTO_VLC (Package) Vehicle Management System (VMS)
IMG Activity
| ID | SIMG_CFMENULEOVELO4 | Define Additional Data for Vehicle |
| Transaction Code | S_KA5_12000624 | (empty) |
| Created on | 20001129 | |
| Customizing Attributes | SIMG_CFMENULEOVELO4 | Define Additional Data for Vehicle |
| Customizing Activity | SIMG_CFMENULEOVELO4 | Define Additional Data for Vehicle |
Document
| Document Class | SIMG | Hypertext: Object Class - Class to which a document belongs. |
| Document Name | SIMG_CFMENULEOVELO4 |
You use this IMG activity to define the qualifiers and assign qualifiers and attributes to elementary actions.
Qualifiers and attributes are different technical concepts. From a business point of view however they are the same. They both contain parameters that have additional customer-specific information for a vehicle.
Working with attributes and qualifiers is advisable if you need additional information on a vehicle that characteristics do not cover, such as vehicle indicators, and registration numbers, and if you want to make this information accessible to action interfaces and the vehicle search.
The technical differences are listed below:
- Attributes are written directly in the vehicle table.
To do this you put these attributes into an append structure for table VLCVEHICLE as additional fields . This increases the scope of the vehicle table and this may negatively influence performance when executing actions .
Attributes are also displayed as individual fields on the action interface. - Qualifiers on the other hand are created in this IMG activity and administered in their own supplementary table.
This does not alter the vehicle table scope and therefore does not influence performance.
Qualifiers are displayed in their own area as an ALV-List on the action interface.
This causes the following differences in usage:
You use qualifiers, if you want to define (for a vehicle) additional data that meets at least one of the following criteria:
- Data is descriptive, and has no controlling influence.
- The number of data fields required is relatively large.
- Data is only being used by a few actions.
If it does not meet any of the above criteria, it is a better idea to work with attributes.
For more information on attributes and qualifiers and how to program them see the IMG activity documentation Program Actions .
Example
Requirements
Standard settings
Recommendation
Activities
Further notes
Business Attributes
| ASAP Roadmap ID | 153 | Design enhancements |
| Mandatory / Optional | 2 | Optional activity |
| Critical / Non-Critical | 1 | Critical |
| Country-Dependency | A | Valid for all countries |
Assigned Application Components
| Documentation Object Class | Documentation Object Name | Current line number | Application Component | Application Component Name |
|---|---|---|---|---|
| SIMG | SIMG_CFMENULEOVELO4 | 0 | KA50000029 | Vehicle Management System |
Maintenance Objects
| Maintenance object type | C | Customizing Object |
| Assigned objects | ||||||
|---|---|---|---|---|---|---|
| Customizing Object | Object Type | Transaction Code | Sub-object | Do not Summarize | Skip Subset Dialog Box | Description for multiple selections |
| VC_VLC04 | C - View cluster | SM34 |
History
| Last changed by/on | SAP | 20010315 |
| SAP Release Created in | 46C |
