Dealer Portal Vs DBM

[Former Member]

Hi Gurus,

I would like to understand few things here.

There is this Dealer Portal which uses the services of VMS, Spare Parts Functions and WMS.

Now as I understand there is add-on called DBM. What are the differences we have incase DBM is activated.

Secondly, if we activate DBM, will it be like previous VMS, WMS settings are irrelevant or those are still useful.

Thanks for your replies and points will surely be rewarded.

Regards,

Rahul

[Former Member]

Hi Rahul,

the VMS is for the importer processes.

In contradiction DBM is for the sales&service processes.

Usage of DBM is more or less independent for the dealer portal usage.

Kind regards

Robert

[Former Member]

Hello Rahul,

the Dealer Portal is the web-enabled front-end for the dealer for vehicle and service/spare parts ordering at the importer. Additonally, the dealer can create warranty claims and track the processing status. The Dealer Portal is to be implemented by the importer to collaborate with the dealer who may not run an integrated system landscape with the importer's systems*.

The SAP DBM is an addon to ERP, and makes use of some VMS functionality, eg. the vehicle object and its action execution. The DBM is mainly intented to be used by dealers who sell vehicles to endcustomers, perform service orders for customers' vehicles, and also create warranty claims (based on service order items, if appropriate).

• Nevertheless, the dealer may purchases vehicles via the dealer portal; the vehicles are then later created in his DBM/DMS system automatically or manually, depends on the overall integration scenario of the dealernetwork and the importer.

Best, Ute

[stephan_bantlin]

Hi Rahul

just to be precise.

DBM also has spare parts management functionality which is delivered within the ERP. So you have a whole inventory management system, Purchase ordering system and an material resource planning is available within DBM.

best regards

Stephan Bantlin

[Former Member]

Hi

I came to know that DBM as a product is replaced by ADP (Automotive Dealer Portal) which may be still using DBM as the backend. Does anyone know about this?

BR

Niranjan Rao

[former_member265044]

Hello guys!

Does enybody has disk 51019708, which is add-on for Dealer Portal (SAP DI - WES INTERFACE 3.0)?

Thanks!

[kaus_desh]

Hey rahul

As far as i know DBM is only for Service operations of u r dealership also warranty mgnt and .....which can be integrated with VMS and SPM ( spare parts mgnt )

Otherwise its benificial for worskshop.Can be used at DEALER end.

VMS is limited to VEHICLE SALES and is used as IMPORTER.

SPM is again to activate for dealership spareparts operations.

Hope so answer is clear

[Former Member]

Hi Kaustubh,

VMS is not limited just to vehicle SALES and IMPORTERS. VMS manages also the purchase of vehicles, and by its kind of composite/service-like architecture pretty open to manage other processes as well, eg. integration to production. Some SAP customers use the VMS as central vehicle repository just to store vehicle data. The VMS may not serve all feature&function requirements in vehicle related-businesses, but it is designed to allow addons and extensions.

The Dealer Portal is not only in use by importers, also suppliers and OEMs have implemented it to give access to service parts ordering, warranty claims creation and tracking as well as vehicle (direct) ordering functionality to external and internal parties.

Best, Ute

[Former Member]

As a dealer management system, this component supports the industry-specific sales and services processes of dealers and dealer organizations, as well as vehicle importers, authorized dealers, and OEM-dedicated vendors. This includes handling of new and used vehicles sales, vehicle service, and parts management.

The component is distinguished by its multi-brand capability as well as its ability to manage different locations. Customer-specific settings with regard to language and country, such as currency and taxes, for example, also mean that it can be deployed worldwide.

The component supports the integration of processes between the dealer and the Original Equipment Manufacturer (OEM) within a vehicle order (vertical integration). Furthermore, it also supports horizontal integration between dealers. For example, members of dealer organizations can obtain an overview of the parts and vehicles in stock for the entire dealer organization.

As a dealer, you can manage an order from its creation, through its completion, and right down to its billing phase. Orders are controlled using an order engine that enables processes to be modeled flexibly. In this way, different requirements can be met that arise from the OEM or due to the size of a company. To ensure that country-dependent OEM requirements are met, SAP provides relevant techniques, for example, Business Add-Ins (BAdIs) and condition technique.

