sap pp,bom

7/24/2019 sap pp,bom

1/66

For instance In this case the way in which the material can be procureddepends 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 orinternally manufactured.

-Whether the requirements are individualor collective or both

-

Whether the material can be procured inadvance.

The control data of the proect definitiondetermines whether stocks can be built or not

4


2/66

The BOM transfer functionality in SAP PS helps you to assign the material from BOM to

the network activities base on the reference point fiel which is assigne to the material

an network activities!

"BS BOMs can be assigne to Pro#ect BOMs using the BOM Transfer transaction !

The corresponing selection parameters must be chosen to perform the same!

Avantage of BOM transfer functionality is that the changes in the BOM uring the course

of the pro#ect will change in the activities $you nee to run BOM%transfer again every time

you make changes in BOM&!

'ou can also manually assign materials to network activities without reference point fiels!

4


3/66

!eference point : This is the logical link between a "#$ component and anetwork activity. It ensures that the automatic assignment of the materialcomponent happens correctly.

%While the assignments by themselves are proect specific& they can be madesimultaneously for a large number of networks in the proect.

%Individual components& individual "#$ assemblies or a multi level "#$ canbe assigned.

%These assignments can happen manually without reference points as well.

Proceure )or BOM Transfer*

%Field in the "#$ and the network activity which needs to be used asthe reference point needs to be specified.

%These fields must have the same structure in both the obects. Forinstance : '()!& eight digits .

%*ossible entries for the reference point can be defined incustomi+ing.

%!eference points in the "#$ 'omponents and the network activitiesmust be defined.

%The "#$ *, Interface must be started -after changing the "#$

4


4/664

%"#$ 'omponents are assigned to activities in this process.

