Hierarchy
ECC-DIMP (Software Component) DIMP⤷
IS-A-VMS (Application Component) Vehicle Management System⤷
ISAUTO_VLC (Package) Vehicle Management System (VMS)
IMG Activity
| ID | VLC_EXECUTE_ACTION | BAdI: Execution of Actions |
| Transaction Code | S_KA5_12001304 | (empty) |
| Created on | 20021129 | |
| Customizing Attributes | VLC_EXECUTE_ACTION | BAdI: Execution of Actions |
| Customizing Activity | VLC_EXECUTE_ACTION | BAdI: Execution of Actions |
Document
| Document Class | SIMG | Hypertext: Object Class - Class to which a document belongs. |
| Document Name | VLC_EXECUTE_ACTION |
Use
This business add-in (BAdI) is used in the Vehicle Management System (IS-A-VMS) component.
With this BAdI you can, amongst other things, execute additional checks and change and enhance data for the actions.
It is processed if an action is executed or the function module VELO09_SET_ACTION is called.
The BAdI has the following methods:
- CHECKS_BEFORE_ACTION: Carry out checks before executing the action
Before executing an elementary action, additional checks can be implemented. When executing an interlinking action, this method is processed before each elementary action.
- INCOMING_ACTION_IS: Data on the action to be processed. If it is an interlinking action, the data in ELEMENTARY_ACTION_IS is the data of the elementary action to be processed at that point.
- VLCDIAVEHI_IS: Dialog structure with the vehicle data
- VLCACTDATA_IS: Vehicle data for execution of an action
- VLCSTATUS_IT: Table with the vehicle status
- VLCH_MSSG_IT: Table with the error messages
- DATA_CHANGES_BEFORE_ACTION: Change or add data before executing the action
This action is processed directly before the EXECUTE module is called
- INCOMING_ACTION_IS: Data on the action to be processed. If it is an interlinking action, the data in ELEMENTARY_ACTION_IS is the data of the elementary action to be processed at that point.
- VLCSTATUS_IT: Table with the vehicle status
- VLCBAPICU_IT: Table with the vehicle configurations
- VLCDIAVEHI_CT: Table with the vehicle data
- VLCACTDATA_CS: Vehicle data for executing an action
- VLCH_MSSG_CT: Table with the error messages
- DATA_CHANGES_AFTER_ACTION: Change data after executing the action or trigger follow-up actions
This action is processed directly after calling an EXECUTE module process.
- INCOMING_ACTION_IS: Data on the action to be processed. If it is an interlinking action, the data in ELEMENTARY_ACTION_IS is the elementary action to be processed at that point.
- VLCSTATUS_IT: Table with the vehicle status
- VLCBAPICU_IT: Table with the vehicle configurations
- VLCDIAVEHI_CT: Table with the vehicle data
- VLCACTDATA_CS: Vehicle data for executing an action
- VLCH_MSSG_CT: Table with the error messages
- EXECUTE_FURTHER_ACTIONS: Call customer-defined actions
- ACTION_TO_BE_PERFORMED_IV: Action to be processed
- INCOMING_ACTION_IS: Data on the action to be processed. If it is an interlinking action, the data in ELEMENTARY_ACTION_IS is the data of the elementary action to be processed at that point.
- VLCSTATUS_IT: Table with the vehicle status
- DIALOGUE_ALLOWED_IV: If the indicator is set, popups are allowed during execution of the action.
- VLCBAPICU_IT: Table with the vehicle configurations
- RFCDEST_CT: Table with the RFC destinations
- VLCDIAVEHI_CT: Table with the vehicle data
- VLCACTDATA_CS: Vehicle data for executing an action
- VLCH_MSSG_CT: Table with the error messages
- VEHICLE_ISOLATION: Isolate vehicles
Here processing can be implemented for which the EXECUTE module for an action is called individually for each vehicle to be processed. Example: If the action in the standard Create order is carried out for 5 vehicles, a purchase order document is created with 5 items. Using a suitable implementation in this BAdI, it is possible to automatically create 5 purchase order documents, each with one item.
- COMMIT_IV: Type of COMMIT WORK
- ACTION_COUNTER_IV: Counter which specifies which elementary action is to be processed at that point.
- DIALOGUE_ALLOWED_IV: If the indicator is set, popups are allowed when executing an action.
- INCOMING_ACTION_IS: Data on the action to be processed. If it is an interlinking action, the data in ELEMENTARY_ACTION_IS is for the elementary action to be processed at that point.
- VLCSTATUS_IT: Table with the vehicle status
- VLCBAPICU_IT: Table with the vehicle configurations
- VLCDIAVEHI_CT: Table with the vehicle data for all vehicles
- VLCDIAVEHI_OK_CT: Table with the vehicle data for the vehicles for which the action can be executed
- VLCDIAVEHI_NO_CT: Table with the vehicle data for the vehicles for which the action cannot be executed
- VLCACTDATA_CS: Vehicle data for execution of an action
- VLCH_MSSG_CT: Table with the error messages
- DETERM_PLANNED_SDATE: Determine planned delivery date
- CALE_IV: Factory calendar to be used
- PSDATU_CV: Planned delivery date
- VLCACTDATA_CS: Vehicle data for executing an action
- VLCH_MSSG_CT: Table with the error messages
- GET_LOC_AVAIL_STIME: Get data on location, availability and delivery date
When executing an action the data defined in Customizing can still be changed after being read from the database. - CNTRL_IV: Action control
- AKTION_IV: Action
- STATUS_IV: Vehicle status
- VLCACTDATA_IS: Vehicle data for executing an action
- VLCDIAVEHI_IS: Dialog structure with the vehicle data
- LOC_AVAIL_STIME_CS: Data on location, availability and delivery date
- PREPARE_ADDVDATA: Prepare additional data
In Customizing you can define which fields in the vehicle table are processed for which actions. With this method, data can be prepared for the action interface. A time stamp can for example be converted to date and time.
- FIELDNAME_IV: Valid vehicle attributes from the structure VLCDIAVEHI
- VLCDIAVEHI_IS: Dialog structure with the vehicle data
- VLCACTDATA_CS: Vehicle data for execution of an action (Head and items)
- VLCACTDATA_ITEM_CS: Vehicle data for executing an action (items)
- EXECUTE_ADDVDATA: Execute additional data
With this method, data prepared with method PREPARE_ADDVDATA can be adjusted for execution of the action.
- FIELDNAME_IV: Valid vehicle attributes from the structure VLCDIAVEHI
- VLCDIAVEHI_IS: Dialog structure with the vehicle data
- VLCACTDATA_CS: Vehicle data for execution of an action (head and items)
- VLCACTDATA_ITEM_CS: Vehicle data for execution of an action (items)
- COMMIT_MODE: Choose update mode
In the standard setting single actions with commit work are posted and the elementary actions of an interlinking action with commit work and wait. Here, the settings can be changed.
- INCOMING_ACTION_IS: Data on the action to be processed. If it is an interlinking action, the data in ELEMENTARY_ACTION_IS is the data for the elementary action to be processed.
- INCOMING_ACTION_IS : Update mode
- COMMUNICATE_WITH_EXT_SYSTEM: Communicate with another system, for example SCEM, in order to transfer data there.
- INCOMING_ACTION_IS: Data on the action to be processed. If it is an interlinking action, the data in ELEMENTARY_ACTION_IS is the data for the elementary action to be processed.
- VLCSTATUS_IT: Table with the vehicle status
- VLCBAPICU_IT: Table with the vehicle configurations
- VLCACTDATA_CS: Vehicle data for execution of an action
- VLCDIAVEHI_CT: Table with the vehicle data
- VLCH_MSSG_CT: Table with the error messages
Requirements
Standard settings
This BAdI does not have a default implementation.
Activities
Procedure for BAdI implementation
Example
Business Attributes
| ASAP Roadmap ID | 257 | Create User Exits |
| 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 | VLC_EXECUTE_ACTION | 0 | KA50000029 | Vehicle Management System |
Maintenance Objects
| Maintenance object type | E | Business Add-In - Definition |
History
| Last changed by/on | SAP | 20021219 |
| SAP Release Created in | 471 |
