Hierarchy

⤷

⤷

Basic Data
Data Element | STOPGR |
Short Description | Stop Reasons |
Data Type
Category of Dictionary Type | D | Domain |
Type of Object Referenced | No Information | |
Domain / Name of Reference Type | STOPGR | |
Data Type | CHAR | Character String |
Length | 2 | |
Decimal Places | 0 | |
Output Length | 2 | |
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 | 0 | |
Medium | 0 | |
Long | 0 | |
Heading | 0 |
Documentation
Definition
Indicates why a scheduling agreement release was stopped at the time of release creation.
Use
An SA release can be stopped either statically or dynamically.
You make forecast and/or JIT delivery schedules subject to static stopping by setting the Activate stop indicator in the additional data of the scheduling agreement item.
You define the criteria for dynamic stopping in the release creation profile that you assign to the scheduling agreement item.
Possible stop reasons include the following:
@F1@ Tolerance violation 1st check interval
@F1@ Tolerance violation 2nd check interval
@F1@ Tolerance violation 3rd check interval
@4F@ Follow-up material relevant
Note
@00@ indicates in the list of stopped SA releases, that these criteria did not lead to the stop of the SA release
History
Last changed by/on | SAP | 20050301 |
SAP Release Created in | 46C |