Погледнете ги упатствата за PANTHEON™

 Categories
[Collapse]User Manual for DataLab PANTHEON 5.5
  End-User License Agreement
  Uvodna beseda
 [Expand]PANTHEON Editions
 [Collapse]Getting Started
   Instructions for Ensuring Compliance of PANTHEON with SAS
   Ensuring Your Data Is Compliant with SAS
  [Expand]Installation of PANTHEON and Required Components
  [Expand]PANTHEON Help
  [Expand]PANTHEON Basics
  [Collapse]Assigning Identifiers
    Non-transparent IDs
    Transparent IDs
    Semi-transparent IDs
   [Expand]Automatically Assigned Subject IDs
    Automatically Assigned Non-/Semi-transparent IDs
    Automatically Assigned EAN Codes
   [Expand]Special Identifiers
   [Expand]External Identifiers
  [Expand]Materials and Goods Movements
  [Expand]ZEUS Business Intelligence System
 [Expand]Settings
 [Expand]Orders
 [Expand]Accounting with Goods and Materials
 [Expand]Value-Added Tax
 [Expand]Service
 [Expand]Customs Warehouses
 [Expand]Financials
 [Expand]Personnel
 [Expand]Manufacturing
 No formula defined!
[Expand]Datalab PANTHEON 5.5 Guide
 Opening or closing round bracket missing!
 Debugging Formulas
[Expand]Testing and Debugging Formulas
 Opening or closing square bracket missing!
 Conditional statement at position x not enclosed in square brackets!
 Syntax error in conditional statement. Correct syntax is [condition:value]
 Adjacent operators (xx)!
 Last character of the formula is an operator!
 Variable not enclosed in hashes (#)!
 Illegal characters: xyz
 Unknown error!
[Expand]User Manual for Datalab PANTHEON Farming
[Expand]User Site
 Adjacent hashes!
 The line number must be an integer (#xx#)!
 The first character of #xx# must be a transaction type or a column mark!
 The first character of #xx# must be an operation type (R, S, O or A)!
 The second character of #xx# must be a transaction type (D, K, S, P, or O)!
 Variable not defined
[Expand]Kralicek Quicktest Financial Ratios

Load Time: 1015,654 ms
print   |
Label

Transparent IDs

Transparent IDs

010379.gif010380.gif010381.gif010411.gif010382.gif010383.gif

 

Transparent IDs give us information about an item; its type and use. Each transparent ID should be clearly defined: that is, each part of ID should represent a corresponding part of the item.

Let’s take a look at transparent IDs. We’ll be using 10-digit IDs. The first three characters represent the product group, that is, the group to which the item belongs. The remaining seven characters will be used for the item itself and include information about the manufacturer of the item. Before using transparent IDs, you must clearly define what each part of an ID represents.

 

Initial

2nd and 3rd letter

Group

C

 

coffee

 

IN

instant

 

GR

ground

 

ES

esspresso

F

 

food

 

CA

cakes

 

SW

sweets

Now let’s use this classification to generate IDs: chocolate chip cookies will be assigned ID: FCACHOCCHP; cinnamon raisin cookies will be assigned ID: FCACINRAIS.

Transparent IDs make it easy to search for items in the Items register and enter items in documents. Now let’s take a look at what the example we used to explain non-transparent IDs would look like if we used transparent IDs:

 

ID

Item

Category

PBTRARA15

Water bottle, 1.5 L

PBT

PBTUNIC15

Ice tea light 1.5L

PBT

MLPLMYOGP

Yoghurt, plain

MLP

VHSBAE240

Videotape cassette ASF I-320

VHS

VHSDPE120

Videotape cassette DOMI E-120

VHS

Notice how transparent IDs help us recognize items. Of course, you can create your own system for classifying items. All you need to do is decide what particular parts of ID represent: category, secondary category, manufacturer, etc.

For example, you could use the first part of an ID to specify the manufacturer or item use. The possibilities are endless... You can create a classification that suits the particular needs of your company. This is why transparent IDs are used whenever possible.

 

 




Rate this topic
Was this topic usefull?
Comments
Comment will also bo visible in forum!