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_EXTSE_SEARCH | BAdI: Vehicle Search Via External Search Machine |
| Transaction Code | S_KA5_12001336 | (empty) |
| Created on | 20021129 | |
| Customizing Attributes | VLC_EXTSE_SEARCH | BAdI: Vehicle Search Via External Search Machine |
| Customizing Activity | VLC_EXTSE_SEARCH | BAdI: Vehicle Search Via External Search Machine |
Document
| Document Class | SIMG | Hypertext: Object Class - Class to which a document belongs. |
| Document Name | VLC_EXTSE_SEARCH |
Use
This business add-in (BAdI) is used in the Vehicle Management System (IS-A-VMS) component.
You can use this BAdI to connect an external search engine to the VMS in order to improve the performance of the vehicle search. The only method for this BAdI is called at the beginning of the vehicle search. You can therefore influence the search process before the VMS standard search begins.
This BAdI has the method EXTERNAL_SEARCH:
- FAMILYCLASS_CV: family class according to which the search takes place
- USERDATA_CS: information on the user who started the search
- ADDDATA_CS: qualifying data on the vehicle according to which the system should search
- LIMITS_CS: hit list restrictions
- KMATLIST_CT: list of the vehicle models in which the search should take place
- GUIDS_CT: list of vehicle GUIDs. This list can contain data at the start. If this is the case, the external search should only search for vehicles with these GUIDs that also fulfill the other search criteria. Normally however, this list will be empty and the external search engine fills it with the GUIDs of the vehicles that have been found during the search.
- CONFDATA_CT: vehicle configuration being sought
- VLCSEARCHCRIT_CT: general vehicle data (for example, from VLCVEHICLE) according to which the search takes place
- MESSAGES_CT: error messages and success messages that have occurred during the search
- NO_STD_CONF_SEARCH_CV: if this parameter is set, the configuration search in the database is switched of. This should be done, if the external search engine already has taken care of the configuration search criteria.
In the implementation of the method you have to call the external search engine and this search machine has to return the GUIDs of the vehicles that are found in the parameter GUIDS_CT. Furthermore, the search engine has to delete all the search criteria that it has used from parameters ADDDATA_CS and VLCSEARCHCRIT_CT so that these criteria are no longer used by the VMS standard search.
If your external search engine cannot handle specific search criteria, leave these criteria in the above-named parameters. The VMS standard search then makes sure that these criteria are also taken into account. Furthermore, the VMS standard search also has the GUIDS_CT list at its disposal in this case. This restricts the number of checked vehicles and improves performance.
SAP provides the search engine TREX as a possible external search engine. If you want to connect TREX to the VMS search, you have to call function module VELO08_TREX_SEARCH in this BAdI implementation. Moreover, you have to change the coding in order to define in which search index TREX should search for the vehicles.
Requirements
Standard settings
Activities
Procedure for Implementing a BAdI.
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 |
Assigned Application Components
| Documentation Object Class | Documentation Object Name | Current line number | Application Component | Application Component Name |
|---|---|---|---|---|
| SIMG | VLC_EXTSE_SEARCH | 0 | KA50000029 | Vehicle Management System |
Maintenance Objects
| Maintenance object type | E | Business Add-In - Definition |
History
| Last changed by/on | SAP | 20021129 |
| SAP Release Created in | 471 |
