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_TIVCDDUEDATE | Due Date Correction Rule |
| Transaction Code | S_PLN_06000028 | (empty) |
| Created on | 20030429 | |
| Customizing Attributes | REFXV_TIVCDDUEDATE | Due Date Correction Rule |
| Customizing Activity | REFXV_TIVCDDUEDATE | Due Date Correction Rule |
Document
| Document Class | SIMG | Hypertext: Object Class - Class to which a document belongs. |
| Document Name | REFXV_TIVCDDUEDATE |
Use
The due dates for a condition are specified by the frequency term. Here you first specify how due dates fall in relation to the calculation period by entering the payment form (due at the start, middle, or end of the period).
In order to reflect more complex methods for determining the due date (for example, always due on 3rd business day of month), you can relate the frequency term to a due date correction rule.
Here you can define these more complex rules for determining due dates. Keep in mind that the specifications you make here always apply in relation to the due date determined by the payment form.
On the contract, you can still manually change both the due date itself in the cash flow, as well as the parameters of the due date correction rule defined here (with the exception of the parameters for due dates of follow-up postings). It is therefore not necessary to enter rules in Customizing for absolute exceptions.
The due date in the cash flow is transferred to Financial Accounting. This date controls payment and dunning processes for accounts payable and accounts receivable processes.
During periodic posting, the items to be posted can be selected either by due date or by calculation date.
Requirements
Standard settings
SAP provides an empty rule. This rule corresponds to the way due dates were determined in Classic RE and in RE-FX up to and including Release 1.10.
Activities
Define the due date correction rule that should be used as the standard for most contracts, and give this rule the key " " (default setting). Subsequent changes you make in Customizing are applicable only when they affect due dates for follow-up postings, and only when there is a contract or rental object with follow-up posting items that are not yet posted.
Define the following parameters for your due date correction rules:
Due Date Correction
First specify how the due date should be corrected (moved). You have two basic options. First, you can shift the originally calculated due date by a given number of days, months and/or years. The shift can be forward (" - " sign) or backward (no positive/negative sign). Second, you can specify that the due date is always a given weekday (for example, "3rd Monday," together with a monthly frequency and "in advance" payment form would mean the rent is always due on the third Monday in the month) or you can specify that it is the nth business day. If you use a business day, then you also have to enter the calendar that is used to determine what days are business days.
In the No. field in front of the due date correction rule, you can specify the sequence in which the due dates determined by the payment form are corrected.
Example:
A three-month rent should be due on the 3rd business day of the 3rd month.
You define the following rule: No. 1 Move (+/-) By Days Months 2 Years No. 1 Move (+/-) To 3 Working Day Calendar USA
In the frequency term of the contract, you choose 3 months as the frequency, and the payment form "in advance."
On the other hand, if you agreed that rent is due on the 3rd business day of the month, and you give the tenant two months in which to pay, then you should set the rule as follows: No. 2 Move (+/-) By Days Months 2 Years No. 1 Move (+/-) To 3 Working Day Calendar USA
The rule only appears in maintenance of the frequency rule if you entered a number here. The system displays the rules in the contract in ascending order based on the number entered here. It can be usefulto enter a number but leave the parameter empty, if you want to define the correction on the contract.
Behavior of Due Dates at Start and End
If you do not make any entries here, then the system uses the due date determined by the rules defined above, even if the contract starts or ends in the middle of a period. The result could be that rent due in advance would then be due before the start date of the contract. You can prevent this by setting the appropriate indicator here. The due date is then moved to the start date or the end date of the contract as specified.
Due Dates for Follow-Up Postings
Follow-up postings are created when data relevant to the cash flow (values affecting determination of the condition amount, or data of the frequency term) is changed, and the change affects calculation periods that were already posted.
If the due date relates to payments, then it is usually not possible to calculate it using the "normal" rule for follow-up postings, since the tenant is usually not informed of the change until after the due date determined in this way.
For credit memos and receivables, you can decide separately how the due date is calculated. The options are:
Due Date: Due Date As in Source Flow
The due date is determined according to the rule that is already set. SAP recommends that you set the "Move to Current Date" indicator, at least for follow-up postings. The result is that the due date is moved to the current date (the system date at the time of the change) if the due date is before this date.
Due Date As Entered
When follow-up postings result from a change to the contract, the system asks in the application dialog when these should be due. For all follow-up postings that are due before the date determined by the set rule, the system moves the due dates to this date.
Move +/- Days
Here you can specify that the due date determined in this way for follow-up postings is moved forward or backward by this number of days.
You can make separate settings for follow-up postings from the object cash flow and from the partner-related cash flow. If your object transfers are always synchronous with periodic posting of payments, then SAP recommends setting the "As Partnr-Rel.CashFlow" (as partner-related cash flow) indicator.
Otherwise, it can make sense to leave the due dates originally determined in the object cash flow as they are. (This makes the cash flow easier to understand, and the due date is irrelevant from an accounting perspective in the object cash flow.)
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_TIVCDDUEDATE | 0 | ALN0000031 | Flexible Real Estate Management |
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_TIVCDDUEDATE | V - View | SM30 |
History
| Last changed by/on | SAP | 20030502 |
| SAP Release Created in | 200 |
