Using Control key in SAP PS system, you can determine the business transactions to be performed when you perform an activity. An activity can be an internal activity, external activity or both. While defining the control key, you have to specify the indicators and keys for different functions in the control key. The Access control list function should be activated in project profile or network profile. If a higher authorization applies for a user or PS object, the system overwrites the inherited authorization.
Example Consider user A is assigned to user group 1 that has read authorization for a PS object and the user has change authorization for PS object. The user gets change authorization in this scenario. Creating Access Control List To create an access control list, navigate to the PS object for which you want to assign authorizations. Select insert line button to enter the new data. Cost planning Cost planning means the costs that is expected to incur in connection with your project as it is executed.
In addition, you can perform automatic cost planning to integrate project costs with enterprise controlling. Costing variants are used to define the pricing strategy in the system for costing and how overhead should be determined. Example You determine the price to be considered in accounting view in material master record.
Costing variants are used to maintain unit costing in the general costs activity. Click the save button to save the configured cost variant.
To save the data, click the save button at the top. Select execution profile and double-click on Execution Service icon in the left pane.
To save the Execution service profile, click the save button at the top. Different budget types exist in a Project system. Original Budget In Project system, original budget is defined as the allocated cost assigned for a development order.
You can update the budget using the budget update options. Budget update is known as the unexpected events that occur. You define your own number range for all budget documents created for allocation, supplement, transfer, release, etc. Once you define the tolerance limit, click the save button at the top. Revenue planning defines the revenue you expect when a project is executed.
The use of date scheduling is to determine phases in a project and duration of the phases, critical paths, and events in project schedule. In Work breakdown structures WBS and Network, you enter the dates and these dates can be changed during full project lifecycle. Maintaining Dates in Projects When you define a project in system, you enter the start and the finish dates of the projects.
The dates are calculated for full part of part of project for activities using the scheduling function. You can use WBS element basic dates as basic dates to schedule the activities.
When a network contains few activities that are not assigned to same WBS, they are treated as external networks in system in project scheduling.
Possible options are as shown in the screenshot given below. SAP PS - Material This component is used to plan and manage material requirement in project and to manage the material flow in the project.
Material requirement planning in project comes from Material management and Production Planning and Control. The following planning methods are available: Book. If the time scheduling is not consistent, the project cannot be saved. However, no dates are automatically changed. EE Bottom-up When saving, the system automatically changes the dates of WBS ele- ments and project definition via bottom-up extrapolation.
EE Strict Bottom-up When saving, the system automatically changes the dates of WBS ele- ments and project definition using a strict bottom-up extrapolation. EE Open Planning The system does not automatically check or change the dates. How- ever, you can manually trigger the Check dates within project structure or Extrapolate dates functions.
You specify the planning method to be used separately for the basic and the forecast set of dates in the project definition. In the project profile, you can store default values for the planning methods of both sets of dates. Because the dates of mile- stones are exclusively derived from the scheduled dates, you must run the WBS Scheduling function at least once in this case. For WBS with- out assigned networks, the WBS scheduling only causes the planned dates to be accepted as scheduled dates.
This determination of the planned dates of networks is called scheduling. Depending on the transaction you used to trigger the scheduling, you use network scheduling, overall network schedul- ing, or WBS scheduling. All activities of the network are selected and their dates are calculated. If you use over- all network scheduling, several networks are scheduled at the same time, provided they are linked via relationships or subnetworks.
All activities of these networks are then scheduled. The system now selects only those activities for scheduling that are assigned to the selected WBS elements and calculates their dates. Before we elaborate on more differences between the various schedul- ing methods, we will first describe the scheduling concept, which is the same for all three methods. Beginning with a start date, the system calculates the earliest possible start date for these activities.
Depending on the schedul- ing settings, the start date of forward scheduling can originate from the header of the network or from the assigned WBS elements WBS deter- mines the dates , or be the current date. After the earliest start date of these activities has been determined, the system calculates the earliest possible end date of these activities using the scheduling-relevant duration. Then, the system selects the direct suc- cessors of these activities and calculates their earliest start and end dates.
Each type of relationship see Section 2. Earliest dates The scheduling now goes through all selected activities in a forward direction and calculates their earliest possible start and end dates. For- ward scheduling results in the earliest dates of activities. Starting from an end date — depending Book.
Based on the scheduling-relevant duration of the activities, the latest start dates of these activities are then calculated. The system then goes through the network in a backward direction, fol- Latest dates lowing the relationships, and thus successively calculates the latest pos- sible start and end dates for all selected activities, considering their types of relationship and their durations.
Backward scheduling determines the latest dates of activities. The earliest start date and the latest end date of the network activities are forwarded to the network header as the scheduled dates.
In WBS sched- uling, the activity dates are also indicated in an aggregated fashion as scheduled dates at the level of the assigned WBS elements.
This logic of forward and backward scheduling requires a number of additional notes regarding the various influencing factors that are rel- evant to scheduling.
Without relationships, the result of scheduling in SAP Project System Relationships in would not be a chronological sequence of the activities. The type of scheduling relationship determines how two activities will interact chronologically. If you specified a time interval for a relationship, this will be taken into account during scheduling.
This time interval, however, is only inter- preted as a minimum time interval, that is, the scheduled time interval between predecessor and successor can be longer than the time interval defined in the relationship. If the activities selected for scheduling have relationships to activities that are not scheduled at the same time, these relationships are still taken into account.
If relationships cannot be met, the system issues warnings that you can analyze in a scheduling log. The calculation of the scheduling-relevant duration and the consider- Scheduling- ation of nonworking times depend on the respective activity type; how- relevant duration ever, for all activity types, the control key of the activities must permit scheduling so that a duration unequal to zero is used during the date calculation.
Typi- cally, however, you will store the standard formula SAP in the work center, which references the value of the Normal duration field in the activity. The Unit of the Normal duration field is relevant as well. For example, if you enter a duration of 24 hours, these hours are interpreted as work- ing hours. If the scheduling-relevant capacity of the work center has an operating time of eight hours per day, this results in a scheduling-rele- vant duration of three working days.
If you entered a duration of one day, the system would only use one working day as the scheduling- relevant duration.
Non-working times The scheduling of internally processed activities also considers nonwork- ing times. If you maintained a work center in the activity, the system only uses the working times of the scheduling-relevant capacity of the work center for scheduling.
Start and end dates are only scheduled for working days. The differentiation between working and nonworking days originates from a factory calendar that is determined according to the following priority: 1. Factory calendar in the activity 2. Factory calendar in the work center 3.
Factory calendar of the plant in the activity For externally processed activities and service activities, the system, by default, uses the planned delivery time as the scheduling-relevant dura- tion without differentiating between working and nonworking days. But, if you want to use a deviating duration for scheduling, you can define a control key with the Scheduling external operation indicator and manually enter the scheduling-relevant duration in the Normal dura- tion field of the Internal tab.
Using factory calendars in the costs activities, you can restrict scheduling to working days. If necessary, the system can automatically reduce the duration of activi- Reduction ties if the scheduled dates are outside of the basic or forecast dates of the network header.
The system can therefore automatically adapt the duration of activities to enable the network to be carried out in a given timeframe. This automatic adaptation of activity durations is called reduc- tion.
By specifying a minimum duration in an activity, you can ensure that a time interval that is required for processing an activity is not fur- ther reduced. The reduction of the activity durations is performed in several successive Reduction levels stages.
A maximum of six stages could be implemented. After scheduling, you will find the actual number of required reduction levels in the network header. For a system to automatically reduce the duration of an activity, you Reduction strategy must store a reduction strategy in the activity.
In the definition of a reduc- tion strategy, for each reduction level, you specify the percentage by which the planned duration of an activity is to be reduced. Finally, you need to specify in the scheduling parameters that a reduc- tion is to be carried out. To do this, you specify the maximum number of levels to run through. In addition, you can specify in the scheduling parameters whether all activities that have a reduction strategy are to be reduced or only those that are time critical.
Scheduling calculates the planned earliest and latest dates of activities, Scheduling and the scheduled dates of network headers and WBS elements. The cor- constraints responding fields cannot be changed manually.
To do this, you can specify schedul- ing constraints for activities see Figure 3. You can manually enter scheduling constraints or graphically determine them in the project planning board, depending on the options or the planning board profile see Chapter 2, Section 2.
In scheduling, the various influencing factors are considered according to the following prioritization: 1. Actual dates see Chapter 5, Section 5. Scheduling constraints 3. Relationships 4. Start and end dates of the network header or the assigned WBS ele- ments if the work breakdown structure determines dates From the scheduled dates of the activities, the system also determines Floats floats for each activity, which can be displayed in the detail screen of the activities and the network graphic, or graphically illustrated in the proj- ect planning board, respectively.
Regarding floats, there is a distinction between a total float and a free float. The total float of an activity results from the difference between its lat- Total float est and earliest dates, and therefore specifies the time interval by which you can shift an activity from its earliest date without exceeding the end date defined in the network header or — if it determines dates — of the assigned WBS element.
Activities with a total float smaller than or equal to zero are regarded as time-critical and are highlighted in color in the network graphic and the diagram section of the project planning board. For two activities that are linked to each other by a finish-start relationship without a time interval , the free float of the pre- 4 In the project planning board, you can use the options or even the planning board profile to control the total float starting from which activities are to be highlighted in color.
Because you can use the free float to perform activities without affecting subsequent activities with regard to scheduling, you can set the Flex- ible indicator for an activity to cause the earliest dates of this activity to be calculated based on the normal duration plus the free float. Conse- quently, the capacities have more time for performing the activity. Just like activities, however, activity elements have earliest and latest start and end dates. These dates are derived from the sched- uled dates of the activity to which the activity elements are assigned and from the time intervals you may have entered in the activity elements.
The planned dates of the activity elements always fall within the activity dates. Scheduling constraints can be defined at an activity level, but not for activity elements. If you use a milestones time reference, you can use appropriate indicators to specify whether the milestone date is to be taken from the earliest or latest date, and the start or the end date of the activity. Furthermore, you can specify a time interval either in absolute terms e. When using a time reference, every date shift of the activity directly affects the milestone date.
Even if you assign material components to an activity see Section 3. The scheduling parameters control whether the date reference should refer to the earliest or the latest date of the activity. If necessary, you can also specify an absolute time interval that is considered when deriving the requirement date from the activity date. Network Scheduling In network scheduling, all activities of an individual network are sched- uled.
Whenever you call the scheduling from the specific maintenance function CN22 or from the Project Builder, provided you have selected a network header or a network activity in the structure tree, you trigger a network scheduling. How to Visualize Data with R [Video]. The Complete Linux Manual July WebUser 29 July The main tool used in SAP PS to schedule a project is called the Planning board Transaction CJ2B , this tool displays the project Gantt chart and allows to modify the project dates, project master data and a large set of options.
This tool is also accessible from other transactions such as the project builder CJ20N. Figures can be broken down by fiscal year.
This type of planning in cost element based. Automatic cost planning using networks and assigned orders. In Cost planning using networks, costs are automatically calculated based on the resource requirements identifies for network activities and operations.
This type of planning has the following advantages :. Planned costs of assigned orders :. WBS elements identified as account assignment can also be assigned orders other than networks such as Internal orders, service and maintenance orders or production orders.
The assignment to the WBS elements can be stored manually in the order or created automatically. A plant maintenance order can derive the assignment to a WBS element from the functional location. The prerequisite to this being that the WBS element is already stored in this functional location. Production orders referencing project stocks are automatically assigned to the respective stock-holding WBS elements.
Depending on the order category, different options for cost planning are available. Internal orders use the same forms of cost planning as WBS elements. Planned costs for maintenance and production orders are calculated in a similar way as the planned costs of networks. Planning statistical key figures :.
Statistical key figures SKF are statistically measurable values which can be applied to projects, cost centers, profit centers, internal orders or business processes.
In the Project System module they allow to monitor specific units, such as mileage spent, number of project team members, etc The actual planning process for SKF is similar to detailed cost planning. Manual revenue planning :. The following forms of manual revenue planning are available in Project System :. Hierarchical revenue planning : This type of planning enables revenue to be planned by WBS billing element and year.
A distribution of revenues to individual periods for a fiscal year is not possible in this type of revenue panning. Detailed revenue planning :. This type of revenue planning enables revenue planning by revenue element for each WBS billing element. Revenue values are assigned to a period within a fiscal year.
Values can be entered for each period for each fiscal year or on annual basis and distributed to the appropriate fiscal year periods. Billing plan :. A billing plan is used to plan the dates on which payment requests or invoices affecting sales are sent to customers.
Planned revenues are recorded in the revenue element that has been defined in the planning profile. Billing plans for WBS elements can be assigned to billing elements of a project in every processing transaction of work breakdown structures.
They can also be implemented in simulation versions. Billing plans can also be created in the Sales and Distribution module for customer quotations or sales order items.
0コメント