For reasons of simplicity, the term dealer is used in the following documentation; this term could, however, be referring to the vehicle dealer or dealer organizations, vehicle importers, franchised or authorized dealers, or OEM-dedicated vendors.

Integration

Dealer Business Management (IS-A-DBM) is fully integrated in the following SAP application components:

· Materials Management (MM)

· Sales and Distribution (SD)

· Financial Accounting (FI)

· Controlling (CO)

· Logistics u2013 General (LO)

DBM uses the vehicle as a central object. You can save warranty claims directly in the order. For this, the component is integrated in Warranty Claim Processing .

The component offers the following functions:

· Customer management

· Processing of actions, for example, a mailing campaign

· Processing of business activities, for example, a sales call, a letter, a telephone call

· Crossmatching

· Vehicle model management in the vehicle model master

· Vehicle management in the vehicle master

· Vehicle search

· Material data management

· Availability check for parts

· Creation of DBM orders

· Customer credit limit check

· Pricing

· Processing of confirmations

· Handling of goods movements and invoice receipts

· Billing

· Order Splitting

· Printing of documents

· Cash desk functions for sales of parts

· Creation of warranty claims

· Status check for parts to be returned

[Former Member]

As a dealer management system, this component supports the industry-specific sales and services processes of dealers and dealer organizations, as well as vehicle importers, authorized dealers, and OEM-dedicated vendors. This includes handling of new and used vehicles sales, vehicle service, and parts management.

The component is distinguished by its multi-brand capability as well as its ability to manage different locations. Customer-specific settings with regard to language and country, such as currency and taxes, for example, also mean that it can be deployed worldwide.

The component supports the integration of processes between the dealer and the Original Equipment Manufacturer (OEM) within a vehicle order (vertical integration). Furthermore, it also supports horizontal integration between dealers. For example, members of dealer organizations can obtain an overview of the parts and vehicles in stock for the entire dealer organization.

As a dealer, you can manage an order from its creation, through its completion, and right down to its billing phase. Orders are controlled using an order engine that enables processes to be modeled flexibly. In this way, different requirements can be met that arise from the OEM or due to the size of a company. To ensure that country-dependent OEM requirements are met, SAP provides relevant techniques, for example, Business Add-Ins (BAdIs) and condition technique.

The term dealer could refer to the vehicle dealer or dealer organizations, vehicle importers, franchised or authorized dealers, or OEM-dedicated vendors.

Dealer Business Management is fully integrated in the following SAP application components:

· Materials Management (MM)

· Sales and Distribution (SD)

· Financial Accounting (FI)

· Controlling (CO)

· Logistics u2013 General (LO)

DBM uses the vehicle as a central object. You can save warranty claims directly in the order. For this, the component is integrated in Warranty Claim Processing .

The component offers the following functions:

· Customer management

· Processing of actions, for example, a mailing campaign

· Processing of business activities, for example, a sales call, a letter, a telephone call

· Crossmatching

· Vehicle model management in the vehicle model master

· Vehicle management in the vehicle master

· Vehicle search

· Material data management

· Availability check for parts

· Creation of DBM orders

· Customer credit limit check

· Pricing

· Processing of confirmations

· Handling of goods movements and invoice receipts

· Billing

· Order Splitting

· Printing of documents

· Cash desk functions for sales of parts

· Creation of warranty claims

· Status check for parts to be returned

[Former Member]

Hi Rahul,

Yes, DBM is add on to R/3. We require VMS component for vehicle master configuration. This require IS auto activation.

This is highly flexible for dealer business segment due to object oriented action event based customizable programming.

It covers complete domain process of automobile dealer business segment. I am working in one of the major implementation of DBM for last 2 years.

Regards,

Shabeer

[Former Member]

I believe it can be verified in SAP Solution Map. As a matter of fact we are trying to ascertain this information ourselves as we have an upcoming project in Sri Lanka for a year. So we are also looking for a good resource to join the project. If you can refer someone please email to me on the email listed in my profile

Cheers

[Former Member]

Tirtha

Your mail id is not displayed...Can you give the id here....