Hierarchy
SAP_APPL (Software Component) Logistics and Accounting⤷
MM-PUR-PO (Application Component) Purchase Orders⤷
WIND (Package) Document index processing
Basic Data
| Data Element | B_KAEDT |
| Short Description | Date condition changed |
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 | Chg. date |
| Medium | 15 | Cond. chg. date |
| Long | 20 | Cond. change date |
| Heading | 14 | Cond. chg. dt. |
Documentation
Definition
Date on which the condition was changed.
Use
This date is used to limit the selection of change pointers for condition changes that are to be processed while worklists are created for dopcument adjustments (see example). A single date or a time interval can be entered for the validity date.
Example
The examples show the possible order in time of the days in which the condition changes were made for the validity date entered here.
Case 1: Entry of a single date
Date entry: 1.7.2002
|
Date of change 1-3: | | |
1.5. 1.7. 1.9.
Only the change made on 1.7.2002 is included.
Case 2: Entry of an interval
1.6. 31.8.
Date entry: |----------------------|
Date of change 1-4: | | | |
1.5. 1.7. 1.8. 1.10.
Only changes "2" from 1.7. and "3" from 1.8. are included.
Supplementary Documentation - B_KAEDT 0001
Use
You can limit the automatic document adjustment process to condition changes that have taken place within a certain time period.
History
| Last changed by/on | SAP | 19971109 |
| SAP Release Created in |
