Microsoft Dynamics Nav (Navision) – Lanham E-ship

Microsoft Dynamics Nav (Navision)

How to manage package dimensions for Lanham E-ship

Microsoft NAV 2015, 2013 R2, NAV 2009. Lanham E-Ship SEO.60 and above.

This article discusses Lanham E-ship package dimension processing and related “Tips”.  This following topics will be outlined:

  • The formula for calculating dimensional package weight.
  • Lanham Rate Shopping options as per package dimensions.
  • Creating Standard Options to apply default package dimensions.

 

Calculating Dimensional Package Weight

As or January 2015, UPS and FedEx required all ground and air shipments to have package dimensions.  Dimensional weight is calculated as follows:

  • For Domestic Shipments: Divide the cubic size in inches by 166 to determine dimensional weight in pounds. Increase any fraction to the next whole pound.   L x W x H/166.
  • For International Shipments: For export and import shipments, divide the cubic size in inches by 139 to determine the dimensional weight. Increase any fraction to the next whole pound. L x W x H/139

When determining the correct weight and rates, compare the package’s actual weight to its dimensional weight. The greater of the two is the billable weight and should be used to calculate the rate.

 

What about large packages?

When calculating freight charges, there are additional surcharges for large packages.  Although each carrier has a number of specific rules and parameters, the basic guide in defining a large package is calculated as per the following formula:

Large Package = Length plus girth [(2 x width) + (2 x height)] > 130 inches. 

For example, if the package dimensions are: 24 (L) x 24(W) x 36(H), then the above formula would result in 132 inches (24+ (2×24) + (2×36)).  For UPS, large packages are subject to a minimum billable weight of 90 pounds, For FedEx, there surcharge structure is more complicated with different surcharges with minimum and maximum rules.

 

 

Lanham Rate Shopping Functionality

With above dimension calculation rules and what dimensions are considered oversize, using Lanham’s Rate Shopping functionality to test and compare rates will be easier. What may not be so well known is that using Lanham current Rate Shopping from the sales order for UPS and FedEx will not calculate meaningful rates as rate shopping from the sales order does not apply package dimensions. Without a development update, there are two work arounds that can be used:

  1. Pack Line Scanning (PLS)
    1. Create a package in Pack Line Scanning
    2. Pack the items
    3. Enter the dimensions on the package
    4. Issue the //RP (Rate Page) command

 

  1. Create a miscellaneous package
    1. Enter the appropriate address
    2. Populate the miscellaneous package lines
    3. Functions

 

Navision Miscellaneous Packages

 

While the above workarounds will work, it lacks user simplicity and forces the CSR to go to other screens when attempting to determine what the least costly carrier and service to use.

Entering Package Dimensions during PLS and Standard Option Setups

As per PLS processing, to enable manual entry of package dimensions, the packing rule “Manually Enter Dimensions” can be flagged on packing station page.  When the user issues the close package print command //CPP, the E-ship Override Dimensions page is displayed where the user would flag “Override Dimensions” and then enter the dimensions.

Dynamics NAV E-ship Dimensions

 

 

Alternatively, a standard option could be created that would be scanned during PLS before the package is closed. In the sample below, for the Standard Option setup for a package dimension of 9x9x6, the user would scan //XBOX9X9X6.  These standard options can be created for multiple standard size boxes and can enable faster and more efficient processing.

Dynamics NAV - Standard option Setup

 

Written by Mark Stept

Clients First Business Solutions, LLC

 

This article assumes the reader has a working knowledge of Lanham E-Ship functionality and processing.  Additionally, this article assumes that NAV code changes related to package dimensions have been applied.