You can make various settings for the characteristic here.
- You specify a unit InfoObject that is a unit of measure. The unit InfoObject must be an attribute of the characteristic. This unit InfoObject is used when quantities are converted for the master data-bearing characteristic in the Business Explorer. More information: Quantity Conversion
- You can define units of measure for the characteristic. The system hereby creates a DataStore object for units of measure.You can specify the name of the quantity DataStore object, the description, and the InfoArea that you want to add the object to. The system proposes the name: UOM<Name of the InfoObject that the quantity DataStore Object is being added to>.More information: Prerequisites for InfoObject-Specific Quantity Conversion
- You select a unit InfoObject that is a currency that you have created as an attribute for the characteristic. In this way, you can define variable target currencies in the currency translation types. The system determines the target currency using the master data when you perform currency translation in the query and dynamically when loading data.
- You can allow the characteristic to be used as a Document Property. This enables you to assign a comment or any document to a combination of characteristic values. More information: Documents
- You can specify a fixed unit of measure.
- By assigning a constant, a fixed value is assigned to a characteristic. The characteristic then exists on the database (for verifications for example) but does not appear in the query. It is particularly useful to assign constants to compound characteristics.
The Storage Location characteristic is compounded with the Plant characteristic. If just one plant is always used in the application, a constant can be assigned to this plant. Validation against the storage location master table should then be performed using this value for the plant. In the query, the storage location only appears as a characteristic however.
- You can specify a DataStore object for checking the characteristic values. If you create a DataStore object for checking the characteristic values in a characteristic, the valid values for the characteristic are determined from the DataStore object rather than from the master data during transformaton. The DataStore object must contain the characteristic itself and all the fields in the compound as key figures.