Codes (numbers) of configuration objects can be used depending on their purposes. You can use codes (numbers) in the following cases:
1.1. Users deal with long lists of items.
Example: the Products catalog.
1.2. Search by codes (numbers) is easier than by other properties.
Example: the Expense items catalog. Users are likely to remember the code than read the item name. Besides, item names can change.
1.3. The code purpose is defined by specifics of the area being automated.
The length of the code (number) is set according to its purpose and receiving (input) method:
For example, the Units of measure catalog code matches the unit of measure code in UOM classifier. The CCD numbers catalog code matches the cargo customs declaration number, and so on.
3.1. The code (number) length for objects that are numbered automatically is selected according to the potential number of all objects in the database,
objects belonging to a certain period (for documents and business processes), or objects belonging to a certain owner (hierarchical and subordinate catalogs and tasks).
When selecting the code length, take into account the length of such numbering prefixes as infobase and company prefixes (if supported by configuration), and other.
When developing standard configurations, we recommend that you use the following code (number) lengths: 3, 5, 9, 11. When selecting the code length, take into account the length of such numbering prefixes as infobase and company prefixes (if supported by configuration), and other.
If the Object prefixes subsystem from Standard Subsystems Library is used in the configuration, the minimum total length of document numbers and catalog codes must be 11 characters (11, 13, 15, ...) including prefixes. For more information, see "Object prefixes" subsystem documentation at ITS website.
3.2. If object codes are used as a short presentation of the data item as a string (see cl. 2.1), the code length must be sufficient to store a short string presentation of the objects depending on the code purpose.
3.3. If codes (numbers) of objects are received from external sources (see cl. 2.2), the code (number) length depends on this source.
3.4. We recommend that you set an allowed code (number) length for variable objects.
If the application allows users to access data entered from several sources simultaneously (within DIB or in other applications), it must automatically assign prefixes to configuration objects, which meet the following conditions:
- String code (number) is used.
- Autonumbering is used.
- Data that matches the respective area within which codes (numbers) must be unique, can be entered from several sources simultaneously (DIB nodes, applications) and later consolidated, for example, as a result of data synchronization. In most document kinds, such areas are a company and a period.
If Standard Subsystems Library is used in the configuration, take advantage of the Object prefixes subsystem to meet this requirement.