Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

In DSW, the salesperson can choose to create a lead via a configurator or directly from a list of published vehicles (inventory). An initial offer can be prepared for the customer with typical automotive pricing structure which includes the functionality to add discount by percentage or absolute amount, add upselling additional items or upselling additional packages, capture financing or leasing information, capture down payment information and assign sales campaign. Pricing simulation function offers the ability to verify the latest pricing condition and ensures the price displayed in the offer is according to the price maintained in VSS. Saving the sales offer in DSW triggers the creation of sales quotation in VSS.   

Once the customer is satisfied with the offer, the salesperson can convert the sales offer to a sales order
in DSW 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 . Status update of the vehicle and the sales order occurs on real-time basis between VSS and DSW. 

Solution Overview 

...

Integration Component Overview  

...

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 VSS-DSW integrationsolution. This component delivers different type of interfaces (inbound, outbound, or bi-directional) for different integration objects
(for example business partners, vehicle, and sales order). 

DSW application can be integrated with other application or solution via the One Dealer Integration Layer
or commonly known as ODIL Neuro. ODIL deliver standardized API that offers inbound and outbound integration with DSW. It is a set of services implemented in MS Azure focusing on security, configuration, and data transfer. It supports not only exchanging business transaction 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 constructed for different direction depending on the integration objects. 

...

  1. VSS has the REST Client as a component to generating generate the connection to DSW.  

  2. Distribution controller defines when a particular integration object needs to be processed (immediate, time interval, etc). 

  3. Data access controller performs the relevant activities on the integration objects depending on the request coming from the interface for example read, write, update, etc. 

  4. REST Server responds to the initiated call from DSWthe incoming application

...

VSS-DSW Component Communication 

The following describes the integration point in scope of VSS-DSW integration:

...

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

Process

Vehicle Reservation

DSW > VSS

9

Process

Vehicle Reservation

VSS > DSW

10

Process

Sales Order (Contract)

  • Quotation

  • Sales Order

  • Trade In

  • Down Payment

DSW > VSS

11

Process

Vehicle Assignment to Sales Order

VSS > DSW

12

Process

Vehicle Status Management

VSS > DSW

13

Process

Sales Order Status Management

DSW > VSS

14

Process

Sales Order Status Management

VSS > DSW