SAP ABAP Data Element BF_TTZ (Backflush: BOM Explosion by Deadline Technical State Logic)
Hierarchy
☛
SAP_APPL (Software Component) Logistics and Accounting
⤷ LO (Application Component) Logistics - General
⤷ DIMP_STD (Package) Standard Objects of DIMP Industries
⤷ LO (Application Component) Logistics - General
⤷ DIMP_STD (Package) Standard Objects of DIMP Industries
Basic Data
Data Element | BF_TTZ |
Short Description | Backflush: BOM Explosion by Deadline Technical State Logic |
Data Type
Category of Dictionary Type | D | Domain |
Type of Object Referenced | No Information | |
Domain / Name of Reference Type | BF_TTZ | |
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 | DTS Logic |
Medium | 15 | DTS Explosion |
Long | 37 | BOM Explosion by DTS Logic |
Heading | 3 | DTS |
Documentation
Definition
Specifies that the Deadline Technical State (DTS) function should be activated.
Use
If you set this indicator, the system behavior changes when there is a backflush in repetitive manufacturing:
- The backflush (MFBF) takes place with reference to a production version without the user specifying a planned order number.
- The backflush posts the goods issue for the components based on the component list for the planned orders, which are reduced with the backflush.
- This procedure is different from the standard behavior. In the standard, the BOM is exploded with the posting date (posting date of the backflush) or with the revision level of the BOM, which you can enter in transaction MFBF.
Dependencies
The field is only shown if you have activated the DIMP_GENERAL switch.
Example
History
Last changed by/on | SAP | 20100310 |
SAP Release Created in | 46C |