Integration of SAP and
Expedition at Petro-Canada
using ClearingHouse®
Technology
Bryan Vincze, B. ENG, MBA
Presentation Outline
• Software focus
• Company backgrounds
• The end-user and Expedition
• Reasons for integration
• Constraints of the integration development
• Technical details of software
• Qualities of the integration tool
• Realized benefits
Software Focus
• Expedition 8.58
– Oracle database
• SAP
• SAP to Expedition Data Integration using
ClearingHouse®
technology
The Client
• Integrated oil and natural gas company
• Multi-national
• Extract, refine, and market
The End-user: Project Group
• Expedition users
– Major Projects Group
– Cost Control
• Refinery projects in Canada
• Approximately $ 2 billion in refinery upgrades
scheduled until 2008
Emerald Associates: The Consultants
• PSP and PAR
• Rollouts, integration, training, and turnaround
scheduling
• Expedition, Primavera Enterprise, and P3
• Pertmaster and Common Point dealers
The End-user and Expedition
• Major Projects Group
– Cost Control
• Rollout began in late 2003
• Focus on Owner Cost
• Required for monthly cost reporting
• Interested in incurred, actual, and
incremental costs
The End-user and Expedition
• Complete capture of project costs - both Owner
Costs and EPC Costs
• Developed hierarchical budget cost codes
• Expedition focus modules
– Cost Worksheet
– Contracts
– POs
– Invoices
– Change Management
Expedition and SAP
• Expedition Benefits
– Expedition provided
more flexible and
responsive reporting
– Expedition provided
Change Management
and Budget control
• SAP Process Concerns
– Double entry of data
Expedition and SAP
• Expedition Benefits
– Invoice log tracked
manually in Expedition
– Actuals from SAP
loaded as contracts,
processed to invoices
• SAP Process Concerns
– Commitment contracts not
tracked in SAP
– Invoices paid without
commitment document
– Large potential for double
counting costs
Constraints of Integration Development
• Soft issues
– Buy-in from all groups
– Limited end-user availability
– Non-involvement of SAP group
Constraints of Integration Development
• Required low cost data load solution
• Rapid solution required
• Database level communication not possible
Expedition Integration Modules
• Cost Worksheet
• Purchase Orders
• Actuals
– Commitment Contracts
– Invoices
• Contacts
Project Identification
•AFEs
– Purchase Orders
– Actuals
•Multiple AFEs to one
Expedition Project
•Custom field added to
Project Properties
Cost Information Requirements
• Capture complete project costs
• Segregate Owner versus EPC costs
• Maintain ID of source AFE
• Capture Actual costs
• Capture Period End and Incremental costs
Cost Worksheet – Integration Details
• Create Cost Codes
– SAP based code
– User maps hierarchical budget codes
• Custom Fields Populated
– Actuals paid
– Incremental Actuals paid
– Source AFE
Contacts – Integration Details
• Create new contacts linked to POs
• Uniqueness based upon SAP vendor number
• Contact abbreviation system defined
Cost Categories and Documents
• Purchase Orders
• Actuals Paid
– Commitment Contracts
– Invoices
Purchase Orders – Integration Details
• Create and detail line items
• Cost distribute
• Maintain foreign currency information
– Forecast outstanding value
– Capture settlement exchange rate and amount
• Invoices entered manually
Commitment Contracts – Integration
Details
• Actuals paid without commitment POs or
contracts in SAP
• Create Commitment Contract
– Invoice
– Actual Paid
– Filter values captured through manual invoice log
Commitment Contracts – Integration
Details
• Contract value grouped by period end dates
– User defined and maintained
• Complete details available in line items
• Cost distribute
• Capture back posting information
Integration Technical Details
• Java – programming language
• JaCoB – Java Com Bridge
• Primavera SDK
– API
SAP CSV
File
PRIMAVERA
C
O
M
API
JaCoB
Integration
Application
ClearingHouse®
technology
Business
Rule
Library
ORACLE
DB
Expedition Benefits for our Client
• Flexible and responsive reporting
• Single source of cost information and
reporting
• Change Management
• Budget management and control
Data Load Benefits
• Cost effective and efficient (less than a
six-month ROI cycle)
• Facilitate user acceptance
• Accurate
• Current data information
Questions?

