Ansicht
Dokumentation

/DSD/BF: Automatic Processes in Route Settlement (New) ( RELN/DSD/603_DSDBF_SLAUT )

CPI1466 during Backup   ROGBILLS - Synchronize billing plans  
This documentation is copyright by SAP AG.

Short text

/DSD/BF: Automatic Processes in Route Settlement (New)

Use

As of SAP ECC 6.0, Enterprise Extension SCM, Enhancement Package 3(EA-SCM 603), business function Enhancement of the DSD Process (/DSD/BF), you can automate additional process steps in route settlement. The following new functions are available:

• Create orders automatically

• Start final settlement run automatically

• Improved mass data processing during final settlement run

Create orders automatically

Up to now, you could only create orders in the system during the final settlement run. A tour had to be released before the settlement process could be started. In practice, this can be too late for the subsequent process flow. This would be the case, for example, if a driver brought back a new order from a tour and the subsequent tour settlement was delayed, meaning that shipment preparations and loading were already complete for the next tour. This would mean that the driver's new order could not be delivered until the next tour.

You can now create orders separately from the final settlement run as soon as the data is available in the system, in other words, once the tour data has been transferred to the database table RADB on physical completion of the tour (upload).

Start final settlement run automatically

You could previously start the final settlement run of a tour automatically if the tour data had been transferred back to the system (upload), and you used the appropriate settlement type.

In conjunction with the new status concept of the overall tour status, you can also determine the conditions for an automatic final settlement run. The option of activating an automatic final settlement run, and not having to intervene manually in this process step, is particularly significant for the mobile process. The final settlement run is included in the automatic process chain.

Improved mass data processing during final settlement run

Up to now, you could only process individual tours manually for the final settlement run. This can result in a heavy workload if there is a large number of tours to be settled using the paper-based process.

There is not a more efficient mass data processing tool available for manual processing of the route settlement in the settlement cockpit. You can execute several tours simultaneously in each settlement step. Reports are provided for this purpose, which can be scheduled as background jobs.

Effects on Existing Data

The following user interface elements are new:

Transaction	Program/Screen	UI element
/DSD/SL_AUTOFSR_EXCL	SM30	/DSD/SL_ASL_EXCL
/DSD/SL_MS_PRESALES	/DSD/SL_ASL_MS_PROCESS/2000	Dialog box DSD: Settlement for Mass Processing
/DSD/SL_MS_SETTLE	/DSD/SL_ASL_MS_PROCESS/1000	Dialog box DDSD: Settlement in Mass Processing

Effects on Data Transfer

Effects on System Administration

Effects on Customizing

You make the settings for this function in Customizing for Direct Store Delivery Customizing under Route Accounting -> Basic Functions -> Settlement Type -> Define Settlement Types.

In the SAP Easy Access menu under Logistics -> Logistics Execution -> Direct Store Delivery -> Route Settlement -> Automatic Settlement Process -> Edit Exclusions, you can specify which scenarios should have an automatic final settlement.

Further Information

For more information, see the central Release Note for the business function Enhancement of the DSD Process.

SUBST_MERGE_LIST - merge external lists to one complete list with #if... logic for R3up   PERFORM Short Reference  
This documentation is copyright by SAP AG.

Length: 4935 Date: 20240417 Time: 014412     sap01-206 ( 80 ms )