You can create invoicing plans directly for network activities (external, service, or general

costs) or components procured externally.

This means that it is possible to plan costs and outgoing payments on the basis of dates
entered in the invoicing plan. Costs are not simply distributed, but are calculated precisely
at the times specified in the invoicing plan.
You can create an invoicing plan by copying a reference invoicing plan.
The reference invoicing plan fixes cost and payment times relative to a start date.
Alternatively, you can copy billing milestones as dates to the invoicing plan of the activity. If
you copy the milestones rather than creating them manually, they can be postponed
along with the dates in the invoicing plan if the activities are rescheduled.
You cannot create invoicing plans in combination with unit costings (for general costs
activities or material components).

30

On the basis of days, periods or fiscal years one can plan payment flows i.e. revenues
and expenditure.
In WBS elements, manual planning of revenues and expenditure is by period. At
commitment item level (Project Cash Management master data) planning takes place.
The quantity structure in the network and the billing plans in the WBS or SD document
are valuated in the automatic planning of financial data.
Automatic planning will be done by day. Planned line items will be written.
Based on assignment to G/L accounts commitment items will be determined. Unlike
revenue and costs calculation, payment date calculation takes account of the
customer and vendor payment terms respectively.
Note: The credit side payment plan of the network is determined using the
asynchronous network costing only.
The dates and the payment terms are used in the PS billing plan for planning incoming
payments. Sales order items will also be used in assigning the billing plan data and
payment terms(of the dates or sales order item).The delivery date including the
payment conditions is used if there is no billing plan for the sales order item.

31

In the case of activities processed externally and externally procured components,

invoicing plan including payment conditions are used or, the delivery dates including
payment conditions are used where there is no invoicing plan
If an invoicing plan has been maintained, payment data is only planned for
general costs activities

31

For instance In this case the way in which the material can be procured
depends on both item category and material attributes.

The material master stores the information of

the material attributes.
-It contains information like :
-Whether the material is purchased or
internally manufactured.
-Whether the requirements are individual
or collective or both
-Whether the material can be procured in
advance.
The control data of the project definition
determines whether stocks can be built or not

43

The account assignment category of the sales

order determines whether sales order can be
built up
A setting within the BOM can be specified to
determine whether the components can be
procured independently of the material master
settings.

43

The components can be assigned to the

activity with the help of the procurement
indicator.
The Procurement indicator contains the
default values for determining the stock and
the procurement type.
A procurement indicator can be specified in
the network profile. This gets defaulted in the
component assignment.

44

The BOM transfer functionality in SAP PS helps you to assign the material from BOM to
the network activities based on the reference point field which is assigned to the material
and network activities.
WBS BOMs can be assigned to Project BOMs using the BOM Transfer transaction .
The corresponding selection parameters must be chosen to perform the same.
Advantage of BOM transfer functionality is that the changes in the BOM during the course
of the project will change in the activities (you need to run BOM-transfer again every time
you make changes in BOM).
You can also manually assign materials to network activities without reference point fields.

45

Reference point : This is the logical link between a BOM component and a
network activity. It ensures that the automatic assignment of the material
component happens correctly.
While the assignments by themselves are project specific, they can be made
simultaneously for a large number of networks in the project.
Individual components, individual BOM assemblies or a multi level BOM can
be assigned.
These assignments can happen manually without reference points as well.
Procedure For BOM Transfer:
Field in the BOM and the network activity which needs to be used as
the reference point needs to be specified.
These fields must have the same structure in both the objects. For
instance : CHAR, eight digits .
Possible entries for the reference point can be defined in
customizing.
Reference points in the BOM Components and the network activities
must be defined.
The BOM PS Interface must be started (after changing the BOM)

46

BOM Components are assigned to activities in this process.

Purchase requisitions and reservations are created for the assigned
components if Reservation/Purchase Req. indicator is activated.

46

