Home Contact Search form

SAP-Centric Projects

In Charge and In Control

Main Menu
Home
Projects With SAP
Building Blocks of SAP Projects
SAP-Primavera Integration
SAP Modules and Projects
Our Project Solutions
NEWS About Projects and SAP
BLOG About Projects and SAP
Links
Contact Us
Search
News Feeds
FAQs
Administrator
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
Page 2 of 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.  

 
 
[ Back ]
Related Items
Top 6 Questions to Ask
4. What do you know about Primavera?

Let's not assume that a vendor is an expert in Primavera. One may be surprised, particularly when looking at the interface as a mainly technical issue. Often internal IT departments who get concerned about "throwing good money after bad money" have the tendency to look at the integration issue from that side. Some EAI vendors are the same, and companies (mainly service organizations) that have worked with SAP for many years - but not with Primavera.

 

This question has two dimensions. First, how extensively have you worked with the Primavera Java API? Second, how well do you know how to map fields and processes in Primavera with SAP?