Feature - Amazon Routing Number (ARN) - ASN Label & VICS BOL Creation

Release Date - 11/2/2020
Version - 8.5 & Up

The nature of this project has to do with the Amazon Routing Number (ARN). The design is generic so it can work with other trading partners if they require routing number with your EDI ASN (Advanced Shipping Notice or 856.) In this article, we use "Amazon Routing Number", ARN or "Routing Number" interchangeably. 

Before shipping to Amazon, customers need to go to Amazon’s portal and indicate the PO they want to ship. Amazon will then assign the ARN for the PO. The carrier will also be specified. ARN is a unique shipment number assigned by Amazon for their tracking purpose. In the past, Amazon only needed the ARN with truck shipments. For truck shipments, the Elliott VICS BOL can be used which has the ability to enter routing numbers. During the export of ASN (Shipped Order Data Export or Shipped History Data Export), if the order has a BOL number, then Elliott will look it up in the VICS BOL database to find the routing number and export it as part of the shipment record.

Amazon is making a procedural change. Parcel shipments (UPS or FedEx) will now require an ARN. Since the parcel shipment does not go through VICS BOL, Elliott does not have a place to store the ARN in the order header. Recently, Amazon made another change: for a back-order shipment, even if it is parcel, they will require the ARN which is different from the original shipment ARN.

The solution to this problem is to let Elliott control the ARN. When the ASN is exported, if Amazon requires an  ARN, we will need to find the ARN in Elliott. If not, then Elliott will report an error. From there, the user needs to figure out the operation mistake and take the necessary action before exporting the ASN again. The current procedure does not enforce the requirement of ARN when exporting the Amazon ASN. Therefore, even if there’s a procedural error by the user, they do not know.

To resolve this issue, a new order/invoice attribute, ^ROUTINGNUMBER, is supported. Users can manually enter this attribute for each order or the routing number can be imported to create this attribute.

^ROUTINGNUMBER Attribute Setup

System Utilities-> System File Setup-> Maintenance-> Attribute File         

 

Create the ^ROUTINGNUMBER attribute:

1.      Reference 1 – Routing Number
2.      Reference 2 – Carrier SCAC

 

Customer EDI Profile (Screen7)

The following fields have been added to screen 7 of Customer EDI Profile Maintenance:


3.      Require Order ^ROUTINGNUMBER Attribute for ASN? – Does the customer require a routing number attribute be entered for every order? You could answer "N" if you are in a "mixed" mode operation. In that case, Shipped Data Export (ASN/856) will always attempt to user ^ROUNTINGNUMBER attribute if it exist in the order. But it will not stop users if that attribute does not exist.
4.      Routing Number CSV Filename and Path – Default path to the Routing CSV File
5.      Routing Number CSV PO Number Column – CSV column for the purchase order number
6.      Routing Number CSV Routing Number Column – CSV column for the routing number
7.      Routing Number CSV Carrier SCAC Column – CSV column for the Carrier SCAC. Enter 0 if there's no SCAC column.
8.      Routing Number CSV Has Header Row – Does the CSV file have a header row?
 

Import Routing Number CSV

Under COP -> Processing -> Print Pick/Pack Ticket & Lbls -> Shipping, a new entry, Import Routing Number CSV,” has been added under “Shipment Data Update” and before “Pick Order Processing.”

To access the new import application the ^ROUTINGNUMBER attribute must be set up with Ref1 and Ref2 fields enabled. That’s the minimum requirement. Users can have more fields enabled. If the attribute setup does not meet our minimum requirements, an error message is displayed and the user is advised about the expected attribute layout.

If the user has the proper attribute set up, this function has a choice of pre-Interface and Interface but there’s no “layout” choice. Different trading partners can have a different layout. Therefore, the user is allowed to define the layout in EDI Trading Partner Profile. 

The pre-interface and interface will prompt for the following:


1.      Customer Number - Enter the customer number to be used when processing the CSV file.
2.      Routing Number CSV Filename And Path: Enter the default path where the CSV file resides.
3.      Print CSV Raw Data: Should the CSV raw data be printed on the report?

After the user enters the customer number, the application will look up the EDI Trading Partner Profile for “4. Routing Number CSV Filename And Path” and display as field 2 default, and the user still can override this value. If there’s no path, or the field values 5 – 7 are not valid (should have value between 1 – 20) then the application will display a message that “Customer is Not Setup to Use Routing Number CSV Import. Please Change Trading Partner Profile.”

