on ‎2016 Jun 03 7:02 PM
Hello Experts,
We need to populate the transit time on the freight order based on the carrier info ( not from the MTR or lane ) . For example : To go from place A to place B - UPS takes 3 days whereas FedEx takes 2 days . This transit time is available to us from another server - Connectship that we access during planning of the freight order
We have tried using the BADI /SCMB/EX_DDD and /SCMB/EX_LDDD_DDD but the option of passing the carrier does not exist . Also we tried with creating a custom Distance duration determination strategy but this gets triggered before the carrier selection takes place and thus we are not able to get the transit time .
Can you please advise any way to update the Transit duration on the Freight Order ?
Thanks,
Saksham
Request clarification before answering.
Saksham,
There is a workaround, provided the number of carriers are limited for each lanes.
We used different means of transport for each of the carriers. Now the duration that you define at the MTR level can be specific to the carrier. But as I said this is just a work around considering the number of carriers. Be careful about the performance factor too before finalizing this workaround.
Bimal
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
there is a lot of transit duration functionality in the Freight Agreement. You are almost describing a classic small parcel or LTL scenario. Make sure your FA config allows those fields to be edited and then you have lots of options for determination duration - calendar, condition (which could include multiple o/d pairs), service level...
Hope this helps
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Saksham,
This is pretty much 'duration determination' though it's carrier specific. Custom process controller methods can be created, specifically for distance and duration determination. If your requirement is only the duration then you could also update only duration. You could explore the method DDD_IGS and accordingly assign a custom class. This would work better if distance is fixed on your lane so that Distance & Duration determination is primarily used for duration only. This way you can remove the buffer related methods (check & update) because if the duration is carrier specific then buffer won't help.
Best Regards,
KC
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi KC,
Thanks for your response !
We tried that already however the carrier is not determined till the point DDD_IGS. the TSP determination happens after the DDD strategy and therefore we cannot pass the carrier in DDD_IGS to determine the duration.
Can you advise how to achieve that ?
Thanks ,
Saksham
Saksham,
Have you explored the change strategy, i.e. have the change controller determine when a carrier is being assigned and accordingly trigger the distance & duration determination? If DDD is already enhanced, then the duration will be updated when you assign a carrier and save the FO.
Best Regards,
KC
Hi Saksham,
if your business process permits, use Schedules where you can update transit time at carrier level and communicate with connectship to update the transit time at the time of creation of schedule.
let me know if it helps.
Regards
Srinivas.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Srinivas,
Presently we are not using schedules.
Not sure if I followed you - per my understanding the schedules can be created location to location and also the transit time varies from zip to zip . So if lets say we have 10 plants , 20,000 customers , 40 carriers - in this case the overall master data volume would become very huge - I doubt if it is feasible to maintain schedules to that extend .
Can you please cite an example of the schedules to be created
Thanks,
Saksham
| User | Count |
|---|---|
| 17 | |
| 16 | |
| 4 | |
| 3 | |
| 2 | |
| 2 | |
| 1 | |
| 1 | |
| 1 | |
| 1 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.