Dates

Unit Overview

In this unit you learn about functions for manual and automatic planning of dates in work breakdown structures and networks. In doing so, the various Customizing settings and influential factors for scheduling are also dealt with in detail. At the end of this unit, creation of actual dates, the necessary prerequisites for this and the influence on scheduling of actual dates are discussed.

Unit Objectives

After completing this unit, you will be able to:

• Schedule dates for WBS elements using the project planning board • Perform scheduling with the aid of the project planning board • Set the relevant tables in Customizing

• Enter actual dates for WBS elements and activities

Unit Contents

Lesson: Time Scheduling with WBS Elements ... 28 Lesson: Scheduling of Activities and Networks ... 32 Exercise 2: Scheduling ... 53 Lesson: Actual Dates... 66 Exercise 3: Actual Dates from Confirmations... 71

I n t e r n a l U s e S A P P a r t n e r O n l y

Lesson: Time Scheduling with WBS Elements

Lesson Overview

This lesson focuses on time scheduling with WBS elements You will learn about various functions that support you in time scheduling for work breakdown plans.

Lesson Objectives

After completing this lesson, you will be able to:

• Schedule dates for WBS elements using the project planning board

Business Example

Start by familiarizing yourself with the options for planning dates only for WBS elements. Take a look at how to use planning methods to simplify time scheduling.

I n t e r n a l U s e S A P P a r t n e r O n l y

The following functions are available to you:

• Sets of dates: Basic and forecast dates can be used as planned dates. Actual dates are also shown here.

• Check dates: You can check consistency of the dates within the project structure with or without taking activities into account.

• Inherit: Dates within the WBS can be inherited.

• Extrapolate: You can use the extrapolate function to calculate the dates for higher-level WBS elements.

• Shift: You can shift all of the planned dates for the WBS elements or just the dates in subhierarchies.

• Planning different calendars: You can use a different factory calendar for each activity or WBS element.

• Scheduling: The scheduling function calculates the dates for activities and networks.

• Planning form: You can use the planning form to extrapolate dates automatically - for example, when you save your data.

I n t e r n a l U s e S A P P a r t n e r O n l y

Basic Date Planning with WBS Elements

Figure 12: Basic Dates WBS

In projects without networks, dates can be planned manually for the WBS elements (basic dates).

You can use the project planning board to plan basic dates for the WBS elements simply by dragging your mouse. You can plan these dates in the form of a table in Structure Planning.

Basic dates can be extrapolated from lower to higher-level WBS elements or, conversely, inherited from higher to lower-level WBS elements. You can check the consistency of your scheduling data within the WBS structure.

In the execution phase, you can enter actual dates by dragging your mouse. In the project planning board or the information system, you can compare the actual dates with the planned basic dates.

I n t e r n a l U s e S A P P a r t n e r O n l y

Lesson Summary

You should now be able to:

I n t e r n a l U s e S A P P a r t n e r O n l y

Lesson: Scheduling of Activities and Networks

Lesson Overview

In this lesson you will become familiar with various aspects of network scheduling. The lesson also deals with dates for objects assigned to network activities such as milestones and material components as well as date exchange with WBS elements.

Lesson Objectives

After completing this lesson, you will be able to:

• Perform scheduling with the aid of the project planning board • Set the relevant tables in Customizing

Business Example

You have already created a project structure to produce a turbine. The project manager now wants to know whether the project can be completed on time. Schedule your project to find out the answer.

Introduction

I n t e r n a l U s e S A P P a r t n e r O n l y

Figure 14: Scheduling

Each time a network is scheduled, the system carries out forward and backward scheduling; determines floats and capacity requirements (if activated).

• Forward scheduling determines the earliest dates. • Backward scheduling determines the latest dates.

Floats occur if the earliest dates are different from the latest dates. The scheduling results:

• Scheduled start and finish for the network header

• Earliest start and finish dates (earliest dates) and latest start and finish dates (latest dates) for the activities

• Earliest and latest dates for the relationships • Reduction levels used to schedule the network • Float times (total and free float) for the activities • Capacity requirements for activities

I n t e r n a l U s e S A P P a r t n e r O n l y

Figure 15: WBS / Overall Network Scheduling

