Hierarchy
⤷ 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
IMG Activity
ID | SIMG_CFMENUOFDINACHB | Follow-up Postings |
Transaction Code | S_ALR_87007734 | IMG Activity: SIMG_CFMENUOFDINACHB |
Created on | 19981222 | |
Customizing Attributes | SIMG_CFMENUOFDINACHB | Follow-up Postings |
Customizing Activity |
Document
Document Class | SIMG | Hypertext: Object Class - Class to which a document belongs. |
Document Name | SIMG_CFMENUOFDINACHB |
Follow-up postings are due when rental agreement conditions are changed retroactively (if condition rates are changed after a debit position has been carried out).
In these cases, a reference flow type derived from the corresponding flow type is used for posting:the condition type that was changed is used as a base.
Reference flow types must be used if situations arise such as those described in the chapter "Reference flow types" which make the use of the original flow type impossible.
Relationship keys are used to differentiate the reference flow types derived for individual reference actions. Relationship keys 002 and 032 are used to derive the reference flow type for follow-up posting.
Example
The following condition was determined for the rent in January:
Condition type 10 Basic rent 300 USD
After the debit position has been carried out, the rent is retroactively changed to 350 USD.
The flow type "1000 Basic rent" is assigned to the condition type "10 Basic rent" (Customizing dialog "Condition types and condition groups").
When the conditions are changed, a follow-up posting condition item (flow type of which is derived from flow type 1000 using relationship key 002) is placed into the cash flow. This is the flow type "1001 Post-receivable basic rent" (Customizing action "Maintain reference flow types").
During the next debit position, the follow-up posting is made with flow type 1001 (if the due date has been reached). Its account determination is defined in the Customizing dialog "Account determination -> Rental agreement/customers":
Flow type 1001 Group indicator + Main usage type + Acc.Ass.Value
Debit 01 * Reconc./spec.G/L acct
Credit 50 100 Revenue basic rent
Document type DA
In this case, the posting would be:
Document type DA
01 Customer account (autom.entry to reconc.acct) 50 USD
- to -
50 Account 841000 with acct. assign. to RA 50 USD
A credit memo has to be posted to the customer account when the condition is reduced from 300 USD to 280 USD. In this case, the reference flow type is located by relationship key "032 Follow-up postings credit" and is the flow type "1002 Credit memo basic rent". The following posting record is assigned to this flow type:
Flow type 1001 Group indicator + Main usage type + Acc.Ass.Value
Debit 40 100 Revenue basic rent
Credit 11 * Reconc./spec.G/L acct
Flow type DA
The posting would then be
Document type DR
40 Account 841000 with acct. assign. to RA 20 USD
- to -
11 Customer account (automatic entry to reconc. account) 20 USD
Recommendation
Follow-up postings are only available if you maintain the respective reference flow types for relationship keys 002 and 032 for all condition types/flow types in the rental agreements.
Further notes
Combination of own use and follow-up postings:
In this case, the reference flow type for own use is derived first and then the reference flow type is determined for the follow-up posting for the derived reference flow type. The same applies for vacancies.
Business Attributes
ASAP Roadmap ID | 105 | Define functions and processes |
Mandatory / Optional | 1 | Mandatory activity |
Critical / Non-Critical | 1 | Critical |
Country-Dependency | A | Valid for all countries |
Assigned Application Components
Documentation Object Class | Documentation Object Name | Current line number | Application Component | Application Component Name |
---|---|---|---|---|
SIMG | SIMG_CFMENUOFDINACHB | 0 | I090004614 | Rental Accounting |
Maintenance Objects
Maintenance object type |
History
Last changed by/on | SAP | 19981222 |
SAP Release Created in |