Hierarchy
⤷
⤷
⤷
Basic Data
| Data Element | VVIS_DBERBIS |
| Short Description | 'Calculation to' Date |
Data Type
| Category of Dictionary Type | D | Domain |
| Type of Object Referenced | No Information | |
| Domain / Name of Reference Type | DATUM | |
| Data Type | DATS | Date field (YYYYMMDD) stored as char(8) |
| Length | 8 | |
| Decimal Places | 0 | |
| Output Length | 10 | |
| Value Table |
Further Characteristics
| Search Help: Name | ||
| Search Help: Parameters | ||
| Parameter ID | ||
| Default Component name | ||
| Change document | ||
| No Input History | ||
| Basic direction is set to LTR | ||
| No BIDI Filtering |
Field Label
| Length | Field Label | |
| Short | 10 | Calc.upto |
| Medium | 15 | Calcul. upto |
| Long | 20 | Calculation To |
| Heading | 10 | Calc. upto |
Documentation
Definition
In the cash flow you can find out which calculation period (calculation date from - to) each item is based on.
For periodic postings you can use the 'Calculation upto' date as an additional selection criterion for cash flow items. Since follow-up postings, which always result from a backdated condition change, are always given the calculation period of the original item, you can use this field to group follow-up postings in a separate posting run.
Example:
You have carried out the periodic posting for January 2000, and have correctly posted all items. Now a backdated change has been made to the conditions and the due date for follow-up postings is 02/01/2000. A new item for follow-up postings with the calculation period 01/01/2000 - 01/31/2000 is created in the cash flow.
This new follow-up item is usually selected and posted according to due date during the following debit position. However, if you want to post the follow-up items in a separate run from the February items, start an additional posting run before the regular periodic posting for February, limiting the 'Calculation upto' date to 01/31/2000.
History
| Last changed by/on | SAP | 19990520 |
| SAP Release Created in |