File Reference Numbers

From UG

(Difference between revisions)
Jump to: navigation, search
(→Core need)
(→Requirements)
Line 15: Line 15:
=== Requirements ===
=== Requirements ===
-
Have CT automatically generate/create Jaguar's file ref #’s, instead of us keeping a log book for them and add reporting capabilities.
+
*Have CT automatically generate/create Jaguar's file ref #’s
 +
*Allow user to add new file sequences
 +
*Add reporting capabilities
 +
**to report on the file sequence individually or corporately per office 
 +
*Have some sort of admin ability for each office to set their sequence numbers, with the ability to create new sequences as each office has their own specific sequence. See [[]]
-
Note phase 1 functionality would be for the user them self to select which file reference sequence to apply to their shipment.
+
Note phase 1 functionality would be for the user themselves to select which file reference sequence to apply to their shipment upon CT creation.
-
Have some sort of admin ability for each office to set their sequence numbers, with the ability to create new sequences as each office has their own specific sequence.
+
With phase 2 to be for CT to auto assign these sequences according to ops user groups
-
Phase 1 would be for user to select which ref # they would like to create and assign to their CT record
+
=== File Reference Number Sequence per Office ===
-
 
+
-
With ability to report according to file sequence numbers
+
-
 
+
-
With phase 2 to be for CT to auto assign these sequences according to ops user groups
+
As each office has a sequence of file reference #'s that they use to identify the shipment as an import or an export, below are the current file ref sequences:
As each office has a sequence of file reference #'s that they use to identify the shipment as an import or an export, below are the current file ref sequences:
 +
==== Jag NY file reference sequence ====
JFS NY – their file ref #'s are per Client Company, which is according the operation team that handles that specific client company.
JFS NY – their file ref #'s are per Client Company, which is according the operation team that handles that specific client company.
    
    
Line 39: Line 40:
IE 7, Consolidation Import files from other Jaguar office’s, begin with 86  
IE 7, Consolidation Import files from other Jaguar office’s, begin with 86  
IE 8, All other Export file #'s, including client company Coty, begin with 81
IE 8, All other Export file #'s, including client company Coty, begin with 81
 +
 +
==== Jag UK file reference sequence ====
JFS UK – their file ref #'s are per mode of transportation, as follows:
JFS UK – their file ref #'s are per mode of transportation, as follows:
Line 47: Line 50:
General Sea Export: 12SE + “CT ref”
General Sea Export: 12SE + “CT ref”
General Air Import: 21AI + “CT ref”
General Air Import: 21AI + “CT ref”
 +
 +
==== Jag FR file reference sequence ====
JFS FR – their file ref #’s are per mode of transportation as follows:
JFS FR – their file ref #’s are per mode of transportation as follows:
Line 58: Line 63:
Each file reference starts with the MOT, the year and finally the month = AI1108001
Each file reference starts with the MOT, the year and finally the month = AI1108001
-
 
+
==== Jag HK file reference sequence ====
-
 
+
JFS HK – their file ref #’s, which they call Job numbers, are per mode of transportation as follows:  
JFS HK – their file ref #’s, which they call Job numbers, are per mode of transportation as follows:  
Line 69: Line 73:
“HK” stands for JFS HK & “11” stands for 2011
“HK” stands for JFS HK & “11” stands for 2011
 +
 +
==== Jag Shenzhen file reference sequence ====
JFS SZX - their file ref #’s, which they call Job register, are per mode of transportation as follows:
JFS SZX - their file ref #’s, which they call Job register, are per mode of transportation as follows:

Revision as of 20:26, 19 September 2011


Contents

Info

  • parent: 0000100: (Ops Misc)

Glossary

Business Needs

Core need

Automate the assignment of file reference numbers to CT records (Jaguar export ref, import ref, third party ref). These fields are are found on the CT records Gen tab, see CT_bo#References. By managing this somewhere inside of the CT2 Admin menu, so as not keep a separate log book per office.

Requirements

  • Have CT automatically generate/create Jaguar's file ref #’s
  • Allow user to add new file sequences
  • Add reporting capabilities
    • to report on the file sequence individually or corporately per office
  • Have some sort of admin ability for each office to set their sequence numbers, with the ability to create new sequences as each office has their own specific sequence. See [[]]

Note phase 1 functionality would be for the user themselves to select which file reference sequence to apply to their shipment upon CT creation.

With phase 2 to be for CT to auto assign these sequences according to ops user groups

File Reference Number Sequence per Office

As each office has a sequence of file reference #'s that they use to identify the shipment as an import or an export, below are the current file ref sequences:

Jag NY file reference sequence

JFS NY – their file ref #'s are per Client Company, which is according the operation team that handles that specific client company.

IE 1, Elizabeth Arden Import file ref #'s begin with 87 IE 2, Elizabeth Arden Export file ref #'s begin with 82 IE 3, Elizabeth Arden Domestic Trucking file ref #’s begin with DO IE 4, Hanover Trucking records (Domestic, Air & Ocean) file ref #’s begin with HDO IE 5, Coty Import file ref #'s begin with 89 IE 6, All other client companies Import file #'s begin with 88 IE 7, Consolidation Import files from other Jaguar office’s, begin with 86 IE 8, All other Export file #'s, including client company Coty, begin with 81

Jag UK file reference sequence

JFS UK – their file ref #'s are per mode of transportation, as follows:

General Air Export: 11AE + “CT ref” General Sea Import: 22SI + “CT ref” Consolidation: 44CO + “CT ref” General Sea Export: 12SE + “CT ref” General Air Import: 21AI + “CT ref”

Jag FR file reference sequence

JFS FR – their file ref #’s are per mode of transportation as follows:

AE AIR EXPORT AI AIR IMPORT SE SEA EXPORT SI SEA IMPORT RE DOMESTIC TRUCK

Each file reference starts with the MOT, the year and finally the month = AI1108001

Jag HK file reference sequence

JFS HK – their file ref #’s, which they call Job numbers, are per mode of transportation as follows:

HK111xxxxx = Air export HKD112xxxxx = Air import HK113xxxxx = Ocean export HKD114xxxxx = Ocean import

“HK” stands for JFS HK & “11” stands for 2011

Jag Shenzhen file reference sequence

JFS SZX - their file ref #’s, which they call Job register, are per mode of transportation as follows:

SZ111xxxxx = Air export SZ112xxxxx = Air import SZ113xxxxx = Ocean export SZ114xxxxx = Ocean import

“SZ” stands for JFS SZX & “11” stands for 2011

Retrieved from "https://wiki.jaguarfreight.com/File_Reference_Numbers"
Personal tools