Shipper Interface

This wiki section is managed by: Module Owner

Core business need is to "outsource" entering of new CTs to Vendors (Shippers). This supposed to meet these goals:

• 1) significantly cut man hours at Jaguar
• 2) streamline / minimize communications

Later (in 1-3 months) another big problem should be solved with a help of Shipper Interface: complicated approval process.

This wiki section is managed by: Business Analyst

Required core functionality:

• password protected web based access to below
• add, edit, delete, view CTs
• E Query functionality
• #BR: Lock for edit condition

BR: Lock for edit condition

Lock the record once a pick up trucker or estimated date is assigned

BR: password protected web based access

We realize that there are possibly 3 options:

a) to "trim down" Internal App

b) to "expand" Client App

c) create separate App

It is up to Dev to decide which way to go because one of the requirements here is "to create this module ASAP". So we can sacrifice "style" for speed if necessary.

We assumed that option "b" is most probable that is why some requirements are formulated based on this assumption.

• We suggest to use existing Non-Jag profile to create "Shipper" users. In this case we need:
  • add User type radio: "Client" (existing non jags), "Shipper" (shipper users)
  • Set "E0. Client Company" = E.A. USA Domestic
  • Part C. Link to Address Book = <this is a link to Shipper's company and user l;ocation>

BR: Add CT

This could be on one tab or multiple tabs

BR: Gen Tab fields

System should generate CT# and let shipper user enter some CT2 fields (some fields will be set by the system):

• E0. Client Company:
  • system sets it automatically to E.A. USA Domestic (not visible)

• E1
  • system sets it automatically to Elizabeth Arden
  • (not visible)

• E2
  • Based on log in, copy from "Part B. Visibility, E0. Client Company" in user profile (design idea)

• C. Customer Ref #:

• 2. Shipper (T1):
  • pre-filled based on login company (not visible)

• 5. Export Pick-up (T4):
  • required
  • same as on internal but only USA/Canada

• 3. Consignee (T2):
  • required
  • same as on internal but only USA/Canada
  • system should copy to Delivery to as usual

• Created by
  • not editable

• Created on time
  • new field see mantis

• Created on date
  • make it visible

• 7. Pick-up Comments:

• 15. Commodity description:
  • required

• Cargo Available:

• Cargo Due:

BR: Cont Tab fields

Everything we have on internal but: copy, move functionality

BR: Query Tab fields

Allow Client functionality.

This feature is lower priority.

BR: Edit CT

Ability to open record and edit fields above unless #BR: Lock for edit condition is true.

After record is locked show read-only version.

BR: Delete CT

Allow unless #BR: Lock for edit condition is true

BR: View CTs

If implementation is Client App based - use existing CT list. Else any basic CT list is fine.