VSS

Skip to end of metadata
Go to start of metadata

You are viewing an old version of this content. View the current version.

Compare with Current View Version History

Version 1 Next »

Prerequisites

You can use this function to use a vehicle created in the Vehicle Management System (IS-A-VMS) in Dealer Business Management (DBM). For example, you can purchase a vehicle in VMS and then use this vehicle in the DBM 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 DBM and VMS.
Dealer Business Management (DBM) 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 DBM 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 DBM, for example for pre-delivery inspection.
DBM usually handles one vehicle at a time, not several in parallel.
Typically, in DBM a purchase or a sales order contains one vehicle. DBM does not use variant configuration. DBM provides an integrated solution for the complete vehicle service and warranty processes including split capabilities. The DBM vehicle master provides dealer-specific data such as registration, registration history, warranties, partner information (such as owner or driver), and leasing information. DBM 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 DBM

You can use action QDBM (enable vehicle for DBM), in transaction VELO. This action enhances the VMS vehicle with the relevant DBM object information, for example warranty and registration data. You also enter some additional data that is required for DBM, for example the model sales code. You can then use the vehicle in DBM, 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 DBM

You can use action QVMS to enable a VMS vehicle from the DBM application.
For example, if you select a VMS vehicle from the DBM 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 DBM. The system then uses action QVMS to enable the vehicle for DBM.
Note: To enable a VMS vehicle for DBM, action QVMS must be allowed for the vehicle. This depends on the action matrix Customizing for the vehicle.

A variant configuration subscreen

In the DBM vehicle master transaction (/DBM/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 Dealer Business Management 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 Dealer Business Management 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 /DBM/SAPLVM07, 2100, Active.

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

  • In Customizing for Dealer Business Management 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 Dealer Business Management 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: /DBM/SAPLORDER_UI, 2240.
  • In Customizing for Dealer Business Management 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/DBM 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/DBM 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/DBM integration possibilities.

The ability to differentiate between VMS and DBM actions

You can differentiate between the actions that belong to DBM, and the actions that belong to VMS. You can specify whether a vehicle action can be used in VMS, DBM or both in Customizing for Dealer Business Management (DBM) under Vehicle > Vehicle Master > Vehicle Control. This ensures that when you use transaction /DBM/VM, the system displays valid actions only.
You usually use actions in DBM 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 DBM vehicle master transaction (/DBM/VM). Also, the coding for the function modules of the action is typically written for either DBM or VMS, not both.

The ability to view VMS documents in DBM

In the DBM vehicle transaction (/DBM/VM), you can view attachments created in VMS. The DBM 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 DBM, but you cannot edit them. You can also view and edit DBM attachments.
You can restrict VMS attachments for DBM. For example, you may not want DBM users to view VMS legal or accounting documents. To specify the VMS attachments you want to display in DBM, see Customizing for Dealer Business Management (DBM) under Vehicle > Business Add-Ins (BAdIs) > BAdI: Change and Filter of VMS Attachments in DBM 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 DBM Vehicle. For example, you create a document type VMS Documents not to be Displayed in DBM. In the BAdI, you can specify that attachments for this document type do not display in DBM. You can add attachments to this document type in VMS, but DBM 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.

  • No labels

Vehicle Sales and Service