Hierarchy
⤷ PP-REM (Application Component) Repetitive Manufacturing
⤷ MD04 (Package) Repetitive Manufacturing
Basic Data
Data Element | SA_PZPKT1 |
Short Description | Subs.posting of processes at time "immed. in update task" |
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 | Time "1" |
Medium | 15 | Time "1" |
Long | 36 | Sub.posting of processes at time "1" |
Heading | 10 | Time "1" |
Documentation
Definition
If this field is selected, the system includes the backflushes that should have been carried out at time "1" ("immediately in the update task") when subsequently posting the backflushing processes. This time is defined in Customizing for Repetitive Manufacturing ("Define Backflushing Processes"). However, it can also be overwritten in the backflush.
In a separated backflush with option, "immediately in update task", the processing of the goods issues and/or production activities are immediately transferred to the update task. This means that the user can immediately continue working online. The separated processes are usually processed independently in the update task and no further steps have to be taken to complete the separated processes.
In exceptional cases, an assembly may be locked. Then the separated processes cannot be carried out immediately in the update task. The backflush remains in the work list and has to be processed using the transaction "Separated backflush" or in a Background job. In this case, you have to select the appropriate checkbox.
History
Last changed by/on | SAP | 19990503 |
SAP Release Created in |