Hierarchy
⤷ IS-M (Application Component) SAP Media
⤷ JSD (Package) Appl. dev. R/3 Publishing Sales and Distribution System
Basic Data
Data Element | ISM_DATE_RESTORE |
Short Description | IS-M/SD: Date on which IAC Entry Updates Reactivated |
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 | React.Date |
Medium | 15 | Date IAC React. |
Long | 25 | Date IAC Reactivated |
Heading | 10 | React.Date |
Documentation
Definition
If you use the Internet Application Components (IACs) from Periodical Sales and Distribution and direct changes to objects are allowed, this means that changes to orders can theoretically occur at any time of the day or night. This may mean that regenerative planning is not possible, since planning is blocked by the IACs.
To prevent this blocking conflict from arising, you can have the program suspend any changes to orders by IACs before planning takes place. To do this, you must change the data target in the Customizing settings for the IACs. All orders and changes are then stored in a temporary table. These orders and changes can be processed later. You have the system restore the original data target setting automatically once planning is complete.
The value stored here indicates the date on which an IAC entry was changed back to its original value with regard to the data target (and therefore the date on which order changes can once again be made directly).
History
Last changed by/on | SAP | 20050224 |
SAP Release Created in |