SAP Mobile Direct Store Delivery - Process
Overview 
Purpose
This overview covers all activities that need to happen in a Direct Store Delivery process that includes mobile devices:
- Data download
- Check-out
- Tour processing
- Check-in
- End-of-day
- Data upload
Process Flow
The SAP Mobile Direct Store Delivery (MDSD) process consists of the following main steps:
Download from backend system to mobile device
During synchronization, transactional data and master data is downloaded from the backend system to the mobile device.
Start-of-day
This is the initial activity a sales representative performs at the beginning of the day. Start-of-day consists of recording basic tour data, such as driver ID, vehicle ID, and odometer reading.
Check-out
Check-out consists of checking what was loaded onto the vehicle. This includes both materials and cash. Sales representatives can enter potential discrepancies, which can then be verified and approved by their supervisors.
Tour processing
Sales representatives view a list of all visits. For each visit, they either perform the associated activities or update the visit status with a reason code to indicate why they could not visit a customer (for example, customer was closed, driver ran out of time). Sales representatives can also rearrange the order of their visits as well as create new unplanned visits. The main activities performed at the customer site are:
·
Delivery with pre-sold orders – At the customer site,
sales representatives take the pre-ordered stock out of their truck and print
a delivery note or an invoice.. If necessary, sales representatives can add
items and change item quantities.
The system also supports the return of goods (for example, spoiled goods,
wrong items) and the return of empties. Sales representatives can add returned
goods and empties to deliveries.
· Delivery without pre-sold orders – This is the delivery of materials that were not ordered. The sales representative sells the materials directly off his vehicle. In this process, the sales representative creates new deliveries. This includes both normal outbound deliveries and return inbound deliveries. The physical processing of the delivery is similar to that of pre-sold order deliveries.
· Invoice issuing – In Direct Store Delivery, unlike other SAP systems, delivering and invoicing are part of the same basic process. The sales representative can issue a legal invoice. Customers who do not receive an invoice, receive a delivery note instead.
· Payment collection – Sales representatives collect payments for current deliveries or outstanding open items. Customers are issued payment receipts.
· Order taking for future deliveries – Sales representatives perform pre-selling order taking. These orders are then delivered during one of the next tours.
The following general tour-related activities are also supported:
· Recording of inventory adjustments – Sales representatives can record inventory adjustments, for example, in the case of breakages.
· Recording driver expenses – Sales representatives can record miscellaneous expenses, such as tolls, parking fees, and gas.
Check-in
Check-in is a validation of materials returned to the warehouse. The sales representative enters returned quantities, which can then be verified and approved by a supervisor. During pre-settlement balancing, the returned materials (initial balance – deliveries + returns = check-in balance) are checked.
End-of-day
End-of-day consists of recording end-of-tour data and returned cash/payments. During pre-settlement balancing, the returned cash/payments (beginning balance – driver expenses – payments to customers + collections from driver + collections from customers = end-of-day balance).
Upload from mobile device to backend system
During synchronization, transactional data is uploaded from the mobile device to the backend system.