Gem-Code|
<< Click to Display Table of Contents >> Navigation: Software Description > Software Functions > Master Data > Item-Management >
|
The gemcode is the linchpin of the entire software.
The code is not comparable with an item number of a product, but is a speaking key,
which contains all information (qualities) needed to describe the gem-stone(s).
The code is structured as follows:
Number of characters |
Content |
Comment |
2 |
Stone type (alphanumeric) |
e.g. RU = Ruby (ruby) |
2 |
Stone quality 1 (alphanumeric)1 |
e.g. for rubies the country of origin ("MY" = Myanmar) |
2 |
Stone quality 2 (alphanumeric) |
e.g. for rubies the color ("PR" = pigeon blood) |
1 |
Stone quality 3 (alphanumeric) |
e.g. for rubies the treatment ("T" = Treated) |
5 |
Carat number (numeric) without decimal point with leading zeros |
e.g. 12,75ct = "01275". |
2/3 |
Number of stones in stone box (with leading zero) (3 digits if there are 100 or more stones in the box) |
max. 999 stones per box |
2 |
Shape of stones (alphanumeric) |
e.g. "TR" = trapezium |
1 |
Stone cut (alphanumeric) |
e.g. "F" = faceted |
7 |
Price per carat (numeric) without decimal point with leading zeros |
if necessary coded with individual letter code |
1 |
Price code (alphanumeric) |
"F" = fixed price / "M" = market price |
6/8 |
Stone size (00.0/00.00 mm length x 00.0/00.00 mm width ) |
The number of decimal places is selectable (1 or 2) |
(3) |
Optional index, which is automatically inserted if a stone code should already exist against expectation |
e.g. /01 for the first identical stone code Indexes can appear especially when trading with industrial stones. |
(2) |
Split index, which is optionally used if a can is split to another (sub-) can |
e.g. /01 for the first split can |
31-39 |
Digits in total |
|
Description
1 - Stone qualities
The combination of the stone types and the qualities results in the stone class as a basis for the price determination