Hierarchy
BBPCRM (Software Component) BBPCRM⤷
FI-FM-PO (Application Component) Postings⤷
FMRE (Package) Funds Management: Earmarked Funds
Basic Data
| Data Element | DATU |
| Short Description | Date of last revaluation |
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 | Reval.date |
| Medium | 15 | Reval.date |
| Long | 20 | Revaluation date |
| Heading | 0 |
Documentation
Definition
Revaluation date used as the translation date for the exchange rate table.
Supplementary Documentation - DATUB 0001
Procedure
If you want to display the BOM
- for a specific date, set the delete character "!" here. The system sets the valid from date as the cutoff date for validity.
- for a specific time interval, enter the valid to date as well as the valid from date.
If you enter a valid from date which is before the valid from date, the system ignores your entry. - for its entire period of validity, delete the valid from date by entering "!" at the beginning of the field.
- as it relates to a change number, the system determines the date automatically.
Supplementary Documentation - DATUB 0002
Dependencies
The maximum valid to date is programmed as the 31.12.9999.
If the valid to date is changed with history
- the validity period is divided up into shorter periods
- the valid to date is determined by the program
the point in time defined as the start of the next validity period is at the same time the end of the current period.
Supplementary Documentation - DATUB 0006
Use
If you want to display the where-used list
- for a specific date, do not make an entry here
- for a specific time period, enter a valid-to date as well as the valid-from date
- for its entire period of validity, delete the valid-from date by entering "!" at the beginning of the field, and do not make an entry
- up to a specific date, delete the valid-from date by entering "!" at the beginning of the field and enter a valid-to date
Supplementary Documentation - DATUB 0007
Use
The valid to date determines the date up to which PP calendar periods are to be calculated by the system.
Supplementary Documentation - DATUB 0008
Use
If you want to display a where-used list for the document:
- on a particular date, enter the date here.
- within a particular time period, enter both the valid-from date and the valid-to date.
- over its entire validity period, delete the valid-from date using the delete character "!" and do not enter a valid-to date.
- up to a particular date, delete the valid-from date using the delete character "!", and enter a valid-to date.
Dependencies
In Customizing (Bills of material), you define whether the current date or the system low date is used as a default valid-from date.
Supplementary Documentation - DATUB 0009
Use
If you want to see where the class is used:
- on a particular date, enter the date here
- within a particular time period, enter both a valid-from date and a valid-to date
- over its entire validity period, delete the valid-from date using the delete character "!" and do not enter a valid-to date
- up to a particular date, delete the valid-from date using the delete character "!" and enter a valid-to date
Dependencies
In Customizing (Bills of material), you define whether the current date or the system low date is the default valid-from date.
Supplementary Documentation - DATUB 0040
Use
This date is determined by the system.
Examples
It an item is changed with reference to a change number, the valid-from date of the change master automatically becomes the valid-to date of the previous validity period.
Supplementary Documentation - DATUB 4220
Supplementary Documentation - DATUM1 0001
Use
You can use report RPRDUR00 to select employees who have been on business trips for a specific number of days by making entries in the Interval duration and Day limit fields.
This report also takes into account business trips before the period in question by the number of days specified as the interval duration (also read the documentation on report RPRDUR00).
Procedure
Examples
Dependencies
Supplementary Documentation - DATUM2 0001
Use
You can use report RPRDUR00 to select employees who have been on business trips for a specific number of days by making entries in the Interval duration and Day limit fields.
Procedure
Examples
Dependencies
Supplementary Documentation - DATUV 0000
Use
The system determines this date from the change master record.
Supplementary Documentation - DATUV 0001
Procedure
If you enter a change number or a revision level, the system copies the valid-from date from the change master record.
- For bills of material, the current date is proposed as a default, unless you have defined in the IMG (BOM) that the system low date (01.01.1970) is the default.
- If you remove the valid-from date, the object is displayed over its full validity period. To do this, enter the delete character "!" at the beginning of the field.
Supplementary Documentation - DATUV 0002
Dependencies
The system determines the valid-from date from the change master record. This is usually the valid-from date of the change header. If the object is allocated to an alternative date, the alternative date is copied.
Supplementary Documentation - DATUV 0003
Use
The system selects all items which are valid on this date in the alternative you selected.
Dependencies
In the IMG for production (BOM), you define whether the current date or the system low date is the default.
If you change the bill of material with reference to a change number or revision level, the system determines the date from the relevant change master record.
Supplementary Documentation - DATUV 0004
Use
Procedure
If you only enter one date, the validity period is infinite. If you maintain different validity periods with different alternatives for a material, each validity period lasts until the start of the next validity period.
Examples
Dependencies
Supplementary Documentation - DATUV 0005
Use
All changes that you enter for this change number are valid as of this date.
Exception:
If a change object is allocated to an alternative date, the valid-from date of the alternative date determines when the change takes effect.
Supplementary Documentation - DATUV 0006
Procedure
If you want to display the where-used list for a material:
- on a specific date, enter the date here.
- over a specific time period, enter the valid-to date as well as the valid-from date
- over its entire validity period, remove the valid-from date with the delete character "!" and do not enter a valid-to date.
- up to a specific date, remove the valid-from date with the delete character "!" and enter a valid-to date
Dependencies
You define the default date (current date or system low date) in the IMG (BOM).
Supplementary Documentation - DATUV 0007
Use
The valid from data determines from which date PPS calendar periods are calculated by the system.
Supplementary Documentation - DATUV 0008
Use
If you want to display a where-used list for the class:
- for a particular date, enter the date here.
- within a particular time period, enter both the valid-from date and the valid-to date.
- over its entire validity period, delete the valid-from date by entering the delete character "!" and do not enter a valid-to date.
- up to a particular date, delete the valid-from date by entering the delete character "!" and enter a valid-to date.
Dependencies
Settings in Customizing (Bills of material) determine whether the current date or the system low date is used as the default valid-from date.
Supplementary Documentation - DATUV 0009
Use
If you want to display a where-used list for the class:
- on a particular date, enter the date here
- within a particular time period, enter both a valid-from date and a valid-to date
- over its entire validity period, delete the valid-from date by entering the delete character "!" and do not enter a valid-to date
- up to a particular date, delete the valid-from date by entering the delete character "!" and enter a valid-to date
Dependencies
Settings in Customizing (Bills of material) determine whether the current date or the system low date is taken as the default valid-from date.
Supplementary Documentation - DATUV 0011
Use
Procedure
Examples
Dependencies
- Unless the change object is allocated to an alternative date, the system determines the valid-from date from the change master header.
- If the change object is allocated to an alternative date, the system determines the valid-from date from this alternative date.
Supplementary Documentation - DATUV 0015
Use
The system determines this date from the change master record.
Supplementary Documentation - DATUV 0040
Use
This date is determined automatically by the system.
Supplementary Documentation - DATUV 0045
Dependencies
The system determines the valid-from date from the header of the change master record.
If the material has been assigned to an alternative date in the change master record, the system takes this specific date as the start date of the revision level.
Supplementary Documentation - DATUV 0131
Use
This specific valid-from date replaces the valid-from date in the change master header. You can use it to define the start of the validity period for individual objects.
Supplementary Documentation - DATUV 0700
Definition
Earliest date on which you can use the dataset to generate a batch input session.
Procedure
Examples
Dependencies
Supplementary Documentation - DATUV 1000
Use
End date for the validity of an object (such as material, BOM, or task list) in the SAP R/3 System.
Supplementary Documentation - DATUV 4220
Supplementary Documentation - DATUV_NARB0400
Definition
Date for which the system searches for valid process instructions that are not flagged for deletion.
History
| Last changed by/on | SAP | 20010720 |
| SAP Release Created in |