A material that you allocate to activities in a network can be kept in various stocks.
Depending on your project, you can access different types of stock for materials
planning:
Sales order stock and project stock are important for controlling purposes (for monitoring
the stock value in a sales order or project) and from an MRP point of view (the stocks
are reserved for the sales order item or WBS element; other stock elements cannot
access them).
The various stock types are managed for each material component using the account
assignment category. You define the account assignment category when you assign the
material to the network activity (popup in manual assignment, strategies in BOM-PS
interface and standard network).
The possible account assignment categories depend on the assignment of the network
activity to a stock object (WBS element or sales order item), on the item category for
the assignment (direct procurement for non-stock items) on the material master, which
can exclude collective or specialist stock management.
As of Release 4.5A, you can use MRP elements (grouping) to manage a joint project
stock for an entire project or for several projects (this is a rougher method than managing
stock per individual WBS element).
You maintain the account assignment categories possible for network purchase

47

requisitions in customizing.

47

Instead of managing the material either in a plant stock or for each individual WBS
element and having no control at all over procurement or being fully responsible we
can go for requirement grouping. Through requirement grouping we can determine
the degree of control ourselves.
Prerequisites for using requirement grouping :
Valuated group stock
Grouping WBS elements
MRP Groups that allow requirement grouping
Assigned components should have periodic lot sizes.
The most basic scenario involves grouping the requirement of all the WBS
elements in the project into one WBS element.
Or we can create projects which are only meant for grouping requirement of other
projects.

48

49

Valuated project stock must be allowed in the project definition control data.
With the exception of automatic requirement grouping MRP element indicator
must be set for WBS elements.
MRP groups involved in requirement grouping must be determined in customizing
for the WBS.

50

51

52

It is common in engineering projects for critical components with long and unreliable
delivery times to be purchased at an early stage in the project much before the
project activities in which the components will be used are specified. Advance
procurement process is used in such situations.
Advance procurement can only be used when you are using sales order or project
stock .

53

Order Categories and order types

Documents are used to enter business transactions in the R/3 System. Orders are
one type of business transaction. Orders are determined by their order category.
The network is an order category. Order types are prescribed by the system for the
relevant applications.
You can define your own order types within an order category. The order type
describes how the order is controlled.
Customizing includes two tables, one for the order type and another for the
order type/plant combination.
The order category is used to control:
1. Number assignment
2. Default value settings
3. User-specific status management
4. User-specific field control
In the case of networks, order types/plants can be header-assigned or activityassigned. Normally, activity-assigned networks are used, where costs are gathered
in each activity. Header-assigned networks are only significant for the assignment of
networks to sales orders (without WBS).
Project Assignment of orders

54

You can assign various SAP orders to a project; examples include internal orders,
production orders, and plant maintenance orders. You can then use the project
hierarchy reports to evaluate these assigned orders with the WBS element.
Each order is a cost object with its own costing parameters such as planned costing
variant, actual costing variant, and overhead sheet. The planned costs of assigned
orders are used to determine the planned costs of the project.
You assign orders to the project either by assigning a WBS element to the order
header or by assigning the order to a network and activity as a subnetwork. If the
assignment is required only for cost control and analysis, you need to assign order to
the relevant WBS element. If the assignment is required both for scheduling and
cost control, you need to assign the order as a subnetwork. The WBS element is
derived from the network activity. Note that production orders cannot be assigned as
subnetworks.
Documents are used to enter business transactions in the R/3
System. Orders are one type of business transaction.
Orders are determined by their order category.
The network is an order category. Order types are prescribed by the system for the
relevant applications.
You can define your own order types within an order category. The order type
describes how the order is controlled.
Customizing includes two tables, one for the order type and another for the
order type/plant combination.
The order type is used to control:
Number assignment
Default value settings
User-specific status management Userspecific field control
Plant and order type parameters are used to control:
If the network is activity- or header-assigned
Planned and actual costing variants
The settlement rule strategy

54

You can use the "appended" indicator to specify, per order category, whether an
order is appended - that is, whether the planned values for the order are included
in the planned value of the corresponding WBS element:
1. If the "appended" indicator is set, the order planned value increases the
WBS element planned value. The information system shows the total
as the project plan. When cost planning is taken over as the budget,
the values from appended orders also contribute to the budget.
2. If the "appended" indicator is not set, the order planned value is not
added to the WBS planned value. In budgeting, the plan total for such
orders must be added manually so that these orders can use funds
later.

55