The actual CSV import will use the information in 5 – 8 to decide how to process the CSV file. The ARN (Routing Number) will be written to order ^ROUTINGNUMBER attribute reference 1 field. The Carrier SCAC will be written to reference 2 field.

Some considerations:

A CSV record will not be processed if the order (PO) is not found. This can happen because the sales order could have been purged. This is not an error condition. This is simply an “information” message.

If the order is already posted, the CSV record will not be processed.

If the order is not posted yet, the ASN is exported already but the existing attribute shows a mismatch ARN number with the current one, that is a warning.

If the PO number is blank, the CSV record will not be processed.

If the PO number, ARN or SCAC column exceeds 30 digits, an error message will be printed.

If the attribute already exists and the order is not posted but the ARN and SCAC are not the same, a warning message to indicate the ARN or SCAC does not match is printed.


Errors and warnings are tallied and totals are printed at the bottom of the report:

   ** Total No. of Warning          :                  2
   ** Total No. of Blank PO No.    :                  1
   ** Total No. of Posted Orders    :                  6
   ** Total No. of Actions          :                59
   ** Total No. of Error            :                10
   ** Total No. of Records          :                272

ASN Label to Support Routing Number

In EDI Trading partner Profile Screen 5, if the user enters “Y” in “6. Custom Ship Label CSV Format (UCC-128)?," then a window pops up allowing the user to select the fields to be used for Item Barcode Label. A new selection “Routing Number” has been added after “Bill of Lading No.”

If this field is selected, then the Routing Number captured in the order attribute ^ROUTINGNUMBER will be used if it exists. If not, the application will look for a corresponding value in VICS BOL. If not found, then a blank value will be exported.

 

Users are able to see this “Routing Number” as a selection item whether or not they have the ^ROUTINGNUMBER attribute set up. But if they select the field and the ^ROUTINGNUMBER attribute is not set up, then we will display the proper message and indicate the attribute is not set up.

VICS BOL Creation

In EDI Trading Partner Profile Setup screen 4, field “10. VICS BOL Conf# Literal," this field is now populated by default if the ^ROUTINGNUMBER attribute is found during the creating of VICS BOL. 


However, there could be exceptions:

(1) Multiple orders are included in creating the VICS BOL, and their value in ^ROUTINGNUMBER is not consistent. In this case, the application will give a warning message “Order routing numbers are inconsistent” and a default value is not assigned.

(2) Multiple orders are included in creating the VICS BOL, and some of the them have ^ROUTINGNUMBER while some of them don’t. In this case the application will give a warning message “Not all orders have routing number assigned” and a default value is not assigned.

If none of the orders have a ^ROUNTINGNUMBER attribute, that’s OK. The user can manually enter field 18 if they need to do so.

ASN Export

For those trading partners that have the flag “3. Require ^ROUTINGNUMBER Attribute for ASN?” set to “Y,” during the ASN export (both shipped data and shipped history data), the application must be able to find the routing number. If the routing number exists in the order attribute or invoice attribute (for the shipped history export), then the application will export it. If not and there’s a BOL number on the order, then the application will look up the routing number from the VICS BOL database. If both fail, then the application will give an error message on this order and the export will fail. If the flag 3 above is “N,” we will export it using the same procedure, but the application will not fail if the routing number is not found.

Invoice Posting

During the invoice posting, the attribute on the order header will be transferred to the invoice header. The attribute in the invoice header will be used for shipped history data export.

Because there can be a back order, the original ARN and the back-order shipment ARN will not be the same. If there’s a partial post, the application will not keep the original ^ROUTINGNUMBER attribute on the order to avoid confusion. On the other hand, if it is fully posted, there’s no need to delete the attribute.

Programs Changed: EDSHPLBL.WS, EDSHPLBL.PL, CP0200, CPSHPBAR, ARCUSEDI, NSCTLMNV, CP0305, CPBOLINS, CPSHPEDP, CPINHEDP

Programs Added: CPRTEIMS, CPRTEIMP, CPIMPER3.DS, CPIMPER3.FD, CPIMPER3.SL, CPIMPER3.WS, CPIMPRTE.DS, CPIMPRTE.FD, CPIMPRTE.SL, CPIMPRTE.WS, CPRTEASC.DS, CPRTEASC.FD, CPRTEASC.SL, CPRTEASC.WS

CLS 

 


Feedback and Knowledge Base