You can schedule networks individually (network scheduling). You can schedule all networks linked by relationships together (scheduling of overall network). You can also trigger network scheduling from WBS elements (WBS scheduling).

The activity data, relationships between the activities and date restrictions form the basis for determining dates automatically (scheduling).

As of Release 4.6A you can schedule maintenance orders from the Project System. In the Project Scheduling and Overall Network Scheduling transactions, you can specify whether networks are scheduled together with maintenance orders that have been assigned as subnetworks.

You can display an overview of the maintenance orders assigned to a project in the project planning board.

I n t e r n a l U s e S A P P a r t n e r O n l y

Scheduling Scenarios

Figure 16: Bottom-Up Scenario

In projects with assigned networks, you can use scheduling to derive the dates of the activities and WBS elements automatically.

Using the project planning board, you can select WBS elements and schedule the activities assigned to them. The scheduling parameters determine how the activities are scheduled.

Networks are always scheduled forwards and backwards. The scheduling type determines the original direction in which scheduling is carried out. The system determines the earliest dates of the activities by means of forward scheduling and the latest dates by backward scheduling.

The differences between the earliest and latest dates of an activity are referred to as floats. If these are less than or equal to zero, the activity is termed “critical”.

The dates of the assigned activities are summarized to give the scheduled dates of the WBS elements (thin time bars in the project planning board).

The dates scheduled in the WBS structure can be copied to the basic dates of the WBS elements for the purpose of extrapolating them up the project hierarchy.

I n t e r n a l U s e S A P P a r t n e r O n l y

Figure 17: Top-Down Scenario

In work breakdown structures with assigned networks, you can plan basic dates for the WBS elements in order to specify that a certain part of the project has to be completed within a fixed time period.

You can use the “Top-Down” scheduling scenario or suitable scheduling parameters to stipulate that activities be scheduled within these time constraints: deselect the Network determines scheduling and Adjust basic dates indicators.

I n t e r n a l U s e S A P P a r t n e r O n l y

Figure 18: Scheduling Scenarios

As of Release 4.6, you have the option of using predefined scheduling scenarios. The standard scheduling options are of course still available. Depending on the transaction from which you trigger the scheduling, you use either the “Parameters for WBS scheduling” table or “Scheduling parameters for the network type”.

Caution: The scheduling result depends on the transaction from which you

I n t e r n a l U s e S A P P a r t n e r O n l y

Customizing in Time Scheduling

Figure 19: Customizing for Scheduling 1

Scheduling types are used both for network scheduling and for WBS scheduling. The indicators have the following meanings: Forward: Forward scheduling is carried out first, followed by backward scheduling. Backward: Backward scheduling is carried out first, followed by forward scheduling. Cap.requirements only: No scheduling is carried out at all. Instead, the start and finish dates of the network header are copied to each activity. Today’s date: Backward scheduling is carried out first, followed by forward scheduling starting from today’s date. Basic dates with times: This indicator is not relevant for networks.

Scheduling parameters are created for specific plants and network types. The scheduling parameters determine scheduling, for example, in the transactions network maintenance (CN22) and scheduling of the overall network (CN24). The indicators have the following meanings: Adjust basic dates: Determines that the scheduled dates are copied to the basic dates of the network header after a scheduling run. The settings for secondary requirements do not have any impact in the network. Scheduling type:

I n t e r n a l U s e S A P P a r t n e r O n l y

the system deals with partially-confirmed activities during scheduling (see below). Latest material dates: The requirements dates for a material are determined based on the earliest or latest date. Reduction type: Either all activities or only those along the critical path are reduced. Maximum reduction level: A reduction strategy can have up to six levels. The highest level of reduction is specified here. Rescheduling: Determines how the system deals with work allocated in “workforce planning” after another scheduling run has been carried out.

Figure 20: Customizing for Scheduling 2

The profile for WBS scheduling is used for scheduling in the project planning board transaction CJ2B or in the project scheduling transaction (CJ29).

