Hierarchy
EA-FIN (Software Component) EA-FIN⤷
RE-FX (Application Component) Flexible Real Estate Management⤷
RE_CA_CU (Package) RE: Customizing (IMG) and Area Menu
IMG Activity
| ID | REFXV_TIVCDFLOWREL | Assign Reference Flow Types |
| Transaction Code | S_ALN_01000803 | (empty) |
| Created on | 20020129 | |
| Customizing Attributes | REFXV_TIVCDFLOWREL | Assign Reference Flow Types |
| Customizing Activity | REFXV_TIVCDFLOWREL | Assign Reference Flow Types |
Document
| Document Class | SIMG | Hypertext: Object Class - Class to which a document belongs. |
| Document Name | REFXV_TIVCDFLOWREL |
Use
In this step, you assign reference flow types to flow types.
Definition
With certain business transactions, postings cannot be made using the flow type that was originally assigned (the flow type derived from the condition type). For such transactions, reference flow types must be assigned. You make these assignments in this activity using a relationship key.
- Example of Using a Relationship Key
- 10 Follow-Up Postings Due to Condition Increase
You use this reference flow type when rent receivables are increased retroactively (that is, after a debit position posting). Flow types that are referenced by the reference flow type can be the basic flow types that are assigned directly to a condition type, or they can be flow types for own use and vacancy.
- 20 Follow-Up Postings Due to Condition Reduction
You use this reference flow type when rent receivables are reduced retroactively (that is, after the debit position posting). Flow types that are referenced by the reference flow type can be the basic flow types that are assigned directly to a condition type, or they can be flow types for own use and vacancy. Usually the reference flow type consists of the reversed account determination (whereby the debit and credit postings are transposed) of the account determination in the original flow type.
- 30 Distribution Transfer Posting (Object Transfer Postings)
In the real estate contract, the periodic posting function generates a primary posting on the basis of the condition type. In the case of vendor contracts, this posting debits costs to the contract and credits payables, while in the case of customer contracts it debits receivables and credits revenue (contract). If it is specified in the contract that the costs are to be distributed to the objects (this should normally be the case to enable the costs and revenues on the objects to be seen in Controlling), a reference flow type determined via relationship key 30 has to be specified for the costs to be transferred to the objects. For vendor contracts, the transfer posting debits costs (object) and credits cost allocation (contract) and for customer contracts it debits revenue allocation (contract) and credits revenue (object).
- 40 Own Use
The reference flow type for this relationship key is used when the cash flow is generated from a contract with contract type Internal Contract.
Caution:
All flow types for condition types that are to be used on internal contracts require a reference flow type here. Otherwise you cannot activate the contract.
Specify a G/L account posting for account determination. For the reference flow types 040 Own Use, you also define reference flow types with relationship keys 10 Follow-Up Postings Due to Condition Increase and 20 Follow-Up Postings Due to Condition Reduction. - 60 Vacancy
The reference flow type is used for the vacancy debit position of the rental objects (only for the time during which there is no active occupancy contract for the rental object).
Caution:
Vacancy flows are only generated and posted for condition types if a reference flow is defined here for the corresponding flow type.
By defining vacancy flow types, you can control whether a condition type on the rental object is for information purposes only (default value for the contract) or whether vacancy postings are to be made for this condition type.
Specify a G/L account posting for account determination. For flow types assigned to these with relationship keys 10 Follow-Up Postings Due to Condition Increase and 20 Follow-Up Postings Due to Condition Reduction, you also have to enter reference flow types with relationship key 60 Vacancy. - For information on reference flow types for service charge settlement (relationship key in the range 100 - 199), see Reference Flow Types for Service Charge Settlement.
- 310 Installment Payment
You use this reference flow type to post an installment payment for an item posted with RE-FX. The posting specification is debit customer, credit customer. The open item originally posted is cleared.
To define installment payment for items that were posted to a customer account without a flow type, specify a reference flow type with this relationship type for the empty flow type. - 320 Irrecoverable Debt
You use this reference flow type to write off an item posted with RE-FX (such as because no more payments are expected on the receivable). The posting specification is debit costs, credit customer. The open item originally posted is cleared.
To be able to write off items that were posted to a customer account without a flow type, specify a reference flow type with this relationship type for the empty flow type.
Requirements
Standard settings
Activities
Example
Business Attributes
| ASAP Roadmap ID | 203 | Establish Master Data |
| 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 | REFXV_TIVCDFLOWREL | 0 | ALN0000043 | Service Charge Settlement |
Maintenance Objects
| Maintenance object type | C | Customizing Object |
| Assigned objects | ||||||
|---|---|---|---|---|---|---|
| Customizing Object | Object Type | Transaction Code | Sub-object | Do not Summarize | Skip Subset Dialog Box | Description for multiple selections |
| V_TIVCDFLOWREL | V - View | SM30 |
History
| Last changed by/on | SAP | 20020131 |
| SAP Release Created in | 110 |
