[ebauchwitz]

Our group is currently implementing a new process to allow non-traditional lanes into OTM 4.5. Our goal is to automate each step (planning, tendering) through reoccurring scheduled jobs. We've established new ref nums from integration which include the carrier scac code and buy shipment rate. These will carrier through to the buy shipment but will not update the shipment table. We're able to build buy shipments using a generic rate with open ended locations, but we haven't had success applying a specific carrier and rate to the load without having to edit the service provider and cost (manually).

Does anyone know the best way to update the buy shipment with these two ref num values? We're looking for a function similar to the 'editing the service provider and cost' function from the shipment manager screen but as an automation piece rather than having to manually apply this process. Or...is there a better way to manipulate an automation agent to fulfill this task prior to or in the process of building a shipment? Any help would be greatly appreciated!

Eric

[bob_romijn]

Hi,

I'm talking about version 5.0, so don;t know if it is applicable for 4.5, but I will give you my thoughts.

The carrier would be the simplest I think. You have a agent action "Change Service Provider" which does what you want for that part (if I understand it correctly).

The costwill be another challenge...... There is no standard action. The only thing you can do (or what I should do in you position) is doing it via direct SQLs. It is not my favorite to do it, but sometimes you need to.

Hope this helps.

Best regards,

Bob

[AlejandroBarba]

Hi Eric,

I can only think of three alternative approaches:

• The first is a cleaner approach using an XML update to correct the carrier as well as the cost of the shipment but you might need to create a second touch point and probably the major challenge could be identifying the Shipment Gid for the XML update.
• Instead of sending the transmission of the Order, send a Shipment as Work with the desired cost and carrier but this may be a big change to your process and the Shipment ID may need to follow a different naming convention.
• The third approach may be a little more complex despite not requiring a second touch point but it "bastardizes" the use of the Declared Value field. The Order Reference Number Value cannot be used as a way to rate a shipment directly within OTM so in order for this to work you may need to:
  • Instead of sending the carrier as a Reference Number, send it as an Order Constraint.
  • Instead of sending the Shipment Cost as a Reference Number, send it as the Declared Value.
  • Create "dummy" rate records for your alternate carriers covering all their possible geographies and based in the Declared Value.

The last approach should plan the shipments based on the declared value but special care should be placed if more than one order is consolidated in the same shipment.

Hope this helps,

Alejandro B.

[ebauchwitz]

The recommendation above worked very well. Through integration I was able to enter a buy rate into the declared value as well as the service provider id into the order release constraints. Once a buy shipment was built both values were used.

I've now found myself struggling with the sell side. Other than the declared value, I don't see any other charge multipliers within the rate basis that would pull a value from the order release. I'm searching for another way to force a sell rate to the sell shipment. Has anyone been successful in doing so?

Thanks!

Eric Bauchwitz

[AlejandroBarba]

Hi Eric,

Glad to know that you got it to work for the Buy Shipment. About the Sell Shipment, can you please let me know how is it rated? Is it a percentage over the buy shipment cost, a fixed amount over the buy shipment cost or is it a totally independent rate?

Thanks,

Alejandro B.

[ebauchwitz]

The sell shipment cost is independent from the buy shipment cost. The sell rate is a flat amount.

[AlejandroBarba]

Hi Eric,

If it is a flat rate; is it dependant on the lane or does it change for every shipment? If it is dependant on the lane, I strongly suggest creating Sell Rate Records for these flat rates.

If the flat amount changes for every shipment, the approach I can think of is kind of complex but here it comes:

1. Create a "dummy" sell rate record just to be able to plan the sell shipment (lets say $0.01 per shipment)
2. Send the sell shipment cost as a order release reference number in the XML transmission
3. Have an agent listening to the sell shipment creation with a Direct SQL Command action that will copy the reference number value to the Sell Shipment Cost.

Finally, make sure that no one re-assigns a rate to the sell shipments because it will change the cost back to the "dummy" sell rate and also that the sell rate record can only be used for only these sell shipments.

Hope this helps, if you still have any questions, please let me know.

Alejandro B.