Hierarchy
EA-FIN (Software Component) EA-FIN⤷
RE-FX-MI (Application Component) Migration⤷
RE_MI_CL (Package) RE: Migration RE Classic => RE-FX
IMG Activity
| ID | REFXMIV_TIVCDFLOWREL | Assign Reference Flow Types and Define Account Determination |
| Transaction Code | S_XEN_65000044 | (empty) |
| Created on | 20050726 | |
| 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 | REFXMIV_TIVCDFLOWREL |
Use in Migration
You previously defined new flow types for transfer postings and for service charge settlement. Now you assign these flow types to the original flow types.
For transfer postings, use the relationship:
30 Distribution Posting
Use standard Customizing as a guide. You created flow types that are analogous to these: 2007 SCS: Transfer Paid AP Op.Costs 2045 Neutraliz. Trsf AP OC Credit 2046 Neutraliz. Trsf AP OC Recv. 2048 Transfer AP OC G/L Account
You then have to assign the following relationships to these new transfer flow types:
110 SCS: Receivable from Settlements
120 SCS: Credit from Settlements
130 SCS: Legacy Data Transfer of Service Charges
160 SCS: Advance Payment Transfer Credit Balance
170 SCS: Advance Payment Transfer Debit Balance
180 SCS: Advance Payment Transfer to G/L Account
Below is an example of how this looks in standard Customizing:
Relationship Type 30: Distribution Postings (Object Transfers): 30 2000 Op.costs AP 2040 AP oper.costs transfer 30 2001 Op.costs AP recvbl 2041 AP oper.costs trsfr receivable 30 2002 Cred.OC AP foll-up post. 2042 AP oper.costs trsfr f.u.credit 30 2004 Own use OC AP 2044 AP oper.costs trsfr own use 30 2024 Own use OC AP f.u.post 2064 AP oper.costs trsfr own f.u.p. 30 2034 Own use OC AP f.u.cred.post 2074 AP OC trsfr own f.u. credit Relationship Type 110: SCS: Receivable from Settlements: 110 2040 Trsfr AP OC 2045 Neutraliz. Trsf AP OC Credit 110 2044 Own use trsfr AP OC 2045 Neutraliz. Trsf AP OC Credit
Relationship Type 120 SCS: Credit from Settlements: 120 2040 Trsfr AP OC 2046 Neutraliz. Trsf AP OC Recvbl 120 2044 Own use trsfr AP OC 2046 Neutraliz. Trsf AP OC Recvbl
Relationship Type 130 SCS: Legacy Data Transfer of Service Charges: 130 2000 Op.costs AP 2007 SCS: Transfer Paid AP Op.Costs
Relationship Type 160 SCS: Advance Payment Transfer Credit Balance: 160 2000 Op.costs AP 2007 SCS: Transfer Paid AP Op.Costs
Relationship Type 170 SCS: Advance Payment Transfer Credit Balance: 170 2000 Op.costs AP 2008 SCS: Transfer Unpaid AP Op.Costs 170 2003 Vacancy op.costs AP 2011 SCS: Trsfr Vacancy AP OC
Relationship Type 180 SCS: Advance Payment Transfer to G/L Account 180 2000 Op.costs AP 2048 Transfer AP OC G/L Account
You need the settings for relationship types 110, 120, 130 and 160 only for advance payments (service charge settlement or sales-based settlement).
You need the setting for relationship type 180 only in the following case: you use advance payments for service charge settlement, and you also choose to post the balance of receivables and advance payments (Post Balance indicator is set) or you use the current occupancy principle.
You need the setting for relationship type 170 and flow type 2000 only if you use the actual principle. You need the setting for relationship type 170 and flow type 2003 only if you post vacancy advance payments to rental objects.
If you use the current occupancy principle, you also need to make the following settings for advance payments for service charges:
Relationship Type 180 SCS: Advance Payment Transfer to G/L Account 2003 Vacancy oper.costs AP 2051 Trsf AP OC COCP Vac.->CustAcct 2004 Own use oper.costs AP 2052 Trsf AP OC COCP OwnUse ->Cust
Relationship Type 190 SCS: Advance Payment Transfer COCP: 2000 Operat.costs adv.pmt 2050 Trsf AP OC COCP Cust->G/L Acct 2003 Vacancy oper.costs AP 2053 Trsf AP SC COCP Vac.-> G/LAcct 2004 Own use oper.costs AP 2054 Trsf AP SC COCP Own -> G/LAcct
Make these settings in the Assign Reference Flow Types for Receivables/Credits from SCS IMG activity.
Then assign account symbols to all your newly created flow types in the Assign Account Symbol to Flow Type IMG activity. You can use standard Customizing as an example here as well.
Keep in mind that there is a different account determination for rent reductions, and that there are two additional flow types for advance payments for service charge settlement and sales-based rent.
Once you have recorded your Customizing settings in a transport request, you can use transaction SE09 (look at the key for view V_TIVCDFLOWTYPE) to see which flow types are new. (The first three characters designate the client, the following four characters designate the flow type.)
If you are using new account symbols, you also have define these, either beforehand or in parallel, in the Account Symbols IMG activity. You need at least one new account symbol for transfer postings. (In standard Customizing, this is symbol TREV).
Assign your newly created account symbols to FI accounts in the Replace Account Symbols IMG activity. You may have to create the FI account beforehand.
It is not absolutely mandatory for each transfer flow type to post to a different account. It makes much more sense, for example, to have all transfer postings for rent payments post to one common account, and all transfer postings for operating costs to post to a different account.
For a complete description of the settings for reference flow types, see the following text.
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
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 |
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 | 20051213 |
| SAP Release Created in | 600 |
