CompRef8 / SAP®ProjectSystemHandbook/KieronDowling/0-07-154450-X/Chapter4
4
CHAPTER
Features of Project System
P
ShasmanyfeaturesyoucanusetodevelopaBlueprintforaclient.Theyarethe
buildingblocksthatformthebasisofyourdesign.Thefollowingpagesexplainthe
elementsPSoffersformanagingaproject.Toassistyouinfindingwheretoconfigure
andoperatethesefeatures,transactionreferencesareprovidedaftereachfeaturedescription
laterinthischapter.
PScanbedividedintoseveralprogressive“workingelements.”Insummary:Youneed
aStructureinordertoPlanCostsandResource,whichcanbethebasisforaBudget.In
ordertoScheduleandTimetheworktobedone,youneedDatesandResources,whichmay
ormaynothaveaCapacitytoperformthework.Ifyouwanttogetpaidforwhatyou
manufactureorsell,youneedaRevenuePlan.Whenyou’rereadywithyourPlanning,you
goaheadandExecutetheprojectbychangingitsStatus.Periodically,youmonitoryour
ProgressandSettleyourActualstothecorrectFinancialreceiversotheproject“sheds”its
values.
R EMEMBER ProjectsareatemporaryrepositoryforCostsandRevenues—theyhaveasetlifeand
aresubjecttoclosurewhenallworkiscompleted,butcannotbeclosediftheystillhaveunsettled
values.
Structural Elements
Coding Masks
Project Profiles
Project Definition
WBS Elements
Templates
Milestones
Networks
Internal Orders
Attachments and PS Text
37
ch04.indd37
2/1/0812:40:07PM
CompRef8 / SAP®ProjectSystemHandbook/KieronDowling/0-07-154450-X/Chapter4
38
SAP Project System Handbook
Cost/Resource Planning
Structure Cost Planning (WBS)
Detailed Cost Planning (WBS)
Detailed Cost Planning (Network)
Easy Cost Planning (WBS)
DIP Profiles
Plan Versions (CO)
Statistical Key Figures
Overheads (CO)
Value Categories
Budgeting
In Projects
In Investment Programs
Availability Control
Time and Capacity Planning
Dates in WBS
Scheduling in Networks
Work Centeres and Activity Types
Workforce Planning
Revenue Planning
Structure Revenue Planning
Detailed Revenue Planning
Sales Orders (SD)
Execution
Status Management
Actuals
Simulation
Versions
Period-End
Settlement
Period-End
Progress
Archiving
Billing
StructuralElements
Aprojectcannotexistwithoutastructure.Ataminimum,youneedaProjectDefinitionplus
atleastoneWBS.Thesetwoelementsarewhatmakeupthebasisofaproject.Extending
yourprojecttoincludeNetworksmakesitmorecomplexandusuallymeansyouneed
schedulingandcomplexmaterialhandling.However,someimplementationsonlyuseWBSs
toplanandcapturecosts.Inallcases,itiswise(thoughnotmandatory)tohaveamethod
bywhichyourWBSstructureisrecognizedbyitsvariouslevels—henceCodingMasks.
ch04.indd38
1/28/084:05:10PM
CompRef8 / SAP®ProjectSystemHandbook/KieronDowling/0-07-154450-X/Chapter4
Chapter 4:
Features of Project System
39
Dependingontheimplementation,amaskthatcarriesintelligence(thatis,itcontains
numbersandlettersthatmeansomethingtothebusiness)maynotbethebestapproach,as
oftenthecodingbecomesredundantovertime.
CodingMasks:HowProjectNumbersAreCoded
CodingMasksareimportantasfollowsifyouneedtohavesomeintelligenceintheway
yourProjectDefinitionandWBSElementsappeartotheuser:
• Therecanbemany.
• Theycanreflectthestructureofaproject.
• Theycancontrolprojectidentification.
• TheyonlyrelatetoProjectDefinitionsandWBSElements.
• Theydeterminewhatspecialcharactersarepermittedtoseparatethestructureview.
• TheyarenotconnectedtoProfiles—the“ProjectID”usedinOperativeorTemplate
projectsdeterminesthemask.
• DifferentMaskscanbeusedwithoneormanyProjectProfiles.
NOTE Thisinformationisprovidedtoassistyouinfindingconfigurationpointsandwherethe
functionalitymaybefoundintheoperationofPS.Itisnotalwaysclearwhereeitherisfound
becausethefunctionalitymaybeembeddedwithinatransaction,sopleaseuseitasaguideonly.
Customization:
OPSK, OPSJ
Operation:
CJ20N
ProjectProfiles:HowaProjectShouldBehave—WhatIt’sAllowedtoDo
AProjectProfileismandatorywhencreatingaproject:
• Therecanonlybeoneperproject.
• Theycontainthecontrolparametersusedinaproject:Businessrules,
Organizationalsettings,andsoon.
• Theyinfluenceaproject’sbehaviourbyprovidingdefaultinformation.
Theycarry“subprofiles”thatfurtherinfluenceaproject:
• VersionProfile
• PlanningProfile
• BudgetProfile
• InvestmentProfile
• StatusProfile
• SimulationProfile
• NetworkProfile
andsoon.
ch04.indd39
1/28/084:05:10PM
CompRef8 / SAP®ProjectSystemHandbook/KieronDowling/0-07-154450-X/Chapter4
40
SAP Project System Handbook
Customization:
OPSA
Operation:
CJ20N
ProjectDefinition:WhataProject’sDefaultsAre
Whenaprojectiscreatedforthefirsttime,allsettingsfromtheProjectProfilearecopied
intotheProjectDefinition:
• ItcannotPlanCostsorRevenues.
• ItcannothaveCostsorRevenuespostedtoit.
• Itisthe“Header”oftheProject.
• TherecanonlybeoneProjectDefinitionforaproject.
• SubsequentlycreatedWBSElementswillalwaysinheritkeyorganizationaland
profiledatafromtheProjectDefinition(butthesecanbechangedmanually).
Customization:
OPSA
Operation:
CJ06, CJ20N
WBS(WorkBreakdownStructure)Elements:TheHierarchicalStructure
AWorkBreakdownStructurerepresentsthestructuralrelationshipthatworkelementsofa
projecthavewitheachother:
• Itisamodeloftheworktobeperformedinaprojectinahierarchicalstructure.
• Itformsthebasisfororganizationandcoordinationinaproject.
• Itcarriesthedatesassociatedwithapackageofwork.
WorkBreakdownStructurescanberepresentedinavarietyofways:
• Logic-OrientedaccordingtoPHASE(Plan,Define,Acquire,andsoon).
• Function-OrientedaccordingtoFUNCTION(Engineer,Construct,Commission,
Support,andsoon).
• Object-OrientedaccordingtoPHYSICALobjects(Asset,Assetcomponents,and
soon).
• WBSElementscanhavecostsplannedandpostedtothem.
• WBSElementscanhaverevenuesplannedandpostedtothem.
• WBSElementscanhaveacontrolledBudget.
ch04.indd40
Customization:
OPSA
Operation:
CJ01, CJ11, CJ20N
1/28/084:05:11PM
CompRef8 / SAP®ProjectSystemHandbook/KieronDowling/0-07-154450-X/Chapter4
Chapter 4:
Features of Project System
41
Templates:HowaProjectShouldLook
AtemplateisaneutralstructurethatcanbeusedtostandardizeWBSstructures,Networks,
andMilestones:
• TemplatesareMasterData.
• Youcanhavemanytemplatestoreflectdifferentprojectscenarios.
• ProjectandNetworkTemplatescontainaProjectorNetworkProfile.
• Templatescancontaininherentbusinessrules.
• Templatesarenotmandatory(unlessyouareusingAssemblyProcessing),butif
youhavecommon,complexstructures,theyhelpmaintainconsistency.
• OperativeProjectsandtheirNetworkscanbeusedastemplates,butareproneto
inheritingerrorsinstructure.
• WithAssemblyProcessing,ProjectsarecreatedinthebackgroundfromaSales
Order,soyoumusthaveStandardWBSsandStandardNetworks.
• MilestoneTemplates(StandardMilestones)canbeattachedtoStandardWBSsand
StandardNetworks.
• StandardTemplatesdonotcarrySettlementRules.
Customization:
UPUI, OPUH
Operation:
CJ92, CN02
Milestones:ThingsaProjectMustRemembertoDo
Milestonescarrydatesandfunctionsthatcanbetriggeredinthefuture:
• TheycanbeattachedtoaWBSoraNetwork(withslightlydifferentfunctionality).
• Intheirsimplestform,Milestonescanjustbereminderdates.
• Intheirmostcomplexform,Milestonescanbeusedfor:
• AutomatictriggeringofCustomerBilling(byPercentageorAmount).
• PresetCustomerBillingPlan(bysetamount).
• Automatictriggeringofsubsequentevents,suchastheReleasingofarelated
NetworkActivity.
• MilestonescantriggeraWorkflowmessagetoremindthereceiverofanevent.
• MilestonesformthebasisofSAP’s“MilestoneTrendAnalysis”reportingfunction.
• WhenAssemblyProcessingisusedtocreateauto-projects,andMilestonesexistin
theStandardNetworks,theSalesOrderBillingPlanisautomaticallycreated.
• BillingissensitivetotheDateCategoriesconfiguredinMilestones:
• ByPercentage
• ByAmount
ch04.indd41
Customization:
OPSR, OPT6
Operation:
CN11, CJ20N
1/28/084:05:11PM
CompRef8 / SAP®ProjectSystemHandbook/KieronDowling/0-07-154450-X/Chapter4
42
SAP Project System Handbook
Networks(Part1):HowtoCarryOutTasks
inaSpecificWay,Order,andTimePeriod
NetworksareusedtoprovideforschedulingofActivitiesinaproject:
• UnlikeWBSElements(whichcanonlybeconnectedinalinearfashion),Network
Activitiescanbeconnectedtooneanotherusingspecialdependenciescalled“Start/
Finish”rules.
• Networkshaveathree-tierstructure:
• NetworkHeader
• NetworkActivity
• ActivityElement
• Networksareidentifiedbyauniquenumber.
• NetworkActivitiesareidentifiedbytheirowningNetworkNumberplusa
sequentialnumber.ActivityElementsareidentifiedbyafurthersequentialnumber.
• Networksarenot“effective”untiltheyareReleased.
Customization:
OPUU, OPSC, OPUV, OPSU, OPU6
Operation:
CN21, CJ2D, CJ20N
Networks(Part2):WhatMaterialsandResources
AreNeededtoCarryOutaTask
NetworkActivitiescanperformanumberofcomplextasks:
• Plan/ReceiveCosts.
• Order/ReserveMaterialsandServices.
• BookResources.
• Scheduletasks.
• TherearethreetypesofActivity,plusspecialsettingsforService:
• Internal—forplanningInternalresourcessuchaslabour
• External—forplanningexternallyprocuredServicesorContracts
• GeneralCost—forplanningbyCostElement
• Service—forplanningServices(forexample,Contractors)
• ActivityTypesareattachedtoNetworksbyusingControlKeys.
• SubnetworksareothertypesofOrders(suchasMaintenanceorCSOrders)that
havebeenmanuallyassignedtoaWBSorNetwork.
ch04.indd42
Customization:
OPUU, OPSC, OPUV, OPSU, OPU6
Operation:
CN21, CJ2D, CJ20N
1/28/084:05:11PM
CompRef8 / SAP®ProjectSystemHandbook/KieronDowling/0-07-154450-X/Chapter4
Chapter 4:
Features of Project System
43
Networks(Part3):InternalActivities—PlanningInternalResources
• InternalActivitiesaredefinedbyControlKeys.Usually,theyutilizetwoobjectsto
makethemeffective:
• WorkCenter—forCapacityPlanning
• ActivityType—forpricingofresources
• WorkCentersareindependentlymanagedobjects.Theycanbeanindividual,a
groupofpeople,orapieceofequipment.Theyexisttohelpmanage“Capacities”
andtocarryalltheinformationrequiredtodetermineavailableCapacitiesandto
provideforCapacitylevelling.
• ActivityTypesareindependentlymanagedobjects.TheybelongtoCostCenters.
Theyareattachedtoa“PricingSchedule,”meaningtheyhaveaplannedcostper
unit(whichcanbeastandardUnitofMeasure).
• WhenWorkCentersandActivityTypesareusedinconjunction,theyeffectively
“PlantheResource”and“PlantheCost”atthesametime.
• CostsassociatedwithaNetworkActivityaggregatetotheWBStowhichtheyare
assigned.
• InternalActivitiescanhaveattachedasetofComponentsorBOMs(BillsofMaterials).
Customization:
OPUU, OPSC, OPUV, OPSU, OPU6
Operation:
CN21, CJ2D, CJ20N
Networks(Part4):ExternalActivities—PlanningExternalResources
ExternalActivitiesarethebasisforexternallyprocuredresourcesincludingServicesand
Contracts.TheyaredefinedbyControlKeys.
• ExternalActivitiescanhaveattachedasetofComponents(Materials)orBOMs
(BillsofMaterials).
• CostsassociatedwithanExternalActivityaggregatetotheWBStowhichtheyare
assigned.
• When“Released,”ExternalActivitiestriggerevents:
• APurchaseRequisitioniftheMaterialComponentis“Non-stock”(becomesa
commitment).
• AReservationiftheMaterialComponentis“Stock”(AssignedCost).
• AReservationiscancelledwhenaNetworkActivityis“TechnicallyClosed.”
• APurchaseRequisition/OrderremainsopenwhenaNetworkActivityis
“TechnicallyClosed.”
• SomeExternalActivitiesare“Services.”Servicesareregardedasbeingconsumedat
thetimeoftheirperformance.Theycannotbestoredortransported,forexample,
constructionwork,cleaningservices,legalservices.
ch04.indd43
1/28/084:05:11PM
CompRef8 / SAP®ProjectSystemHandbook/KieronDowling/0-07-154450-X/Chapter4
44
SAP Project System Handbook
• TheycanhaveapreliminaryTotalPlannedCostthatisreducedasandwhen
MaterialComponentsareadded.
Customization:
OPUU, OPSC, OPUV, OPSU, OPU6
Operation:
CN21, CJ2D, CJ20N
Networks(Part5):GeneralCostActivities—PlanningUnspecifiedCosts
GeneralCostActivitiesarethesimplestformofCostinginNetworks.Theyaredefinedby
ControlKeys:
• TheycarryanAmountinthecurrencyselected.
• TheyrequireaCostElementtodeterminewhattypeofcostisbeingplanned.
• TheycanhaveattachedasetofComponentsorBOMs(BillsofMaterials).
• Inthemselves,theydonotgenerateanyPurchasingDocuments.However,if
MaterialComponentsareattached,theywill.
Customization:
OPUU, OPSC, OPUV, OPSU, OPU6
Operation:
CN21, CJ2D, CJ20N
Networks(Part6):MaterialComponents—PlanningMaterials
MaterialComponentsrepresentthephysicalmaterialsyouneedtoplanforwithinan
Activity:
• ComponentscanbeaddedtoanyActivity.
• ThereisnorestrictiononhowmanyMaterialsyouhave.
• TheyformthebasisofallyourProjectProcurement(unlessyouareusingEasyCost
Planning).
• TheycarrythemethodsbywhichMRPwillorderMaterials.
• TheycanbeStockorNon-stock.
• EachMaterialComponentcantriggeraReservation/Requisition.
• TheyformthebasisofMaterialProjectCostPlanning.
• AllMaterialComponentsbelongtooneActivityatatime.
Customization:
OPUU, OPSC, OPUV, OPSU, OPU6
Operation:
CN21, CJ2D, CJ20N
InternalOrders:ObjectsthatCanBeAssignedtoaProjectStructure
InternalOrders(IOs)are“ProjectIndependent”unlessassignedtoaWBSorNetwork
Activity.TheybehaveinasimilarwaytoasingleWBSElement,except:
• Theydonothaveastructureandarenothierarchical.
• Theycannotbescheduledandarenottime-oriented.
ch04.indd44
1/28/084:05:12PM
CompRef8 / SAP®ProjectSystemHandbook/KieronDowling/0-07-154450-X/Chapter4
Chapter 4:
Features of Project System
45
• TherearethreetypesofIO:
• Type1—Controlling
• Type2—AccrualCalculation
• Type3—ModelOrder
• IOscanhavecostsplannedandpostedtothem.
• IOscanhaverevenuesplannedandpostedtothem.
• IOscanhaveacontrolledBudget.
• IOscanbeSettled.
Customization:
KOT2_OPA
Operation:
K004
AttachmentsandPSText:AttachmentstotheProjectStructure
AttachmentscanbemadetoWBSelementsandNetworkActivities.SAPalsopermits
attachmentofStandardText,calledPSText:
• Documents
• Documentsaresimple“hyperlinks”orURLreferences.
• Theycanbeofanyextensiontype—Word,Excel,Access,andsoon.
• Therecanbemany.
• Youcanalsocreatea“PrivateNote”asanon-hyperlinkedattachment.
• Youcan“Send”documentsandmessagestootherusers.
• PSText
• Ispredefinedwithadescription.
• CanbeattachedtoaWBS.
• CanbeassignedtoaTemplateforautomaticinclusioninaProject.
Customization:
OPS3
Operation:
CJ20N
CostandResourcePlanning
Anyplanningyoumayperformisdeterminedbytheamountofdetailyouneed.Froma
Costperspective,planningcanbeassimpleasenteringaplannedvalueagainstaWBS.
Moredetailisachievedbyspecifyingwhereexactlythecostsmaybeincurred(Cost
Element)andexactlyhowmanyUnitsyouwanttoplanfor(UnitCosting).Evenmore
detailcanbeappliedbyplanningataNetworklevelbyMaterialandthenintegratingit
withCO,sothesourceCostCentersareinformed.
ResourcePlanningismainlyaboutthepeople(orroles)youmaywanttoplanforvia
WorkCentersandActivityTypes.ThistypeofplanningoptionallyinvolvesCapacity
Planning,whereyoumayshareresourcesfromanotherdepartment.
ch04.indd45
1/28/084:05:12PM
CompRef8 / SAP®ProjectSystemHandbook/KieronDowling/0-07-154450-X/Chapter4
46
SAP Project System Handbook
Further,youmaywanttoplanvalueswherethereisnocostinvolved,onlyavaluethat
representsvolumesorquantitiesbasedonUnitsofMeasure.Thesetypesofplanscanbe
usedtogenerateCustomerInvoicesviaStatisticalKeyFigures.
RememberthatallplanningdatatotalsarekeptinPlanVersionsagainsttherelevant
object(WBSandNetwork).
StructureCostPlanningviaWBS:DirectEntryofCosts
AgainstaWBSStructure,WithoutRegardtoCostElements
TheseareCostsassociatedwiththeWBSasawhole.
• StructureCostPlanningisthesimplestformofcostplanning.
• Itisindependentofcostelements.
• Planvaluesenteredhierarchicallytoestimatetheexpectedcostsforaproject.
• Usually“Rough-Cut”—meaningthatwhenmoredetailisknown,youwillprobably
bemorepreciseandprogresstoDetailedCostPlanning.
• CanbeenteredagainstanyWBS(unlessconfigurationinPlanProfilesaysotherwise).
• PlanningisusuallyBottom-up,meaningcostsareaggregatedfromthelowestlevel
WBSupwardautomatically.
• Canbe“integrated”withControlling.
Customization:
OPSB
Operation:
CJ40
DetailedCostPlanningviaWBS:PlanningCosts
AgainstaWBSatCostElementLevel
• CostsassociatedwiththeWBS,butsplitbyCostElements(forexample,Labour,
Materials,Travel,etc.).
• Costplanningbycostelementisusedwhenpreciseinformationbecomesavailable.
• Itcoversplanningofprimarycosts,capacitiestobetaken,andstatisticalkeyfigures
bycostelement.
• WBScostplanningcanbeappliedtoanyCOPlanVersion.
Customization:
OPSB
Operation:
CJ40
DetailedCostPlanningviaNetwork:PlanningCostsAgainstaNetwork
ActivityUsingCostElements,Materials,Services,orActivityTypes
• CostsassociatedwiththeNetworkandcalculatedinoneofthreeways:
• GeneralCosts—ByCostElement
• InternalCosts—ByActivityType(LabourandMachinery)
• ExternalCosts—ByMaterialandServices
ch04.indd46
1/28/084:05:12PM
CompRef8 / SAP®ProjectSystemHandbook/KieronDowling/0-07-154450-X/Chapter4
Chapter 4:
Features of Project System
47
• WhenperformingdetailedcostplanningatNetworkActivitylevel,calculatedcosts
aggregatetotheowningWBSElement.
• NetworkActivitycostplanningcanonlyeverbeappliedtoPlanVersion0.
Customization:
OPUU, OPSC, OPUV, OPSU, OPU6
Operation:
CN21, CJ2D, CJ20N
EasyCostPlanningviaWBS:PlanningCostsAgainstaWBSviaUnitCosting,
butwiththeUseofCostModelstoMakeDataEntrySimpler
CostModelsneedtobedesignedforEasyCostPlanning(ECP)towork.
• ECPModelshavethreeattributes:
• Characteristics(thetypeofdata)
• Derivatives(howthecostisderived)
• EntryScreen(HTMLCode)
• TheycanbeusedtocalculatecostsbasedonUnits×ActivitypriceorMaterials.
• TheycancarrydefaultCostElementsformanualentryofplannedcosts.
• TheysimplifyentryofcostsagainstaWBSbecausethe“model”usedcarriesall
referenceinformation.
• ECPcanonlybeusedintheProjectBuilder.
• ECPcannotbeusedforNetworks.
• ECPitems(thecosts)arenotdistributedovertime.
• ExecutionServicesareanextensionofECPforcreatingsubsequentdocumentssuch
asPRs,POs,andsoon.
• CostsPlannedinECPwillshowunderAnnualPlanningforthestartyearoftheWBS.
Customization:
SPRO
Operation:
CKCM
PlanVersions:DistinctRepositoriesforKeepingYourPlannedCostsSeparate
PlanVersionsaredesignedtokeepahistoryoforiginalandrevisedversionsofyour
plannedcosts:
• Youcanhaveasmanyasyouwant.
• Theyarecreatedinoneoftwoways:
• Bydirectlyenteringplannedcostsintothem
• Bycopyingoneplanversiontoanother
• Theyare“FiscalYear”dependent.
• PlanVersion0isreservedasthebaselineplanandalsocarriesActualCosts.
• NetworksalwaysplantoPlanVersion0.
ch04.indd47
1/28/084:05:12PM
CompRef8 / SAP®ProjectSystemHandbook/KieronDowling/0-07-154450-X/Chapter4
48
SAP Project System Handbook
• EasyCostPlanningcanplanagainstanyCOVersion.
• PlanVersionscanbeusedtotrackaproject’sPOC(PercentageofCompletion).
Customization:
OKEQ
Operation:
CJ9BS, CJ9CS, CJ9FS, CJ9C, CJ9B, CJ9F
StatisticalKeyFigures:ObjectsUsedforStoringand
PlanningInvisibleCostsorConsumption
• SKFsaredesignedtocarryplannedandactualstatisticalvalues(usuallyQuantities).
• Oncedefined,theycanhaveactualdatesandvaluesenteredagainstthemthatare
assignedtoaWBSsorNetworkActivity.
• SKFsareusedonlyforrecordingpurposesandhavenoaccountingimpact.
• SKFscanbeusedasinputsforSDBilling(ResourceRelatedBilling).
• SKFscanbedistinguishedinthreeways:
• Non-aggregatedvalues
• Aggregatedvalues
• Progresslevelforresultdetermination
Customization:
KK01
Operation:
CJS2, CJK2, KB31N
Overheads(CO):AdditionalCostsCalculatedviaCostingSheets
PlannedoverheadcostsarebasedonPlannedcostsplusamark-up(bypercentageorfixed
amount):
• CostingSheetscarrythecalculationuponwhichplannedoverheadcostsarebased.
• TheycanbecalculatedbaseduponCostElement,ActivityType,orMaterial.
• TheycanbecalculatedagainstaWBSoraNetwork.
• Theyarecalculated“onthefly”whencostsareplanned.
• Theycanbeseenasseparateline-itemsinthecostplan.
• CostingSheetsareattachedtoWBSsandNetworks.
Customization:
KZS2
Operation:
CJ20N
ValueCategories:GivingMeaningtoValues
ValueCategoriesareintervalsofCostCenters,CommitmentItems,andStatisticalKey
Figures.Theyarerequiredfor:
• Updatingtheprojectinformationdatabase
• Calculatingprojectinterest
ch04.indd48
1/28/084:05:13PM
CompRef8 / SAP®ProjectSystemHandbook/KieronDowling/0-07-154450-X/Chapter4
Chapter 4:
Features of Project System
49
• Definingstructurereportsforcosts,revenues,andpayments
• UpdatingquantitiesintheprojectinfodatabaseRPSQT
Customization:
OPI1
Operation:
Not Applicable
Budgeting
AclearunderstandingofBudgetingismandatorywhenusedinPS.Thoughsimilarto
Planning,itisdefinitelynotthesame.AbudgetisusedinPStocarryvaluesthataremore
“definitive”thanPlannedCostsbecausetheyrepresentanapprovedvalueratherthanone
usedtocalculatetheplan.Usually,thebusinesswouldperformPlanning,thenusethatPlan
asthebasisforgeneratingaBudget.Then,anyactivitythatresultsina“Commitmentto
spend”canbemonitoredandacteduponwithAvailabilityControl.
BudgetinginProjects:WhentheBudgetIsControlledfromWithinaProject
BudgetingistheprocessoftransferringthePlan(usuallyVersion0)totheareareservedin
theprojectforthebudget(itisnotmandatorytocopyfromthePlan):
• WhethercostplanningwasperformedatWBSlevelornot,thebudgetcanbekeyed
directly.
• BudgetsonlyapplytoWBSElements(orInternalOrdersisused).
• TheBudgetdoesnothavetoequaltheCostPlan.
• ForCapitalProjects,thebudgetcanhaveoriginallybeendistributedfromthe
InvestmentProgramtowhichitbelongs.
• TheBudgetProfilecontainsyourdefaultsettingsanditisthesesettingsthatwill
influencePSbehaviour.
• AprojectBudgethasthefollowing“columns”:
• OriginalBudget
• SupplementBudget(within,ortoproject)
• ReleasedBudget
• Carried-ForwardBudget
• EverytimeaBudgetischanged,arecordiskeptforauditingpurposes.
• WhenaWBShasabudget,itsStatusissettoBUDG.Thiscanbeundonein
transactionOPSX,butonlyifreversalconditionsaremet.
• AvailabilityControlappliesatthelowestlevelofaWBS—itcannotbeapplied
exclusivelyathigherWBSlevels.
ch04.indd49
Customization:
OPS9, CJBN, OPTK
Operation:
CJ30, CJ37, CJ38, CJ32, CJ3A, CJBV
1/28/084:05:13PM
CompRef8 / SAP®ProjectSystemHandbook/KieronDowling/0-07-154450-X/Chapter4
50
SAP Project System Handbook
BudgetinginInvestmentPrograms:WhentheBudgetforAll
ProjectsIsControlledbyaCapitalInvestmentProgram
BudgetingfunctionalityinInvestmentManagement(IM)programsisalmostidenticalto
thatofBudgetinginProjectSystems:
• AnIMBudgetiseffectivelyabudgetmanagedanddistributedtoeitherWBS
ElementsorInternalOrders.
• AnIMBudgetcanbederivedfromaProjectPlanaslongas:
• ThelowestlevelIMPosition(calledtheInvestmentMeasure)islinkedtoa
ProjectorInternalOrder.
• ACostPlanexistsintheProjectorInternalOrder.
• EvenifthebudgetisdistributedtoaprojectfromanIMprogram,thebudgetcan
stillbemanagedfromwithintheproject(ifconfigured).
Customization:
OIB1, OIB3
Operation:
IM34, IM32, IM44, IM52, IM32, IM30, CJ34, CJ37
AvailabilityControl:WhenYouNeedtoControlExpenditure
AvailabilityControl(AC)istheprocessofcheckingexpenditureagainstallowedlimits.Itis
triggeredwhenyouattempttopostcoststoaprojectthathasACactivatedattheWBSthat
willgetthecost,oratahigherWBSifACisactivatedtoincludesubordinateWBSs.
Thesystemusesconfiguredtolerancelimitsbothaboveandbelowtheactualbudget
amounttodeterminewhatactionistaken.
If,whencostsarechargedtoaWBS,thetoleranceisdetectedashavingbeenreached,
certainactioncanbetaken.YoucanconfigurePSto:
• Displayawarningmessageandallowthetransactiontocontinue.
• Sendamailmessagetothepersonresponsiblefortheprojectdetailingwhat
happened(andoptionallydisallowthetransaction).
• Ifrequired,haveACactivatedviaaregularbatchjob(executedinthebackground)
tocheckwhichprojectshavereachedapredeterminedexpenditurelevel.Any
thathave,willautomaticallygetACactivated.Theadvantageofthisismorea
performanceissue(whyhaveatime-consumingcalculationoccurringbeforeitis
reallyrequired?).
• SelectedTransactionGroupsandCostElementscanbeexemptedfromAC.
• Whenthebudgetchanges,ortolerancelimitschange,automatically“reconstruct
AC”(thatis,allrelevantWBSelementswillbemodified).
• AvailabilityControlinUserStatusifyouwanttomanageitatindividualWBSlevel.
ch04.indd50
Customization:
SPRO
Operation:
CJBV, CJBW
1/28/084:05:13PM
CompRef8 / SAP®ProjectSystemHandbook/KieronDowling/0-07-154450-X/Chapter4
Chapter 4:
Features of Project System
51
TimeandCapacityPlanning
ThesearethemethodsatyourdisposalformanagingSchedulesrelatingtoDatesandTimes
andtheHumanResourceswithinaProject’slifecycle.Howyoumanagethedates
associatedwithbothWBSandNetworksdependsonthedetailyouwant:forexample,if
youonlyuseWBSElements,youcannot“schedule”yourprojectbasedonconstraintsor
durations(asyoucanwithNetworks).Datesdo,however,playapartinCostPlanning,as
thedurationofthevariousWBSsdetermineswhereinthecalendartheplanningwillshow.
ForNetworks,true“Scheduling”canbeperformedbecauseeachActivitycanhave
dependenciesonotherActivities.
DatesinWBS:ManagingBasicandForecastDates
• DatesinWBSsaredividedintothreecategories:
• Basic—eitherenteredmanuallyortakenfromtheearliestbasicstartdatesand
thelatestbasicfinishdateoftheactivitiesassignedtotheWBSelement.
• Forecast—asforBasicDates.
• Actual—canbemanuallyenteredorenteredviaConfirmationsandActuals.
• AlldatescarryaDuration.
• Datescanbereconciled,extrapolated,andshiftedbyreferencingsubordinateWBS
Elements.
Customization:
OPTQ
Operation:
CJ21, CJ24, CJ29, CJ20N
SchedulinginNetworks(Part1):Managing
Start/FinishRulesandExecutingScheduling
SchedulingisonlyappropriateforprojectsthatuseNetworkActivities.Tobeeffective,itis
dependentupontheStartandFinishdatesofActivitiesbeingassociatedwithoneanother
via“Start/Finish”rules.
Thefollowingdatesarerelevanttoscheduling:
• ScheduledStart Whenyouarescheduledtostartthiswork.
• ScheduledFinish Whenyouarescheduledtofinishthiswork.
• LatestForecast IfyouwillmisstheScheduledFinish,whatisyourbestestimateof
afinishdate.
• ActualDatesofeventsoccurred Whenyoureallydidstart.Thisinformationcan
beautomaticallycompletedbyotherrelatedtriggers(suchasaTimeRecording,or
thecompletionofaPurchaseOrder).
• LatestStartDate IfyouwillnotmaketheScheduledStart,whatwouldbethe
latestdatetostart.
ch04.indd51
1/28/084:05:13PM
CompRef8 / SAP®ProjectSystemHandbook/KieronDowling/0-07-154450-X/Chapter4
52
SAP Project System Handbook
• LatestFinishDates IfyouwillnotmaketheScheduledFinish,whatwouldbethe
latestdatetofinish.
Customization:
OPU6
Operation:
CJ20N, CN24(N)
SchedulinginNetworks(Part2):Managing
Start/FinishRulesandExecutingScheduling
• Therearetwoschedulingtechniques:
• Forward—Scheduledactivitiesstartingwiththebasicstartdateandcalculating
forwardstodeterminetheearlieststartandfinishdates.
• Backward—Scheduledactivitieswherethelateststartandfinishdatesforthe
activitiesarecalculatedbackward,startingfromthebasicfinishdate.
• FloatsarethenumberofdaysbetweentheLatestStartDateandtheScheduledStart
Date.TheycanbenegativeifBackwardSchedulingcalculatesanunrealisticFinish
Date:
• TotalFloat—NumberofdaysthatcanbeshiftedwithoutaffectingtheLatest
datesofthesubsequentNetwork.
• FreeFloat—NumberofdaysthatcanbeshiftedwithoutaffectingtheEarliest
datesofthesubsequentNetwork.
• AProjectcan“StartinthePast.”
• ActivitiesareconnectedusingRelationshipTypes:FS—Finish/Start,SS—Start/
Start,FF—Finish/Finish,SF—Start/Finish.
• DurationdeterminesthelengthoftimeanActivitytakes.
• RelationshipsbetweenActivitiesdeterminethesequenceofphasesintermsoftime.
Customization:
OPU6
Operation:
CJ20N, CN24(N)
WorkCentersandActivityTypes:PlanningCapacitiesand
theCostofUtilizingtheResource
• WorkCenterscanrepresent,forinstance,apieceofmachinery,aroleoran
individualjob.Thecarrysetvaluesthatdeterminethefollowing:
• Usage—Whatsectionoftheorganizationusesit,whatValueKey(dimension,
time,area)isapplied,howitissetupandsoon.
• Defaults—ControlKeytodeterminetasklistsorOrderTypes(inthecaseofPS,
theNetworkType)andUnitsofMeasure.
• Capacities—TospecifytheFormulausedwhendeterminingthecapacity.
• Scheduling—Tocalculatehowlongittakestoperformoneunit.
ch04.indd52
1/28/084:05:14PM
CompRef8 / SAP®ProjectSystemHandbook/KieronDowling/0-07-154450-X/Chapter4
Chapter 4:
Features of Project System
53
• Costing—AssignaCostCenterandoptionallythedefault(allowed)ActivityType(s)
thatwillbedefaultedwhentheWorkCenterisusedtoplaninaproject’sActivities.
• Technical—Typeofmachine,RoundingCategories,forinstance.
• ActivityTypescanrepresentaspecificunitofchargeablework,suchasalaboratory
testoraperson’sjob.Theyalsocarrysetvaluesthatdeterminethefollowing:
• BasicData—UnitofMeasure,CostCenterCategory,defaultCostElement,
PricingIndicator(forinstance,basedonPlanPriceorManuallycalculated).
• TheybelongtoaCostCenter.
• Theyhaveavalidity(betweendates)andcanexpire.
• ActivityTypeshavePlannedPrices,whicharethebasisforCostPlanningin
Networksand/orWBSElements.
Customization:
OP40, OP45, OP42, OP13
Operation:
CMP2, CNR2, CM01, CM01, CM51
KP26, KL01–KL05
WorkforcePlanning:PlanningWhoDoesWhat,andWhen
WorkforcePlanninginvolvestheHR(HumanResources)moduleofSAPtoprovidea
PersonnelNumberforuseindeterminingtheactualcapacityandcostofprovidingan
individualresource.ItisusedinrelationtoaWorkCentre,andanActivityTypethathavebeen
enteredagainstanInternalNetworkActivity(ifNetworksareused)orinUnitCosting(ifnot).
• WhenaPersonnelNumberisaddedtothePersonAssignmenttabofaNetwork
Activity,PSwilldeterminetheCapacityfortheWorkCentretoperformthetask.
• EnteringthePersonnelnumberassistsintheprocessofconfirmingtimeinCATS
(Cross-ApplicationTimeSheets).
• DataenteredintheNetworkActivityisavailableforCapacityPlanningand
Leveling.However,thesystemwillnotpreventyoufromover-utilizingaresource.
Customization:
CMPC
Operation:
CJ20N, CMP9
RevenuePlanning
ThisinvolveshowexpectedincomeisplannedandmanagedforSales-orientedProjects.
RevenuecanbeplannedagainstaprojectevenifthereisnoconnectiontoaSalesOrder.
However,theWBSElementmustbemarkedasaBillingElement.Therevenueplancan
comefromaQuotationoraSalesOrder,ifyouconfigureyourPlanProfiletodoso
(meaningthatifyoutickthe“AutomaticRevenuePlanning”box,plannedrevenuewill
showinprojectreporting).Inessence,themostbasicofrevenueplanning(structural)works
inexactlythesamewayasStructureCostPlanning.Atadetailedlevel(byCostElement),
youuse“RevenueElements,”whicharejustCostElementswithaspecialindicator.
ch04.indd53
1/28/084:05:14PM
CompRef8 / SAP®ProjectSystemHandbook/KieronDowling/0-07-154450-X/Chapter4
54
SAP Project System Handbook
RevenueassociatedwithaprojectalwaysshowsupwiththeNegative(–)symbolin
reporting.
StructureRevenuePlanning:DirectEntryofRevenueAgainstaWBS
Structure,WithoutRegardtoRevenueElements
ItisRevenueassociatedwiththeWBSasawhole.
• Itisthesimplestformofrevenueplanning.
• Itisindependentofrevenueelements.
• ValuesareenteredhierarchicallyagainstWBSElementstoestimatetheexpected
revenueforaproject.
• Itisusually“Rough-Cut”—meaningthatwhenmoredetailisknown,youwill
probablybemorepreciseandprogresstoDetailedRevenuePlanning.
• RevenuePlancanonlybeenteredagainst“BillingElements.”
• ItbearsnorelationtoRevenueplannedinaSalesOrder.
Customization:
OPSB
Operation:
CJ42
DetailedRevenuePlanning:PlanningRevenue
AgainstaWBSbyRevenueElement
RevenueassociatedwiththeWBS,butsplitbyRevenueElements(forexample,Labour,
Materials,Travel,etc.).
• RevenueplanningbyRevenueElementisusedwhenpreciseinformationbecomes
available(whenyouknowwhichRevenueElementstouse).
• RevenuePlanningcannottakeplaceinaNetwork.
• Ifa“BillingPlan”iscreatedfromwithinaWBS,thesubsequentSalesOrderwill
recognizeitfor“PeriodicBilling.”However,ifaBillingPlaniscreatedagainsta
SalesOrderthatisconnectedtoaWBS,theProjectBillingPlanwillbedeleted.
• WBSrevenueplanningcanbeappliedtoanyPlanVersion.
Customization:
OPSB
Operation:
CJ42
SalesOrders(SD):RevenuePlanningviaSalesOrder(orQuotation)
ItisnotmandatorytohaveaSalesOrder(SO)associatedwithaProjectforRevenue
PlanningifStructurePlanningisused.
• RevenueplanningtoaprojectviaanSOisperformedinoneoftwoways:
• ByenteringrevenuevaluesagainstanSOLineItemthatisassignedtoaWBS.
• CreatingaBillingPlan(musthaveaCostElement).
ch04.indd54
1/28/084:05:14PM
CompRef8 / SAP®ProjectSystemHandbook/KieronDowling/0-07-154450-X/Chapter4
Chapter 4:
Features of Project System
55
• WhenperformingdetailedcostplanningatNetworkActivitylevel(whichcanonly
bedoneviaSalesOrders),revenueplansaggregatetotheowningWBSElement.
• WBSrevenueplanningcanbeappliedtoanyPlanVersion.
• NetworkActivityrevenueplanningcanonlyeverbeappliedtoPlanVersion0.
Customization:
OPSB
Operation:
CJ20N
Execution
ThoughnotspecifictoPS,“Execution”isagenerictermforthepointatwhichaprojectis
readytobereleased.Itisusuallythepointatwhich“Actual”costs,revenues,dates,andso
on,willbepostedtoaproject.So,normally,aprojectthathasbeenReleasedbySystem
Statuswouldfallintothiscategory.ExecutioncanalsobecontrolledbyUserStatus—
meaningthataprojectcanremaininaCreatedstate,butcanhaveBusinessTransactions
openedviaaUserStatus.Inanyevent,itislogicaltoassumethatmostprojectsreachthis
phase,whichwouldalsoincludethePeriod-end.
StatusManagement:SettingProjectRestrictions
(BusinessProcesses)byStatus
• TherearetwotypesofStatus:
• System—PredeterminedSAPstatus.
• User—Determinedbyconfiguration.
• SystemstatusCRTDisautomaticallysetbySAPwhenaprojectiscreated.
• ThesystemStatussetbyuserisrestrictedto:
• REL—Released.
• TECO—TechnicallyClosed.
• CLSD—Closed.
• OthersystemstatusescanbeusedtoLOCKcertaininformationwithinaproject.
• SystemStatussetathigherlevelsaffectsalllowerlevels(notsowithUserStatus—it
mustbecopieddownthehierarchy).
• UserStatuscanbeconfiguredtopreventcertainbusinesstransactions.
• AhistoryofStatusescanbekeptifyouhaveconfiguredthetickbox“Change
Documents”inProjectProfileStatusManagement.
• Anumberof“Hidden”SystemStatusesinformyouofpastevents,suchasBudgeted,
CostsPlanned,AvailabilityControl,DatenotUpdated,Activated,andsoon.
ch04.indd55
Customization:
OK02
Operation:
CJ20N
1/28/084:05:14PM
CompRef8 / SAP®ProjectSystemHandbook/KieronDowling/0-07-154450-X/Chapter4
56
SAP Project System Handbook
Actuals:PostingActualCosts,Revenues,andDatestoaProject
Actualsare“real”valuesthathitaprojectbasedonactualevents.
Thereareseveralwaysthatactualscanhitaproject:
• FinancialJournals(CostandRevenue).
• Time-sheets(Confirmations).
• COPostings(Overheads).
• MaterialandServicedeliveries.
• ActivityAllocations.
• Payments.
• RealizedMilestones(releasesBillingBlocksifconnectedtoaSalesOrder).
• Settlementfromotherobjects(forexample,MaintenanceOrders,InternalOrders).
• StatusmustbeRELtoreceiveActualsorTECOtoreceiverealizedcommitments.
• AWBSmusthavethe“AccountAssignment”indicatorsettoOnbeforeitcan
receivecosts.
• ActualDatesareautomaticallyupdatedwhencostshitaproject.
• ActualsareusuallypostedtothelowestlevelofaProject’sstructure(withthe
exceptionofRevenue).
Simulations:SimulatingWhatYouWanttoDoBefore
YouReallyDoIt,WithoutCommitting
Simulationsmeanwhattheysay—theyprovideyouwithatooltotrythingsoutinaproject.
Theycarrythefollowinginformation:
• Structures.
• Dates.
• Costs.
• Materialcomponents.
• Milestones.
• Billingplans.
• Theyareidentifiedbywhat’stermedasaVersionKey,whichisattachedtoyour
“simulated”project.
• TheyrequireaSimulationProfile,whichtellthesimulatedprojectwhattypeofdata
canbemanaged.
• Inessence,youareusingallthefunctionalityofPSstructuresandPlans,butarenot
doinganyactualpostings.
• It’saplanningtoolandusesthePlanningBoardtomanagestructuresand
planningdata.
• SimulationscanbecreatedfromexistingOperative/Standardprojectsandfrom
othersimulatedprojects.
• Operativeprojectscanbegeneratedfromsimulatedprojects.
ch04.indd56
1/30/082:58:49PM
CompRef8 / SAP®ProjectSystemHandbook/KieronDowling/0-07-154450-X/Chapter4
Chapter 4:
Customization:
OPUS, SPRO
Operation:
CJV1–CJV6
Features of Project System
57
ProjectVersions:SnapshotsofaProjectforComparisonPurposes
• ProjectVersionsshouldnottobeconfusedwithPlanVersions.
• Theyareexactcopiesofaproject,includingallplans,actualcosts,andprogress
information.
• Theyaresubjecttoa“Profile”thatisusedtodeterminethekindofinformationa
versionwillcarry.
• TheycanbeautomaticallycreatedbasedonProjectStatus.
• Theycannotbemodified.
• Theyareusefulwhencomparingbaselineinformationwithcurrentinformation.
• Theycanbeseeninmoststandardreports.
Customization:
OPTS
Operation:
Not Applicable
Period-End(andRegularProcesses)
Thistermnotonlyappliestothefinancialmilestonethatoccursonamonthlyorannual
basis,butalsotoprocesseswithinaprojectthatneedtobeperformedonaregularbasis,
suchasSettlementandBilling.
Settlement:TransferringActualValuestothe“Owner”
Settlementisnotmandatory,butifitisnotcarriedoutonaprojectthathasreceivedcosts,
theprojectcannotbeclosed.TheexceptiontothisisaSettlementProfilethatstates“Notto
beSettled.”
• ThepurposeofSettlementistobalanceaprojecttozero.
• Itisnecessarybecauseofthetemporarynatureofaproject.
• Aprojectcanbesettledtoalmostanyotherentity:
• ProfitabilitySegment(forResultsAnalysis)
• Asset
• AnotherProject
• AMaterial
• ACostCenter
• AP&LAccount
• Settlement“Rules”mustbeinplace—thatis,theremustbeanOrigin(byCost
Element)andaReceiver.
ch04.indd57
1/28/084:05:15PM
CompRef8 / SAP®ProjectSystemHandbook/KieronDowling/0-07-154450-X/Chapter4
58
SAP Project System Handbook
• AmountssettledfromaWBSorNetworkcanbesubdividedbypercentageor
specificamounts.
• Settlementcanbeperformed“Individually”or“Collectively”usingVariants.
• SettlementRulescanbegeneratedautomatically(CJB1andCJB2).
• WhenaWBSisdeemedanAssetUnderConstruction,SettlementRulesaregenerated
automaticallyatfirstsettlement.
Customization:
OKO7, OKEU, OKO6
Operation:
CJB1, CJB2, CJ88, CJ8G, CJIC
Period-End:ExecutingRegular,CyclicalProcesses
InProjectSystems,Period-endClosing(PEC)isnotnecessarilybaseduponafinancial
period.YouperformPECforthefollowingreasons:
• EarnedValueAnalysis EachtimeyourunEarnedValue(theprocessofcalculating
therealprogressofaprojectfromacost/time/percentageofcompletionviewpoint),
EVfieldsintheprojectarerecalculatedandoverwritten.
• ResultsAnalysis EachtimeyourunResultsAnalysis,RAfieldsintheProjectare
overwritten.ResultscanbeusedasinputtoSettlement.
• Settlement Dependingonthereceiver,Projectcostsareusedtotransfercoststo
FixedAssets,ProfitabilitySegment,CostCenter,andsoon.
• ProjectVersion Totakea“snapshot”oftheprojectatacertaintimeinitslifefor
futurecomparisonpurposes.
• Interest CalculateinteresttobepostedtoProjects/SalesOrdersandother
applicableobjects.
• Periodictransfers Postingsrelevanttocostaccounting(suchastelephone
expenses)arecollectedinclearingcostcentres.Thepostingscollectedarethen
transferredtothereceivercostcentersatthePeriod-end.(Telephoneexpenses,for
example,aretransferredtoallthecostcentersinthebusinessinproportionto
telephoneunitsusedbythereceivercostcenters.)
• Determiningoverheadsurcharges Overheadsforprovisionofmachines,
buildings,materials,personnel,andsoon,areappliedtocostsusingsurchargesin
CostingSheets.Bothplanandactualvaluesapplyforoverheadsurcharges.All
reportsshouldberunatthistimetoensureresultsofPECarecaptured.
Progress(Part1):UpdatingandReviewingaProject’sProgress
Progress(PercentageofCompletion—POC)isdeterminedbyseveralfactors:
• ProgressVersion.
• MeasurementTechnique.
• Start-Finish
• Milestone
ch04.indd58
1/28/084:05:15PM
CompRef8 / SAP®ProjectSystemHandbook/KieronDowling/0-07-154450-X/Chapter4
Chapter 4:
Features of Project System
59
• Estimation
• TimeProportional
• DegreeofProcessing
• QuantityProportional
• SecondaryProportional(apportionedeffort)
• CostProportional
• Actual=Plan
• Individual(user-exit)
• POCcanbeusedasinputforResultsAnalysis.
• AspecialCOPlanVersionmustexistforProgressanalysis.
• POCisrecordedinspecialStatisticalKeyFigures(assignedtoyourControllingArea).
Customization:
SPRO
Operation:
CNE1, CNE2
Progress(Part2):UpdatingandReviewingaProject’sProgress
• InputstoPOCCalculationinclude:
• PlannedCosts.
• ActualCosts.
• InfluencesforPOCcalculationaretheMeasurementTechniqueused.
• AProject’sPOCisupdatedwhenyourunProgressAnalysis.
• ForMilestoneTrendAnalysis,aProjectVersionwillhavebeencreatedtorecord
the“before”situation.
• ProjectProgresscanbemonitoredinanumberofways,including:
• PlanningBoard.
• Standardreporting.
Customization:
SPRO
Operation:
CNE1, CNE2
Archiving:TakingYourProjectsoutoftheLiveSystem
ArchivinginProjectsrequiresyoutohavetheDeletionFlagset.
• Archivingisperformedinthreestages:
• SetDeletionFlag(CJ20N).
• SetDeletionIndicatorinbatchmode(setforallDeletedProjectsinCN80).
• PerformArchiveinCN80.(Networksarearchivedonlyafterresidencetimes1
and2havebeenmet.)
ch04.indd59
1/28/084:05:15PM
CompRef8 / SAP®ProjectSystemHandbook/KieronDowling/0-07-154450-X/Chapter4
60
SAP Project System Handbook
• Somedatacannotbearchived:
• SimulationVersions
• BillingplanforWBSelement
• Invoicingplanfornetworkactivityorcomponent
• Unitcostingfornetworkactivityorcomponent
• Additionalattributesforprojectsummarizationusingmasterdatacharacteristics
• ClassificationdataforsummarizationofWBSelements
• Classificationdataforordersummarizationofnetworks
• Characteristicvalueassignmentsinvariantconfiguration
• Deliveryinformationfornetworks/workbreakdownstructures
• Deliveryaddressesformaterialcomponentsinthird-partyorders
• Capacityrequirements
• Workforceplanning
• OperativeProjectswillbearchivedwiththeirrespective“StatusDependent”
Versions.TimeDependentversionsmustbearchivedseparately
Customization:
Not Applicable
Operation:
CJ20N, CN80
Billing:SendingtheCustomeranInvoice
CustomerprojectscanhaveActualCostsbilledusingResourceRelatedBilling(RRB).
• DIPProfilesareusedtogathertherelevantactualcostsfrombothWBSElements
andNetworkActivities.
• ProjectMilestonescanbeusedtogenerateaBillingPlan.
• SalesOrdersthatarelinkedtoprojectscanhavetheirBillingPlanupdatedfrom
withinaproject.
• TheprojectPlanProfiledetermineshowtheRevenuePlanissenttotheproject.
Customization:
ODP1
Operation:
DP91
Summary
YoushouldbynowbeprettyfamiliarwiththemainaspectsandfeaturesofPS.Armedwith
thisknowledge,youcanprogresstoConfiguration(orCustomizationasitisalsocalled).
ThroughoutChapter4,therehavebeenreferencestowheretheconfigurationisdone—but
thisdoesnotmeanyouknowitallyet;youstillneedtoknowwhateachconfiguration
transactioncontains.Inthenextchapter,youwillbeshownhowthisisdone.
ch04.indd60
1/30/082:59:30PM