You can use the "appended" indicator to specify, per order category, whether an
order is appended - that is, whether the planned values for the order are included
in the planned value of the corresponding WBS element:
Once released, all orders are apportioned - this means that their plan, commitment,
and actual values are funds assignments against the funds in the project. The
order value table contains an indicator which you can use to make orders
"apportioned" earlier, at the "created" stage.
You can set appended and apportioned indicator based on the order category,order
type, and controlling area
An exception to apportionment at release is in the case of networks for preliminary
planning.In Project System customizing,you can specify network types to be used
for preliminary planning.Preliminary planning networks are never apportioned.Their
related plan values do no increase the assigned value for the relevant WBS
element
In the case of networks (order category 20), you can use the network type
parameters to determine whether the network is:
Header-assigned or activity-assigned - that is, whether costs are managed in
the network activities or collected in the header

56

A preliminary planning network whose plan, commitment, and actual values

are not apportioned - meaning that they do not appear as assigned values
in the project.

56

Header-Assigned Networks
In a Header-assigned networks all the costs (activity and material) are assigned at
network header level
After assignment of network header to a WBS element, All costs are transferred to
WBS element. Assignment of activities to WBS elements is only to summarize the
dates
We you have to use header-assigned networks to assign networks to sales order in
case sales order are not assigned to projects as no assignments can be made to a
sales order item in the network activity.
Activity-Assigned Networks
Costs are collected on activities in case activites are used as account assigned
objects.Plant/network type parameters deines the condition if the network header
or network activities are to be used as cost objects.
Activity- assigned networks are usually used when activities are assigned to various
WBS elements.Here every activity in the network is an account assignment object.
Which implies we can analyze planned costs, commitments and actual costs
for each activity.
The costs are aggregated and displayed for the WBS elements to which
the activities are assigned.

57

Activity account assignment is a special feature of networks. All other order types are
header-assigned. Activity account assignment is controlled via the appropriate
indicator in the table "Parameters for network type".
Header assigned networks should be used when networks are assigned to sales
orders without WBS.Header assigned networks can also be used when the
enitre network is assigned to a single WBS element

57

SD document item assignment is controlled via the account assignment category.

The account assignment category is controlled via SD requirements type
determination.
Important factors that affect account assignment are the strategy group, the MRP
type and item category group from the material master of the product as well as
the document type of the SD document.
The system defaults the item category when you create an order. You can accept
the default or overwrite it. Permitted item categories are defined in Customizing.
The permitted planning strategies are assigned to the material using the planning
strategy group. This is necessary so that you can find the correct requirements type
in independent requirements management and sales order management.
The default requirements type is the main strategy in the planning strategy group.
If no planning strategy group is defined in the material master, the system uses the
item category group (sales and distribution screen in the material master) and, if
necessary, the MRP characteristic to search for the requirements type for the sales
order.

58

The account assignment category determines the CO object to which document

quantities and values are assigned. You use it to determine the following:
Using the special stock indicator (SSI above), that goods movements in Logistics use
plant stock, sales order stock or project stock.
Using the consumption posting indicator (Cons. above), the CO object to which the
values of a material document are assigned.
Settings:
F = Collective stock, consumption posting to the consumer (order, activity)
The account assignment category is important for procuring components directly.
E = Quantities and values managed in the sales order item
This account assignment category is important for make-to-order production without
WBS.
D = Quantities managed using sales order item, values managed in projects
This account assignment category is important for non-valuated project
stock, with WBS and sales order item
Q = Quantities and values managed in projects
This account assignment category is important for project stock

59

G = Plant stock, values managed using project

This account assignment category is important for sales order items sold
from plant stock, with
value posting to the project. It differs from account assignment category "F" in
the field control
of the account assignment block.

59

Activity-Based Costing offers a facility for allocating and distributing the overhead to its cause.
Activity-Based Costing provides useful information on:
Overheads reduction by process improvement
Profitability increase by highlighting unprofitable products or customers
Activity-Based Costing is advantageous for having:
Transparent overheads
Parallel quantity and value flows
Precise assignment of internal activities to consumer
Peanut butter effect" can be avoided through even distribution of overheads among all
the cost drivers.

