You are on page 1of 7

Four51 PunchOut User Guide

VERSION 2.0

NOVEMBER 2007

Table Of Contents

Overview ...................................................................................................................................... 2
Getting Started.............................................................................................................................. 2
Understanding PunchOut .................................................................................................... 2
PunchOut Event Sequence .................................................................................................. 2
Supported Platforms .......................................................................................................... 3
Supported Features ........................................................................................................... 4
Setting Up The Service ................................................................................................................... 5
Four51 Buyer Interface Configurations ................................................................................. 5
Four51 PunchOut Service Configurations .............................................................................. 6
Customer Procurement Application Configurations ................................................................. 6
Implementation ............................................................................................................................. 7
Additional Reference Material .......................................................................................................... 7
Customer Service & Support............................................................................................................ 7
Overview
PunchOut enables users of procurement applications to access and purchase
products that reside on your Four51 website. PunchOut enabled procurement
applications include Ariba, PeopleSoft, Oracle, SAP, CommerceOne/PerfectCommerce,
Ketera, SciQuest, and others.

This guide is intended to provide a description of Four51’s PunchOut features and a


guide to implementing PunchOut with your customer.

Getting Started
ƒ Understanding PunchOut

o What is PunchOut? - PunchOut is a protocol for interactive sessions managed


across the Internet. PunchOut is a communication from one application to another,
achieved through a dialog of real-time, synchronous cXML messages, which support
user interaction at a remote site. It is the best way to manage user sessions
distributed across web applications.

Four51 supports Procurement PunchOut, which specifically supports interactions


between a procurement application and the Four51 application. Procurement
PunchOut describes the "traditional" PunchOut scenarios that use the regular
PunchOut Setup Request and PunchOut Setup Response. The PunchOut session is
initiated with a PunchOutSetupRequest and terminates with a posting of a
PunchOutOrderMessage, which contains the initiating transaction’s cookie and a
shopping cart or “quote”. The final purchase order is delivered from the
procurement application to Four51 in an OrderRequest cXML document.

ƒ PunchOut Event Sequence

A PunchOut session is composed of several distinct steps.

1. Users log on to their procurement application and open a new purchase order.

2. Users click a link to shop in your Four51 website, which opens a web browser
and logs them into your Four51 web site automatically.

3. Users shop on Four51, and place items into their shopping cart.

4. When ready, they click Submit in the shopping cart.

5. Four51 sends the order back to the procurement application in cXML format.
User is simultaneously redirected back to the procurement application.

6. The order is routed through the procurement application’s established requisition


and approval process.

7. The procurement application confirms the order with Four51 via a cXML
transaction. You receive customer’s order in your Four51 administration
interface.

Four51 PunchOut User Guide 2


