Hierarchy
⤷ CRM (Application Component) Customer Relationship Management
⤷ CRM_APPLICATION (Package) All CRM Components Without Special Structure Packages
⤷ CX (Package) R/3 Application development: R/3 Scheduling
Basic Data
Data Element | DADJ1 |
Short Description | Scheduling level for adjusting basic dates |
Data Type
Category of Dictionary Type | D | Domain |
Type of Object Referenced | No Information | |
Domain / Name of Reference Type | DADJ1 | |
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 | SchedLvlBD |
Medium | 15 | SchedLvlBD |
Long | 25 | Sched level f.bas. dates |
Heading | 10 | SchedLvlBD |
Documentation
Definition
Determines which scheduling (detailed scheduling or rate-based scheduling) level is used for adjusting the basic dates when you carry out lead time scheduling or dispatching within capacity planning.
Use
You can set up the system so that the basic dates are automatically adjusted, if after lead time scheduling using lead times, floats and the original basic dates, the new dates do not agree with the original basic dates.
You determine if and how basic dates and dependent requirement dates are adjusted in lead time scheduling and during dispatching within capacity planning by using Adjust sched. and Dispch.pl.ords .
Dependencies
If you set the scheduling based on takts indicator, scheduling based on takts in Sequencing determines the planned order dates:
- Dates that have been determined by lead time scheduling are not overwritten by scheduling based on takts.
- The basic dates for planned orders that are determined in scheduling based on takts are not adjusted in lead time scheduling or finite scheduling. The stem automatically makes the requisite settings in the date adjustment screen section.
Example
You have determined which scheduling level is to be used for adjusting basic dates and activated scheduling adjustment. You have chosen backward scheduling. The Scheduling based on takts indicator has not been set.
In lead time scheduling the production start date is calculated starting from the basic end date in the planned order header. To do so, the float times and the times of each operation are subtracted from the basic finish date. This production start time is then compared with the basic start date in the planned order header. A new basic start date is calculated and transfered to the planned order header. The following situations can occur:
- The production start date is on or after the basic start date.
The new basic start date is calculated by subtracting the float before production from the production start date.
- The production start date is before the basic start date.
In this case, reduction measures are applied, if applicable, to fit the the production start date into the period defined by the basic dates. To calculate the new basic start date, the (possibly reduced) float before production is substracted from production start date (which was possibly shifted due to the reduction measures).
Note
- If during backward (forward) scheduling you only enter a basic finish (start) date in the planned order header, the basic start (finish) date is calculated using the in-house production time from the material master.
- In planned orders the basic finish date can only be adjusted for dispatching within capacity planning, not for lead time scheduling.
History
Last changed by/on | SAP | 19980728 |
SAP Release Created in |