- #MAINTENANCE BASIC DATA SAP HOW TO#
- #MAINTENANCE BASIC DATA SAP SERIES#
- #MAINTENANCE BASIC DATA SAP FREE#
This will have an impact on how the data can be read later on. Note how if we use this method of value assignment, the values are created as key/value pairs. Also, we set Black as the default by checking the respective box.
#MAINTENANCE BASIC DATA SAP FREE#
In our case, we use the Allowed Values strategy to create suggestions for the colors our cars usually have, but leave the user free to enter more. However, it only works for catalogs 1 (Characteristic Values) and 3 (Usage Decisions, this is needed in the QM calibration process). It can contain codes from multiple catalogs, which then restrict the possible values of the characteristic if the set is linked. A Selected Set can be created using transaction QS51. Via the Catalog Characteristic strategy, the characteristic can be linked to a Selected Set.
#MAINTENANCE BASIC DATA SAP HOW TO#
More information on how to do this can be found in the F1 help for the function module name field or here: Function Module Interface. This is by far the most sophisticated (and work-intensive) way to check the values for a characteristic in SAP ERP®. It must have exactly one field and its data type must correspond exactly to the characteristic’s data type.Ī function module can be entered here that allows the implementation of custom logic to check the characteristic value. By unchecking the Additional Values box it’s also possible to restrict the possible values to only the ones listed in this tab.Ī table which contains the allowed values can be named here. This way of value control allows to create suggestion values for characteristics that the user can pick from during object classification. By clicking the Other Value Check button, we can pick four ways to suggest or restrict the values. In the Values tab, we have very detailed control over the values that the characteristic will allow. The “entry required” indicator will make this characteristic mandatory during classification. In this case, it can be entered more than once for any object (which doesn’t really make sense for color). It’s also possible to mark the characteristic as multi-value. In this case, the character field we choose lets us enter the maximum number of characters as well as an indicator for case sensivity. Depending on what data type you pick, you can further refine options for the characteristic field. The system offers you data types for character fields, currency, dates, numbers, or time. When creating a characteristic, you can choose between different data types. For a car, you might want to create a characteristic called “COLOR” to maintain the color of your cars. A characteristic describes a specific property of an object. To add custom data to objects, the first thing we need to do is create Characteristics for it. Maintaining characteristics – transaction CT04 Instead, we follow these steps to set up classification for our object.
With classification, there is an easy way to maintain this in the equipment master data transactions (and much more, as we’ll see) without doing any development or customizing. Cars have very specific properties, such as color, number of doors, fuel type, et cetera. Let’s say we want to maintain our company fleet as PM equipments, which is not uncommon to do. In plant maintenance, we often have a situation where we manage many different objects of the same kind, which have the same specific properties and require to be handled the same way. In the first part of the series, I’d like to give you a general overview about what the SAP ERP® classification can do. Starting with this post, where I give an overview of the topic and mention important terms, I will go through the data model and demonstrate how to read data from classification and how to set up authorization.
#MAINTENANCE BASIC DATA SAP SERIES#
This is the start of a several-part series in which I want to give an in-depth explanation of the classification functionality in SAP ERP®. SAP Classification Explained Part 1: Classification Basics and Transactions
0 kommentar(er)
