Home Contact Search form

SAP-Centric Projects

In Charge and In Control

The Product Owner's Perspective for Integrated Capital Projects Print E-mail
Written by Berthold Kastel   
Article Index
The Product Owner's Perspective for Integrated Capital Projects
Page 2
Page 3

 

 

Basic Setup in SAP

 

The following are the basic tools and objects needed to be set up in SAP.

  • SAP-IM is used for overall program management and top-down budget control starting with the corporate budget.
  • Project expenditures will be settled on a monthly basis to assets under construction (AUC) and upon capitalization to assets.
  • The WBS will be set up in SAP and controlled there.
  • All general cost planning and budgeting (approved cost plan) will be done on the WBS level.
  • Milestones will be defined on the WBS or activity level in SAP.
  • One network will be set up in SAP, with scheduling deactivated. Its activities are to be associated with key tasks (and WBS milestones, differentiated by a key) in the Primavera master schedule. Key tasks (beyond milestones) are defined as summary tasks and those that require interaction with purchasing and/or MRP.
  • Work centers will be defined in SAP.
  • Purchasing will be used in SAP.
  • Actuals will be collected in SAP.
  • Cost plan starts on WBS level (structure level).
  • Cost plan refined on WBS or key activity level through association of work centers that reflect purchase orders.
For more details about the setup and use of fields, and their interaction with Primavera, please check out the "Our Solutions" section.  

 



 
Related Items
Top 6 Questions to Ask
6. How open is your technology?

 

It is so easy to say "yes" and "we are open" - but what does that mean? You may want to get more specific and try to find out what that really means.

 

Are you using any proprietary technology that is not open? Do you support all Java/J2EE compliant web application servers (like WebLogic, WebSphere, Tomcat, NetWeaver)? Can you please name all programming languages you used to build your application?


Questions like these should flush out your real support needs, risk and potential vendor dependency.