Ansicht
Dokumentation

VMS_USER_INTERFACE - BAdI: Influence Interface of Transaction VELO

You can use this BAdI to access interface processing of transaction VELO.

The BAdI has the following methods:

CHECK_ACTION_SUBSCREEN: data that is entered on the subscreens of actions is subjected to checks

The method has the following parameters:

UCOMM_IV
Current function code. You can use this function code to control if customer-specific checks are constantly executed or only after choosing the pushbutton Execute Action. If the second is the case, the following is valid: UCOMM_IV = FC_AKTN_GC.

ACTION_IV
4-digit ID of action to be executed. You can control for which action customer-specific checks should be executed.

VLCACTDATA_IS
Action-specific data (header, item, and additional data). This is data that was entered by the user on the interface.

LIST_OF_VEHICLES_IT
Data of vehicles that were selected for the action. This table is empty for actions that create vehicles.

FILTER_HISTORY_DISPLAY: Change contents of vehicle history in the vehicle detail screen

VEHICLE_SINGLE_SEARCH: Maintain single search for a vehicle
This method is called up during the single search for a vehicle directly before the VMS standard search is started.

SINGLE_SEARCH_TYPE_IV
ID types for the vehicle single search. The content of these parameters corresponds to that of the F4 help for the field in which you select the ID type for the vehicle single search in transaction VELO. If you have defined a customer-specific ID type in addition to the existing ID types internal vehicle number, external vehicle number, and vehicle ID number, this will also be displayed.

VLCDIAVEHI_CONF_CT und VLCSEARCHCRIT_CT
This parameter is transferred to the VMS standard search after executing the BAdI implementation. If you have defined your own SINGLE_SEARCH_TYPE, you can search in your implementation for the vehicle that corresponds to the SINGLE_SEARCH_TYPE_IV and SINGLE_SEARCH_VEHICLE_IV, and then write the VGUID of this vehicle into the VLCSEARCHCRIT_CT table. The VMS standard search then determines your vehicle using the VGUID.

CHECK_EVENT_HANDLER_EXIST: Checks whether a SAP Supply Chain Event Manager (SCEM) is connected to the VMS

CALL_SCEM_DIALOG: Display SCEM tracking data for the vehicle
The method is called up in transaction VELO using the pushbutton SCEM on the vehicle detail screen.

WARRANTY_DEACTIVATE: Controls whether the Warranty tab index in transaction VELO is actived or not. The tab index is displayed by default.

Addresses (Business Address Services) SUBST_MERGE_LIST - merge external lists to one complete list with #if... logic for R3up
This documentation is copyright by SAP AG.

Length: 3644 Date: 20240523 Time: 174236 sap01-206 ( 58 ms )

VMS_USER_INTERFACE - BAdI: Influence Interface of Transaction VELO