Ansicht
Dokumentation

SIMG_CFMENUOFDIFZC1 - Maintain Condition Types and Condition Groups

CPI1466 during Backup   BAL_S_LOG - Application Log: Log header data  
This documentation is copyright by SAP AG.

In this section, you edit the required condition groups and condition types for rental agreements, rental units, and management contracts as well as general contracts by:

1. Checking or maintaining condition types
2. Checking or maintaining condition groups
3. Checking the assignment of the condition groups to product types
4. Assigning condition types to the condition groups

Proceed as follows:

1. Condition types
1. Check if the existing condition types are sufficient for your enterprise. For more detailed information on the condition types, double click on the condition type.
2. Should you need additional condition types, create them using the "New entries" or "Copy entry" function:

• Assign a flow type to each condition type. The flow type has to exist ("Define flow types" activity).

• Generally, you do not need an entry in the flow type field. If the field for the flow type maintained for the condition type is filled, the flow category defined in the flow type appears.

• If you want to base the rent on an area type other than the reference area type, assign an area type to the condition type as a reference value.

Example: In a commercial rental agreement (for example, for a store), different rents for shop floor space, corresponding office space, storage space, and so on, are agreed by contract. So that these areas are displayed in the lease with the corresponding rent, define different condition types for this and assign the area types to them:

,,Condition type,,,,Area type
,,Basic rent shop,,,,Shop floor space
,,Basic rent office,,,,,,Office space
,,Basic rent storage,,,,Storage area
By means of the description of condition categories, you can prevent the condition type 'Basic rent' from being chosen in addition.

1. To support the administrator when choosing the correct condition type, you can create documentation for each condition type (display within the processing of the rental agreement and the rental unit).
   Here in the "Documentation" field, you determine which documentation is to be displayed. Via the "Display documentation" pushbutton, you can display the contents.
   If the available documentation modules do not suffice, you can create new modules as follows:

• Call up the "Data Dictionary" transaction (SE11).

• Enter BKOND as object name and choose the object class "Data elements".

• Choose the "Display" function. You reach the overview screen for the data element BKOND.

• Switch from the display mode to change mode.

• Choose "Data element supplement documentation". Enter a four-digit number that describes the data element supplement documentation. The number should come from the customer name range (9000-9999).

• Maintain the documentation text.

• Maintain the number of the text and a short description text in the "Documentation key for documentation dependent on condition type" (second item in this section). The standard entries supplied by SAP should first be copied from client 000 (comparison).

• In this Customizing section, include the number of the data element supplement documentation for the required condition type.

1. Check and maintain condition groups
2. Checking the assignment of the condition groups to product types

1. Assign condition types to the condition groups
   
   Here, you maintain the assignment of condition types to the condition groups (rental agreements, rental units management contracts). That is: You specify which condition types may be used for which business application components.

• Choose the "Determine condition groups" level.

• Position the cursor on a condition group, to which you want to assign condition types.

• Then choose the "Assign condition types to condition groups" level and check the standard setting.

The following attributes are determined for each condition type within the condition group:

Display sequence of the condition types within the group

The condition types are listed in the rental agreement, the rental unit, the offer, the management contract (condition group) sorted by this field in ascending order.

Display hierarchy when inserting new conditions:

The display hierarchy also affects master data maintenance (rental unit, rental agreement, management contract, offer). If there you choose the "New condition type" function, first only the condition types of hierarchy level '0' are displayed. When you use the "Display" function, the condition types of the following level are displayed.

Hierarchy level '9' is used for condition types that are indeed required by the system but it cannot be accessed directly by the user. Please assign hierarchy level '9' to the condition types for cash deposit.

Condition type required entry?

With the indicator, you specify whether the entry of an amount for this condition type is always required. However, it recommended to define this functionality using the control of the condition category.

Superimpose the condition type on the entry screen for the conditions or not (hidden)?

Condition types, for which the 'Hide' indicator is set, are not proposed when creating a new object but have to be explicitly chosen via the "New condition types" function.

Preselection

Specify whether the condition type may also be filled with the value 0 (the condition should be stored as noted items), that is, a condition item

Sublease surcharge EUR 0.00.

may appear on the rental agreement, for example.

• If you want to assign additional condition types, enter them using the "New entries" function

• Save your entries.

If you want to delete a condition type, first check whether dependent entries exists in the "Assign condition types to condition groups" table. Delete these entries if there are any. Then, delete the entries in the "Condition types" table.

PERFORM Short Reference   rdisp/max_wprun_time - Maximum work process run time  
This documentation is copyright by SAP AG.

Length: 8204 Date: 20240606 Time: 044806     sap01-206 ( 79 ms )