60

In Activity-Based Costing, processes are the controlling objects. Prices can be either
maintained manually or using activity and cost input planning in the case of cost
centers and activity types. Through activity based costing, processes are debited to
cost objects or profitability segments.

60

Templates are created in Customizing and determined by controlling area, costing sheet,
overhead key and template environment (for networks 004; for WBS 005) for the
function. In the Project System, templates can be assigned to WBS elements, networks
(header assigned), or network activities. Process costs are allocated to cost objects or
profitability segments by assigning a process template. Process costs are calculated based
on the templates selected for the project.

After template selection, the calculation program

determines the following

Processes in the template relevant for the

project

Quantity of each process consumed by

the

61

project

Calculated value to be added to the

project at the start, end or continuously

The price for the process and the allocation cost element are determined by
entering one process per line in the process template. Multi-level processes can be
mapped by referencing another process template in the working template.
The quantity used by the cost object is determined using the cost driver. This enables
the allocation of the relevant values to all the levels in the process hierarchy as far
as cost objects or profitability segments.
Cost drivers can originate from many different sources in the R/3 System or external
systems. Examples : weight (material master), number of components, activities of a
particular category, work center (network), number of sales orders for market
segment (LIS) etc. The quantities determined by the cost driver are multiplied by the
price of the process. The resulting value is charged to the cost object (in the
example, the WBS or network/activity), and the process is credited.

61

Actual prices for activity types and business processes are calculated in Overhead
cost controlling at the end of the period.
Actual prices = Actual costs / Quantities consumed
The possibility of revaluation at actual prices and its specification for each
activity type are controlled in Customizing in the parameters for the actual
version depending on the fiscal year.
The difference between the actual price and the originally allocated price is
charged to the cost objects.
Revaluation at actual prices for activities and business processes can be done
in the Project System and in the Cost Object Controlling.
Revaluation at actual prices using an activity type is illustrated in the example given
in the slide

62

Overheads calculation is used to allocate overhead costs to cost objects such as activities
and WBS elements. Calculations are done based on the Costing sheet entered in

the cost object and the overhead key entered on the WBS element,
network header or network activity. Overheads can be calculated for
planned, commitment and actual values. Overhead calculations are
done using the quantity based or percentage allocation rates.
The following postings get generated through overheads allocation:

Debits to cost object (WBS element, Network header or

Network activity )

Credits to cost center ( overhead order or process )

63

Overhead costs are updated using the secondary cost elements

in the costing sheet credit rows and these can be simulated also.

63

Costing sheet is derived by means of the costing variant from the "Parameters for
Network Type" table, in the case of networks. The costing sheet and the overhead key
can be changed in the network header.
The costing sheets to be used in the activities are made a default through this.
For WBS elements, the costing sheet is derived directly from the project profile. In
the case of Easy Cost Planning and the unit costing for WBS elements, the cost
planning draws on a costing sheet for a costing variant which is assigned to the
project profile through the planning profile.
Overhead keys for activities are inherited from their respective WBS elements.

64

Overheads are calculated using a costing sheet.

The overhead surcharge can either be a percentage if it is value driven or an absolute value
of measure if it is quantity driven. The overhead is calculated against a base which is defined
by the cost elements. Cost elements or cost element areas are collected in base lines.
Factors such as Controlling area, company code, plant, overhead group, network type, time
period and plan versus actual determine the overhead rate applied. Overhead key assigned
to the cost object decides the determination of overhead group in customizing. Thus a single
costing sheet with flexible rates can be made use of different organizational units or
individual activities.

65

networks/activities.
As part of the network costing, the system automatically determines planned
costs when you plan dates and resources for the following objects:
a. For internally processed activities: activity inputs
b. For externally processed activities & service activities: Primary costs
c. For genreal costs activities: primary costs
d. Material componenets: primeary costs.
You can use planning templates to create quantity structures for Easy Cost
Planning.
You can enter quantities and prices in the template, or regulate activation using
formulas or conditions.
You can use characteristics assigned to the planning template as variables for the
formulas/conditions. The characteristics are valued by the user when the
planning templates are copied into Easy Cost Planning.

66