%*urchase requisitions and reservations are created for the assignedcomponents if !eservation/*urchase !eq. indicator is activated.


5/66

A material that you allocate to activities in a network can be kept in various stocks!,epening on your pro#ect- you can access ifferent types of stock for materials

planning*

Sales orer stock an pro#ect stock are important for controlling purposes $for monitoring

the stock value in a sales orer or pro#ect& an from an M.P point of view $the stocks

are reserve for the sales orer item or "BS element/ other stock elements cannot

access them&!

The various stock types are manage for each material component using the account

assignment category! 'ou efine the account assignment category when you assign the

material to the network activity $popup in manual assignment- strategies in BOM%PS

interface an stanar network&!

The possible account assignment categories epen on the assignment of the network

activity to a stock ob#ect $"BS element or sales orer item&- on the item category for

the assignment $irect procurement for non%stock items& on the material master- which

can e0clue collective or specialist stock management!

As of .elease 4!(A- you can use M.P elements $grouping& to manage a #oint pro#ect

stock for an entire pro#ect or for several pro#ects $this is a rougher metho than managing

stock per iniviual "BS element&!

'ou maintain the account assignment categories possible for network purchase

4


6/664

re2uisitions in customiing!


7/66

nstea of managing the material either in a plant stock or for each iniviual "BS

element an having no control at all over procurement or being fully responsible we

can go for re2uirement grouping! Through re2uirement grouping we can etermine

the egree of control ourselves!

Prere2uisites for using re2uirement grouping *

5aluate group stock

6rouping "BS elements

M.P 6roups that allow re2uirement grouping

Assigne components shoul have perioic lot sies!

The most basic scenario involves grouping the re2uirement of all the "BS

elements in the pro#ect into one "BS element!

Or we can create pro#ects which are only meant for grouping re2uirement of otherpro#ects!

4


8/664


9/66

5aluate pro#ect stock must be allowe in the pro#ect efinition control ata!

"ith the e0ception of automatic re2uirement grouping M.P element inicator

must be set for "BS elements!

M.P groups involve in re2uirement grouping must be etermine in customiing

for the "BS!

(


10/66(


11/66(


12/66

t is common in engineering pro#ects for critical components with long an unreliable

elivery times to be purchase at an early stage in the pro#ect much before the

pro#ect activities in which the components will be use are specifie! Avance

procurement process is use in such situations!

Avance procurement can only be use when you are using sales orer or pro#ect

stock !

(


13/66

Order Categories and order types

,ocuments are use to enter business transactions in the .


14/66(

'ou can assign various SAP orers to a pro#ect/ e0amples inclue internal orers-

prouction orers- an plant maintenance orers! 'ou can then use the pro#ect

hierarchy reports to evaluate these assigne orers with the "BS element!

ach orer is a cost ob#ect with its own costing parameters such as planne costingvariant- actual costing variant- an overhea sheet! The planne costs of assigne

orers are use to etermine the planne costs of the pro#ect!

'ou assign orers to the pro#ect either by assigning a "BS element to the orer

heaer or by assigning the orer to a network an activity as a subnetwork! f the

assignment is re2uire only for cost control an analysis- you nee to assign orer to

the relevant "BS element! f the assignment is re2uire both for scheuling an

cost control- you nee to assign the orer as a subnetwork! The "BS element is

erive from the network activity! >ote that prouction orers cannot be assigne as

subnetworks!

,ocuments are use to enter business transactions in the .


15/66

'ou can use the appene inicator to specify- per orer category- whether an

orer is appene % that is- whether the planne values for the orer are inclue

in the planne value of the corresponing "BS element*

:! f the appene inicator is set- the orer planne value increases the

"BS element planne value! The information system shows the total

as the pro#ect plan! "hen cost planning is taken over as the buget-

the values from appene orers also contribute to the buget!

;! f the appene inicator is not set- the orer planne value is not

ae to the "BS planne value! n bugeting- the plan total for such

orers must be ae manually so that these orers can use funs

later!

(


16/66

'ou can use the appene inicator to specify- per orer category- whether an

orer is appene % that is- whether the planne values for the orer are inclue

in the planne value of the corresponing "BS element*

Once release- all orers are apportione % this means that their plan- commitment-

an actual values are funs assignments against the funs in the pro#ect! The

orer value table contains an inicator which you can use to make orers

apportione earlier- at the create stage!

'ou can set appene an apportione inicator base on the orer category-orer

type- an controlling area

An e0ception to apportionment at release is in the case of networks for preliminary

planning!n Pro#ect System customiing-you can specify network types to be use

for preliminary planning!Preliminary planning networks are never apportione!Their

relate plan values o no increase the assigne value for the relevant "BSelement

n the case of networks $orer category ;9&- you can use the network type

parameters to etermine whether the network is*

@eaer%assigne or activity%assigne % that is- whether costs are manage in

the network activities or collecte in the heaer

(


17/66(

A preliminary planning network whose plan- commitment- an actual values

are not apportione % meaning that they o not appear as assigne values

in the pro#ect!


18/66

Header-Assigned Networks

n a @eaer%assigne networks all the costs $activity an material& are assigne at

network heaer level

After assignment of network heaer to a "BS element- All costs are transferre to

"BS element! Assignment of activities to "BS elements is only to summarie theates

"e you have to use heaer%assigne networks to assign networks to sales orer in

case sales orer are not assigne to pro#ects as no assignments can be mae to a

sales orer item in the network activity!

Activity-Assigned Networks

=osts are collecte on activities in case activites are use as account assigne

ob#ects!Plant


19/66(

Activity account assignment is a special feature of networks! All other orer types are

heaer%assigne! Activity account assignment is controlle via the appropriate

inicator in the table Parameters for network type!

@eaer assigne networks shoul be use when networks are assigne to salesorers without "BS!@eaer assigne networks can also be use when the

enitre network is assigne to a single "BS element


20/66

S, ocument item assignment is controlle via the account assignment category!

The account assignment category is controlle via S, re2uirements type

etermination!

mportant factors that affect account assignment are the strategy group- the M.P

type an item category group from the material master of the prouct as well as

the ocument type of the S, ocument!

The system efaults the item category when you create an orer! 'ou can accept

the efault or overwrite it! Permitte item categories are efine in =ustomiing!

The permitte planning strategies are assigne to the material using the planning

strategy group! This is necessary so that you can fin the correct re2uirements type

in inepenent re2uirements management an sales orer management!

The efault re2uirements type is the main strategy in the planning strategy group!

f no planning strategy group is efine in the material master- the system uses the

item category group $sales an istribution screen in the material master& an- if

necessary- the M.P characteristic to search for the re2uirements type for the salesorer!

(


21/66

The account assignment category etermines the =O ob#ect to which ocument

2uantities an values are assigne! 'ou use it to etermine the following*

?sing the special stock inicator $SS above&- that goos movements in Cogistics use

plant stock- sales orer stock or pro#ect stock!

?sing the consumption posting inicator $=ons! above&- the =O ob#ect to which the

values of a material ocument are assigne!

Settings*

) D =ollective stock- consumption posting to the consumer $orer- activity&

The account assignment category is important for procuring components irectly!

D Euantities an values manage in the sales orer item

This account assignment category is important for make%to%orer prouction without

"BS!

, D Euantities manage using sales orer item- values manage in pro#ects

This account assignment category is important for non%valuate pro#ect

stock- with "BS an sales orer item

E D Euantities an values manage in pro#ects

This account assignment category is important for pro#ect stock

(


22/66(

6 D Plant stock- values manage using pro#ect

This account assignment category is important for sales orer items sol

from plant stock- with

value posting to the pro#ect! t iffers from account assignment category ) in

the fiel control

of the account assignment block!


23/66

Activity%Base =osting offers a facility for allocating an istributing the overhea to its cause!

Activity%Base =osting provies useful information on*

Overheas reuction by process improvement

Profitability increase by highlighting unprofitable proucts or customers

Activity%Base =osting is avantageous for having*

F Transparent overheasF Parallel 2uantity an value flows

F Precise assignment of internal activities to consumer

GPeanut butter effect can be avoie through even istribution of overheas among all

the cost rivers!

+


24/66+

n Activity%Base =osting- processes are the controlling ob#ects! Prices can be either

maintaine manually or using activity an cost input planning in the case of cost

centers an activity types! Through activity base costing- processes are ebite to

cost ob#ects or profitability segments!


25/66

Templates are create in H=ustomiingI an etermine by controlling area- costing sheet-overhea key an template environment $for networks J 994/ for "BS J 99(& for the

function! n the Pro#ect System- templates can be assigne to "BS elements- networks

$heaer assigne&- or network activities! Process costs are allocate to cost ob#ects or

profitability segments by assigning a process template! Process costs are calculate base

on the templates selecte for the pro#ect!

After template selection- the calculation program

etermines the following

Processes in the template relevant for the

pro#ect

F Euantity of each process consume by

the+


26/66+

pro#ect

=alculate value to be ae to the

pro#ect at the start- en or continuously

The price for the process an the allocation cost element are etermine by

entering one process per line in the process template! Multi%level processes can be

mappe by referencing another process template in the working template!

The 2uantity use by the cost ob#ect is etermine using the cost river! This enables

the allocation of the relevant values to all the levels in the process hierarchy as far

as cost ob#ects or profitability segments!

=ost rivers can originate from many ifferent sources in the .


27/66

Actual prices for activity types an business processes are calculate in Overhea

cost controlling at the en of the perio!

Actual prices D Actual costs < Euantities consume

The possibility of revaluation at actual prices an its specification for each

activity type are controlle in =ustomiing in the parameters for the actual

version epening on the fiscal year!

The ifference between the actual price an the originally allocate price is

charge to the cost ob#ects!

.evaluation at actual prices for activities an business processes can be one

in the Pro#ect System an in the =ost Ob#ect =ontrolling!

.evaluation at actual prices using an activity type is illustrate in the e0ample given

in the slie

+


28/66

Overheas calculation is use to allocate overhea costs to cost ob#ects such as activities

an "BS elements! =alculations are one base on the =osting sheet entere in

the cost ob#ect an the overhea key entere on the "BS element-network heaer or network activity! Overheas can be calculate for

planne- commitment an actual values! Overhea calculations are

one using the 2uantity base or percentage allocation rates!

The following postings get generate through overheas allocation*

,ebits to cost ob#ect $"BS element- >etwork heaer or>etwork activity &

=reits to cost center $ overhea orer or process &

+


29/66+

Overhea costs are upate using the seconary cost elements

in the costing sheet creit rows an these can be simulate also!


30/66

=osting sheet is erive by means of the costing variant from the Parameters for

>etwork Type table- in the case of networks! The costing sheet an the overhea key

can be change in the network heaer!

The costing sheets to be use in the activities are mae a efault through this!

)or "BS elements- the costing sheet is erive irectly from the pro#ect profile! n

the case of asy =ost Planning an the unit costing for "BS elements- the cost

planning raws on a costing sheet for a costing variant which is assigne to the

pro#ect profile through the planning profile!

Overhea keys for activities are inherite from their respective "BS elements!

+


31/66

Overheas are calculate using a costing sheet!

The overhea surcharge can either be a percentage if it is value riven or an absolute value

of measure if it is 2uantity riven! The overhea is calculate against a base which is efine

by the cost elements! =ost elements or cost element areas are collecte in base lines!

)actors such as =ontrolling area- company coe- plant- overhea group- network type- time

perio an plan versus actual etermine the overhea rate applie! Overhea key assigne

to the cost ob#ect ecies the etermination of overhea group in customiing! Thus a single

costing sheet with fle0ible rates can be mae use of ifferent organiational units or

iniviual activities!

+


32/66+

networks


33/66

?nit costing is one to calculate cost plan per "BS element! @ere we use

planne 2uantities instea of cost!

t is not perio epenent

At cost element level- plan values are isplaye

nput information relate to sources of supply- 2uantities an prices mark the useof unit costing to generate cost plan per "BS element

+


34/66

Structure Oriented Planning

Simplest type of planning is structure base planning! Plan values are isplaye

in hierarchy

The total cost planne is aggregate

t is neither by cost element nor is perio specific

5arious views are use to isplay the ifferent values in structure%oriente

planning

Planne total 5iew%this shows total aggregate at superior "BS element $Cevel

: "BS element&

The istributable or istribute view%This view is use to check istribution of

buget among chil "BS element

=umulative or remainer view%This view is use to check istribution of buget

across years

Orer


35/66+

package scheule is change

This planning is aopte if precise information is available as it becomes sure not

to rescheule


36/66

The plan profile is use to control overall cost


37/66+

relevant if we are using unit costing an easy cost planning

=O plan version is re2uire to be specifie if we are using easy cost planning!

Planner profile an planning layouts are specific to use of etailing planning

using Gcost element


38/66

Planning profile is contains the settings for overall planning- etaile planning

an unit costing

,etails for each fiel can be checke using

): mportant fiel etails are as*

Total 5alue* ,efines overall planning without any reference to fiscal year

Annual Planning* ,efines overall planning with reference to fiscal year

Bottom up Planning* Overall planning values are e0trapolate after saving

0change rate type* ,etermines which e0change rate is to be use for currency

conversion of overall values

1


39/66

Transaction OT to eit costing an valuation variant

=osting variant is mostly use for unit costing -easy cost planning an also use for

costing networks! The fiel costing type etermines for which "BS element

$costing ob#ect& costing is one

5aluation variant etermines the prices an rates! n the above mentione slie-system will first check for GPlanne price :L if it fails- system will check for Gstanar

priceL an again if it fails it will check for Gmoving average priceL from material

master! f system now fails- it will trigger an error message uring cost etermination

1


40/66

!nternally-processed activities

f no istribution key or work center is maintaine in the activity- the costs are istribute

evenly over the earliest ates in the activity! 5aluation is at the rate in the valuation variant!

,epening on the strategy being use- the system can etermine the most current ate!

valuation is etermine by the rate maintaine in the valuation variant! Base on the

strategy aopte- system etermines the latest ate! f no work center


41/661

istribute to the perios base on the istribution key maintaine in the activity

=ase 3*nvoicing plan not maintaine an istribution key not maintaine*The

costs are istribute evenly over the earliest ates in the activity

f an invoicing plan has been maintaine- the values in the perios are set

as specifie in the invoicing plan!

Otherwise- the activity value is istribute to the perios using the istribution key in

the activity! f no istribution key is maintaine in the activity- the costs are istribute

evenly over the earliest ates in the activity!

Service activities or e"ternally-processed activities

=ase :*nvoice plan maintaine*the values in perios are as per the

values mentione in invoicing plan

=ase ;*nvoicing plan not maintaine*The activity value is set in the perio of the

latest activity start ate!Also the system etermines the price from the purchasing info

recor or the activity value!

nvoicing plan has priority for the values

f an invoicing plan has been maintaine- the values in the perios are set

as specifie in the invoicing plan!

Otherwise- the activity value is set in the perio of the latest activity start

ate!

The invoicing plan has priority for the values! f no invoicing plan has been

maintaine- the system etermines the price from the purchasing info recor or

the activity value!

#aterial components

=ase :*nvoice plan maintaine*the perios an -in some cases-values are

taken from invoicing plan

=ase ;*nvoicing plan not maintaine*The system etermines the price from the

purchasing info recor or the price is taken from material master as per

valuation variant!@ere material re2uirement ate etermines the perio

f an invoicing plan has been maintaine- the perios an- in some cases- the

values are taken from the invoicing plan! f no invoicing plan has been maintaine-

the values are taken from the purchasing info recor or the price is taken from the


42/661

material master per the valuation variant! n this case- the perio is that from

the material re2uirements ate!


43/66

The customer accepts the 2uotation! A sales orer is create in the system- where

appropriate using the 2uotation as a template! The activities liste in the 2uotation

are entere in the sales orer as sales orer items!

The items are assigne to the pro#ect! They are use for revenue planning an for

posting revenues to the pro#ect by means of milestone billing!

Two companies are responsible for e0ecuting the pro#ect % ,S A6 an ,S ?!

,S ? creates a sales orer for ,S A6 an assigns the ocument item to the

billing element T%:99NN!:!;!

Cater on- ,S ? bills its services to ,S A6 on a resource%relate basis!

A billing re2uest is create in the system via resource%relate billing! This is bille an

results in revenues for ,S ?!

1


44/66

n SAP where pro#ect is a controlling ob#ect*

Sales orer create an after structuring of pro#ect sales orer will account assigne to"BS! Then revenue planne in sales orer!

Once "ork complete in pro#ect- actual cost capture in "BS an )inal prouct will

be elivere to =lient!

Billing will be complete an actual revenue generate! Actual .evenue will

be transferre to "BS!

"hile .esult analysis performe for pro#ect the Actual .evenue an =ost will settle

to the profitability segment!

Sale document structureF Sales ,ocument type represents the type of business transaction an functions an

the flow of ocument with in sale orer! Processing!

F tem =ategories are assigne to sales ocument category! "hile creation of Sales orer

it will efault the item category but user can change it as per re2uirement!

F Scheule line category is assigne to tem =ategory! "hile creation of ocument

system will efault the scheule line category but it can change accoring to

re2uirement!

1


45/661

!tem Category

F Item Category is determine by Sales Document type and thematerials Items category group in a sales order.

F Item Category controls function for Sales Order like Item Type,Pricing, illing Plan, resource related or deli!ery related.

F It controls if pricing is rele!ance for billing, rele!ance for Deli!erySchedule "ine Item, and contains Incompletion "og and Partner te#t.


46/66

$:&.epresents a process of make%to%orer prouction without a work breakown structure!

n this case- the sales orer item is the contolling instrument! Account assignment category

specifies that the sales orer item forms a separate =O ob#ect!

=osts an revenues of the sales orer item are usually settle to the profitability segment!

$;&?sing assembly processing- you can generate a network when you create the sales orer!

"hen you save your ata- the system creates a "BS an assigns the sales orer item to a

"BS element in this "BS! n this case- the sales orer epicts the sales view- the pro#ect is

the controlling instrument- an logistical processing is represente by the network!

Account assignment categories , or E $=ons! D P in each case& specify that revenues

are assigne to the billing "BS element of the pro#ect!$3&As an alternative to assembly processing- you can assign a sales orer item to a "BS

element in a pro#ect! =ontrolling takes place in the pro#ect! 'ou can assign orers or

ocuments to the pro#ect! 5alue assignment to the pro#ect is controlle via account

assignment categories 6- , an E! These iffer from each other in the way that they

manage 2uantities!

1


47/66

Methos for plan revenue in a pro#ect are*

a! Manual revenue planning* this can be base on structure or revenue element

where the later is a cost element an perio base!

b! PS billing plan* this is cost element an perio base planning!

c! S, ocument* this is part of integration with S, moule where sales orer itemor 2uotation items are use as revenue planning! This kin of planning is cost

element an perio base!

1


48/66

.evenues can be planne in pro#ects using the following methos*

Manual planning in billing elements in the pro#ect structure!

This type of planning can follow the same proceure as cost planning- or can be by

revenue element!

Sales orers $all S, ocuments assigne&!

Sales orer items are assigne to "BS elements! n =ustomiing- you can stipulate- for a

combination of sales ocument category $2uotation- orer- an so on&- sales

ocument type- controlling area- an system status- whether the billing ata $for

e0ample- in a billing plan& from a sales orer shoul upate the revenue plan for an

assigne "BS element! The ates an planne revenues concerne originate eitherfrom the billing plan for the sales orer items or $if there is no billing plan& from the

net value an apportionment ata for the item! The revenue element originates from

6


49/66

There are ifferent ways of creating billing plans*

Manually

By copying a reference billing plan

n S, an PS- reference billing plans can be

calle upon automatically

By copying billing milestones from work

breakown structures or networks

By copying billing milestones automatically from

the network in assembly processing

1


50/66

n the S, ocument- you can efine a etaile billing plan with a number of billing ates

instea of #ust a single billing ate! A billing plan is a scheule containing iniviual billing

ata for a particular sales ocument!

Milestone billing is wiely use in pro#ects $for e0ample- construction pro#ects&!

f you use milestone billing- the total value to be bille is apportione to the iniviual ates

in the billing plan per efine rules!

Billing plan ates can be blocke for billing

'ou can set billing blocks manually or remove them by activating billing milestones!

As of .elease 4!9- billing plans can also be entere for billing elements in pro#ects! Such

billing plans can- if re2uire- be copie to the sales orer later $make sure you elete

any e0isting billing plan in the billing element/ if you o not- the planne revenues will be

etermine via the PS billing plan an not the S, billing plan&!

A billing plan can contain own payment ates! These ates affect payment- but not

revenue!

1


51/667


52/66

The term Version" is use in the pro#ect system in ifferent conte0ts! ,ifferent

types of versions inclue simulation versions- pro#ect versions an =O planning

versions are available in SAP Pro#ect System which are iscusse below.

Pro#ect versions- are snapshots of a pro#ect at a specific point in time- an are

use for ocumenting the progress of a pro#ect over time! Both 2uantities an

values are store in versions an it can be create either manually- or

automatically when a status changes! n the case of status change- the pro#ect

profile contains a reference to a version profile which specifies the name of

the pro#ect version to be create when a particular user or system status is

set!

Simulation versions* n the Pro#ect System- these are versions that you can

change! 'ou might- for e0ample- create simulation versions in the following

situations*

n the 2uotation phase* generally speaking- at this stage there is not yet

an operative pro#ect!

To raw up alternative planning scenarios for e0isting operative pro#ects

or parts of these!

=O plan versions are use to plan revenues an costs! 'ou can copy values

from one version to another! 'ou can change planne values manually in every

version an cost values are retaine!

7


53/66

Simulation versions are use to raw up alternative what if planning

scenarios! They are create manually- can be change- an- if necessary-

elete again which is unlike release operative "BSs with activities!

Simulation versions are useful uring the 2uotation phase of a pro#ect

an possible to plan several simulation versions!

'ou can create simulation versions even at the time of e0ecution of pro#ect-

where you can copy from operative to simulation versions- compare- analye

an work with other versions an transfer them back to the operative

pro#ect!

"hen an operative pro#ect is copie to a simulation version or vice versa- a

log file is create which contains the ob#ects that were transferre an any

error messages that were issue in the process!

Simulation versions can be create either for an entire "BS- or for

sub% hierarchies of a "BS!

Simulation versions are eite in the pro#ect planning boar or in pro#ectplanning boar from SAP .


54/66

Simulation customiation consists of two steps*

:! 5ersion keys* one shoul work with permissible version keys since these cannot

be elete once simulations has been create!

;! Simulation profile* This etermines which all ob#ects will be copie while creating

simulations $in aition to the structure information& from simulation tooperative $an vice versa&! f there are no simulation profile- all the te0ts will be

copie! The simulation profile will be efaulte in the pro#ect ue to assignment

in pro#ect profile!

ust like pro#ect version- simulation versions can be compare with each other in

information system- whereas the cost element report oes not support the

simulation versions! ?nlike operative pro#ects- simulation versions cannot be

change in structure info system!

7


55/66

"hen you transfer ata from operative pro#ects to simulation versions $or

vice versa&- the following ob#ects are copie*

"ork breakown structure

>etwork with activities- activity elements- relationships- an

subnetworks Milestones

Materials for the activity

,ocuments- PS te0ts an long te0ts $epening on the simulation profile

use&

=apacity re2uirements

nvoicing plan for the network- an billing plan for the "BS element

$as of .elease 4!(A&

The following ob#ects are not copie*

Other orers $e!g! no prouction orers&

Prouction resources


56/66

Pro#ect versions enable you to recor a snapshot of a pro#ect at a specific

moment in time % this can be use for future comparison with the

operative pro#ect!

'ou can create a pro#ect version automatically $i!e! triggere by a system or user

status&!

'ou can also create a pro#ect version manually*

"hile changing the "BS

"hile changing the network

n the Structure;; or "BS element maintenance =9;

,ata transfer which is nepenent of version profile an epenent on

atabase profile*

3! T= =>1: an =>1;

4! Structure information system

7


57/667

The version profile is maintaine in the PS customiation an assigne to

Pro#ect profile or network profile!


58/66

'ou use a version profile to efine two ifferent kins of information! )irst- you

specify which version is create automatically when a specific system status or

user status is set! Secon- you specify which ata is to be written to the

versions that are create automatically!

'ou nee to efine a version profile- if you wish to have versions create

automatically- or if you wish to generate versions irectly when eiting the "BS

or networks!

'ou o not nee to efine a version profile- if you wish to generate versions

manually from the Structure


59/66

Pro#ect planning boar is a tool in SAP PS which helps an enable you to

process < eit the entire pro#ect structure which are "BS element- activities-

relationships- milestones- material components- PS te0ts- ocuments an

assigne ob#ects to them!

t is similar to 6antt chart base on interactive SAP environment!

This comprises of hierarchy structure of your pro#ect an the corresponing

ate situation!

'ou can custom mae the isplay in pro#ect planning boar to suite your

re2uirement!

Pro#ect planning boar can also be useful for planning ates an resources

i!e! work- e0ternal processing- for planning costs using activities!

7


60/66

Pro#ect planning boar profile contains efault values for the appearance

of planning boar!

The settings in this pro#ect planning boar profile is vali for both- simulation

versions an operative pro#ects!

The graphical isplay can be change an aapt as per user nees inthe planning boar an customiation using pro#ect planning boar

assistant!

7


61/66

Pro#ect planning boar is a graphical interface base on 6antt chart which can

be use for creating an maintaining ata like pro#ect efinition- "BS element-

activities- relationships- milestones- ocuments an PS te0ts!

?seful for Scheuling an monitoring!

'ou can view ate view- an other overviews of pro#ect at the bottom of 6anttchart like capacity overview!

'ou can view logs- hierarchal graphic of "BS element an >etworks an

network activities!

This is the only transaction where we can change simulation versions for

releases earlier than SAP .34!+=- i!e! create of change of "BS elements

in simulation version base on the user specific options!

The entire perio in the pro#ect planning boar screen is calle as valuation

perio which consists of Pre%evaluation perio- Planning perio an Post%

evaluation perio! These are efine by time settings an etermine by 3

profiles which are create in customiing an assigne to pro#ect planning boarprofile!

7


62/66

Assembly processing will be helpful while one is planning an proucing or

servicing same prouct for several times with similar constellations! "hich means

the basic structure will be same while ata like uration- ates- 2uantities etc! will be

changing! n assembling processing- a network an "BS element K Pro#ect $if

re2uire& is automatically create base on the customiation- while a sales

ocument is create an save! The pro#ect number is erive from Salesocument an this process generates assignment between sales ocument K

pro#ect! This incurs that the same information will be share by sales an pro#ect

team! f the ata is change in Pro#ect will upate Sales ocument $an vice versa&

which helps in elays an isagreement between sales an pro#ect epartment!

Process flow*

f a sales orer is create for a material which has strategy group for assembly

processing has been assigne- the assembly processing will start!

The M.P processing is omitte in the assembly processing an creates a operativeorer $network in case of PS& irectly from sales orer!

Assembly processing is carrie out statically in PS which means only one network

for one sales ocument item!

Base on the customer re2uirements ate- backwar scheuling is carrie out an

availability check is one for re2uire material components! "hich enables to

inform customer about feasibility of re2uire ate or else system will propose new

ate!

8


63/668

Also- the calculate cost will be transferre from network the sales orer!

"hile saving the sales ocument- "BS element structure K pro#ect efinition will

be create which is ientifie by sales orer number!

Since the sales ocument an the pro#ect is irectly connecte- any changes

one ob#ect will upate < reflect in other automatically!


64/66

The re2uirement class which is assigne with the sales orer while creating it will

start assembly processing- one assembly orer automatically create by system

an start assembly processing in the back groun! By this metho M.P is ignore

an an operational orer create irectly from Sales Orer!

Below is the list of Assembly orer which can be create*%

>etwork- Prouction Orer- planne orer- Plant maintenance or Service orer an

Process Orer!

Assembly Processing contains all the ate of Sales orer an assembly orer! So

if there is any change one later to any ocument it will reflects in both ocument!

8


65/668


66/66

Documents

sap pp,bom