Enumerations are used in the 1C:Enterprise system to describe permanent sets of values that do not change as the configuration is used.

Unlike a catalog, the values of enumerations are specified at the configuration phase, and cannot be changed at the execution phase.

Typical examples of enumerations are payment types (cash, cashless, barter), client status (permanent, one-time), etc.

One major feature of enumerations that distinguishes them from catalogs is that the set of values in an enumerations does not change as the end user works with the program. For example, a configuration algorithm can be designed so that each client has one of two statuses, either "permanent" or "one-time"; in that case, the client's status is specified by selecting one of the enumeration values. The user cannot add a new status to the enumeration.

Unlike lists, specific values for catalogs are normally entered by the user working with the program, for example: product description, trading partner, etc.

1C:Enterprise Developer's Community