Ansicht
Dokumentation

Master Data for Direct Store Delivery Backend ( RELNLE_DSD_MD_472DSD )

Master Data for Direct Store Delivery Backend ( RELNLE_DSD_MD_472DSD )

PERFORM Short Reference   rdisp/max_wprun_time - Maximum work process run time  
This documentation is copyright by SAP AG.
SAP E-Book

Short text

Master Data for Direct Store Delivery Backend

Use

As of SAP R/3 Enterprise 2.00 (EA-APPL 200) you can use Direct Store Delivery Backend (DSD Backend). Existing master data has been enhanced and new master data created for DSD Backend.

All transactions for maintaining master data can be called from the same menu option: Logistics → Logistics Execution → Direct Store Delivery Backend → Master Data.

Customers:
You can store calendars for planned deliveries, telephone calls, and visits in the customer master.

Customer address data can be geocoded. Clear coordinates such as degree of latitude and degree of longitude are assigned to an address. If you want to geocode house numbers, you must purchase and install the relevant map data for the area from a third party.

You can make enhancements to the payment conditions for on the spot payments, such as cash payer or allowed means of payment.

Drivers:
You create the drivers in the customer master. When you create a driver in the customer master, you can use an existing account group or a separate account group for drivers. You determine the account group for drivers in Customizing.

In the DSD additional data you specify the transportation planning points in whose area a driver works.

You can assign a driver the drivers license categories you have specified in Customizing.

You can determine lock times during which the driver is not taken into account in dynamic transportation planning.

Vehicle:
You create the vehicles in the equipment master or fleet master.

You can assign a vehicle the drivers license categories you have specified in Customizing.

Tour:
A tour is created for a route with a visit plan type, and optionally for a transportation planning point. The tour contains information on the driver and alternate driver, and on the vehicle and trailer. The system checks whether the required drivers license categories for the vehicle are covered by the drivers license categories.

If multiple tours are created for the same route with the same visit plan type and transportation planning point, the deliveries are distributed to shipments in dynamic transportation planning according to the order of the tours.

Material:
On the DSD Additional Data tab in the material master, you can determine the DSD grouping you want the system to use to determine the delivery calendars in the DSD process if the requested delivery date is determined in order entry.

This let you set up different delivery cycles for different materials for the same customer groups (for example, newspapers daily, but magazines only once a week).

On the Vehicle Space Optimization Data and Vehicle Space Optimization Plant Data tabs, you can enter control parameters that are transferred via an interface to an external vehicle space optimizer.

Effects on Existing Data

Existing data is not affected.

Effects on Data Transfer

You do not have to transfer data from an earlier release.

Effects on System Administration

If you use geocoding at street level, you must purchase, install, and administer the relevant third-party map data.

Effects on Customizing

You call the DSD processes using the DSD Backend node in the Reference IMG: Logistics Execution → Direct Store Delivery Backend.

Existing Customizing settings are not affected.

Further Information

For more information on DSD Backend, see the SAP Library.






rdisp/max_wprun_time - Maximum work process run time   BAL Application Log Documentation  
This documentation is copyright by SAP AG.

Length: 4095 Date: 20240603 Time: 042934     sap01-206 ( 73 ms )