2.1 Field Naming Conventions

A suggested naming standard for fields in the repository is:

For In-House Development

For Package Development

XXXXXXiii

PPXXXXiii

 

Where the following points apply:

 

In-House Development

PARTNO

Part number

CUSTNO

Customer number

ITEMNO

Item number

SALQTY

Sales quantity

SALAMT

Sales amount

SALAVG

Sales average

 

 

Package Development

OEPTNO

Part number

OECUST

Customer number

OEITEM

Item number

MKSAQT

Sales quantity

MKSAAM

Sales amount

MKSAVG

Sales average

 

 

   OEPTNO, OECUST, and OEITEM are order entry packages, and MKSAQT, MKSAAM, and MKSAVG are marketing packages.

NXT

Next value of the field

PRV

Previous value of the field

WRK

Working value of the field

USE

Exchanged/using value of the field

RN1

First rename of the field

RQS

Requested value of the field

VIR

Virtual field definition

TOT

Totaled value of field                

 

 

GL

General ledger

AR

Accounts receivable

OE

Order entry

 

 

One advantage of this type of naming standard is that when an attempt is made to change the dictionary and field name XXXXXX or PPXXXX is specified, all the iii variations will also appear due to LANSA's generic search and display facility. This serves as a continual prompt to remember to change/check all the versions of the same field.

The LANSA Product Support Department in Australia maintains a register of all known PP prefixes. If you are assigning a PP prefix it may be advisable to contact your product vendor to check that the prefix has not already been used, and to have your prefix added to the register to prevent others from using it.