SAP ABAP Data Element JUMLF (Cost Elements That Can Be Apportioned)
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
Basic Data
Data Element JUMLF
Short Description Cost Elements That Can Be Apportioned  
Data Type
Category of Dictionary Type D   Domain
Type of Object Referenced     No Information
Domain / Name of Reference Type JANEI    
Data Type CHAR   Character String 
Length 1    
Decimal Places 0    
Output Length 1    
Value Table      
Further Characteristics
Search Help: Name    
Search Help: Parameters    
Parameter ID   
Default Component name    
Change document    
No Input History    
Basic direction is set to LTR    
No BIDI Filtering    
Field Label
  Length  Field Label  
Short 10 Appor. ind 
Medium 15 Can be apport. 
Long 20 Can Be Apport. 
Heading
Documentation

Definition

This indicator determines whether the service charge key is apportionable or not, depending on the respective tenancy law.

Use

Apportionable service charge key

Service charges are apportioned on the tenants according to the apportionment factors

Non-apportionable service charge key

Incurred costs remain on the rental agreement or rental unit. This means that the costs are not passed on to the tenant as a receivable, but instead are posted to the following clearing accounts:

  • 470510 Clear.acct RA w/o furth.clear. or
  • 470520 Clearing account RU

In the settlement result, the affected rental agreements are indicated with NPA (No participation).

Example

There is a settlement unit with costs of 1000 euros for a non-apportionable service charge key, in which two rental agreements participate as follows:

Rental unit 1 : 100 m2 area

Rental agreement : 1.1 01/01/1998 - 04/30/1998

Vacancy : 05/01/1998 - 06/30/1998

Rental unit 2 : 100 m2 area

Rental agreement : 2.1 01/01/1998 - 06/30/1998

The costs distribution is therefore as follows:

Rental agreement 1.1.    01/01/98-04/30/98     NPA     331.49

Vacancy RU 1        05/01/98-06/30/98     VAC     168.51

Rental agreement 2.1.    01/01/98-06/30/98     NPA     500.00

The following postings were generated:

Pst.key    Amount        Acct     Text                        Acct Assign.

40    331.49        470510    Sett. RA w/o furth.clear.     RA 1.1.

40    168.51        470520    Sett. rental units     RU 1

40    500.00        470510    Sett. RA w/o furth.clear.     RA 2.1.

50    1000.00        470499    Clrg apport.op. csts         SU

Credits/Receivables for non-apportionable service charge keys are not created for the affected rental agreements. Therefore, a transfer posting of the advance payments does not take place either.

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