Hierarchy
⤷
⤷
Basic Data
| Data Element | RKTIO |
| Short Description | Response on reaching release order value in value contract |
Data Type
| Category of Dictionary Type | D | Domain |
| Type of Object Referenced | No Information | |
| Domain / Name of Reference Type | RKTIO | |
| Data Type | CHAR | Character String |
| Length | 1 | |
| Decimal Places | 0 | |
| Output Length | 1 | |
| 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 | 8 | Response |
| Medium | 8 | Response |
| Long | 38 | Contract release control |
| Heading | 38 | Response rule in value contract rel. |
Documentation
Definition
This indicator controls how the system reacts when the value of your release order for a value contract item reaches or exceeds the open target value of the value contract item.
The following settings are available:
- ´ ´ No response if target value is exceeded
- A Warning if target value is exceeded
- B Error message if target value is exceeded
- C First time target value is exceeded, permitted with warning
- D As for 'A' but value contract is not blocked
The following lock logic takes place if you activate D or leave the field blank (No response if target value is exceeded):
If the source document is being processed itself, you cannot create a release order (for example, you cannot create a release order for a value contract while someone else is processing it).
Note:
Because the value contract is not blocked when a release order exceeds the target value, the system does not issue a warning if several release orders are created for the same contract at once.
Example:
Release order A and B are created at the same time. Key D has been activated in Customizing. Individually, neither release A or B exceed the target value of the value contract but together, their combined value does. However, a warning did not appear because they were created at the same time, so both releases can be activated and the value contract is not blocked.
History
| Last changed by/on | SAP | 19970812 |
| SAP Release Created in | 470 |