Direct Store Delivery Connector 
Purpose
You can employ the DSD Connector when drivers and presellers use mobile devices on their tours, which need to be equipped with the data and functions the employees require to perform their activities.
The DSD Connector component converts and saves tour-related data received from the backend of the DSD system. The saved data can be received by the mobile device, processed on the mobile device and then sent back to the backend of the DSD system.
Implementation Considerations
Use of the DSD Connector is a technical prerequisite for supplying the mobile devices with the required data.
Integration
The DSD Connector is part of a system landscape that consists of the following components:
- DSD Backend
- DSD Connector
- SAP Mobile Engine
- Mobile DSD
DSD Connector in the DSD system landscape
Features
The DSD system generates IDocs when it saves shipments or DSD visit lists. These IDocs are used as an interface for connecting mobile devices to the backend of DSD and are sent using the ALE layer.
SAP Mobile Engine does not have the SAP_APPL layer and is therefore unable to process IDocs. The DSD Connector Input Interface receives IDocs sent from the DSD system and converts them. The DSD Connector Input Interface is called by the ALE layer. It converts the IDocs using assignment rules.
Using these assignment rules, you define in Customizing which fields from the IDocs the system maps to which fields in the DSD Connector tables. There are much fewer fields in the DSD Connector tables than in the IDocs. When you have assigned the data from the IDocs to the target structures in the DSD Connector, the system saves this data in the DSD Connector tables.
Once the master data has been saved, the DSD Connector Input Interface launches the determination of the condition records in the DSD system for the materials and customers listed in the tour-related data.
The DSD Connector Cockpit is an application interface that is connected to the DSD Connector.
In the DSD Connector Cockpit, you assign a driver and a vehicle to a mobile device. Using this assignment and the driver and vehicle data from the IDocs (that the DSD system has transferred), the DSD Connector Input Interface assigns the tour-related data to a mobile device. This means that the tour-related data can later be sent to the correct mobile device.
You call the DSD Connector Cockpit using transaction /DSD/ME_CPT.
With the next synchronization request, the mobile device transfers all the data that was created or modified during a tour via the SAP Mobile Engine to the DSD Connector. When doing this the SAP Mobile Engine also calls a range of functions in the DSD Connector using RFC. The SAP Mobile Engine passes the data from the DSD Mobile Device on to these functions, which then save the transferred data in the tables in the DSD Connector.
When all data has been successfully uploaded from the DSD Mobile Device to the DSD Connector, the upload from the DSD Connector to the DSD system is started. To do this, the transfer function (upload) in the DSD Connector is called. The upload function reads all data that belongs to a tour from the DSD Connector and converts it into the structures of the DSD system. With this converted data, the transfer BAPIs in the DSD system are then called by RFC. After numerous checks, these BAPIs save the data in the Route Accounting database. The data is then ready to be settled in the DSD Settlement Cockpit.