SAP ABAP Data Element TERMKZ (Scheduling type)
Hierarchy
☛
SAP_ABA (Software Component) Cross-Application Component
⤷ CA-GTF-PS (Application Component) Cross-Application Objects in Project System
⤷ BC (Package) Cross-Application Objects PP/PS
⤷ CA-GTF-PS (Application Component) Cross-Application Objects in Project System
⤷ BC (Package) Cross-Application Objects PP/PS
Basic Data
Data Element | TERMKZ |
Short Description | Scheduling type |
Data Type
Category of Dictionary Type | D | Domain |
Type of Object Referenced | No Information | |
Domain / Name of Reference Type | TERART | |
Data Type | CHAR | Character String |
Length | 1 | |
Decimal Places | 0 | |
Output Length | 1 | |
Value Table | T482 |
Further Characteristics
Search Help: Name | ||
Search Help: Parameters | ||
Parameter ID | ||
Default Component name | SCHED_TYPE | |
Change document | ||
No Input History | ||
Basic direction is set to LTR | ||
No BIDI Filtering |
Field Label
Length | Field Label | |
Short | 10 | SchedType |
Medium | 15 | Scheduling type |
Long | 20 | Scheduling type |
Heading | 2 | ST |
Documentation
Definition
Key which specifies the scheduling type for detailed scheduling.
Note
With production-rate and rough-cut scheduling backward scheduling is always used.
Supplementary Documentation - TERMKZ 0001
Use
Via the scheduling type you can control, how the production order should be scheduled (for example forward, backward).
Dependencies
The scheduling type determines, which dates you must enter:
- If the system schedules forward, you must enter the order start date.
- If you schedule backward, you must enter the order finish date.
Supplementary Documentation - TERMKZ 2120
Procedure
If you maintain a key for forward scheduling or backward scheduling note the following:
- with forward scheduling you must maintain a basic start date for the network
- with backward scheduling you must maintain a basic finish date for the network
History
Last changed by/on | SAP | 19990629 |
SAP Release Created in |