Before creating products, you must first have maintained a prefix for your name range and the attributes.

The prefix is part of a globally unique internal identification key. This key consists of the prefix and a consecutive number. It is automatically generated and assigned to every attribute or product. This means you set the prefix once, and subsequently, for every new creation of an attribute or product, the system automatically assigns the identification key in the set name range.

The prefix is needed to enable differentiation between attributes and products from different manufacturers. Use an own prefix for each system so that newly created attributes and products do not overwrite existing ones.

You maintain the prefix in the Implementation Guide (IMG) by choosing Master data ® Product definition ® Set prefix.

It is not possible to save attributes and products without specifying a prefix.

Attributes determine the functionality of a product, so the more attributes you assign to a product, the greater its functional quality. This assignment is optional.

For a clearer overview, attributes are arranged in hierarchies. For technical reasons, the grouping attribute is on the first hierarchy level and the other hierarchy levels are attached to it. The grouping attribute has no other function.

Each attribute belongs to exactly one attribute category, the following of which are supplied:

• Grouping attribute: Attributes of this category have no direct function. They serve primarily to construct the attribute hierarchy, to classify the attributes and to assign them to attribute groups.
• Field: This attribute is a visible field in an account. You can assign a default value and a field modification (required, optional, display, hidden) to a field. You can assign several default values to multiple-value fields. An example of a field with one value is the currency, an example of a field with several kinds is the check type.
• Feature: Each feature attribute involves a function that you activate by assigning the feature attribute, or deactivate by not assigning it. Example: Bank statement, checks (cheques).
• Matrix: This attribute involves two values, the cross product of which you assign to the product. Example: Payment transaction operation. An operation consists of a transaction type and a medium. There is a certain number of transaction types (n) and a certain number of media (m). You can assign each of the possible n*m cross products to a product.

When you maintain attributes, you first set the attributes you basically wish to use. You have the following options:

1. You can adopt the attributes supplied by SAP without changing them, and need then make no other settings.
2. You can alter the attributes supplied by SAP by changing the hierarchy or the name.
3. You can create your own attributes in addition to those supplied.

Consider the following before maintaining the attributes: Which attributes do you need in your company and which can you do without? How do you want the products to be designed, meaning which general and which specific characteristic features do you want to apply? In which sequence do you want the individual screens with the attributes to appear?

You define attributes in the Implementation Guide (IMG) by choosing Master data ® Product definition ® Product attributes. There is a description of how to change attributes or create new ones in the Implementation Guide.

You have successfully created products and can now assign accounts to them. In the application itself you have the option of having the products displayed. Choose Product ® Display product.