...
| Info |
|---|
|
| Using various function modules, you can adapt the VSS vehicles and use functions for the VSS vehicles. For more information about function modules, see Customizing for Vehicle Sales and Service (VSS) under RFC Interfaces > Function Modules > RFC VSS Vehicle. |
StructureIn Customizing for VSS under Vehicle > Vehicle Master > Navigation in Vehicle Master (SAP GUI), you can define which of the following data for the object Vehicle is displayed:
...
- Control Vehicle Search UIs
- Control Vehicle Master APIs
- Change and Filter of VMS Attachments in VSS Vehicle
- Control Vehicle Order
- Control Maintenance and Service Intervals for Vehicle
- Control Vehicle Master UIs
- Control Vehicle Model Master APIs
- Control Vehicle Model Master UIs
- Control Vehicle Model Master UI Defaults
- Control Reading of Control Values
- Control Vehicle Actions (VMS)
- Control Vehicle Warranties
- Control Replacement Vehicle Search
- Dependency Check for Multiple Vehicles
| Anchor |
|---|
| integration-33 |
|---|
| integration-33 |
|---|
|
IntegrationIn order to create a vehicle in the standard system, you first have to create a vehicle model.
You can use BAdI: Control Vehicle Master APIs (BAdI /DBE/BADI_VEHICLE_API) to copy default data from the vehicle model master to the vehicle master when you create a new vehicle. If you do not wish to use the default implementation of the BAdI, you can create a customer implementation.
You can also create a vehicle without a vehicle model. If you want to do this, there must be a material in the material master for this purpose. When you create the vehicle, you have to enter the material instead of the model, or you can implement your own logic for material determination in BAdI: Control Vehicle Master APIs.
If you create an order from the vehicle master, the vehicle data is copied to this order. To do this, implement BAdI: Control Vehicle Order (/DBE/VEHICLE_SALES).