PRECISION TMS/QAD Freight Management S38
Application Enhancements
Black Box Message Changes
• ShipShipment/CreateShipment
• There is validation of the length of the field values passed in messages. You can switch this validation off using a system value.
BLACK BOX: XML VALIDATION System Value
|
Category
|
Key
|
Description
|
|
SPS
|
BLACK BOX: XML VALIDATION
|
Possible values:
YES - enable validation
NO - disable validation
Default value: YES
|
LTL
Added check digit support for:
• VITY (Vitran Canada)
• WTVA (Wilson Trucking)
• CBNK (Cabano Kingsway)
For a full list of supported LTL check digits, see Topic 045 - Supported TL-LTL Carriers.xls.
Rate and Transit Time Maintenance
• In the tier-based upload format rate file:
• It is now possible to specify the freight class as an axis.
• The issue with the loading of minimum rate values into an incorrect zone record is resolved.
• In the flat-structure upload format rate file:
• Variables that impact zone names are initialized to ensure that there is no impact on subsequent zone names created in the database.
• In both the tier-based and flat-structure upload format rate files:
• Leading and trailing spaces are removed automatically from cell values upon file upload.
• When a new rate upload file is loaded with the same axis characteristics as an existing axis record in the database, it is possible to reuse axis names.
Routing Guide
• The system now checks the Y3IUSE field when determining the system values to retrieve for the FILTER FIELDS list.
For more information on the Routing Guide, see Topic040 - Routing Guide and Rate Shopping.doc.
General Enhancements
• If the country code is set to US for a US Territory, then the system changes the country code to the US Territory code. This approach ensures that, within the application, these codes are processed consistently by the different carriers.
• Non-numeric characters are automatically removed from postal codes for Germany, Luxembourg and Denmark, as these should never be present.
Carrier-Specific Enhancements
This release offers support for a number of additional carrier-specific features.
Canada Post
• 2014 changes for Canada Post domestic shipping requirements (labeling, rating etc).
DHL - Express (SAS Version, US Origin)
• The terms and conditions text on the label is updated to the latest applicable text, and the font size for the AES information on the label has increased.
DHL - Time Definite (non-US)
• It now possible for an external application to pass in an SSCC value so that this value can be used instead of the DHL license plate number.
• There is an option to hide the customs value on the label.
• Lithium Battery information on the label is no longer duplicated.
• The description output on the label for Dry Ice has changed.
• Additional auditing log information has been added to the DHL programs for Breakbulk (BBX) processing.
• It is no longer possible to output a reserved character such as ? to an EDI file as a data value; reserved characters impact the parsing of the EDI file.
• Additional delivery terms validation for shipments of Dutch origin.
• There is a new label macro for the DHL Paket service for domestic shipping in Germany.
DHL - XML PI Integration
• The correct Incoterms value now displays on the label.
• When applicable, the Product code displays on the label as white-on-black.
• For multi-piece shipments, weights are rounded to the nearest 0.5 kg to ensure that there is no overlap of text on the label.
• The Recipient Contact and Recipient Phone values are not displayed in the address lines section of the label.
• Corrections to the sequencing of output for the mapping of fields for the Europe/Asia (E/A) schema.
DPD
• Corrections to the algorithm for the DPD routing code determination.
Endicia
• Labels for APO/DPO, US Territories, and international shipments can print to a thermal label printer.
• It is no longer necessary to map the CountryName node to the Endicia back-end; the ISO country code is sufficient.
• The weight field in the Endicia XML has been extended from 6 to 7 digits in length.
• The MailpieceDimensions node is no longer output unless there is at least one dimension — length, width or height — present with a non-zero value.
ENDC: SHIP REFERENCES System Value
|
Category
|
Key
|
Description
|
|
SPS
|
ENDC: SHIP REFERENCES - <PACKING LOCATION>
|
A comma-separated list specifying information to send to the carrier for tracking purposes. Replace <PACKING LOCATION> with the code that identifies the particular packing location.
The first two items in the comma-separated list that exist for the shipment are sent to the carrier. The other items in the list are ignored.
Possible values:
PO - Purchase Order number - XMSITM0.SIORDN
TN - Transaction Reference - XMSHDR0.SHSHIP
RQ - Purchase Requisition - XMSITM0.SIBREF
EI - Employers Id Number - XMNREF0.NREIN (of shipper)
IK - Invoice Number - XMSHDR0.SHINVN
3Q - FDA Product Code - Taken to be commodity code of product
AE - AES filing reference - AES transaction reference in TRAX as per AES processing (XMS2DR0.S2AESITN)
AJ - Accounts receivable Customer account - XMSHDR0.SHFNCL
AT - Appropriation number - XMSITM0.SIBREF
BM - Bill of landing number - XMSHDR0.SHBLNO
DP - Department number - XMSHDR0.SHOREF
MJ - Model Number - XMSITM0.SIPROD
MK - Manifest Key number - XMSHDR0.SHHAWB
ON- Dealer Order number - XMSITM0.SIBREF
PC - Production code - XMSITM0.SIPROD
PM - Part Number - XMSITM0.SIPROD
SA - Sales Rep - XMSHDR0.SHSREP
SE - Serial number - XMSSRL0.SSRSRLN from first XMSSRL0 of item line
ST - Store number - Packing location per shipment rated
SY - Social Security number - XMNREF0.NRSSN (of shipper)
TJ - Federal Tax Payers ID code - XMNREF0.NRVATN (of shipper)
OREF - Other Reference - XMSHDR0.SHOREF
CREF - Customs Reference - XMSHDR0.SHCREF
FREF - ForwardersReference - XMSHDR0.SHFREF
BREF - BuyersReference - XMSHDR0.SHBREF
XNO1 - AdditionalReference - XMSHDR0.SHXNO1
CORN - CertOfOriginNumber - XMSHDR0.SHCORN
PSL01 - PSL User Defined - XMSHDR0.SHPSL01 (also PSL02 to PSL05)
|
• The Shipper address and Return address can have different values. These values can be passed to the Endicia back-end, and affect the label.
• The PICNumber node has been extended from 30 to 31 characters.
FedEx
• It is possible to print FedEx-generated labels for Smartpost Returns.
• Previously, ship-date text on labels for multi-piece shipments did not display correctly. This issue is resolved.
• A Return Address can be mapped to Alternate Return Address fields on the FedEx server.
• For the Smartpost Return service, the Smartpost RMA field maps to the FedEx server.
• UN codes can be treated as ORMD for FedEx Ground service.
FEDEX: UN NUMBERS GROUND ORMD System Value
|
Category
|
Key
|
Description
|
|
SPS
|
FEDEX: UN NUMBERS GROUND ORMD
|
A comma-separated list of UN numbers.
|
• For US Territory shipments, the country code correctly maps to the FedEx server.
• When a hazmat issue is raised by the FedEx server for a multi-package shipment, the UN numbers that identify the package are included in the error message.
• If the number of UN codes for the shipment exceeds three, then calls to the FedEx server are on a package basis instead of a shipment basis. This approach prevents the FedEx server applying the constraint of three UN numbers to the whole shipment.
GLS
• For GLS-generated labels, macros do not run when printing labels for a multi-piece shipment. The GLS-generate label macro runs for all packages of the shipment.
• Support for the Time Definite services for Unibox integration.
• Support for Dutch origin shipping, in accordance with the specific field mappings for shipments of Dutch origin.
• The integration now allows connection to the GLS back-end without a Unibox server located on the customer network. This feature applies to shipments of Dutch origin.
• Correctly handles special characters in the mapping to and from the GLS Unibox.
Integra2
• Support for consolidation. Displays the relative package count on a label for a consolidated shipment transaction.
• Support for shipments to Andorra.
Nippon Express (Japan)
• The barcode output on the PDF version of the label is now correct.
• It is possible to email the EOD file.
OnTrac
• New carrier. For more details on this carrier, see the Carrier Functionality Guide at https://knowledgebase.qad.com/kmp/article/AA-77163.
TNT - Express Label and Unicom
• The correct relative package count displays on labels for consolidated shipment transactions.
• Product or Service prints as white-on-black on labels.
• The Weight field prints as white-on-black on labels when the Express Label specifies that the information is highlighted.
• Support for Document services for shipments of Belgian origin.
• Support for the Special Express service for shipments of Dutch origin.
• Remove the | value from any Unicom array element returned from the Unicom COM object. This edit prevents a subsequent parsing issue for Unicom details stored in the PRECISION database.
TNT - Express Manager version
• No longer supported for new implementations of accounts.
TNT - iConnections Version
• No longer supported.
UPS
• The UN codes for Lithium Batteries are not printed on the label in the DG Codes section.
• EU domestic shipments have a Document Indicator value on the label.
• A functionality change for zone determination of shipments of Canadian origin.
• In the UPS Transit Time API, if the PickupDate returned by the API differs from the value passed during the call to the API, then the ETA date is not taken from the API. In this case, the Transit Days are taken from the API, and the PRECISION application determines the ETA date.
• UPS 2014 business rules apply to the integration, including:
• Phase 1 of UPS Access Points functionality. Further integration information will be published by UPS in the future.
• Premium Care service for shipments of Canadian origin.
• UPS Express Freight service.
• Up to date labeling and PLD requirements for 2014.
USPS
• The MAC Certification is no longer supported; use the Endicia integration.
Wim Bosman
• Different pallet types can be determined and mapped correctly in the EDI file to the carrier.
• The maximum length allowed for FTX+AAA field has changed. The value mapped for MEA segment is AAW instead of GMC.
• It is now possible to call the standard rating engine structure to enable rating for this carrier.
Yodel
• There are new rate table naming conventions due to changes in product names or codes used internally by Yodel.