TGET

TGET stands for Transportation Global Edit Table. Each service has their own set of valid accounting codes, also known as TAC (transportation accounting codes).

An example of this would be where the TOO (Transportation Ordering Officer) enters a TAC before approving a shipment. A TAC determines who pays for the shipping service (from which account). This TAC needs to be verified as a valid TAC. The MilMove application uses these to make sure that a customers order is valid. However, it should be noted that these codes do change and are updated.

Context

The current implmentation is based from a sample file that had been parsed to retrieve all the unique TAC values. A new table in the database was made called transportation_accounting_codes and a secure migration was done to put all those unique values into the database.

In the MilMove app, when a user enters a value in to the TAC field, a call gets made to our backend to check if the input shows up in the database. If the TAC value is invalid, the user is notified, but still allowed to proceed.

In the future, an SFTP connection would potentially be made to retrieve the updated file.

Resources

• This is the Appendix to TAC procedures and gives an overview of TACs, what they are, and how to maintain them.

• A slightly newer Google Drive folder that contains an example of a TAC file and an overview.

• An older Google Drive folder that notably contains an architectural design document as well as various related TGET things.

• An architectural design document that details how TGET would be incorporated into the application and how it would get updated.

• Pull request that adds the transportation_accounting_codes table.

• Code location where the transportation_accounting_codes table is used inside of the MilMove application.