Here are guidelines for naming Lookups (on the Lookup Field maintenance):

Be specific- the name MUST be unique across all lookups

Don't include a final standard suffix Flag or Lookup (The suffix Lookup is automatically added by the generator to the classes generated for each Lookup field.)

Examples:

WO_​STATUS_​FLG -> writeOffStatus

STM_​RTG_​METH_​FLG -> statementRoutingMethod

Here are guidelines for naming Lookups Value properties (on Lookup Value maintenance):

Try to word the name in a way that makes sense when prepended by is, and is also valid when standing alone as a constant. (eg {isComplete, COMPLETE}, {isFrozen, FROZEN})

The name might match the english description of the lookup value.

Examples:

HOW_​TO_​USE_​FLG : - -> subtractive

ITEM_​STATUS_​FLG : A -> active

DGRP_​PRIO_​FLG : 10 -> highest10

DGRP_​PRIO_​FLG : 20 -> priority20