You can use this function to use a vehicle created in the Vehicle Management System (IS-A-VMS) in Vehicle Sales and Service (VSS). For example, you can purchase a vehicle in VMS and then use this vehicle in the VSS service process.
Some dealerships and dealer groups operate dealer and importer business in parallel. An importer that uses service processes, for example pre-delivery inspection, can also use VSS and VMS.
Vehicle Sales and Service (VSS) is SAP's solution for an automotive dealer, while the Vehicle Management System (VMS) is designed to cover the requirements of the importer. To benefit from the strengths of both solutions, you can run both VSS and VMS in the same system. The importer business typically involves handling large quantities of vehicle. VMS supports this requirement, and allows you to:

Create multiple vehicles in one step
Use the variant configuration feature to determine pricing and object dependencies
Purchase more than one vehicle from the OEM by using one purchase order
Verify goods receipts and invoices for multiple vehicles

You can create, configure, and procure a vehicle in VMS. Once you receive the vehicle from the OEM, you can use it in VSS, for example for pre-delivery inspection.
VSS usually handles one vehicle at a time, not several in parallel.
Typically, in VSS a purchase or a sales order contains one vehicle. VSS does not use variant configuration. VSS provides an integrated solution for the complete vehicle service and warranty processes including split capabilities. The VSS vehicle master provides dealer-specific data such as registration, registration history, warranties, partner information (such as owner or driver), and leasing information. VSS also supports the vehicle sales process and procurement process for dealers.
The following features facilitate the integration:

A VMS action that allows you to use a VMS vehicle in VSS

You can use action QDBM (enable vehicle for VSS), in transaction VELO. This action enhances the VMS vehicle with the relevant VSS object information, for example warranty and registration data. You also enter some additional data that is required for VSS, for example the model sales code. You can then use the vehicle in VSS, for example in a service order. As with other VELO actions, this new action can process more than one vehicle.

An action that allows you to enable a VMS vehicle from VSS

You can use action QVMS to enable a VMS vehicle from the VSS application.
For example, if you select a VMS vehicle from the VSS vehicle search result list, the system displays a dialog box that you use to can enter the data required to enable the VMS vehicle for VSS. The system then uses action QVMS to enable the vehicle for VSS.

Note

To enable a VMS vehicle for VSS, action QVMS must be allowed for the vehicle. This depends on the action matrix Customizing for the vehicle.

A variant configuration subscreen

In the VSS vehicle master transaction (/DBE/VM), you can access a subscreen that displays the vehicle's variant configuration. As this subscreen is only relevant if you use VMS, it is not part of the standard delivery. If you use VMS, you can add the subscreen in Customizing.
To view the VMS configuration subscreen in the vehicle master, make the following Customizing settings:

In Customizing for Vehicle Sales and Service under Vehicle > Vehicle Master > Navigation in Vehicle Master (SAPGUI) > Define Nodes for Vehicle Master Navigation Tree add a new node, such as ZVMC VMS Configuration.
In Customizing for Vehicle Sales and Service under Vehicle > Vehicle Master > Navigation in Vehicle Master (SAPGUI) > Define Navigation Profile and Technical Settings for Navigation Tree, which is used for vehicles (DBM1 in standard), enter a sequence number for the node, and enter the screen data /DBE/SAPLVM07, 2100, Active.

To view the VMS configuration subscreen in the VSS order, make the following Customizing settings:

In Customizing for Vehicle Sales and Service under Order > User Interface Control > Order Layout > Define Order Layout, add a new group box where you want to display the subscreen. The group box 2073, 23 lines is sufficient for the subscreen.
In Customizing for Vehicle Sales and Service under Order > User Interface Control > Order Layout > Subscreen > Define Subscreen add a new subscreen, with parameters ZVMS_CONFIGURATION, VMS configuration and enter the details for the subscreen: /DBE/SAPLORDER_UI, 2240.
In Customizing for Vehicle Sales and Service under Order > User Interface Control > Order Layout > Subscreen > Assign Criteria, add the new line for the group box defined at layout, to include the new subscreen.

A Customizing example of an integrated business process

We provide a Customizing example of an integrated VMS/VSS business process. The primary matrix is DVM1, and the secondary matrices are DVM2 (sales process in VMS). This example does not represent the full capabilities of a real business scenario, but rather allows you to get familiar with the possibilities available for an integrated VMS/VSS process. You can find the example matrices in Customizing for Vehicle Management System (VMS) under Control Data > Define Action Controls and Define Action Matrices. You can use this Customizing example to familiarize yourself with VMS/VSS integration possibilities.

The ability to differentiate between VMS and VSS actions

You can differentiate between the actions that belong to VSS, and the actions that belong to VMS. You can specify whether a vehicle action can be used in VMS, VSS or both in Customizing for Vehicle Sales and Service (VSS) under Vehicle > Vehicle Master > Vehicle Control. This ensures that when you use transaction /DBE/VM, the system displays valid actions only.
You usually use actions in VSS or in VMS, but not in both applications. One reason is the user interface. In SAP GUI, a subscreen that you create for VMS (transaction VELO) differs from a subscreen created for the VSS vehicle master transaction (/DBE/VM). Also, the coding for the function modules of the action is typically written for either VSS or VMS, not both.

The ability to view VMS documents in VSS

In the VSS vehicle transaction (/DBE/VM), you can view attachments created in VMS. The VSS vehicle master has a document management system. In the document management system, you can choose the VMS Attachments pushbutton to view any VMS attachments. You can only view this button if VMS attachments exist. You can view VMS attachments in VSS, but you cannot edit them. You can also view and edit VSS attachments.
You can restrict VMS attachments for VSS. For example, you may not want VSS users to view VMS legal or accounting documents. To specify the VMS attachments you want to display in VSS, see Customizing for Vehicle Sales and Service (VSS) under Vehicle > Business Add-Ins (BAdIs) > BAdI: Change and Filter of VMS Attachments in VSS Vehicle.
To add a document to a VMS vehicle, you select a document type and attach a document. A document type represents a classification for attachments, for example Presentation, or Text. In standard Customizing, you define document types that you can use in the BAdI Change and Filter of VMS Attachments in VSS Vehicle. For example, you create a document type VMS Documents not to be Displayed in VSS. In the BAdI, you can specify that attachments for this document type do not display in VSS. You can add attachments to this document type in VMS, but VSS users cannot view these documents. You define document types in standard Customizing. Navigate to SAP Customizing Implementation Guide > SAP NetWeaver > Application Server > Basic Services > ArchiveLink > Basic Customizing > Edit Document Types.

Browser not supported