SAP ABAP IMG Activity VMS_USER_INTERFACE (BAdI: Influence Interface of Transaction VELO)
Hierarchy
☛ ECC-DIMP (Software Component) DIMP
   ⤷ IS-A-VMS (Application Component) Vehicle Management System
     ⤷ ISAUTO_VLC (Package) Vehicle Management System (VMS)
IMG Activity
ID VMS_USER_INTERFACE BAdI: Influence Interface of Transaction VELO  
Transaction Code S_KA5_12001325   (empty) 
Created on 20021129    
Customizing Attributes VMS_USER_INTERFACE   BAdI: Influence Interface of Transaction VELO 
Customizing Activity VMS_USER_INTERFACE   BAdI: Influence Interface of Transaction VELO 
Document
Document Class SIMG   Hypertext: Object Class - Class to which a document belongs.
Document Name VLC_USER_INTERFACE    

Use

This business add-in (BAdI) is used in the Vehicle Management System (IS-A-VMS) component.

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.
    • SINGLE_SEARCH_VEHICLE_IV
      Value to be searched for
    • USERDATA_IS
      Information about the user who has called up the search
    • 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.

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 2   Non-critical 
Country-Dependency A   Valid for all countries 
Maintenance Objects
Maintenance object type E   Business Add-In - Definition 
History
Last changed by/on SAP  20021129 
SAP Release Created in 471