Unit costing is done to calculate cost plan per WBS element. Here we use
planned quantities instead of cost.
It is not period dependent
At cost element level, plan values are displayed
Input information related to sources of supply, quantities and prices mark the use
of unit costing to generate cost plan per WBS element

67

Structure Oriented Planning:

Simplest type of planning is structure based planning. Plan values are displayed
in hierarchy
The total cost planned is aggregate
It is neither by cost element nor is period specific
Various views are used to display the different values in structure-oriented
planning
Planned total View-this shows total aggregate at superior WBS element (Level
1 WBS element)
The distributable or distributed view-This view is used to check distribution of
budget among child WBS element
Cumulative or remainder view-This view is used to check distribution of budget
across years
Order/network view-This displays the planned cost od appended orders/networks
assigned to WBS element
Cost Element Planning/Activity Input Planning:
When more detailed information is required, cost element planning is done. It
is independent of project scheduling
Manual reschedule of cost planning becomes mandatory if a project or
individual

68

package schedule is changed

This planning is adopted if precise information is available as it becomes sure not
to reschedule/postpone the project

68

The plan profile is used to control overall cost/revenue planning. It contains costing variants
for the unit costing or Easy Cost Planning.
It also contains indicators for updating revenue plan values via customer quotations or sales
orders.
You assign the plan profile to the project by way of the project profile. You can change it in the
project definition.
Costs and revenues can be planned in different CO plan versions.
You either specify the plan version during planning or, if you are using Easy Cost Planning,
you assign it to the controlling area.
Planning layouts are used to plan costs, revenues, payments, and statistical key figures.
You can use the Report Painter to create the layouts and can assign them to planner profiles.
Users can choose planner profiles and assign them to the user master record.
Planning profile: Use transaction OPSB
The Planning profile contains the settings related to planning. It control overall
cost/revenue planning. Planning profile is assigned to project using project profile. Costing
variant are

69

relevant if we are using unit costing and easy cost planning

CO plan version is required to be specified if we are using easy cost planning.
Planner profile and planning layouts are specific to use of detailing planning
using cost element/activity input

69

Planning profile is contains the settings for overall planning, detailed planning
and unit costing
Details for each field can be checked using
F1 Important field details are as:
Total Value: Defines overall planning without any reference to fiscal year
Annual Planning: Defines overall planning with reference to fiscal year
Bottom up Planning: Overall planning values are extrapolated after saving
Exchange rate type: Determines which exchange rate is to be used for currency
conversion of overall values

70

Transaction OKKT to edit costing and valuation variant

Costing variant is mostly used for unit costing ,easy cost planning and also used for
costing networks. The field costing type determines for which WBS element
(costing object) costing is done
Valuation variant determines the prices and rates. In the above mentioned slide,
system will first check for Planned price 1 if it fails, system will check for standard
price and again if it fails it will check for moving average price from material
master. If system now fails, it will trigger an error message during cost determination

71

Internally-processed activities:
If no distribution key or work center is maintained in the activity, the costs are distributed
evenly over the earliest dates in the activity. Valuation is at the rate in the valuation variant.
Depending on the strategy being used, the system can determine the most current date.
valuation is determined by the rate maintained in the valuation variant. Based on the
strategy adopted, system determines the latest date. If no work center/distribution key is
maintained, the system distributes the cost evenly over the earliest dates.
Costs activity:
Case 1:Invoice plan maintained:the values in periods are as per the values mentioned
in invoicing plan
Case 2:Invoicing plan not maintained and distribution key maintained:The activity value
is

72

