Equipment Transaction Codes



This table contains movement codes as used on TIR’s and through other equipment-related functions, such as the posting of loads and discharges, the stuffing and stripping of containers, and equipment repairs.  The code is 4 characters long and is basically an abbreviation of the actual description. For example, RCVF means received full, DCHF, means discharged full.  Although these codes may be user defined, some are ‘hard-coded’ into the system and should not be changed – please check with GDZ support before changing existing entry



As well as the container type table, this table defines the behavior of the container in different documents, such as bookings, TIR’s, bills of lading. Here is a brief explanation of each field:


Empty Move: defines it this type of movement is performed on an empty container

Sent out move: movement that is sent out of the gate, for example SNTE

One Sided Move: Only one movement is expected, container coming directly to the gate (for example SLIN, TREI, TRFI)

Allow on TIR: Movement that will be registered in a TIR. Typically any movement that involves physical movement of a container from point A to point B should be entered in a TIR

Allow on B/L: type of movement that is Ok to be manifested

Off/On Hire: Movements such as LSD, Buy are movements that are bringing container into the system. Anything that increases inventory of containers is On-hire. Off hire is the opposite, for example RTD(returned)

Third Party: containers that are not owned by the line but that belong to other company.

Damaged; defines whether the movement is related to a damaged container or not

Affect booking count: Every time a booking is assigned into a TIR a counter is affected to make sure that once a container has for ex a RCVF for one container, that it should not accept a different container

Allow Line change; for companies that work with several lines, allow the containers to go with any line

Ask for drayage: Option that allows assigning the pro number and the amounts for drayage in the TIR

Start Drayage thread: if ‘Y’ is entered the transaction starts a new sequence of tracking for drayage charges. For example, a Sent Empty should start a drayage thread, whereas a Received Full should not.

Seal required: Required usually in full movements, sometimes in empties as well.

Weight required; requires Yes, in full containers

Job required: Assign ‘N’ for those movements that cannot be associated with a voyage, or ‘O’ (Optional) for movements that may or may not have a voyage. Note that all common movements such as Sent Empty or Received Full do have to have a job under ISIS.


In the lower section, it contains a code validation table, which shows which movements can precede or follow the current one, in a logical way. When needed, users with high security level can modify these entries.


To view a list of all existing transaction types in ISIS, click on the binoculars and a list with the general description will be displayed. To create a new transaction code, just populate all fields accordingly, after selecting the appropriate option from the toolbar or the File menu option. Always double check with GDZ support group, to verify that the setup is correct.