This blog belongs to the overall introduction blog about the About The New, New Automotive Dealer Portal. We would like to give you an overview on the features and function for vehicle sales management, as available per the Business Package “Automotive Dealer Portal for Vehicle Management 1.4“.
When dealers purchase vehicles, they must have access to the systems of the importers and OEMs. The quality of this access significantly impacts the effectiveness of the cooperation between dealers and importers. Are dealers able to access the supply chain of the importers quickly and comprehensively for their needs, can they see planned vehicles, unsold vehicles in production or e.g. used returns from fleet customers, are they able to place orders earlier for a vehicle than waiting for the moment when finished vehicles leave the assembly plant. Backorder processing should become an exception, no more complex change of open sales order items with individual vehicles. Search capabilities across the whole pipeline should not lead to an empty table. The dealers will work within the pipeline of the OEM and importer network and reduce their efforts to check for vehicles in other channels.
These benefits for vehicle sales management can be achieved through the use of the automotive dealer portal. This automotive dealer portal is operated by the OEM, importer or wholesale organization as a web-frontend of their own SAP ERP solution for their retail network. The automotive dealer portal offers role-based and web-enabled user interfaces and functionality of the SAP Vehicle Management System, tailored for the role of automotive dealers.
Let's check the functionality and take a close look at it. Just not to forget, I'm accessing the business package through the SAP Enterprise Portal.
On the left hand side, you see the navigation panel. There are three sections: "detailed navigation", below that is "services", I will explain the purpose a bit later in this blog, and "Portal Favorites", this one should be clear for you.
The work set "work overview" is displayed in the content area.
Here you see the central overview of tasks that are derived out of my user settings and assignments. This central overview includes a powerlist of vehicles that
From here, relevant vehicles for each category are listed. I select a vehicle in the list and work with it by the execution of a user action.
The user actions are context sensitive (remember, in the old dealer portal this was always a long list and untrained users often did the "try&error" way), and only possible actions can be selected from the drop-down box.
Below the Work Overview, is the
The vehicles work set starts with the search screen for vehicles. Let us see whether I can find a suitable vehicle for our customer, the end customer:
First, we select one or more vehicle models from the drop-down list and enter additional data.
Additional data?
In addition to the vehicle configuration - what you see on the right side of the content area -, further vehicle data explain the supply chain status of a vehicle. I can search for vehicles based on their planned delivery dates (that date could be set by the assembly plant) or other logistic data, e.g. status information like "ordered", "sold" or across vehicle locations what can be a storage location but could also be something like "under way to custom stock in Singapore" and so on. These statuses are the same as in the SAP Vehicle Management System, the backend system. The search goes across the vehicle database, and is pre-filtered through user authorization settings done for my user and role to keep control what dealers can see and what has to stay importer internal.
Found vehicles are listed in a table.
I could:
To order one of the found vehicles for a customer, I select a vehicle and then select the user action "Create sales order for vehicle". I'm asked to enter necessary and further order and vehicle data.
A sales order for my dealer account will be placed in the backend system, I just need to click on the "execute" button.
This vehicle is than added to the "vehicles scheduled for delivery" category in the work overview iview.
Let's see what else is there:
In the navigation panel, click on the work set "Documents":
Documents mean ERP SD sales orders and inquiries. Here you can search for sales orders and inquires that are created for your dealer account. Inquiries can be used just to store customer demand; the customer may return later to the showroom and will complete the configuration then and hopefully order a vehicle. The inquiry can be copied to a sales order and the chosen configuration is taken to create a new vehicle. Inquiries can also be used as a template to accelerate the configuration of vehicles, mainly used for complex vehicle configurations - in this situation users don't have to start from scratch.
To complete the close look at the navigation panel - let me spend some time on
First of all, these services have nothing to do with enterprise services or service bundles (as you may think): The three entries are kind of simple shortcuts for this business package.
Is this enough information for a first overview on the new Business Package Automotive Dealer Portal for Vehicle Management? It has a compelling look and is easy to use, right?
What else is for your interest?
I hear you asking ... how is this house built? How can it be extended so to say "customized"? What about user settings and further personalization? Well, this is another blog.
Will come!
Until then, all the best,
Ute