In the R/3 system architecture, the application, presentation and database server

are separated out. This fulfills the prerequisite for distributing load into several
application servers for client-server configurations. Hence in terms of database,
the system can be distributed at different levels.
This architecture enables the host services can be adjusted without any issues i.e.
scalability, in cases where the loads on the system changes comprehensively as
a result of increase in the user numbers or because of components has been
added.
This displays that the R/3 system has the flexibility while choosing hardware or
software.

19

Scheduling uses the quantity structure of network activities to derive dates in an

automated way.
Single network schedules all activities of the network. If it is connected to other
networks by relationships, their dates are treated like constraints.
In overall network scheduling, the system schedules all networks connected by
relationships.
WBS scheduling schedules all activities which are assigned to selected
WBS elements.
Network can be scheduled:
Individually (Network Scheduling)
Overall (Scheduling of Overall network)
WBS scheduling
The activity data, activity relationships and date restrictions form the basis for
determining the dates automatically.
In Projects with assigned networks, the dates of WBS Elements and Activities
can be derived by scheduling. Here, WBS Element transfers the date to higher
level

elements and Extrapolate it.

In WBS with assigned networks, the basic dates for the WBS element can be
planned in order to determine that certain part of the project has to be
completed within a fixed period of time.

Scheduling parameter: They determine scheduling. These are created for

specific plants and network types.
1. Adjust basic dates: It determines that after the scheduling run, the
scheduled dates are copied to the basic dates of the network header.
2. Scheduling Type: It determines the type of scheduling being carried out. For e.g.
forward first and then backward scheduling.
3. Start in the past: It determines how much time back was the start date. If
its more than the days mentioned, scheduling is done from current date.
4. Automatic Scheduling: Scheduling is carried out when saving is carried out.
5. Log Automatic: If log is generated, it is displayed automatically.
6. Break Spec. Scheduling: The exact time at which a break is scheduled.
7. Shift Order: During scheduling. It determines how the system deals with partially
completed activities.
8. Latest material dates: based on latest and earliest dates, the requirements
dates for a material is determined.
9. Reduction type: Either all activities or only those in the critical path are reduced.
10. Maximum reduction level: There are up to 6 levels in reduction strategy. The
highest level is displayed.
11. Rescheduling: After scheduling run is done, it determines how the system is

10

allocating work in Work Force planning(WFP)

10

11

Scheduling Type: Determines type of scheduling being carried out.

1. Start in the past: It determines how much time back was the start date. If
its more than the days mentioned, scheduling is done from current date.
2. Scheduling form: It specifies as in on what basis is the scheduling being
carried out WBS element or Network header.
3. Adjust basic dates: It determines that after the scheduling run, the
scheduled dates are copied to the basic dates of the network header.
4. Log Automatic: If log is generated, it is displayed automatically.
5. Shift Order: During scheduling, it determines how the system deals with partially
completed activities.
6. Schedule when saving: Scheduling is done on saving.
7. Latest material dates: based on latest and earliest dates, the requirements
dates for a material is determined.
8. Maximum reduction level: There are up to 6 levels in reduction strategy. The
highest level is displayed.
9. Reduction type: Either all activities or only those in the critical path are
reduced.

12

1.

Every time a network is scheduled, forward and backward scheduling is

carried out by the system; and if activated it determines float and capacity
requirements for activities, reduction level used to schedule the network,
earliest and latest dates for the relationship.

2.

Forward scheduling determines the earliest dates.

3.

Backward scheduling determines the latest

4.

dates.

Float: If earliest dates are not same as latest

dates, then
float are:
occurs.
The Scheduling
results
Scheduled start and finish for the network.
Earliest start and finish dates (earliest dates) and the latest start and finish
dates (latest dates) for activities and earliest and latest dates for relationships.
Reduction levels used to reduce the network and float times (total and free float)
for activities.
And capacity requirements for activities.

13

Other influencing factors in scheduling:

Internal processing: the normal Duration maintained in the activity is used by
the system for scheduling internally processed activity.
External processing: Planned delivery time or normal Duration (explicitly to
be activated in control key) will be used by system for scheduling externally
processed activity.
General costs activity: Duration
Relationship: Time interval: Fixed or as a percentage.
The work centers can be maintained in internally or externally processed activity
and in relationships, and work centers contains following information's:
1. Formulas for calculating duration of activities
2. Factory calendar and operating time for each workday.

14

