Hierarchy
⤷ IS-A-EMM (Application Component) Enhancements to scheduling agreements MM (Outbound)
⤷ ISAUTO_ME (Package) ISAUTO: Purchasing
Basic Data
Data Element | WFSTPRL |
Short Description | Workflow to MRP Controller in Case of Stopped Release |
Data Type
Category of Dictionary Type | D | Domain |
Type of Object Referenced | No Information | |
Domain / Name of Reference Type | XFELD | |
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 | 10 | WF |
Medium | 15 | Workflow |
Long | 25 | Worflow/Stopped Release |
Heading | 2 | WF |
Documentation
Definition
Determines whether the MRP controller should receive a workitem, that is a notification by workflow, when releases are stopped.
Use
If the indicator is set, the MRP controller is informed in the release creation by workflow, if at least one release (for which he is responsible) is stopped.
Dependencies
Using the indicator, you determine whether you want to use the workflow in the release creation report.
So that work items can be created for the relevant MRP controllers, you must carry out specific settings in the workflow basis.
For the standard rule 80000004, for each combination of plant/MRP controller you desire, you must maintain a responsibility. Technically, this means that each plant/MRP controller combination must be assigned a user ID or a PD organizational unit, so that the work item can be created.
This controls who receives the work item in his workflow inbox.
For further information see the SAP Library under SAP Automotive -> Extensions MM scheduling agreements.
History
Last changed by/on | SAP | 20050301 |
SAP Release Created in |