As you can see the design of this site has changed! We are also changing the way people interact on this site. From now on -
1. All the help needed postings should be done in the forums.
2. Blogs will only be used for writing serious blog posts. Any help needed questions posted under the blogs will be deleted - please use the forums for that!
3. Job postings will be done by registered recruiters. It will continue as a free service.
These rules are to make your networking better and easier.
Characteristic Relationships: Advantages and Prerequisites
class="flexinode-textarea-7">
I love the Characteristic
Relationships as they help and automate the validation and data entry stuff.. here is another piece of gem from the SAP
HELP!!
The following advantages result from data entry in manual planning:
In a planning layout
for which the option "All Possible Characteristic Combinations" was selected, the Cartesian product is not (as in earlier
releases with the option "form-based") formed of all theoretically possible combinations of characteristic values, but
instead only those combinations that were defined as sensible in the defined characteristic relationship. For example, in a
lead column that contains the characteristics cost center and currency only the valid currency for this is offered for data
entry for every cost center (and not all currencies contained in the package selection) As a result, data entry is made much
easier since only the really relevant value combinations are offered. In addition, such planning layouts are now much more
compact and clearer and this leads to better answer times of the system.
Through the derivation of characteristic
values it is possible for the system to determine values of different characteristics from the entry of a single
characteristic value. For example, the system can determine the appropriate value of the characteristic article group from a
value of the characteristic article. As a result of this, data entry is made easier and speeded up, and the danger of
incorrectly entered data is ruled out for the derived characteristics.
With characteristics between which there is a
dependency, the system can check whether a combination of characteristic values entered is valid or not, and thus prevent
that transaction data is entered for invalid characteristic value combinations.
Pre-requisites
Thefollowing prerequisites must be fulfilled to define characteristic relationships:
- The planning area must be a basic
planning area.
> The characteristic relationships defined in a basic planning area are also effective in multi-planning areas in which such a basic planning area is contained.
- The planning area must contain at least two
characteristics.
- In characteristic relationships of the type attribute, the target characteristic must be defined asan attribute of the basic characteristic and be contained in the planning area itself.
- In characteristicrelationships of the type hierarchy, the target characteristic must be contained in a hierarchy on the basic
characteristic.
The following prerequisites must be fulfilled to use characteristic relationships:
- The
source characteristic of a relationship must be contained in the planning level.
courtesy: SAP
Help
Lemme know if this was useful!? Write in the comments - your thoughts on this and any other
related thoughts on Characteristic Relationships
/>