`
User logs on to
1 procurement system.
Requisition &
Approval Process
is completed.
Procurement
6 Application
Order is
Order is sent in
confirmed 7 5 cXML format.
with Four51.
User selects your
2 catalog.

Four51 Admin Four51 Buyer


Cart Submit
Interface Web Site
3 4
User places items User clicks
Into their cart. submit in cart.

- PunchOut Event Sequence –

ƒ Supported Platforms

Four51 has successfully completed PunchOut with numerous procurement applications.


To date, this includes:

ƒ Ariba
ƒ Oracle iProcurement
ƒ Ketera
ƒ SciQuest
ƒ CommerceOne/Perfect Commerce

Other PunchOut enabled procurement systems include:

ƒ PeopleSoft
ƒ SAP
ƒ Birchstreet
ƒ ReQlogic
ƒ PurchasePro
ƒ B2GNow
ƒ ExoStar
ƒ Procure+
ƒ Prollinx

While the cXML specification attempts to create a standardized way for


procurement applications to interface with supplier web sites, each application
may have unique requirements. Four51 does not guarantee support for every
PunchOut enabled application, including all of those listed above and those
not mentioned in this document.

Four51 PunchOut User Guide 3


ƒ Supported Features

There are aspects of the cXML PunchOut specification that Four51 does not support.
Below is a short list of supported and unsupported features. Four51 makes every
attempt to accommodate customer requirements; however, requests for unsupported
features are beyond the scope of Four51’s standard PunchOut services, and may or may
not be considered for application enhancement. Four51 reserves the right to determine
unsupported features and whether to consider specific PunchOut enhancements.

o Supported Features: Below is a high-level description of PunchOut features


supported by Four51.

ƒ PunchOutSetupRequest – Used by the procurement application to initiate a


PunchOut session. Create, Edit and Inspect sessions are supported.

ƒ PunchOutSetupResponse – After receiving a PunchOutSetupRequest, Four51


sends this response back to the procurement application to indicate the
PunchOutSetupRequest was successful.

ƒ PunchOutOrderMessage – After the user selects items on your Four51 website,


configures them, and clicks the “Submit” button, Four51 sends a
PunchOutOrderMessage to communicate the contents of the shopping car to
the user’s procurement application.

ƒ OrderRequest – Used to confirm the user’s final purchase order with Four51.

ƒ UNSPSC Commodity Codes

o Unsupported Features: Below is a high-level description of list of PunchOut


features not supported by Four51. This list is not meant to be comprehensive.

ƒ Source sessions of PunchOutSetupRequest are not supported.

ƒ PunchOut Index Catalog is not supported.

ƒ PunchOut Change Orders are not supported.

ƒ Purchase Order Processing

o Four51 supports only cXML receipt of purchase orders.


o E-mail or Fax orders can be processed offline.
o EDI is not supported by Four51.
o Specific user identification on Purchase Orders is not supported. Each
order will appear as if it has been submitted by the PunchOut Template
User.

ƒ cXML Value Changes

o The cXML documents that are transmitted by Four51 comply with the
Document Type Definition available at www.cxml.org.
o Changes to the structure and values in the cXML documents are not
supported.

ƒ Order Status & Tracking – Customer’s do not have the ability to log on to a
buyer site and track order history and tracking information.

ƒ Four51 Inventory features are not supported.

Four51 PunchOut User Guide 4


ƒ USAData is not supported during PunchOut sessions.

ƒ Buyer Interface – The Four51 buyer interface is scaled down due to the
requirements of PunchOut.

o The Four51 “Orders” and “Reports” button will not appear.


o The Four51 “Logout” button will not appear.
o Four51 Cost Center features are not supported. Cost Center data is sent
from the procurement application in the final OrderRequest document.
o Four51 Billing & Shipping addresses are not supported. Address
information is sent from the procurement application in the final
OrderRequest document.
o Four51 PO ID is not supported. PO ID is sent from the procurement
application in the final OrderRequest document.
o Four51 Custom Order Fields are not supported.
o Four51 Date Needed is not supported.
o Four51 Buyer Super User permissions are not supported.

Setting Up The Service


There are 3 sets of configurations required to setup the PunchOut service.

ƒ Four51 Buyer Interface Configurations – Your organization will be responsible for these.

ƒ Four51 PunchOut Service Configurations – Four51 will be responsible for these.

ƒ Customer Procurement Application Configurations – Your customer will be responsible


for these.

Below is a description of each of these configurations.

ƒ Four51 Buyer Interface Configurations

You will be responsible for completing these configurations. Completion of these


configurations is required before the PunchOut service is completed.

Configuration Comments
1 Buyer Catalog Focus primarily on setting up categories and
products. Custom Themes and Site Customization
are supported. Do not configure features related to
the checkout process: Shipping, Billing, Payment
Methods, Tax, Order Fields, Cost Centers,
Addresses, etc.
2 Template User A template user is required. Create a template user
as you would create any other user. The following
are the minimum permission requirements:
a. Place Standard Orders
b. PunchOut User – If you do not find this
permission in your list of permissions, contact your
Four51 representative. This permission is enabled
once you have subscribed to the PunchOut service.

Four51 PunchOut User Guide 5


ƒ Four51 PunchOut Service Configurations

Four51 is responsible for completing these configurations. Most of these


configurations require information from your customer, and are collected during the
implementation process.

Configuration Comments
1 Identity Unique DUNS number of the buying organization.
Customer typically provides this during
implementation.
2 Template User Name of the Template User. Typically created by
your organization during implementation.
3 Shared Secret Private shared secret used for security purposes to
validate setup request transaction between
procurement application and Four51. Customer
typically provides this during implementation.
4 Email – Order Request Location of the user’s email address within the
OrderRequest cXML document.
5 Cost Center – Order Location of the line item cost center within the
Request OrderRequest cXML document.
6 Unique Name – Setup Location of the user’s unique name (i.e. username)
Request within the cXML PunchOutSetupRequest document.
7 Email – Setup Request Location of the user’s email address within the
cXML PunchOutSetupRequest document.
8 Name – Setup Request Location of the user’s first and last name within the
cXML PunchOutSetupRequest document.
9 Override Unit Price In most circumstances Four51 calculates line item
pricing using Four51’s price schedules. However,
this can be overridden to accept the unit price
calculated by the customer’s procurement
application.
10 Round Unit Price Four51’s default pricing rounds to six decimal
places. This can be rounded to two decimals in
scenarios when the procurement application accepts
only two decimal places.
11 Product Description Four51 can be configured to send either Product
Value Name or Product Description in the
PunchOutOrderMessage.

ƒ Customer Procurement Application Configurations

To interact with Four51, the customer’s procurement application requires two pieces of
information. This information will be provided by Four51 during the implementation
process.

Configuration Comments
1 PunchOutSetupRequest URL The URL to which the customer’s procurement
application will send PunchOutSetupRequest
documents.
2 OrderRequest URL The URL to which the customer’s procurement
application will send OrderRequest documents.

Four51 PunchOut User Guide 6


Implementation
A Four51 solution specialist will work with you throughout your PunchOut implementation until
completion. Four51 will make reasonable efforts to assist you during your PunchOut
implementation. Requests for additional services may increase your project cost and timeline.

Project timeline can vary significantly based on several factors: 1) Availability of your
company’s resources, 2) Availability of your customer’s resources, 3) Four51 buyer site build
out, 4) Other.

Below are the typical implementation steps for a standard PunchOut.

1. You and your customer agree to implement PunchOut.

2. Contact your Four51 representative to subscribe to Four51’s PunchOut service.

3. A solution specialist will contact you to schedule and host an initial call with you and/or
with your customer.

4. Four51 buyer site is constructed and PunchOut Template User created.

5. Customer provides PunchOut configuration information to Four51.

6. Four51 provides PunchOutSetupRequest and OrderRequest URL information to


customer.

7. Test PunchOut connection and event sequence.

8. Go live.

Additional Reference Material


ƒ cXML Documentation – Chapter 4 of the cXML User’s Guide details PunchOut
specification – http://www.cxml.org.

ƒ Ariba Supplier Network – Information about joining the Ariba Supplier Network –
http://supplier.ariba.com.

ƒ PerfectCommerce Supplier Network – Information about joining the


PerfectCommerce Supplier Network - http://www.perfect.com/suppliers/suppliers.html

Customer Service & Support

Questions should be directed to Four51’s help desk.

ƒ Online Resource Center: http://myaccess.four51.com

ƒ Telephone: 952.294.0451

Four51 PunchOut User Guide 7