Hierarchy
BBPCRM (Software Component) BBPCRM⤷
CRM (Application Component) Customer Relationship Management⤷
CRM_APPLICATION (Package) All CRM Components Without Special Structure Packages⤷
MG (Package) Application development R/3 material master prior to 3.0
Basic Data
| Data Element | TAKZT |
| Short Description | Takt time |
Data Type
| Category of Dictionary Type | D | Domain |
| Type of Object Referenced | No Information | |
| Domain / Name of Reference Type | DEC3 | |
| Data Type | DEC | Counter or amount field with comma and sign |
| Length | 3 | |
| Decimal Places | 0 | |
| Output Length | 3 | |
| Value Table |
Further Characteristics
| Search Help: Name | ||
| Search Help: Parameters | ||
| Parameter ID | ||
| Default Component name | CYCLE_TIME | |
| Change document | ||
| No Input History | ||
| Basic direction is set to LTR | ||
| No BIDI Filtering |
Field Label
| Length | Field Label | |
| Short | 10 | Takt time |
| Medium | 15 | Takt time |
| Long | 20 | Takt time |
| Heading | 3 | TT |
Documentation
Definition
If a requirement quantity (for example, for capacity reasons) cannot be procured in a single lot, you have to schedule several receipts. In conjunction with the overlap indicator in the lot size (set in Customizing for the lot size), you can use the takt time to specify that these receipts are offset, that is, that they are delayed by the takt time.
You enter the takt time in workdays.
Use
The system uses the takt time if a requirement is covered by several receipt elements due to restrictions on lot size such as maximum lot size (with all lot-sizing procedures) or rounding value (with fixed lot size with splitting).
Supplementary Documentation - TAKZT 0001
Dependencies
If no takt time is specified for the production campaign, the takt time defined in the material master is used for determining the basic dates, provided a takt time has been defined in the material master.
History
| Last changed by/on | SAP | 19991108 |
| SAP Release Created in |
