File Reference Numbers
From UG
(→Glossary) |
(→Glossary) |
||
| Line 8: | Line 8: | ||
== Glossary == | == Glossary == | ||
| - | [[]] | + | [[Export_Reference_Number]] |
| - | [[]] | + | [[Import_Reference_Number]] |
| - | [[ | + | [[Third_Party_Reference_Number]] |
| - | + | ||
| - | + | ||
== Business Needs == | == Business Needs == | ||
Revision as of 21:38, 9 November 2011
Contents |
Info
- parent: 0000100: (Ops Misc)
- Mantis Task info: 3151
Glossary
Business Needs
Core need
Automate the assignment of file reference numbers to CT records (Jaguar export ref, import ref, third party ref), to take the burden off individual operators. As currently each Jaguar office has a specific sequence for their file reference #'s used to identify how their office is involved in the shipment, meaning if they are arranging the import or export for it. As well by managing this somewhere inside of the CT2 Admin menu, they do not keep a separate log book per office to record these numbers.
Requirements
These fields are are found on the CT records Gen tab, see CT_bo#References.
- 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 #File_Reference_Number_Sequence_per_Office
Note phase I functionality would be for the user themselves to select which file reference sequence to apply to their shipment upon CT creation. With phase II for CT to auto assign these sequences according to ops user groups.