distributed to the periods based on the distribution key maintained in the activity
Case 3:Invoicing plan not maintained and distribution key not maintained:The
costs are distributed evenly over the earliest dates in the activity
If an invoicing plan has been maintained, the values in the periods are set
as specified in the invoicing plan.
Otherwise, the activity value is distributed to the periods using the distribution key in
the activity. If no distribution key is maintained in the activity, the costs are distributed
evenly over the earliest dates in the activity.
Service activities or externally-processed activities:
Case 1:Invoice plan maintained:the values in periods are as per the
values mentioned in invoicing plan
Case 2:Invoicing plan not maintained:The activity value is set in the period of the
latest activity start date.Also the system determines the price from the purchasing info
record or the activity value.
Invoicing plan has priority for the values
If an invoicing plan has been maintained, the values in the periods are set
as specified in the invoicing plan.
Otherwise, the activity value is set in the period of the latest activity start
date.
The invoicing plan has priority for the values. If no invoicing plan has been
maintained, the system determines the price from the purchasing info record or
the activity value.
Material components:
Case 1:Invoice plan maintained:the periods and ,in some cases,values are
taken from invoicing plan
Case 2:Invoicing plan not maintained:The system determines the price from the
purchasing info record or the price is taken from material master as per
valuation variant.Here material requirement date determines the period
If an invoicing plan has been maintained, the periods and, in some cases, the
values are taken from the invoicing plan. If no invoicing plan has been maintained,
the values are taken from the purchasing info record or the price is taken from the

72

material master per the valuation variant. In this case, the period is that from
the material requirements date.

72

The customer accepts the quotation. A sales order is created in the system, where
appropriate using the quotation as a template. The activities listed in the quotation
are entered in the sales order as sales order items.
The items are assigned to the project. They are used for revenue planning and for
posting revenues to the project by means of milestone billing.
Two companies are responsible for executing the project - IDES AG and IDES UK.
IDES UK creates a sales order for IDES AG and assigns the document item to the
billing element T-100##.1.2.
Later on, IDES UK bills its services to IDES AG on a resource-related basis.
A billing request is created in the system via resource-related billing. This is billed and
results in revenues for IDES UK.

73

In SAP where project is a controlling object:

Sales order created and after structuring of project sales order will account assigned to
WBS. Then revenue planned in sales order.
Once Work completed in project, actual cost captured in WBS and Final product will
be delivered to Client.
Billing will be completed and actual revenue generated. Actual Revenue will
be transferred to WBS.
While Result analysis performed for project the Actual Revenue and Cost will settled
to the profitability segment.
Sale document structure
Sales Document type represents the type of business transaction and functions and
the flow of document with in sale order. Processing.
Item Categories are assigned to sales document category. While creation of Sales order
it will default the item category but user can change it as per requirement.
Schedule line category is assigned to Item Category. While creation of document
system will default the scheduled line category but it can changed according to
requirement.

74

Item Category

Item Category is determine by Sales Document type and the

materials Items category group in a sales order.

Item Category controls function for Sales Order like Item Type,
Pricing, Billing Plan, resource related or delivery related.

It controls if pricing is relevance for billing, relevance for Delivery

Schedule Line Item, and contains Incompletion Log and Partner text.

74

(1)Represents a process of make-to-order production without a work breakdown structure.

In this case, the sales order item is the contolling instrument. Account assignment category
E specifies that the sales order item forms a separate CO object.
Costs and revenues of the sales order item are usually settled to the profitability segment.
(2)Using assembly processing, you can generate a network when you create the sales order.
When you save your data, the system creates a WBS and assigns the sales order item to a
WBS element in this WBS. In this case, the sales order depicts the sales view, the project is
the controlling instrument, and logistical processing is represented by the network.
Account assignment categories D or Q (Cons. = P in each case) specify that revenues
are assigned to the billing WBS element of the project.
(3)As an alternative to assembly processing, you can assign a sales order item to a WBS
element in a project. Controlling takes place in the project. You can assign orders or
documents to the project. Value assignment to the project is controlled via account
assignment categories G, D and Q. These differ from each other in the way that they
manage quantities.

75

Methods for plan revenue in a project are:

a. Manual revenue planning: this can be based on structure or revenue element
where the later is a cost element and period based.
b. PS billing plan: this is cost element and period based planning.
c. SD document: this is part of integration with SD module where sales order item
or quotation items are used as revenue planning. This kind of planning is cost
element and period based.

76

Revenues can be planned in projects using the following methods:

