In Transit Report BR

(Difference between revisions)

Jump to: navigation, search

Contents 1 Related concepts and terminology 2 Related standards 3 Core Business Need 4 Key users 5 Introduction and Business background and Current related workflows 6 MOTs supported 7 Hard coded conditions 8 User defined conditions 9 Output 9.1 Header 9.2 Footer 9.3 Groups 9.4 Tabs 9.5 Columns 9.6 Sort conditions 10 Misc requirements 11 Typical use cases and workflow 11.1 Example A Coty all modes but AIR 11.2 Example B Coty AIR

[edit] Related concepts and terminology

• Core Ops Concepts

[edit] Related standards

• OpsReps standards

[edit] 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.

[edit] 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)

[edit] 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".

[edit] MOTs supported

All

[edit] 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

[edit] User defined conditions

Standard list of filters required

[edit] Output

[edit] Header

Standard

[edit] Footer

Standard

[edit] 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

[edit] Tabs

Each MOT has its own tab

[edit] 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

[edit] Sort conditions

Sort by CT#

[edit] Misc requirements

[edit] Typical use cases and workflow

must have several various cases of input, outputs, etc

use cases must be defined step by step

[edit] Example A Coty all modes but AIR

• Select Client = Coty. All other filters - default.
• Schedule for M-F, 8am EST
• Name it: Coty all modes
• Recepients
  • TO: all coty users but coty oper handling AIR
  • CC: marc, denise
  • BCC: simon

[edit] Example B Coty AIR

• Select Client = Coty; MOT = Air. All other filters - default.
• Schedule for M-F, 8am EST
• Name it: Coty all modes
• Recepients
  • TO: coty oper handling AIR
  • CC: marc, denise
  • BCC: simon

Report should have only AIR tab

=== Example C ===