In Transit Report BR
From UG
Contents |
Links to related concepts and terminology
- CT2 report concepts
- core operations concepts
Core Business Need
This report is used by jaguar and client users to identify shipments that are "in transit". There are very specific "in transit" conditions defined for each mode of transport based on the state of specific values of CT fields.
Key users
This report will be typically scheduled by jaguar internal sales for:
- jaguar operators and management
- non jaguar users (covering CTs for one client company)
Introduction and Business background and Current related workflows
There are number of core reports used in operations at Jaguar. In Transit is one of them. This report helps to understand what shipments Jaguar "already started processing". For example for Air "to join In Transit list" shipment must have "Master Airway bill" field filled in.
At some point when activities related to shipment handling are nearly completed it will "fall off of In Transit list".
MOTs supported
All
Hard coded conditions
For CT to appear on this report it must satisfy all conditions below:
- CT does not have *Deleted* status AND
- CT does not have *Archived* status AND
- CT satisfy *MOT specific conditions* - see below:
MOT = Air
- Master Airway bill "is not empty" AND Actual Delivery Date "is empty" OR
- is today's date OR
- is yesterday's date
MOT = LCL/Client Consol
- CT has at least one container AND
- Container# field "is not empty" for one or more containers AND
- Actual Delivery Date "is empty" or today's date or yesterday's date
User defined conditions
Standard list of filters required
Output
Header
Standard
Footer
Standard
Groups
There are 3 levels of groupping for this report:
- group CTs by MOT
- group CTs by master they belong to
- list all commodity table lines per CT
Tabs
Each MOT has its own tab
Columns
- Provide all standard columns
- CT column first
- hyperlink CT#
- Provide mechanism to group CTs per master
- Suggested design: show dropdown with all CTs in a master
Sort conditions
Sort by CT#
Misc requirements
Typical use cases and workflow
- must have several various cases along with screenshots of input, outputs
- use cases must be defined step by step