Variants are articles that only differ from one another in certain characteristics values (for example, color, size or flavor). They are compiled under a generic article, which can be considered a dummy header article, whereas the variants represent the actually available, physical articles used in all business processes, from planning to purchasing, logistics and sales. The generic article (dummy header article) serves as selection and entry help in system transactions and documents. The generic article concept makes it easy to maintain variants, as the data that is valid for all variants only needs to be entered once for the generic article. Still, the generic article also allows you to directly maintain many fields variant-specific, which makes the article data maintenance very efficient.

The generic article and variants concept was originally introduced to support the creation of the typical color/size article combinations in fashion retailing. Anyhow, generic articles and variants can be used in all retail lines of business, when articles only differ from each other in certain characteristics values. You can find some examples in the figure below.

Creating Variants for a Generic Article

To create generic articles, some preparation is necessary: Characteristics have to be defined with their characteristic values - for example, characteristic color with the values white, yellow, green, blue, and so on.
Then, these characteristics have to be assigned to a class of configuration class type 300.
Generic articles are created with the article category 01 Generic article.
The configuration class then has to be selected when creating a generic article.
A variant matrix is formed from the variant-creating characteristics. It then allows you to select the characteristic value combinations, which are to be created as variants. The variant matrix is a grid of the characteristic value combinations. This is a 2-dimensional table, with each axis showing the values of one characteristic. If there are more than two variant-creating characteristics, then the 2-dimensional table is generated for each value of the third characteristic, which are displayed in a separate tab each. It is recommended to not use more than three variant-creating characteristics.
Note
It is possible to use a maximum of five variant-creating characteristics for a generic article. However, fashion retailing typically uses two or three variant– creating characteristics: color / size, or color / size 1 / size 2. Subsequent functions require the typing of these variant-creating characteristics as color, size 1, or size 2 characteristic. This is why it’s recommended to only use up to these three variant-creating characteristics for generic articles in fashion retailing.
Furthermore, it is possible to restrict the values (select values) from variant-creating characteristics,that is, the ones which were assigned to the selected class of class type 300, when creating generic articles. This is done in the intermediate view before the variant matrix is generated.
You can select a characteristics profile (class type 026) when creating the generic article, this requires the compatibility check being switched off:
- Only characteristics profiles which contain an informative characteristic (relevancy indicator blank or 1), or characteristics profiles containing characteristics with relevancy indicator 2 (migrated profiles), which are different than the characteristics selected for this generic article via their configuration class 300, are available.
- The informative characteristics of a selected characteristics profile, or from the merchandise category (hierarchy) then only appear in the Basic Data view, without a previous value restriction option.
When creating a single article, all characteristics assigned to the relevant classes of class type 026 are available in the Basic Data view (as informative characteristics), irrespective of the relevancy indicator. A value restriction is not possible.

In SAP Retail, the generic article variants are by standard numbered based on the generic article's number, with an additional sequential three-digit suffix.
You can use user exit EXIT_SAPLMGNK_003 to compose the article numbers of the variants, for example, from:
The generic article number
The first 2 digits of the characteristic Color.
The size
The user exit is available in the IMG:→Logistics General→Material Master→Enhancements→Influence Number Assignment (Industry and Retail).
The documentation of this customizing activity provides further details.

With variant listing, the system checks if exactly the same variant does not already exist as part of a generic article in the module. You can execute the individual variant listing from within the manual generic article listing in the Material Change transaction (MM42).
Technical Aspects
Relevant tables for generic articles and variants are:
Table INOB Link between Internal Number and Object: Generic articles and variants have an object representation in this table for class type 026. Additionally, the generic articles, but not the variants, have an entry in this table for class type 300. Variants instead are handled as a configuration object instance within the installed base (IBase): Table IBINOWN stores the internal representation number, table IBST then links it with the relevant IBase object. Metadata of the IBase objects are created per variant (table IBIB); Table IBIN holds the link between the generic article (with prefix "MA"), the variant, and the related IBase object for class type 300.
Table KLAH Class Header Data: No entries are created for generic articles. Table KLAH contains entries for classes of class type 026: merchandise category (hierarchy), characteristics profiles, and of class type 300: Configuration class. Variants are not linked to the configuration class in contrast to the generic article. They only have the link to the generic article (MARA-SATNR).
Table KSSK Allocation Table: Objects to Class: This table connects generic articles and variants with the merchandise category (class type 026), and generic articles with the configuration class (class type 300).
Table AUSP Characteristic Values: Characteristic value restrictions on generic article level are only possible for variant-creating characteristics (from classes of class type 300). They are stored based on the internal object number (table INOB) of the generic article, not based on the generic article class (class type 026).
Application Variants
You use application variants to control/restrict the usage of variants of an article in application documents during certain time periods. This is to ensure that only specific variants of a generic article can be ordered from a vendor or ordered by a customer respectively.
If a vendor can provide only a limited range of sizes/colors, a purchasing variant can be created for this vendor excluding the sizes/colors that cannot be provided. For example, if a customer (group) is not allowed to order a specific range of size/colors, a sales variant can be created for this customer (group) excluding the sizes/colors which are not allowed.
Note