A network must and always scheduled forwards and backwards and scheduling type
specifies whether forward scheduling or backward scheduling is carried out first.
Forward scheduling calculates the earliest start and finish dates for all activities, and
the scheduled finish date of the network. A start activity is an activity in a network
that does not have a predecessor.
Backward scheduling calculates the latest start and finish dates for an activity (latest
dates) and the scheduled start date of the network. A target activity is an activity in
a network that does not have a successor.
When forward scheduling is performed first, the date from which scheduling starts
is the basic start date in the network header. When forward scheduling is
performed after backwards scheduling the start date is calculated from backward
scheduling.
When backward scheduling is performed first, the base date from which
scheduling starts is the basic start date in the network header. When backwards
scheduling is performed after forward scheduling the finish date is calculated from
forward scheduling.
Start dates are at the beginning of the day
(00:00). Finish dates are at the end of the day
(24:00).

15

Scheduling Assembly Networks:

Overall Network Scheduling can be performed for a sales order item.
This function schedules the network assigned to the sales order item and all
other networks with relationships to it (total network scheduling).
The function leads to an update of all items in the sales order with assignments
to the total network.
Overall Network Scheduling with Selection Options:
This function is used along with selection criteria to specify which network/subnetwork are to be taken into account as part of overall network scheduling.
A prerequisite for the use of the Overall network scheduling with selection options
function is that suitable levels are defined beforehand for the project system and
network types and number intervals are assigned to it.

16

Activity Element & PRT Dates

The system calculates dates for activity elements with reference to the start or
finish dates of the activity. You maintain a time interval for the start and a time
interval for the finish.
Material Requirements Date
The system calculates the requirements date for components with reference to the
start or the finish date of the activity. With the network type you can control
whether the earliest or latest start date is used as the requirements date in the
network.
If the requirements date is before or after the start date of the activity, you can enter
a corresponding lead time offset.
You can set a manual requirements date for components.

17

You can maintain constraints for the start and finish of activities and / or (offsets
for) activity elements.
Constraints can be relevant for both the earliest and the latest
dates. You can maintain constraints for basic and forecast sets of
dates.

18

Legend:
ES = earliest start
EF = earliest finish
LS = latest start
LF = latest finish
TF = total float
FF = free float
Floats supply information about time reserves available for individual activities and
one can use floats calculated in scheduling, for example in capacity leveling, to
shift activities between their earliest and latest dates or to extend their duration.
Total float: The amount of time an activity can be shifted from its earliest dates into
the future without affecting the latest dates of its successor. (Total float: = LS-ES
or LF-EF)
Free float: The amount of time an activity can be shifted from its earliest dates
into the future without affecting the earliest dates of its successor. (Free float =
ES successor EF activity)

19

The slide describes the calculation of total floats and free floats:
The total float can be calculated as the difference between the earliest and
latest start of an activity.
In the above example:
Day 6 (0:00) - Day 5 (0:00) = 1 Day.
The free float of an activity can be calculated as the difference between the
earliest start of the successor and the earliest finish of the activity.
In the above example:
Day 9 (0:00) - Day 7 (24:00) = 1 Day.

20

Reduction:
Reduction can be used when the time period within which activities are scheduled
is not enough for processing all the activities.
This reduces the scheduled duration of internally-processed activities and for
which reduction strategy has been maintained.
Up to six reduction levels can be defined for each reduction strategy. The
percentage reduction required can be entered for each reduction level.

21

3-4 Cost Planning

1) Based on the resource and material planning using WBS and networks, as
described above, the system can automatically calculate planned costs for the
procurement and the consumption of resources and material. This form of cost
planning is referred to as network costing,
If you only use work breakdown structures for mapping projects,
you manually plan costs on the WBS element level for the later performance of
the individual project parts.
2)Two important criteria for a cost planning's level of detail are the characteristics
by cost element and. by date.
Cost planning by cost element
If a cost planning references one or several cost elements, this
type of cost planning is referred to as a planning by cost element.
Cost elements are defined in the Cost Element Accounting of
Controlling and correspond to cost-relevant chart of accounts
items. Using cost elements, you can structure and classity the
consumption of production factors that is valuated with regard to
the business purpose. Using cost element reports (see Section
7.2.2) or hierarchy reports (see Section
7.2.1)
Use - detailed planning ,Unit costing , Easy cost planing
Date Planning If a cost planning references the period of the
projected cost , this type of cost planning is referred to as being
period based.
Cost plannings by date allow you to analyze planned costs
specifically
for a period (e.g., monthly) in Reporting and to compare them to
the actual costs incurred during a period.
Use - detailed planning (see Section 3.4.3) and network costing ,
Easy Cost Planning is only conditionally date-specific
Note -the other cost planning forms in SAP Project System are

