SAP ABAP Message Class 60 Message Number 922 (Error occurred during settlement unit check (Correct your entry))
Hierarchy
☛ BBPCRM (Software Component) BBPCRM
   ⤷ CRM (Application Component) Customer Relationship Management
     ⤷ CRM_APPLICATION (Package) All CRM Components Without Special Structure Packages
       ⤷ FVVI (Package) R/3 appl.dev. for Financial Assets Management: Real estate
Attribute
Message class 60  
Short Description Real Estate    
Message Number 922  
Documentation status      
Authorization check Error Message      
Changed On    
Message Text
Error occurred during settlement unit check (Correct your entry)
Help Document

Diagnosis

The consistency of the data is checked before it is saved. In doing so, the system has detected errors regarding the settlement participation.

System Response

The system cannot save the data until the errors have been corrected.

Procedure

Please correct the errors and save the data again.

To localize the error, choose "Goto -> Settlement particip." in the master data maintenance screen of the rental agreement and then choose "Edit -> Checks -> Check sett.particip.".

If the settlement participation is not set correctly, you will receive a popup with the corresponding error messages. You can display further details on an error message by positioning the cursor on the message and clicking "Long text".

Check whether the condition types of the contract and the Customizing settings fulfill the conditions described below:

The settlement participation is generated from / checked against:

  1. service charge key of the settlement units for the rental agreement.

    The rental agreement is assigned to settlement units (depending on the rental period) via the rental unit. An entry must exist in the settlement participation for every service charge key of a settlement unit (created automatically when it is regenerated - provided that this is possible)

  2. The conditions of the rental agreement

    The service charge keys that belong to each condition are defined in Customizing (see 3). The Customizing settings for condition categories determine whether a condition type is an advance payment or a flat-rate. The settlement type is determined (when the settlement participation is generated) and checked (if the settlement participation was maintained manually) from this information as well as from the conditions that apply to the rental agreement.

  3. If all entries are correct, Customizing must be checked. In this case, contact your system administrator.

Procedure for the system administrator

Check the defined assignment of service charge key to condition types in Customizing.

If special condition types are to be valid for individual service charge keys, corresponding service charge keys must be assigned to these condition types.

A three-stage search is carried out when the settlement participation is generated/checked:

  1. Stage 1: Is a condition type assigned to the special service charge key? If so, this condition type will be used if it has been defined for the agreement.
  2. Stage 2: Is a condition type assigned to service charge group 1 or 2? If so, this condition type is used if it has been defined for the agreement.
  3. Stage 3: Is a condition type assigned to service charge group 3? If so, this condition type is used if it has been defined for the agreement.

    The error message mentioned above is output if more than one condition type is found at any level.

    Example:

    Condition type 210 Water flat-rate -> SCK 100 Water

    Condition type 211 AdvPmnt water -> SCK 100 Water

    Condition type 220 Oper.costs flat-rate -> SCGr 1 Operating costs

    Condition type 221 Oper.costs flat-rate -> SCGr 1 Operating costs

    If the rental agreement belongs to a settlement unit with service charge key 100, the system first searches for the condition types 210/211.

    If both of these are present, the above error message appears.

    If exactly one is present, it is assigned.

    If neither one is present, the system searches for condition types 220/221.

    This also applies to condition types in group 3.

History
Last changed on/by 19970516  SAP 
SAP Release Created in