The indicators have the following meanings: Scheduling type: Determines the type of scheduling, for example, forward first, then backward. Start in the past: Determines how long ago (in days) the start date can be. If it is more than the specified number of days, scheduling is carried out for today’s date. Scheduling form: Specifies which object - network header or WBS element - is used as a basis for scheduling. Adjust basic dates: Determines that the scheduled dates are copied to the basic dates of the WBS elements after a scheduling run. Log automatic: If a log is generated, it is displayed automatically. Shift order: Determines how the system deals with partially-confirmed activities during scheduling (see below). Schedule when saving: Scheduling is carried out on saving. Latest material dates: The requirements dates for a material are determined based on the earliest or latest date. Maximum reduction level: A reduction strategy can have up to six levels. The highest level of reduction is specified here. Reduction type: Either all activities or only those along the critical

I n t e r n a l U s e S A P P a r t n e r O n l y

Other Influencing Factors in Scheduling

Figure 21: Scheduling: Duration

When scheduling internally-processed activities and general costs activities, the system uses the normal duration you maintained in the activity. The duration can be calculated from the work planned, provided you have stored a formula for calculating the duration from internal processing in the work center.

When scheduling externally-processed activities, the system uses the number of planned delivery days you maintained for an external activity. You can, however, also use the normal duration from the internal processing screen of the external activity if you activate this explicitly in the control key of the external activity.

Scheduling interprets the time interval for relationships as the minimum time interval. When calculating the dates, scheduling can increase the time interval but not reduce it. You can maintain a work center in internally and externally processed activities and in relationships. The following information is stored for scheduling in the work center: • Formulas for calculating the duration of activities.

I n t e r n a l U s e S A P P a r t n e r O n l y

Figure 22: Control Key

The control keys for activities are set in Customizing using transaction OPSU. The control key indicators function as follows: Schedule: Activities and activity elements are scheduled. For activity elements, the dates for the activity are determined. Det. cap. req.: Capacity requirements are determined for activities and activity elements. The capacity requirements are determined using the scheduling results. Therefore, only set this indicator if you also set the scheduling indicator. Costs act.: This indicator specifies that you use the control key for general costs activities. Costing: This indicator determines that activities and activity elements are taken into account in costing. Print time ticket: This determines whether time tickets can be printed. Time tickets are only printed if the Print indicator is also selected. For information on further relationships, see the online help. Confirmation: Determines whether activities and activity elements can be confirmed. External proc.: Determines whether activities and activity elements are processed internally or externally. Service: Determines whether services can be planned for activities and activity elements. Only set this indicator if you select the External proc. indicator to allow external processing. Print conf.: This determines whether completion confirmation slips can be printed. Completion confirmation slips are only printed if the Print indicator is also selected. For information on further relationships, see the online help. Print: Determines whether work papers such as time tickets, completion confirmation slips can be printed. For information on other relationships, see the online help. Sch.ext.proc.: Determines whether activities are to be scheduled in line with the Planned delivery time or Normal duration.

I n t e r n a l U s e S A P P a r t n e r O n l y

Figure 23: Relationships

Relationships determine the chronological sequence of the individual activities in a network (or standard network). You can enter additional data (such as a time interval or reference to a particular factory calendar) in the detail screen for each relationship. The network graphic enables you to represent relationships in a “time-dependent” manner to display the logical sequence. All relationships in the network graphic are displayed as FS relationships by default.

I n t e r n a l U s e S A P P a r t n e r O n l y

Scheduling Example

Figure 24: Example of Scheduling

A network is always scheduled forwards and backwards. The scheduling type specifies whether forward scheduling or backward scheduling is carried out first. Forward scheduling calculates the earliest start and finish dates for the activities. All activities that do not have predecessors are start activities. The scheduling start start date is the start date in the network header or the start date determined from backward scheduling.

Backward scheduling calculates the latest start and finish dates for all the activities. Target activities are network activities that do not have successors. The scheduling start date is the finish date in the network header or the finish date determined from forward scheduling.

In the example above, the start dates are set to the beginning of the day (00:00) and the finish dates to the end of the day (24:00). If work centers are entered for the activities, the start and finish dates are within the operating time of the work centers affected.

I n t e r n a l U s e S A P P a r t n e r O n l y

Figure 25: Total Float, Free Float

Legend:

ES= Earliest Start EF= Earliest Finish

LS= Latest Start LF= Latest Finish

TF= Total Float FF= Free Float

