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_CFMENULEACTION | Program Actions |
| Transaction Code | S_KA5_12000623 | (empty) |
| Created on | 20001129 | |
| Customizing Attributes | SIMG_CFMENULEACTION | Program Actions |
| Customizing Activity |
Document
| Document Class | SIMG | Hypertext: Object Class - Class to which a document belongs. |
| Document Name | SIMG_CFMENULEACTION |
Creating Single Actions (only update of vehicle status)
Single actions are actions which are created using settings in VMS-Customizing. These actions update only the vehicle status. You define the status value in Customizing.
Procedure
In VMS-Customizing, you define the action itself first. Next, include the action in an action grid.
1. Defining the action
Maintain the following fields in the IMG activity Define actions:
- Action (4 character key) and Description (Text)
- Definition of Action as primary and/or secondary action
This setting determines, whether the action is checked in a primary and/ or in a secondary grid.
Leave all other fields empty.
2. Including the action in the action grid
Depending on whether you have defined the action as a primary and/or a secondary action, you should include it in a primary and/or a secondary matrix. In addition, select the desired action control in the IMG activity Defining action controls and action grids and maintain the following fields in the grid:
- Old vehicle status
Before carrying out the action, the system checks whether the current vehicle status is consistent with the old status entered here.
- Action
- New vehicle status
After carrying out the action, the system sets the vehicle status to the value entered here.
- Check entry
In many cases, you must check whether a certain status has been reached, using an entry in the grid, but no new status should be set. If this is the case, enter the old vehicle status for the new value and select the field check entry.
Special features of interlinking actions
You create interlinking actions in exactly the same way as elementary actions (see above). In the view interlinking actions , assign several elementary actions to the interlinking action and define the sequence, in which these actions should be carried out, with a numerical value.
Notes:
- Users can only then carry out the interlinking action, if they have authorization for both the interlinking action and for all the elementary actions.
- Every elementary action is processed by the system as a complete action - including setting a new status and updating. This is why you must include every elementary action in the primary and/ or secondary grid as an individual entry. While the interlinking action is being processed, an intermediate status is set by every elementary action.
- You must also include the interlinking action in the primary and/or secondary grid. Due to the check, this entry is relevant to the old vehicle status. It is not, however, for setting a new status.
- Recursive interlinking is not possible. Interlinking actions can therefore not be used as elementary actions of interlinking actions.
Enhance action interface
In order to be processed, many actions require inbound parameters, which can be entered on an action-specific interface by the user.
Here follows a description of how you can easily find additional fields on action interfaces and process these while performing the action. Using this method, you can both enhance existing interfaces and very easily create your own interfaces.
Procedure
Even if you are making only small changes to existing action interfaces, you should not modify these, but copy them into a functions group and then change the copy.
1. Assigning interfaces to an action
In VMS Customizing, it is very easy to assign a new interface to an action. You maintain the following fields in the IMG activity Define technical information of actions
- Program name of function group, which contains the screen (for example, in function group VELO15, the program is called SAPLVELO15)
- Number of screen
2. Creating individual action function group
So that a function group can include action interfaces, PAI and PBO modules as well as some global definitions must be available in the Top-Include.
All the required PAI and PBO modules are contained in the function group VELO15 (VMS actions) and can be included in the main program of their function group:
* PAI : action screens (general)
* =================================================================
INCLUDE LVELO15I01. " M_CHECK_ENTRY_FIELDS_FILLED (PAI)
INCLUDE LVELO15F04. " F_CHECK_ENTRY_FIELDS_FILLED (PAI)
INCLUDE LVELO15I02. " M_MODIFY_ITAB_FROM_DISP (PAI)
INCLUDE LVELO15F05. " F_MODIFY_ITAB_FROM_DISP (PAI)
INCLUDE LVELO15I03. " M_TRANSFER_DATA (PAI)
INCLUDE LVELO15F06. " F_TRANSFER_DATA (PAI)
* PBO : action screens (with additional vehicle data table)
* =================================================================
INCLUDE LVELO15O04. " M_ADDITIONAL_VEHICLE_DATA_PBO
INCLUDE LVELO15F07. " F_ADDITIONAL_VEHICLE_DATA_PBO
* PAI : action screens (with additional vehicle data table)
* =================================================================
INCLUDE LVELO15I04. " M_ADDITIONAL_VEHICLE_DATA_PAI
INCLUDE LVELO15F08. " F_ADDITIONAL_VEHICLE_DATA_PAI
The required global definitions (LVELO15ACT) are likewise in the function group VELO15 (VMS actions) and can be included in the Top-Include of their function group. The Include LVELO02CON contains all the constants used in VMS. They should therefore include the following lines in their Top-Include:
*=======================================================================
* Vehicle Management System Type Pool
TYPE-POOLS VLCH.
* The Include LVELO02CON contains all constants that are used in the
* Vehicle Management System.
INCLUDE LVELO02CON.
* The Include LVELO15ACT contains declarations that are needed in all
* function groups in that actions are implemented.
INCLUDE LVELO15ACT.
*=======================================================================
Additional fields in the vehicle master
With this method, you can add new table fields to the vehicle master without changing it and then maintain these on the action interfaces.
1.Enhancing vehicle table or history
If you want to save additional data for a vehicle, you can attach an append structure with additional fields to the vehicle table (VLCVEHICLE). If you are interested in the history of a field, you can also attach an append structure with additional fields to the vehicle history (VLCHISTORY).
Note:
If you want to add a field to the history, that is not included in the vehicle table, you must also attach the field to the dialog structure VLCDIAVEHI.
2. Enhancing communication structure VLCACTDATA
The transfer of data between action interfaces and action processing are made available via the communication structure VLCACTDATA. Only fields of this structure can therefore be used on the action interfaces. You must therefore likewise add the desired fields to this structure. Here, the field name must match the field name from the vehicle table or history.
Note:
The communication structure is structured as follows:
- Header data (data which is identical for all vehicles involved in the action)
The structure VLCACTDATA_HEAD_S and substructures respectively must be enhanced.
- Item data (data which are specific to the vehicle within the action)
The structure VLCACTDATA_ITEM_ S and substructures respectively must be enhanced.
3. Enhancing / creating action interface
It is easiest for you to copy an existing action screen in the action function group which you created. In the screen painter, you can now, in principle, include every field of the global structures VLCACTDATA_HEAD_S and VLCACTDATA_ITEM_S on your screen.
Note:
- The frame of the action-specific subscreen must be called ACTIONTEXT_GV. Only then is it guaranteed that the text for describing actions as defined in VMS Customizing will appear&#x
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_CFMENULEACTION | 0 | KA50000029 | Vehicle Management System |
Maintenance Objects
| Maintenance object type |
History
| Last changed by/on | SAP | 20010315 |
| SAP Release Created in | 46C |
