Fieldpine Logo Documentation Home  

NetworkLane PHYSICAL Table Structure

This page contains technical detail about the physical database structure. It is not required for normal day to day operation of the Point Of Sale.

Goto: Documentation Home


FieldNameDatatypeMeta InfoGnapDescription
licidlongPrimary Key. Not zero100/EA unique internal id assigned to this lane. The same machine/system may be allocated different numbers over time as the environment changes.
FirstDtdate/time123/sDate/Time the lane first communicated to the Point of Sale network. This value is automatically populated
Commentsstring124/sFree form comments about this lane
AssetNostring125/sThe asset number associated with this lane
LifePhaseNumber126/E A coded number indicating the status and type of lane.
0Trading Lane. An active checkout in a store
1Back Office Lane. A lane physically located inside a store but not direct selling at checkouts
2Head Office Lane. A lane physically located in Head Office
3IT/Support Lane
65Test Lane
Extended Fields
tush_NNNstringNone Fields with this naming pattern will store information received from TUSH packets. This is solely as an aid for external reporting users and these fields are not used by the Fieldpine system.

If you wish to have a TUSH field stored in networklane, create the field in networklane using the GNAP Field id as part of the field name. Example, to store the SystemName (the manufacturers model name) (Gnap# 125) create a field named "tush_125"


A unique primary key should exist on the licid field.


The value of the licid is determined by Fieldpine licensing. If you are using static licencing, where Fieldpine issue a fixed key, you will have a static value for a given machine. If you are using dynamic licensing, then new licids will be automatically allocated by the system, and may change randomly.