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_TIVFLOWTYPE | Define Flow Types |
| Transaction Code | S_XEN_65000043 | (empty) |
| Created on | 20050726 | |
| Customizing Attributes | REFXV_TIVCDFLOWTYPE | Flow Types |
| Customizing Activity | REFXV_TIVCDFLOWTYPE | Flow Types |
Document
| Document Class | SIMG | Hypertext: Object Class - Class to which a document belongs. |
| Document Name | REFXMIV_TIVFLOWTYPE |
Use After Migration
In RE-FX, a contract can relate to more than one object. Therefore, the revenue that is posted with the contract is transferred to the object in a second posting. This second posting is needed so that the revenue can be shown in Controlling on the object from which it originated.
The logic used here is similar to that used for the general contract in Classic RE. Since there were no postings of this kind for rentals in Classic RE, you have to set up the flow types for the transfer posting. To identify the flow types needed, proceed as follows:
- In a client containing RE-FX standard Customizing, choose transaction SM30, view V_TIVCDFLOWREL.
- Look at the flow types that are assigned for relationship 30 in the Ref (reference flow type) column. For basic rent, the transaction types are, for example:
1040 Basic rent transfer
1041 Trsfr. basic rent receivable
1042 Office basic rent trsfr credit
1044 Office basic rent transfer own
1064 Off.basic rent trsfr own f.u.p.
1074 Off.b.rent trsfr own f.u.cred.
You must create the first three flow types for each condition type that is used in lease-outs and is relevant for posting. You need the last three flow types, in addition, for all condition types that are used in own-use contracts. It is advisable to use numbering that is the same as, or similar to, that used in standard Customizing (as long as these keys do not conflict with already existing keys that were generated from Classic RE).
The simplest method is to copy the six flow types listed above from standard Customizing using the client comparison, and then to use the copies as a template for all further flow types.
The comparable flow types for advance payments for operating costs or advance payments for sales-based rent are:
2040 AP oper.costs transfer
2041 AP oper.costs trsfr receivable
2042 AP oper.costs trsfr f.u.credit
2044 AP oper.costs trsfr own use
2064 AP oper.costs trsfr own f.u.p.
2074 AP OC trsfr own f.u. credit
Since object transfer also takes place for service charge settlement, you have to create additional flow types along the same lines as:
2045 Neutraliz. Trsf AP OC Credit
2046 Neutraliz. Trsf AP OC Recv.
In RE-FX, credits from settlement are also posted using flow types. (In Classic RE, a dummy flow type was used for this instead.) Therefore, you also need a flow type for the customer transfer posting for each advance payment flow type:
2007 SCS: Transfer Paid AP Op.Costs
You may also want to use the posting of balances method. (In that case the settlement posts the difference between the proportional receivable and the advance payment to the customer, rather than posting the proportional receivable as a debit and the advance payment as a credit.) If you do choose posting of balances, you also need these flow types:
2008 SCS: Transf.Unpaid AP Op.Costs
2048 Transfer AP OC G/L Account
This applies only to service charge settlement, not sales-based settlement. You need flow type 2008 only if you perform settlement using the actual principle (based on actual payments). Remember that the system does not support use of the actual principle for advance payments that were migrated from Classic RE.
If you want to use the current occupancy principle (COCP), you also need flow types for the transfer postings for each advance payment flow type:
2050 Trsf AP OC COCP Cust->G/L Acct
2051 Trsf AP OC COCP Vac.->CustAcct
2052 Trsf AP OC COCP OwnUse ->Cust
2053 Trsf AP OC COCP Vac.->G/L Acct
2054 Trsf AP OC COCP Own ->G/L Acct
If there are vacancy advance payments for rental objects, then these are transferred during service charge settlement. In that case, you need the following reference flow type for each advance payment flow type:
2011 SCS: Trsfr Vacancy AP OC
You need the same flow types for flat rates for service charges as you do for basic rent.
For rent reductions copy these flow types and use them as templates:
1940 Rent Reduction Transfer
1941 Incr. RentReduct. Recvbl Trsfr
1942 Reduction RentReduction Trsfr
1944 RentReduction Trsfr Own Use
1964 Incr. RentReduct.Trsfr Own Use
1974 Red. RentReduct.Trsfr Own Use
General Description of "Setting Up New Flow Types"
Use
In this section, you define flow types. This is a prerequisite for creating condition types and for account determination. Flow types classify flows in:
a) The cash flow
b) Accounting
With certain 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 the following activity using a relationship key:
Requirements
Standard settings
Activities
Create unique keys for flows that are for posting and for statistical flows. For each flow record, define whether it is for a debit posting or a credit posting.
If you want an approval workflow to be triggered when changes are made to this flow, then set the Relevant for Approval indicator.
Example
Example
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 |
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_TIVCDFLOWTYPE | V - View | SM30 |
History
| Last changed by/on | SAP | 20050726 |
| SAP Release Created in | 600 |