Floats supply information on the time reserves available for individual activities. You can use the floats calculated in scheduling, for example in capacity leveling, to shift activities between the earliest and latest dates or to extend their duration.

A total float is the difference between the latest start and earliest start (LS - ES) or between latest finish and earliest finish (LF - EF).

A free float is the difference between the earliest start of a successor activity and the earliest finish of the activity in question (ES successor - EF activity). Since the successors for the free float are within their earliest dates, the time reserve is fully available to the current activity.

I n t e r n a l U s e S A P P a r t n e r O n l y

Figure 26: Example of Floats

This slide describes how total floats and free floats are calculated.

The total float of activity 40 can be calculated from the difference between the earliest and latest start of an activity:

Day 6 (0:00) - Day 5 (0:00) = 1 day.

The free float of activity 40 can be calculated from the difference between the earliest start of the successor (activity 50) and the earliest finish of the activity.

I n t e r n a l U s e S A P P a r t n e r O n l y

Time Constraints and Reductions

Figure 27: Time Constraints

You can maintain constraints for the start and finish of activities. Constraints can be relevant for both the earliest and the latest dates. You can maintain constraints for basic and forecast date sets.

I n t e r n a l U s e S A P P a r t n e r O n l y

Figure 28: Reduction

You can use reduction if the time period within which the activities are to be scheduled is not long enough to process all activities. This allows you to reduce the scheduled duration of internally-processed activities.

Reduction only affects the activities for which a reduction strategy has been stored. At the most, the system reduces as far as the level of reduction strategy entered in the network header.

During scheduling, the system determines one reduction level for each activity. For example: The system calculates the earliest dates and determines reduction level 2 for an activity. This reduction level is transferred to the latest dates.

Important: Remember to be careful when using the reduction function as the system does not know whether the duration of an activity can be reduced. It does not carry out plausibility checks or check available capacities.

You can use reduction strategies to control how an activity’s lead time can be reduced in levels. You can enter a reduction strategy in each activity.

You can define up to six reduction levels for each reduction strategy. You can enter by what percent you want to reduce for each reduction level.

I n t e r n a l U s e S A P P a r t n e r O n l y

Scheduling of the Overall Network

Figure 29: Scheduling of the Overall Network

The confirmed delivery date of an item in the sales order corresponds to the finish date of the assigned network. If the end of a network is shifted because of scheduling problems, the confirmed delivery date in the sales order is changed automatically. You can, however, also fix a confirmed delivery date for the item on the Schedule lines tab page.

As of Release 4.0, scheduling of the overall network for the sales order item can be started in the sales order itself.

This function schedules both the network assigned to the sales order item and all other networks linked to this network via a relationship.

I n t e r n a l U s e S A P P a r t n e r O n l y

Figure 30: Overall Network Scheduling with Selection Options

As well as overall network scheduling (transaction CN24), which you can use to schedule several networks and subnetworks together, you also have at your disposal, from ECC 5.0 onwards, the new function overall network scheduling with selection options (transaction CN24N).

You use this function along with suitable selection criteria to specify which networks and subnetworks are to be taken into account as part of overall network scheduling. You can display additional information on the selected activities and subnetworks on a monitor and jump to the next screen to processing or confirmation of activities. A prerequisite for the use of the Overall network scheduling with selection options function is that you have defined suitable levels beforehand in Customizing for the project system and have assigned network types and number intervals. Note that you can only schedule using two levels.

By using a BAdI for Overall scheduling with selection options, you have other functions at your disposal such as control of data exchange between activities and assigned subnetworks.

I n t e r n a l U s e S A P P a r t n e r O n l y

Figure 31: Subnetwork Monitor

Dates of Assigned Objects

Figure 32: Dates: Activity Elements

I n t e r n a l U s e S A P P a r t n e r O n l y

Figure 33: Requirements Date: Material

The system calculates the requirements date for components with reference to the start or finish date of the activity. You can use the Scheduling parameters for network type or the Parameters for WBS scheduling to control whether the earliest or latest start date is used as the requirements date. The transaction used to trigger the scheduling determines which of the two tables is used. If you schedule within the network or

In document PLM220 - Project Management..Logistics (Page 35-89)