Results 1 to 5 of 5

Thread: Transportation rate

  1. #1
    Member
    Join Date
    Jul 2002
    Location
    FRANCE, Europe
    Posts
    97

    Transportation rate

    Sorry to repost I did it in the wrong section

    Hello,
    we are a French company in the food industry and are implementing the transportation system, as the documentation on this is enormous we are facing some difficulties, for now to define a simple rate used commonely in europe :

    - 3 shipments in a load picked in Paris
    -> 1st shipment weight 90 kg, goes to Orleans (ZipCode 45)
    -> 2nd shipment weight 95 kg, goes to Poitiers (ZipCode 86)
    -> 3rd shipment weight 550 kg, goes to Poitiers (ZipCode 33)

    Carrier rate shows as follow :
    .........0-100kg | 101-600kg | 600-22000kg
    33.......10$/kg.......8$/Kg...........6$/Kg
    45.......20$/kg.......18$/Kg.........16$/Kg
    86.......30$/kg.......28$/Kg.........26$/Kg

    We would like to calculate the freight from the Load at the shipment level :
    1st shipment 90 x 20$ = 1800 $
    2nd shipment 95 x 30$ = 2850 $
    3rd shipment 550 x 28$ = 15400 $
    .......................................------------
    Total Cos...........................20050 $

    Our result in testing this was half satisfying as the systems made this calculation :
    1st shipment 90 x 28 $
    2nd................95 x 28 $
    3rd...............550 x 28 $
    All calculation are based on the last postal code delivered !?

    Calculation applies the correct Lookup type 1 (weight) but not the coorect type 2 (postal code), it takes the postal code from the last shipment (in the delivery sequence) of the load !

    We have set up a rate on a weight basis unit amount, Lookup type 1 as Weight and type 2 as Postal code, in the advanced rate definition we selected 'Shipment level payable' ...

    Any clue to the one who had the courrage to read this to the end !

    Regards

    Frédéric Knies - JDE Consultant
    Sales - Purchase - Stock - Pricing - Transportation
    B733.1 & Xe
    FRANCE

    Frédéric Knies
    8.11, 8.10, ERP8, Xe, B7331
    DB2/400, SQL, Oracle
    Sales - Purchase - Stock - Pricing - Transportation - PM
    FRANCE

  2. #2
    New Member ggac's Avatar
    Join Date
    Feb 2002
    Location
    FRANCE - Landerneau (near Brest)
    Posts
    19

    Re: Transportation rate

    (Like fknies is french, I prefer to answer him in french.)
    In short for the others, you can try to invert your schedule.
    Instead of :
    0-100 101-200 201-300 ....
    33
    45
    66

    Try
    33 45 66
    0-100
    101-200
    201-300

    We have try this here successfuly.
    ---------------------------------------------
    French answer.

    Bonjour,

    Nous avons chez nous été confrontés au même problème.
    Pour y arriver, nous avons établi les barêmes dans l'autre sens. Au lieu de définir les plages de poids horizontalement, nous les avons placé verticalement. Cela fonctionne comme attendu de cette manière.
    Attention, d'après JDE, cela ne devrait pas fonctionner ainsi et il est possible que cette solution ramène un jour le même résultat que votre paramétrage actuel. Soyez donc vigilant aux SAR que vous appliquez.

    Cordialement,

    Guenael GAC
    Distribution & Financials
    COOPAGRI BRETAGNE

    One World XE, SP21
    Oracle 8.1.6. / AIX 4.3.3 / Citrix

    One World 8.11 (8.94 B1)
    Oracle 9i / AIX 5.3

  3. #3
    Member
    Join Date
    Jul 2002
    Location
    FRANCE, Europe
    Posts
    97

    Re: Transportation rate

    Guenael,

    thanks for your response,

    we already tried this solution (we found that as we made a mistake during setting up our rate), but we can't work with the limitation of the 25 collumn for Look up type 1 as we need to have a minimum of 97 postal code range ;-((

    Do you think we could set up a schedule with rate1 as dpt 1 to 24, and rate 2 as dpt 25 to 49 etc ... ?

    ++> in the meantime we have achived to test this solution, same result !
    What was your setup ?


    Regards

    -----------------------------------------------------
    Guenael,

    merci pour votre réponse,

    nous avions déja testé ce schéma (pour être honnête c'était pendant la phase d'apprentissage et nous nous étions trompé) mais nous avons le problème de la limitation du nombre de colonnes (25 je crois). Hors nous devons rentrer des tarifs sur 97 départements au minimum, sans compter les tarifs spécifiques à certaines villes (code postal entier) qui explosent le compteur.

    Que pensez-vous d'un barème avec plusieurs taux, dont le taux 1 comprendrait les 25 premiers dpt, le 2nd taux les 25 suivants etc... théoriquement pour un client dans le 30 nous aurons le taux 1 à 0 et le 2 avec le bon tarif non ?

    ++> Entre temps nous avons réalisé le test et aboutissons au même résultat. De plus nous nous sommes rendu compte que si dans un barème un ou plusieurs taux n'étaient pas applicables, aucun taux n'étaient appliqués = 0 .
    Quel est votre paramètrage ?

    Cordialement
    Frédéric Knies
    8.11, 8.10, ERP8, Xe, B7331
    DB2/400, SQL, Oracle
    Sales - Purchase - Stock - Pricing - Transportation - PM
    FRANCE

  4. #4
    Senior Member
    Join Date
    May 2002
    Posts
    305

    Re: Transportation rate

    Actually that's what we did at a client once... when we had more breakouts
    then JDE allowed... we set up rate1 for 1-25 and then rate2 26-50... that
    way it if the number was 30 it would fall out of the rate1 and into rate2.



    thanks for your response,

    we already tried this solution (we found that as we made a mistake during
    setting up our rate), but we can't work with the limitation of the 25
    collumn for Look up type 1 as we need to have a minimum of 97 postal code
    range ;-((

    Do you think we could set up a schedule with rate1 as dpt 1 to 24, and rate
    2 as dpt 25 to 49 etc ... ?

    Regards

    -----------------------------------------------------
    Guenael,

    merci pour votre réponse,

    nous avions déja testé ce schéma (pour être honnête c'était pendant la phase
    d'apprentissage et nous nous étions trompé) mais nous avons le problème de
    la limitation du nombre de colonnes (25 je crois). Hors nous devons rentrer
    des tarifs sur 97 départements au minimum, sans compter les tarifs
    spécifiques à certaines villes (code postal entier) qui explosent le
    compteur.

    Que pensez-vous d'un barème avec plusieurs taux, dont le taux 1 comprendrait
    les 25 premiers dpt, le 2nd taux les 25 suivants etc... théorique!

    Cordialement


  5. #5
    What are the current rates?
    Have there been any major adjustments?
    __________________________________
    Dumitru from Food transportation

Thread Information

Users Browsing this Thread

There are currently 1 users browsing this thread. (0 members and 1 guests)

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •  
The legal restrictions and terms of use applicable to this site are available here.
Use of this site signifies your agreement to the terms of use.
JDELIST is NOT affiliated with JD Edwards® & Company, Oracle or Peoplesoft. Contents of this site are neither endorsed nor approved by JD Edwards® & Company and, or Oracle.