...
Once the customer is satisfied with the offer, the salesperson can convert the sales offer to a sales order
where eventually, the creation of sales order will be triggered in VSS. The subsequent process
or sequence of event on the sales order for example vehicle assignment, goods movement, order split, and invoicing are then traditionally handled in VSS Order Processing.
Solution Overview
...
No. | Description |
|---|---|
1. | Lead processing Lead can be created from multiple sources depending on scope of implementation. DSW can communicate with various lead processing tools either SAP based solution or non-SAP based solution. There are available APIs within DSW that can be consumed by the various lead processing tools to send lead to DSW. Customer processing Customer can be created or maintained in various solution depending on scope of implementation. For example, customer can be created in SAP CRM and transmitted to DSW via an API. On the other hand, for implementation without CRM system, customer master can also be created and maintained in DSW. |
2. | Front-end DSW is the front-end, customer facing solution allowing the salesperson to manage lead and sales activities. The sales process within DSW is workflow driven and configurable depending on customer business requirement. |
3. | Back-end Back bone of the vehicle sales processing that contains functions such as order processing cockpit, order engine, goods movement, order splitting, vehicle assignment and invoicing to complete the end-to-end vehicle sales process. The back end is the source of information for vehicle model, features, prices, vehicle inventory and additional items. It is supported by the standard SAP functionalities such inventory management, pricing condition technique and recording financial accounting entries for profitability analysis. |
Component Overview
...
The above diagram describes the component overview of the solution. This component delivers different type of interfaces (inbound, outbound, or bi-directional) for different objects (for example business partners, vehicle, and sales order).
DSW can be integrated with other application or solution via the One Dealer Integration Layer
or commonly known as ODIL Neuro. ODIL deliver ODIS (OneDealer Integrated Services) is the integration layer which delivers standardized API that offers inbound and outbound integration. It is a set of services implemented in MS Azure focusing on security, configuration, and data transfer. It supports not only exchanging business transaction transactions for various means, but also the user access authentication, user/data mapping, and single sign-on options are embedded in the framework.
The API are is constructed for different direction depending on the integration objects.
Depending on the system architecture of the project implementation, ODIL can communicate with VSS
via the SAP Cloud integration. However, in any case, a direct connection to VSS is also possible.
...
The following describes the integration point in scope of VSS-DSW:
No. | Area | Objects | Description |
|---|---|---|---|
1. | Master Data | Settings/Lookup values | VSS > DSW |
2. | Master Data | Model / Features / Price | VSS > DSW |
3 | Master Data | Pricing Simulation | DSW > VSS |
4 | Master Data | Vehicle (Stock) | VSS > DSW |
5 | Master Data | Business Partner & Contact Person | DSW > VSS |
6 | Master Data | Business Partner & Contact Person | VSS > DSW |
7 | Master Data | Revenue / Additional items | VSS > DSW |
8 | Master Data | Used Vehicles received from DSW | DSW > VSS |
9 | Process | Vehicle Reservation | DSW > VSS |
10 | Process | Vehicle Reservation | VSS > DSW |
11 | Process | Sales Order (Contract)
| DSW > VSS |
12 | Process | Vehicle Assignment to Sales Order | VSS > DSW |
13 | Process | Vehicle Status Management | VSS > DSW |
14 | Process | Sales Order Status Management | DSW > VSS |
15 | Process | Sales Order Status Management | VSS > DSW |
16 | Process | Used vehicle Purchase Order | DSW > VSS |
17 | Process | Used Vehicle Goods Receipt | DSW > VSS |