ASN 20 Solution
From UG
(→SKU Map) |
(→SKU Map browser) |
||
| Line 120: | Line 120: | ||
Currently, it is not possible to see even currently uploaded xls. | Currently, it is not possible to see even currently uploaded xls. | ||
| - | Figure below suggests possible UI design to satisfy stated functionality | + | Figure below suggests possible UI design to satisfy stated functionality. |
[[File:PO Issued with Yes and browser.JPG]] | [[File:PO Issued with Yes and browser.JPG]] | ||
Revision as of 23:23, 7 August 2012
Preliminary Remarks
ASN 2.0 vs ASN 1.X
ASN 2.0 is an extension of ASN 1.X functionality.
This wiki maintains focus on explaining what to add and change without repeating in details what to carry over from previous version (ASN 1.X). At the same time I do briefly mention some of the major functionality that needs to be preserved.
ASN 2.0 vs International Portal
Originally this scope was kept under larger International Portal project. Most recently it was decided to extract ASN related functionality and implement it as soon as possible. This project to be called ASN 2.0.
Some features that were developed or half-developed under I-Portal such as Flexible CT editor, merging of Client and Internal App were put on hold.
Some, such as Flexible User roles will be used for this module, but some adjustment required (some Roles will be defined as Flexible and some as Built In).
Also we need to provide TMS vs non TMS option for Truck Domestic mode.
Preliminary Tasks
Add TMS E0 attribute
Currently "TMS solution" supports only one Client Company (E0) at a time - we can not send shipments to TMS that are identified by more than one E0 - this case is not defined - no code or business process exists to handle this case properly. This restriction will remain in ASN 2.0.
But we need to add parameter to the system that defines what E0 "is linked to" TMS currently. This will help in :
- reporting (for example for DR/KPI reporting we will know what CTs are linked to cost that we receive from TMS and store in special Load table vs costs entered by operators)
- validation (to make sure we do not send CTs from more than one E0 to TMS)
See mock up below.
Add Role Type attribute: Built In vs User Defined User Roles
We have to distinguish between Built In and User Defined User Roles.
Also this should be obvious for the user - what role is of what type.
This is a new attribute of User Role Entity.
User Defined Role is a role that can be created and fully defined by user through Admin > Security > User Roles panel.
See UI changes on the Figure below:
1 - change button label
2 - add "User Type" column
Add Generic Shipper and Generic Planner Built In User Roles
Currently the only Shipper and related Planner roles defined in the system are "EA Shipper" and "EA Planner". These are built in roles.
They currently support only Elizabeth Arden (EA) Domestic Trucking workflow.
Since it is intention to increment/change EA workflow and also to add support for any Client Company without distracting existing operations it is suggested to create two new built in roles "Generic Shipper" and "Generic Planner" that would fully satisfy ASN 2.0 requirements.
See #3 and #4 on the Figure above.
Deploy this into production. After release we would have:
- EA Shipper
- EA Planner
- Generic Shipper
- Generic Planner
At that point In production we could:
- start creating new Generic Shippers/Planners for any E0
- transfer all users from EA Shipper to Generic Shipper
- transfer all users from EA Planner to Generic Planner
- remove EA Planner, EA Shipper (in the following Rel to Prod)
Important Note to Developer ------------------------ Code should be re-used by both EA and Generic Shipper/Planners. Obviously we should not create separate similar code for EA vs Generic roles.
Make PO Issued By attribute Client Company specific
Since every Client Company has its own PO Issued By List it has to be defined in Client Company profile - see 1 on Figure below.
Since approval type will be Shipper specific we have to move related parameters to Shipper profile - see 2 on Figure below.
Also now #SKU Map should become part of this profile - see #3 below.
Y vs N indicate if SKU Map is used for selected PO Issued By or not.
SKU Map is not required feature therefore default is N.
On "Add" the following pop-up will be produced:
SKU Map
"SKU Map" aka "SKU to Planner mapping" as defined in ASN 1X this is a table (uploaded in the form of xls) that links unique SKU# to SKU description and to planners name.
It provides auto-suggest for SKU description on ASN form and planner filter for List CTs under Planners login.
It was required only for CTs that are associated with one particular PO Issued By value.
Link to ASN 1X spec: ASN_1.X#SKU_to_Planner_Mapping_Feature.
SKU Map browser
We need to add one simple important table: history of uploaded files with these attributes per File entity:
- file-name
- file size
- time-stamp when uploaded
- who uploaded (username)
Currently, it is not possible to see even currently uploaded xls.
Figure below suggests possible UI design to satisfy stated functionality.
Shipper Related Functionality
New Shipper Profile
See mock up below.
Shipper Profile General section
First 3 controls remains in ASN 2.X.
NOTE: Limitation on number of E0 companies associated with one Shipper User ------------------------------------------------------------------- Currently one Shipper User can be associated only with one E0. In the future this limitation might be lifted to associate with many.
"Approval options section" has been added. This section defines approval workflow for CTs created by shipper.
PO Issued by list is taken from E0 Client Company.
For every PO Issued By three parameters needs to be defined:
- Approval Process (as defined in ASN 1.X; new types has been added)
- Cargo Due Feature on/off (as defined in ASN 1.X)
- Air Approval (new parameter; see #Air Approval Type)
NOTE: Approval process type might become MOT specific as well in the future ------------------------------------------------------------------ In that case approval type would not only be Shipper and PO Issued By specific but also MOT specific. Approval options table would be repeated for every MOT section in this case.
Shipper Profile MOT specific sections
See mock up above.
If user selects TMS option then system must validate that E0 in Shipper profile is the same as defined in TMS Admin.
Create CT - Universal ASN Form
This new ASN form allows shippers to create CTs for different mode.
See Figure below.
Commodity table
In ASN 20 Commodity table has two additional fields:
- transp mode
- equipment attributes
Transp Mode and Equipment attributes
MOTs that particular user can suggest are defined in specific Shippers profile. Trans Mode is another name for MOT.
Equipment options will change depending on what Transp Mode is selected.
- For FCL it will give options for container size / type.
- For FTL it will give options for truck size.
- For all others it will show "N/A" (not applicable).
Please note that one ASN may have different MOTs defined on each line.
See also "IMPORTANT NOTE" on Figure above (#3). System can not validate this so we rely on Shippers to comply with this requirement.
On Save Logic
Preserve such logic defined in ASN 1.X:
- Preview Screen
- Confirmation Screen
- Email Notification: on ASN create (by Shipper) - email to Shipper
See it defined here: ASN 1.X#Create_CT_record. (NOTE: This wiki might not be completely up to date).
View list of CT records as a Shipper
Preserve existing logic. See ASN_1.X#View_list_of_CT_records_as_a_shipper.
Edit, Clone, Delete CT records as a Shipper
Preserve existing logic. See ASN_1.X#Core Shipper Functionality.
Planner Related Functionality
New Planner Profile
View list of CT records as a Planner
Preserve existing functionality: ASN_1.X#View_list_of_CT_records_as_a_planner
Authorize CT records
Preserve existing functionality: ASN_1.X#Authorize_CT_records.
See also ASN_1.X#Double Approval Process Feature.
Add the following functionality - see below.
Approval types
- single - defined in ASN 1.X
- double - defined in ASN 1.X
- no approval - see #No Approval Type
- air approval - see #Air Approval Type
Air Approval Type
This is an additional layer of approval for Air shipments that is required before CTs become visible to Jag Ops.
CTs created by Shipper Users that have this approval type selected would require Planner User who's is "Air Planner" to approve this shipments.
No Approval Type
CTs created by Shipper Users that have this approval type selected would be automatically available for Jag Ops bypassing any approval layer (unless Air Approval is required).
Jaguar Operator Related Functionality
As in ASN 1X shipments that are approved (or not require approval) needs to come under radar of operators so that they can be handled.
This is achieved by New Approved But Not Handled Shipments Dashboard Report (aka ANH Report).
It is similar in spirit and functionality to TDS Dashboard in ASN 1X for TMS Domestic shipments for EA.
Overview of core ANH DB functionalities
- newly approved shipments should appear on DB and stay there until they are noticed and acted on by operator
- once operator starts handling them they should "drop off" of this DB; this should happen once #Approved but Not Handled (ANH) Condition is achieved
- 1st level:
- provides counters and breakdown per MOT and Client Company
- Jag Ops user profile can be configured to limit to specific subset of MOTs as well as Cient Companies
- 2nd level provides (as in TDS):
- display of shipments with details (selected attributes)
- filters
- "actions" list (ability to select several shipments that satisfy criteria and apply action)
- action to create GRP (new in ASN 20)
[Fig TBD]
Approved but Not Handled (ANH) Condition
CT is approved (or Approval type = No approval) AND CT is not "routed" (Pick Up Trucker is not assigned).
ANH DB Admin
Options for specific user:
- enable/disable
- E0 multiselect - limits list of client companies available on DB
- MOT multiselect - limits list of MOTs available on DB - see below
[Fig TBD]
ANH DB list of MOTs
Air / Ocean LCL / Ocean FCL / Truck Dom (non-TMS) / Truck Air (LDP) / Truck Ocean (LDP)
ANH DB 1st level
Provide counters in a tabular form.
Columns - MOTs - see above.
Rows - Client Company list.
ANH DB 2nd level
- filters - same as in ASN 1X TDS for now
- CT List - same as in TDS
- actions list
- add "create GRP" action
Misc Functionality
Managing Pick Up and Delivery Addresses
On ASN Form it would make most sense to display only Pick Up and Delivery locations that are relevant to specific Supply Chain (E0).
These 2 lists could be defined in Client Company profile.
This spec is subject to approval by Prod Team.
[Fig TBD]
Notification Types
There are the following notification types defined in ASN 1X. They needs to be carried over to ASN 20.
- on ASN create (by Shipper) - email to Shipper
- on any approval related status assignment/change (by Planner) - email to Shipper
- on Trucker assign (by Jag Ops) - email to Shipper
SOWs and Change Requests
SOW 1 Create new branch for this project from trunk; create envir for QA/SIT/UAT
mantis: 0003680
Call it "ASN 20".
