ASN 20 ph3
From UG
(Difference between revisions)
(→SOW 2 Support additional ASN 2.0 Fields and Columns on download to xls and flex shipments list) |
(→Solution) |
||
| Line 53: | Line 53: | ||
* Approved For Pickup On Date | * Approved For Pickup On Date | ||
* Rejected On Date | * Rejected On Date | ||
| - | * | + | * Planners Name |
2) Add ASN 1.x fields: | 2) Add ASN 1.x fields: | ||
| Line 84: | Line 84: | ||
* "Actual Delivery Date" | * "Actual Delivery Date" | ||
* "Created by" | * "Created by" | ||
| - | * "Authorization Status" | + | * <span style="color:grey">"Authorization Status" (2.0)</span> |
* "Last Update Date and Time" | * "Last Update Date and Time" | ||
* "Last Update by" | * "Last Update by" | ||
| Line 93: | Line 93: | ||
* <span style="color:grey">"Rejected On Date" (2.0)</span> | * <span style="color:grey">"Rejected On Date" (2.0)</span> | ||
| - | 3) Add additionally selected fields: | + | 3) Add additionally selected fields from: |
| - | + | * TRUCK | |
| + | :*Load Number | ||
| + | :*PT Number | ||
| + | :*DT Number | ||
| + | * AIR | ||
| + | :*MAWB | ||
| + | :*Flight Number | ||
| + | :*Origin Airport | ||
| + | :*Date of Departure | ||
| + | :*Destination Airport | ||
| + | :*Date of Arrival | ||
| + | *OCEAN | ||
| + | :*Vessel Name | ||
| + | :*Voyage Number | ||
| + | :*Origin Terminal | ||
| + | :*Date of Departure | ||
| + | :*Destination Terminal | ||
| + | * Commodity fields - | ||
| + | :*Container # (OCEAN) | ||
| + | * CT2 Transport Mode (1) | ||
| + | * 3PL Name | ||
==== Related Functionality ==== | ==== Related Functionality ==== | ||
Revision as of 17:32, 23 January 2013
Intro
SOWs
SOW 1 Download to Excel Ability to select fields/columns and specify sequence/order (for ASN 2.0)
mantis: 3926
spec: see below
ASN 20 should function as ASN 1X.
"Download to Excel" link from CT list should lead to pop-up where user can manage what fields to include and in what order - see below.
Example of excel:
SOW 2 Support additional ASN 2.0 Fields and Columns on download to xls and flex shipments list
mantis: 3925
Core Requirements
Add support for additional ASN 2.0 Fields/Columns in shipment lists.
These fields need to be implemented in both:
- 1) Download to Excel
- 2) Flexible shipments list
Solution
1) Use ASN 2.0 fields:
- CT #
- Status
- Pick Up Location
- Ship To Location
- Cargo Due date
- P.O.
- SKU
- Quantity
- Transport Mode
- Submode
- Piece Price
- Total Value
- Item Description
- Created On Date
- Approved On Date
- Approved For Pickup On Date
- Rejected On Date
- Planners Name
2) Add ASN 1.x fields:
- "CT #" (2.0)
- "Shipper"
- "Pick Up Location" (2.0)
- "Ship To Location" (2.0)
- "P.O. Issued by"
- "Pick Up Instructions"
- "Commodity Description"
- "Cargo Available Date"
- "Cargo Due date" (2.0)
- "P.O." (2.0)
- "SKU" (2.0)
- "Quantity" (2.0)
- "Number of Pallets"
- "Packages on Pallets"
- "Loose Packages"
- "Total Gross Weight (lb)"
- "Piece Price" (2.0)
- "Total Value" (2.0)
- "Item Description" (2.0)
- "Hazardous"
- "Stackable"
- "Pick up Trucker"
- "Estimated Pick Up date"
- "Actual Pick Up date"
- "Delivery Trucker"
- "Estimated Delivery Date"
- "Actual Delivery Date"
- "Created by"
- "Authorization Status" (2.0)
- "Last Update Date and Time"
- "Last Update by"
- "Mode Of Transport"
- "Created On Date" (2.0)
- "Approved On Date" (2.0)
- "Approved For Pickup On Date" (2.0)
- "Rejected On Date" (2.0)
3) Add additionally selected fields from:
- TRUCK
- Load Number
- PT Number
- DT Number
- AIR
- MAWB
- Flight Number
- Origin Airport
- Date of Departure
- Destination Airport
- Date of Arrival
- OCEAN
- Vessel Name
- Voyage Number
- Origin Terminal
- Date of Departure
- Destination Terminal
- Commodity fields -
- Container # (OCEAN)
- CT2 Transport Mode (1)
- 3PL Name
Related Functionality
Rename Output Fields in both ASN 1.x and ASN 2.0:
- "Pick up Trucker Name" to "Pick up Trucker"
- "Delivery Trucker Name" to "Delivery Trucker"
SOW 3 Default units of measurement & currency types
mantis: 3927
spec: see below
SOW 4 ASN flag: Notification Email & SMS
mantis: 3942
spec: see below
Core Requirements
- Similar functionality to Client watch list shipment email notification and SMS (see Figure 1 below) but for portal shipper/planner.
- Allow Shipper/Planner to flag shipment with functionality for email/sms notification
Figures
Figure1. Client User Profile