Sales Project Projects which have the recognition of revenue at the starting or
during the course of the project execution. When activities are assigned to
WBS elements, the dates and costs defined in the individual activities are
totaled up (aggregated) at the WBS level, and can be evaluated. Activity funds
already assigned are checked against the budgets of the WBS elements.
Following important steps are carried out during the execution:
Customer inquiry is created and assigned to the project.
Plan dates, materials, costs, and resources
Create sales pricing and sales order.
Enter confirmations, Purchase materials & Services. Post revenues.
Calculate overhead, carry out result analysis and execute settlement.
The above steps are discussed further in the course.

39

You define the company using company codes and business areas (Accounting view) and
controlling areas, profitability segments and profit centers (Controlling view).
The operating concern is the organizational unit for which the market is uniformly
segmented.
The controlling area is the organizational unit within the company used to represent
an internal system for cost accounting purposes.
The company code is the balance sheet unit in Financial Accounting. Company codes can
be assigned to the controlling area in an N:1 or 1:1 ratio (company-code-specific cost
accounting). In the Customizing settings for the controlling area, you can specify whether
company-code-specific cost accounting is possible. This setting should be considered
carefully and made when you create the controlling area.
The financial management area is the organizational unit within which you plan, control,
and monitor funds and budgets.
In the Project System module, it is sufficient to assign the company code to one financial
management area. In Funds Management, you have to assign the financial
management area to the controlling area.
You use the business area for calculating balances internally.

40

The Project System module has no organizational units of its own.

Depending on the project type and configuration, the organizational units from a wide
range of areas are used (sales and distribution, purchasing, production, accounting,
controlling, personnel, and so on).

41

All business processes throughout the supply chain are executed in one
system sharing all information

12

13

15

The picture here illustrates a typical R/3 system.

Multiple presentation layers from multiple computers communicate with
the application servers over the local or wide area network.
For a single R/3 system, there may be multiple application servers in order
to balance the operational load.
All these application servers interact with a single database server.
And as the picture illustrates, the database server acts as the
interface between the external RDBMS and the application servers.
A single database, the R/3 database server that accesses it and the set of
one or more application servers and their processes, that govern the
business administration and the data sent and received from the database
server all these components that constitute a logically single R/3
system, is called as an R/3 instance.

17

The presentation server is simply a GUI (Graphical User Interface) that is running at the
users workstation. It is a very light component, called as a thin client in common
terminology. It is capable of sending requests to the application server, receiving the
requests back and displaying the screen back to the user.
Multiple instances of presentation servers can execute in the same work station.
And generally the presentation layers are, to a good extent, downward compatible with the
application servers, in terms of the version. For e.g., A 4.6 C version GUI would be able to
communicate with a 4.5 B version application server.
The messages exchanged between the presentation layer and the application server are in
a SAP proprietary format. The presentation layer is capable of accepting the screen
information sent from the application server, format and generate the screens appropriately
for the platform it is running on.
The database server, as we saw earlier, acts as an interface between the application server
and the RDBMS.
As we know already, the R/3 system does not include the RDBMS. In other words, R/3 is
independent of the RDBMS. R/3 is operational on a number of commercial RDBMSs.
The vendor specific DB driver resides in the database server.

18

In the R/3 system architecture, the application, presentation and database server
are separated out. This fulfills the prerequisite for distributing load into several
application servers for client-server configurations. Hence in terms of database,
the system can be distributed at different levels.
This architecture enables the host services can be adjusted without any issues i.e.
scalability, in cases where the loads on the system changes comprehensively as
a result of increase in the user numbers or because of components has been
added.
This displays that the R/3 system has the flexibility while choosing hardware or
software.

19

21

 The SAP R/3 system consists

of application modules that
support business
transactions and are
integrated real-time
Because of integration, a change
in one application module will
result in an automatic update of
the data in the other application
modules involved
All application modules have
common

22

architecture and user interface

(same look & feel and
navigation).

22

Accelerated SAP is a comprehensive solution for the implementation of the

R/3 System, comprising a proven methodology, tools and a range of services
for the rapid implementation and ongoing optimization of R/3 installations
It provides a standard implementation "how-to guide" that fills in the gaps of
diverse methodologies and varying individual implementation skills and
experiences.
It is essential that you create a project plan when starting your ASAP
implementation project.

25

Integration allows SAP, as a tool, to support all phases of project management by

communicating with sales and distribution, materials management and accounting
in a real time environment.

26

The Project System is an integrated solution that helps you perform all of the tasks in
a project - no matter which sector of industry you are active in.
It includes the functions you need in all project phases.

27

85