Hierarchy

⤷

⤷

Basic Data
Data Element | PSOBVALDT_PS |
Short Description | Validity Date for Contract Objects |
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 | Valid on |
Medium | 15 | Valid on |
Long | 20 | Validity Date |
Heading | 10 | Valid on |
Documentation
Definition
Date, which the current master data parameters refer to.
Use
The master data changes you made to a contract object on the current system date take immediate effect. However, if you want to activate the changes you made in the future, then enter the date on which the changes should become active here.
Note:
You can only call contract object data from the past in display mode
Dependencies
The master data changes entered for the future are saved as change documents. The changes are not activated automatically by the system on the defined date, you must trigger them under Contract Accounts Receivable and Payable -> Periodic Processing-> For Contract Objects -> Activate Planned Changes.
Example
The control which changes the contract object active payment data on a contract partner because this will change the bank. In the field Validity Date you enter the date from which the payment parameters of the new bank are valid, define the settings on the Payment Data tab page and save your entries.
History
Last changed by/on | SAP | 20050224 |
SAP Release Created in | 464 |