Hierarchy
⤷
⤷
Basic Data
| Data Element | PSOBT_FROM |
| Short Description | Assignment Account to Summzns (PSO26) Valid from Posting Day |
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 from |
| Medium | 15 | Valid from |
| Long | 20 | Valid from |
| Heading | 11 | Valid from |
Documentation
Definition
From-date of the validity period of an assignment from G/L account to summarization key. The from-date and the to-date define the validity period of the assignment of a G/L account to a summarization key. If you do not enter a from- or to-date, the validity is unrestricted in the past and in the future.
Use
In day-end closing, the assignment of the G/L accounts to the summarization keys is determined in accordance with the current posting day. A summarization key is not taken into account if there is no valid assignment to a G/L account for the current posting day. Validity is taken into account in the display of completed posting days.
Dependencies
The following rules apply for validity periods:
- No Overlap:
If a G/L account is assigned to more than one summarization key, the validity periods in the different summarization keys cannot overlap.
- Correct Assignment:
For a payment-relevant G/L account, each posting day on which the account can be posted must be in the validity period of a summarization key.
History
| Last changed by/on | SAP | 20041006 |
| SAP Release Created in | 600 |