Primavera integration with sap

  • 1.
    Integration of SAPand Expedition at Petro-Canada using ClearingHouse® Technology Bryan Vincze, B. ENG, MBA
  • 2.
    Presentation Outline • Softwarefocus • Company backgrounds • The end-user and Expedition • Reasons for integration • Constraints of the integration development • Technical details of software • Qualities of the integration tool • Realized benefits
  • 3.
    Software Focus • Expedition8.58 – Oracle database • SAP • SAP to Expedition Data Integration using ClearingHouse® technology
  • 4.
    The Client • Integratedoil and natural gas company • Multi-national • Extract, refine, and market
  • 5.
    The End-user: ProjectGroup • Expedition users – Major Projects Group – Cost Control • Refinery projects in Canada • Approximately $ 2 billion in refinery upgrades scheduled until 2008
  • 6.
    Emerald Associates: TheConsultants • PSP and PAR • Rollouts, integration, training, and turnaround scheduling • Expedition, Primavera Enterprise, and P3 • Pertmaster and Common Point dealers
  • 7.
    The End-user andExpedition • Major Projects Group – Cost Control • Rollout began in late 2003 • Focus on Owner Cost • Required for monthly cost reporting • Interested in incurred, actual, and incremental costs
  • 8.
    The End-user andExpedition • Complete capture of project costs - both Owner Costs and EPC Costs • Developed hierarchical budget cost codes • Expedition focus modules – Cost Worksheet – Contracts – POs – Invoices – Change Management
  • 9.
    Expedition and SAP •Expedition Benefits – Expedition provided more flexible and responsive reporting – Expedition provided Change Management and Budget control • SAP Process Concerns – Double entry of data
  • 10.
    Expedition and SAP •Expedition Benefits – Invoice log tracked manually in Expedition – Actuals from SAP loaded as contracts, processed to invoices • SAP Process Concerns – Commitment contracts not tracked in SAP – Invoices paid without commitment document – Large potential for double counting costs
  • 11.
    Constraints of IntegrationDevelopment • Soft issues – Buy-in from all groups – Limited end-user availability – Non-involvement of SAP group
  • 12.
    Constraints of IntegrationDevelopment • Required low cost data load solution • Rapid solution required • Database level communication not possible
  • 13.
    Expedition Integration Modules •Cost Worksheet • Purchase Orders • Actuals – Commitment Contracts – Invoices • Contacts
  • 14.
    Project Identification •AFEs – PurchaseOrders – Actuals •Multiple AFEs to one Expedition Project •Custom field added to Project Properties
  • 15.
    Cost Information Requirements •Capture complete project costs • Segregate Owner versus EPC costs • Maintain ID of source AFE • Capture Actual costs • Capture Period End and Incremental costs
  • 16.
    Cost Worksheet –Integration Details • Create Cost Codes – SAP based code – User maps hierarchical budget codes • Custom Fields Populated – Actuals paid – Incremental Actuals paid – Source AFE
  • 18.
    Contacts – IntegrationDetails • Create new contacts linked to POs • Uniqueness based upon SAP vendor number • Contact abbreviation system defined
  • 20.
    Cost Categories andDocuments • Purchase Orders • Actuals Paid – Commitment Contracts – Invoices
  • 21.
    Purchase Orders –Integration Details • Create and detail line items • Cost distribute • Maintain foreign currency information – Forecast outstanding value – Capture settlement exchange rate and amount • Invoices entered manually
  • 23.
    Commitment Contracts –Integration Details • Actuals paid without commitment POs or contracts in SAP • Create Commitment Contract – Invoice – Actual Paid – Filter values captured through manual invoice log
  • 24.
    Commitment Contracts –Integration Details • Contract value grouped by period end dates – User defined and maintained • Complete details available in line items • Cost distribute • Capture back posting information
  • 28.
    Integration Technical Details •Java – programming language • JaCoB – Java Com Bridge • Primavera SDK – API
  • 29.
  • 30.
    Expedition Benefits forour Client • Flexible and responsive reporting • Single source of cost information and reporting • Change Management • Budget management and control
  • 31.
    Data Load Benefits •Cost effective and efficient (less than a six-month ROI cycle) • Facilitate user acceptance • Accurate • Current data information
  • 32.