Supplier Case Study

Sunday 19th October, 2014

Anthony AmingEnterprise Q2C Business Intelligence and Systems Manager

PIDX Past President

2

The Value of Customer E-Procurement

Supplier (Order Fulfilment)

Reduce cost in order fulfilment (paper, handling, postage)

Implement standard data capture and billing procedures across customer base

Maximize visibility of the order fulfilment cycle

Meet customer expectations while maintaining processes that are supportable

Favorable DSO

End to End Visibility

Being a “Vendor of Choice”

Buyer (P2P)

Reduce waste and cost from supply

chain

Automate Accounts Payable

processes

Shorten cycle time for critical goods

and services

Rapidly capture and manage spend

Produce more accurate forecasts in

a more timely fashion

Fewer vendor blocks for slow/no

pay

Assure allocated funds can be used

Yearly Electronic Revenue Growth (000’s)

3

0

50000

100000

150000

200000

250000

300000

350000

400000

0

1000000

2000000

3000000

4000000

5000000

6000000

7000000

8000000

2007 2008 2009 2010 2011 2012 2013

Inv

oic

es

Rev

en

ue (

000's

)

Revenue

Invoices

4

Network Providers

ADP (formerly DO2)

Ariba

Coupa

Cortex

Hubwoo

ICG

OB10

Oildex

Pervasive

Quadrem

5

Bill Barrett

26 others

Baker Hughes

P

I

D

X

34 others

Marketplace Connections

6

PIDX Documents Enabled

Invoice

Invoice Response

PO

PO Change

Field Ticket

Field Ticket Response

PO Response (testing)

Learning and doing

Middle

Ware/

3rd Party

Buyer

ERP

System

Middle

Ware/

3rd Party

Supplier

ERP

System

Technology Related: • Standards (PIDX )

• Message types (Inv. create, change, cancellation, Response, etc.)• Envelope, (RosettaNet, AS2, etc.)• Format, (PIDX XML, EDI. Etc.)• Protocol, (HTTPS, Digital Signatures, Encryption, etc.) • Catalogs• Attachments

• Technology related processes (Receipt acknowledgement, etc.)• Mitigation (Notification of Failure, Invoice issues, etc.)

High Level Technical Overview

Documentum

SAP ECC 6.0

Customer’s System or

Marketplace

Field

Ticket

Integration Landscape for E-Invoicing

Returned Status

webMethods

Invoice

IDOC

Field

Ticket /

Attachment

Customer

Accounts

Payable

Transform PIDX XML

Attach F.T.

Envelope & Route

Status Handling

RNIF

PIDX XML

Returned Status

Invoice Tracking

Report

9

SAP Readiness Check

Reduce errors in the marketplace

Configurable by customer Bill-to and Product Line

Pattern recognition or add customer values to a check table

One SAP interface for sales order or invoice

Header or line item validation

10

webMethods

Single base map for all customers

Partner Parameters to handle customer variation

Send PIDX response documents via email to end users

Send PIDX PO to BakerHughesDirect for back end routing

Invoice Tracking Report to maintain document status

Marketplace reports uploaded daily to reconcile BHI and Customer

invoice status

11

Customer Conversion

Evaluate

Readiness

Determine

eProcurement

readiness

Determine

eProcurement

Marketplace

ADP

Oildex

Quadrem

Pervasive

OB10

Cortex

Hubwoo

Direct Connect

Preferred Data

Transmission

Method

Preferred

Method of

PIDX XML

Transmission

- AS/2

- RNIF

Mapping

Specifications

Marketplace

Profile

Partner

Profile

SAP

Configuration

And Testing

Customer

Marketplace

BHI

Marketplace

Acceptance

Customer

Acceptance

Steps for converting a customer to eProcurement

Go Live

Planning

12

Your Turn!