Manual planning in billing elements in the project structure.
This type of planning can follow the same procedure as cost planning, or can be by
revenue element.
Sales orders (all SD documents assigned).
Sales order items are assigned to WBS elements. In Customizing, you can stipulate, for a
combination of sales document category (quotation, order, and so on), sales
document type, controlling area, and system status, whether the billing data (for
example, in a billing plan) from a sales order should update the revenue plan for an
assigned WBS element. The dates and planned revenues concerned originate either
from the billing plan for the sales order items or (if there is no billing plan) from the
net value and apportionment data for the item. The revenue element originates from
G/L account determination in SD.
Billing plan in project billing elements.
The revenue element is defined in Customizing.

77

There are different ways of creating billing plans:

Manually
By copying a reference billing plan
In SD and PS, reference billing plans can be
called upon automatically
By copying billing milestones from work
breakdown structures or networks
By copying billing milestones automatically from
the network in assembly processing

78

In the SD document, you can define a detailed billing plan with a number of billing dates
instead of just a single billing date. A billing plan is a schedule containing individual billing
data for a particular sales document.
Milestone billing is widely used in projects (for example, construction projects).
If you use milestone billing, the total value to be billed is apportioned to the individual dates
in the billing plan per defined rules.
Billing plan dates can be blocked for billing
You can set billing blocks manually or remove them by activating billing milestones.
As of Release 4.0, billing plans can also be entered for billing elements in projects. Such
billing plans can, if required, be copied to the sales order later (make sure you delete
any existing billing plan in the billing element; if you do not, the planned revenues will be
determined via the PS billing plan and not the SD billing plan).
A billing plan can contain down payment dates. These dates affect payment, but not
revenue.

79

80

The term "Version" is used in the project system in different contexts. Different
types of versions include simulation versions, project versions and CO planning
versions are available in SAP Project System which are discussed below.

Project versions, are snapshots of a project at a specific point in time, and are
used for documenting the progress of a project over time. Both quantities and
values are stored in versions and it can be created either manually, or
automatically when a status changes. In the case of status change, the project
profile contains a reference to a version profile which specifies the name of
the project version to be created when a particular user or system status is
set.

Simulation versions: In the Project System, these are versions that you can
change. You might, for example, create simulation versions in the following
situations:
In the quotation phase: generally speaking, at this stage there is not yet
an operative project.
To draw up alternative planning scenarios for existing operative projects
or parts of these.

CO plan versions are used to plan revenues and costs. You can copy values
from one version to another. You can change planned values manually in every
version and cost values are retained.

81

Simulation versions are used to draw up alternative "what if?" planning

scenarios. They are created manually, can be changed, and, if necessary,
deleted again which is unlike released operative WBSs with activities.

Simulation versions are useful during the quotation phase of a project

and possible to plan several simulation versions.

You can create simulation versions even at the time of execution of project,
where you can copy from operative to simulation versions, compare, analyze
and work with other versions and transfer them back to the operative
project.

When an operative project is copied to a simulation version or vice versa, a

log file is created which contains the objects that were transferred and any
error messages that were issued in the process.

Simulation versions can be created either for an entire WBS, or for

sub- hierarchies of a WBS.

Simulation versions are edited in the project planning board or in project

planning board from SAP R/3 4.6C release.

The system performs the test run while transfer to check if the operative
or simulation version can be transferred.

Multiple Simulation version can be created, compared and evaluated.

82

Simulation customization consists of two steps:

1. Version keys: one should work with permissible version keys since these cannot
be deleted once simulations has been created.
2. Simulation profile: This determines which all objects will be copied while creating
simulations (in addition to the structure information) from simulation to
operative (and vice versa). If there are no simulation profile, all the texts will be
copied. The simulation profile will be defaulted in the project due to assignment
in project profile.
Just like project version, simulation versions can be compared with each other in
information system, whereas the cost element report does not support the
simulation versions. Unlike operative projects, simulation versions cannot be
changed in structure info system.

83

When you transfer data from operative projects to simulation versions (or
vice versa), the following objects are copied:
Work breakdown structure

Network with activities, activity elements, relationships, and

subnetworks

Milestones

Materials for the activity

Documents, PS texts and long texts (depending on the simulation profile

used)

Capacity requirements

Invoicing plan for the network, and billing plan for the WBS element
(as of Release 4.5A)

The following objects are not copied:

Other orders (e.g. no production orders)

Production resources/tools

84

