DSD remain on truck Function

[Former Member]

Dear All,

I have a Question Concerning the DSD Cycle (Paper Based):

The Cycle is as follows:

1- Sales order to the Driver {Speculative Load} (Order 1)

2- Outbound delivery with referance to order 1

3- No Posting for Goods.

4- Visit List Created for Driver D1 , and Customer C1, Matrial M1 Quant 100 CAR

5- Dynamic Transportation Planning

6- Shipment Created.

7- Tour Data Entry Started

8- Check-Out M1 Qty = 100

9- Delivery execution for Customer C1 by M1 = 70 CAR

10- Check-In by 30 CAR for Driver D1

The System Behaves in this simple scenario as follws:

a Market Order for the customer by 70 CAR, and a return loading note by 30 CAR to the driver D1

Note that {Customer Sales Transaction Type 31} Activated in the Setting of (Document Control for Each Customer Sales Transaction Type)

and so that, the Goods Issue Takes Place as follows after settlement:

a- Goods Issue for Delivery 100 CAR for order 1 (Driver)

b- Goods Return by 100 CAR to clear the load of the (Driver)

C- Goods Issue for the Delivery Created for the Market Order for the Customer by 70 CAR

d- Return loading note by the 30 CAR (Driver)

my Q is: how to make the system behaves that the 30 CAR with the driver will remain on the truck , in other words to make the 30 CAR as the next day loading order as step 1 in the above mentioned scenaro, since in many cases the goods remains on the truck and the customer needs to see that with the driver and to be the next loading order to the driver, instead of returning the goods and re issue them again to the driver.

Thanks to give a closed solution for that problem, with detailed steps to carry on.

[marcin_milczynski]

Hi Omar,

In the check-in items there is a field 'Return on truck', which can be used to mark goods, that stayed on truck in order not to include them as a difference during difference determination before FSR. Otherwise the items that stayed on truck and are not included in the check-in will be added to the debit memo request for differences on driver account. However marking the field will only solve the problem of charging the driver with the goods stayed on truck, the other thing is that you need to have a load delivery for the tour next day in order to include the goods as speculative stock. For this you could implement determination of CSTT for driver order created for check-in based on reason code (until ECC6.0EHP6 it can be done using method BADI_DETERMINE_CSTATYP_DRV of BAdI /DSD/SL_FSR_DEFFMT_P) and for a new reason code 'Stayed on truck' create a load order for next day, the order can have automatic delivery, but the delivery has to be planned in the shipment for the next day. The delivery should be non-goods movement relevant, as the goods issue for goods on truck had been posted when they left warehouse and don't really come back to warehouse stock. This should be done automatically in case you have a mixed of truck sales only scenario with a visit list and you use Dynamic Transportation Planning (/DSD/RP_DYNDISP) for shipment creation otherwise you need to organize it with business.

Anyway seems you will need to implement

Regards,

Marcin

[Former Member]

This message was moderated.