Project versions enable you to record a snapshot of a project at a specific

moment in time - this can be used for future comparison with the
operative project.

You can create a project version automatically (i.e. triggered by a system or user
status).

You can also create a project version manually:

While changing the WBS

While changing the network

In the Structure/Dates information system for one or more projects

Data transfer when Version profile settings are used while using these transactions:
1. Status dependent project versions.
2. TC network maintenance CN22 or WBS element maintenance CJ02
Data transfer which is Independent of version profile and dependent on
database profile:
3. TC CN71 and CN72
4. Structure information system

85

The version profile is maintained in the PS customization and assigned to

Project profile or network profile.

85

You use a version profile to define two different kinds of information. First, you
specify which version is created automatically when a specific system status or
user status is set. Second, you specify which data is to be written to the
versions that are created automatically.

You need to define a version profile, if you wish to have versions created
automatically, or if you wish to generate versions directly when editing the WBS
or networks.

You do not need to define a version profile, if you wish to generate versions
manually from the Structure/Dates information system.

The version profile is entered in the project profile and network profile.

86

Project planning board is a tool in SAP PS which helps and enable you to
process / edit the entire project structure which are WBS element, activities,
relationships, milestones, material components, PS texts, documents and
assigned objects to them.
It is similar to Gantt chart based on interactive SAP environment.
This comprises of hierarchy structure of your project and the corresponding
date situation.
You can custom made the display in project planning board to suite your
requirement.
Project planning board can also be useful for planning dates and resources
i.e. work, external processing, for planning costs using activities.

87

 Project planning board profile contains default values for the appearance
of planning board.
The settings in this project planning board profile is valid for both, simulation
versions and operative projects.
The graphical display can be changed and adapt as per user needs in
the planning board and customization using project planning board
assistant.

88

 Project planning board is a graphical interface based on Gantt chart which can
be used for creating and maintaining data like project definition, WBS element,
activities, relationships, milestones, documents and PS texts.
Useful for Scheduling and monitoring.
You can view date view, and other overviews of project at the bottom of Gantt
chart like capacity overview.
You can view logs, hierarchal graphic of WBS element and Networks and
network activities.
This is the only transaction where we can change simulation versions for
releases earlier than SAP R34.6C, i.e. create of change of WBS elements
in simulation version based on the user specific options.
The entire period in the project planning board screen is called as Evaluation
period which consists of Pre-evaluation period, Planning period and Postevaluation period. These are defined by time settings and determined by 3
profiles which are created in customizing and assigned to project planning board
profile.

89

Assembly processing will be helpful while one is planning and producing or

servicing same product for several times with similar constellations. Which means
the basic structure will be same while data like duration, dates, quantities etc. will be
changing. In assembling processing, a network and WBS element & Project (if
required) is automatically created based on the customization, while a sales
document is created and saved. The project number is derived from Sales
document and this process generates assignment between sales document &
project. This incurs that the same information will be shared by sales and project
team. If the data is changed in Project will update Sales document (and vice versa)
which helps in delays and disagreement between sales and project department.
Process flow:
If a sales order is created for a material which has strategy group for assembly
processing has been assigned, the assembly processing will start.
The MRP processing is omitted in the assembly processing and creates a operative
order (network in case of PS) directly from sales order.
Assembly processing is carried out statically in PS which means only one network
for one sales document item.
Based on the customer requirements date, backward scheduling is carried out and
availability check is done for required material components. Which enables to
inform customer about feasibility of required date or else system will propose new
date.

90

Also, the calculated cost will be transferred from network the sales order.
While saving the sales document, WBS element structure & project definition will
be created which is identified by sales order number.
Since the sales document and the project is directly connected, any changes
one object will update / reflect in other automatically.

90

The requirement class which is assigned with the sales order while creating it will
start assembly processing, one assembly order automatically created by system
and start assembly processing in the back ground. By this method MRP is ignored
and an operational order created directly from Sales Order.
Below is the list of Assembly order which can be created:Network, Production Order, planned order, Plant maintenance or Service order and
Process Order.
Assembly Processing contains all the date of Sales order and assembly order. So
if there is any change done later to any document it will reflects in both document.

91

92

93