Punchouts – Introduction & Implementation Details

Oracle Cloud Procurement

Srini Samy & Ananya Peddu

May 31, 2016

© Copyright 2016. Apps Associates LLC. 1
 Confidentiality

The content of this document is proprietary, confidential information pertaining to

Apps Associates’ products, services, solutions and methods. Information herein is
intended for use by the client or prospective client only and must not be shared
with any third party without consent from Apps Associates.

© Copyright 2016. Apps Associates LLC. 2

 Goal/Target Audience
• Course Goal/Expectations
– Introduce Punchout functionality
– Components required for enabling Punchout in Cloud Procurment
– Implementation Steps in Cloud Procurement
• Target Audience
– Anyone interested in Cloud Procurement/Punchout
– Everyone in the Cloud ERP Practice
• Assumptions
– Familiar with concepts like Vendor, Vendor Site, Purchase Order, Requisition, UOM,
Categories, etc. Those are not explained in this session.

© Copyright 2016. Apps Associates LLC. 3

 Agenda
• Punchouts – Introduction
• Punchouts – Implementation Details
– To Supplier
– To Catalog Hosting Supplier
• Documentation
• Wrapup
• Q&A
• Contact Info

© Copyright 2016. Apps Associates LLC. 4

 Introduction
• What is a Punchout?
• Why do customers need it?
• Is it different from eBS?
• Different Models available for Punchouts, How are they different?
• How to choose the right one for your customer?
• Focus on one specific model in detail

© Copyright 2016. Apps Associates LLC. 5

 Introduction
• Punchout – a functionality available in SSP, allows employees to
create a requisition using online shopping-like functionality, go to a
supplier’s website, search thru a catalog, add it to the cart, return to
SSP to submit a requisition.
• Why – Products that are highly configurable, dynamic items and
pricing, costly and difficult to maintain as a local catalog or Inventory
Items
• Advantages - reduced cost/effort; increased efficiency
• Different from eBS? No. Same functionality.

© Copyright 2016. Apps Associates LLC. 6

 How does it work?
1. Setup a punchout catalog (connection to supplier site)
2. Add punchout catalog to a Content Zone (security, who can see it)
3. Define Mapping (BU level, Supplier level) – more later
4. User Logs in to SSP, accesses catalog, go to Suppliers’ site
5. Search and add items to cart, Check out. No need to pay now.
6. REQ is created in SSP using the contents of the shopping cart.
7. UOM, Categories, Supplier, etc., are derived based on mapping
assigned to the catalog
8. REQ triggers approval WF; PO is created when REQ is approved.

© Copyright 2016. Apps Associates LLC. 7

 How does it work?

1
2

4/5/6/7

© Copyright 2016. Apps Associates LLC. 8

 Available Models
• Available Models
• How to choose the right one for your customer?
• Focus on one specific model in detail

© Copyright 2016. Apps Associates LLC. 9

 Punchout Models in Oracle SSP
Model Name Description
IS THE CONTENT ON SUPPLIER SITE OR ORACLE
Model 1 From SSP to Oracle Exchange (XML) EXCHANGE?
Model 2a From SSP to Supplier Hosted Catalog
(XML) Exchange Supplier Site

Model 2b From SSP to Supplier Hosted Catalog

(cXML) MODEL 1 DO YOU WANT TO PUNCHOUT VIA EXCHANGE?

Model 4 From SSP to Supplier Hosted Catalog via

Yes No
Oracle Exchange (XML)
Model 5 From SSP to Supplier Hosted Catalog via WHICH PROTOCOL DO YOU WANT TO
USE?
WHICH PROTOCOL DO YOU WANT TO
USE?
Oracle Exchange (cXML)
Model 3a & 3b Punchout from Oracle Exchange to XML cXML XML cXML
Supplier hosted catalog. Not available in
Cloud Procurement in the current release.
MODEL 4 MODEL 5 MODEL 2a MODEL 2b

© Copyright 2016. Apps Associates LLC. 10

 Detailed Information about all the Models
• Punchout in Fusion Self Service Procurement Explained (Doc ID
1323912.1)

© Copyright 2016. Apps Associates LLC. 11

 Model 2b

© Copyright 2016. Apps Associates LLC. 12

 Model 2b - Advantages
• Point to Point connection between Customer & Supplier
• Allows supplier to control security – which buyers access their site
• Maintain cXML catalog (items, configurations, prices) specific to this
customer

Mapping
1. Any supplier specific mapping @ Catalog level applied, if exists.
2. If none, Use any mapping defined at Procurement BU of the catalog
3. If not, no mapping is performed.

© Copyright 2016. Apps Associates LLC. 13

 Components, Where to Setup?
Where Objects Functionality
Cloud ERP Suppliers, Sites, DUNS#, UOM, Punchout
Purchasing Categories
SSP Catalog, Content Zone, Map Sets Punchout

B2B B2B Definition for Customer, Electronic xmission

Console Partners, Documents, Agreements of documents
OSN Partners, Message Queue, cXML Electronic xmission
Messages of documents

© Copyright 2016. Apps Associates LLC. 14

Configure Punchout to (End) Supplier
Rel. 9 & Rel. 10

© Copyright 2016. Apps Associates LLC. 15

 Step 1. Create Supplier and Site
How much lead time do you need to deploy a punchout configuration?
How much lead time do you need to migrate punchout setup in Production? Do you migrate to production any day of the week OR only certain
days of the week?
Who is the Punchout contact at your site? Name –
What is their contact info? Email –
Phone -
Is there a test punchout site? If yes, please provide credentials. URL =
User ID=
Password =
Provide credentials to production punchout site. URL =
What is the preferred authentication method? Domain ID or DUNS#? User ID =
Password =
Will you accept POs transmitted by fax, email? Or, will you accept POs by cXML format only?
Are the items in the TEST punchout site assigned with UNSPSC codes? Please provide the list of codes used for TEST site.
Are the items in PRODUCTION punchout site assigned with UNSPSC codes? Please provide the list of codes used in Production punchout site.
Provide the list of Unit of Measure codes for the items in your punchout site. If they are different between TEST and production, provide both lists.
Authentication details for cXML data exchange
- Test
- Production
Do you have an account with Oracle Supplier Network (OSN)? If yes, what name is your company listed under?
What documents do you accept as cXML thru OSN?
PO Creation (007)
PO Change (006)
What is your DUNS#?

© Copyright 2016. Apps Associates LLC. 16

 Step 1. Create Supplier and Site

Use an ID with Supplier Manager role assigned to Create/Edit a supplier.

Create a Supplier, an address, a site and assign site to the Procurement BU.

© Copyright 2016. Apps Associates LLC. 17

Step 1. Create Supplier and Site

© Copyright 2016. Apps Associates LLC. 18

Step 1. Create Supplier and Site

© Copyright 2016. Apps Associates LLC. 19

Step 1. Create Supplier and Site

© Copyright 2016. Apps Associates LLC. 20

Step 2. Create Catalog

© Copyright 2016. Apps Associates LLC. 21

Step 2. Create Catalog

© Copyright 2016. Apps Associates LLC. 22

Step 2. Create Catalog

© Copyright 2016. Apps Associates LLC. 23

Step 2. Create Catalog

© Copyright 2016. Apps Associates LLC. 24

Step 2. Create Catalog

© Copyright 2016. Apps Associates LLC. 25

Step 2. Create Catalog

© Copyright 2016. Apps Associates LLC. 26

Step 3: Attach Image URL for Catalog

© Copyright 2016. Apps Associates LLC. 27

 Step 4: Mange Content Zones

Create Content Zones as needed – like Office Supplies, Chemicals, Consulting Services.
Catalogs are assigned to Zones. Zones are assigned to BU/Users. This way, we can
control who can see certain Supplier Punchouts.

© Copyright 2016. Apps Associates LLC. 28

Step 4: Manage Content Zones

© Copyright 2016. Apps Associates LLC. 29

Step 5: Create Mapping

© Copyright 2016. Apps Associates LLC. 30

Step 5: Create Mapping

© Copyright 2016. Apps Associates LLC. 31

Step 5: Create Mapping

© Copyright 2016. Apps Associates LLC. 32

 Step 5: Create Mapping
This UOM and Category
values will appear on the
REQ Lines based on
External values sent by
the supplier.

8 Digit UNSPSC code sent

by Supplier site in the cart.
Map those to Purchasing
Category values.

Need to have Desktop Application

Integrator installed locally for the
spreadsheet upload functionality to work.

© Copyright 2016. Apps Associates LLC. 33

Step 6: Assign MapSets to Supplier Catalog

© Copyright 2016. Apps Associates LLC. 34

User Experience - Punchout

© Copyright 2016. Apps Associates LLC. 35

User Experience - Punchout

© Copyright 2016. Apps Associates LLC. 36

User Experience - Punchout

© Copyright 2016. Apps Associates LLC. 37

 User Experience - Punchout
• Upon return, a Requisition is created with one or more lines, based on # of items in
the cart returned from the supplier.
• Verify the UOM Code, Category Code are populated for every REQ Line.
• Verify the quantity, cost.
• Submit the REQ for approval.
• Approval WF will fire, get necessary approvals based on the REQ Total Amount.

© Copyright 2016. Apps Associates LLC. 38

 Configure B2B
if Customer has the requirement to electronically
transmit the document(s) to Supplier

© Copyright 2016. Apps Associates LLC. 39

 What are the Documents?
Typically
• Purchase Order – Outbound
• PO Change Request – Outbound
• AP Invoice – Inbound

You choose the document(s) by Supplier.

© Copyright 2016. Apps Associates LLC. 40

 Step 1: Configure Customer Info

Search for Task = Configure Oracle B2B e-Commerce Gateway Setups

Go to this task.
It will launch a new window/tab on your browser.
OR
Go there directly using URL- https://exxx-xxxx.fs.us2.oraclecloud.com/b2bconsole
If you don’t have an active session, it will prompt for credentials.
© Copyright 2016. Apps Associates LLC. 41
Step 1: Configure Customer Info

© Copyright 2016. Apps Associates LLC. 42

Step 1: Configure Customer Info

© Copyright 2016. Apps Associates LLC. 43

 Step 2: Configure eCommerce Partner

Add a Partner. Give it a name.

Select Supplier Site that needs to be enabled for B2B.

© Copyright 2016. Apps Associates LLC. 44

Step 2: Configure eCommerce Partner

© Copyright 2016. Apps Associates LLC. 45

Step 2: Configure eCommerce Partner
URL = https://osn-prod.oracle.com:443
/HTTPService/Receiver
Username = <OSN Username>
Password =
ATH =
USERNAME=awhelan#PASSWORD=Welc
ome1#DOC_TYPE=PROCESS_PO_007#D
OC_FORMAT=OAG#FORMAT_VERSION=
007#DOC_REF=001#RECEIVER_ID=0799
28354#RECEIVER_ID_TYPE=DUNS#SEND
ER_ID=021905363#SENDER_ID_TYPE=D
UNS#

© Copyright 2016. Apps Associates LLC. 46

Step 2: Configure Partner Agreement

© Copyright 2016. Apps Associates LLC. 47

Step 2: Configure Partner Agreement

© Copyright 2016. Apps Associates LLC. 48

Step 2: Configure Partner Agreement

© Copyright 2016. Apps Associates LLC. 49

Step 3: Attach B2B profile to Supplier Site

© Copyright 2016. Apps Associates LLC. 50

 Validation

© Copyright 2016. Apps Associates LLC. 51

 OSN Setup

https://osn.oracle.com/snw/faces/home.jsf
© Copyright 2016. Apps Associates LLC. 52
 OSN Setup

© Copyright 2016. Apps Associates LLC. 53

 OSN Setup

© Copyright 2016. Apps Associates LLC. 54

 OSN Setup

© Copyright 2016. Apps Associates LLC. 55

 OSN Setup

© Copyright 2016. Apps Associates LLC. 56

 OSN Setup

© Copyright 2016. Apps Associates LLC. 57

 OSN Setup

© Copyright 2016. Apps Associates LLC. 58

Configure Punchout to Catalog Hosting Supplier
Rel. 9 & Rel. 10

© Copyright 2016. Apps Associates LLC. 59

 Key Differences
• Supplier is just a catalog host; does not actually sell any products
• Typically hosts catalog from multiple suppliers, many of whom could be direct
supplier to your customer
• Value-add is the pre-negotiated price, often better than what your customer can
get from the end supplier
• Punchout connection is to the catalog host supplier
• Need to create a new Supplier mapping to translate the DUNS# to Supplier
• If Supplier is not defined (DUNS# not found), it will fail since REQ lines will fail to
identify the actual supplier. So, additional business process needed to configure
new Supplier(s) and update Supplier mapping.
• One REQ can refer to multiple suppliers => multiple POs.
• End Supplier Site name need to match DUNS# returned in the cart.

© Copyright 2016. Apps Associates LLC. 60

Punchout to Catalog Host Supplier
Supplier = SciQuest
Catalog definition is same.
One extra step in Mapping definition.

© Copyright 2016. Apps Associates LLC. 61

Punchout to Catalog Host Supplier

© Copyright 2016. Apps Associates LLC. 62

Punchout to Catalog Host Supplier

Typically DUNS#

© Copyright 2016. Apps Associates LLC. 63

Punchout to Catalog Host Supplier

© Copyright 2016. Apps Associates LLC. 64

Punchout to Catalog Host Supplier

© Copyright 2016. Apps Associates LLC. 65

 Terminology
• SSP – Self Service Procurement, part of Cloud Procurement
• OSN – Oracle Supplier Network
• XML, cXML – Commerce eXtensible markup language
• OAG – Oracle Applications Group, proprietary standard of XML (OAGXML) used to
communicate between Cloud ERP and OSN.
• B2B – Business to Business
• Catalog – Secure connection to a Supplier’s website
• Mapping – Data Transformation logic to map UNSPSC, UOM codes sent in the cart
by Supplier site to Oracle Cloud ERP values.
• DUNS# - Unique Identifier for a supplier for eCommerce
• UNSPSC Code – (United Nations Standard Products and Services Code) Universal
Identifier for product categories, specifically among items that are present in a
catalog. 99990000 (parent level), 99999999 (detailed)
© Copyright 2016. Apps Associates LLC. 66
 How Would You Go About this?
• Requirements Gathering for your Punchout Implementation
• From your Customer • From each Supplier
• Supplier Names • Connection Details (for catalog)
• Integration Needs • OSN Details
• Punchout Contacts • DUNS#
• Document names • Testing Cycle
• OSN Details • Test/Prod Switch notice period
• UOMs • UOM
• Purchasing Categories • UNSPSC Codes

© Copyright 2016. Apps Associates LLC. 67

 Common Issues
• UOM code is empty
• Category code is empty
• Requisition can’t be edited in Oracle
• Unable to submit mappings – ADI not installed/not configured correctly
• Messages stuck in OSN – Supplier hasn’t created/updated settings on their side
• B2B message delivery errors – incorrect OSN Password or syntax error in parameters

© Copyright 2016. Apps Associates LLC. 68

 Lessons Learned
• One-time help, per instance, needed from Oracle Support to
enter Keystore password before configuring B2B Console; Need
to raise SR w/ Oracle.
• Some Suppliers use high-level UNSPSC codes, some use low level
codes; Impacts # of entries to create in the category mapping.
• Authentication in multiple ways (Unique ID, DUNS#, etc.)

© Copyright 2016. Apps Associates LLC. 69

 Documentation
• Punchout in Fusion Self Service Procurement Explained (Doc ID 1323912.1)
• How To Setup Punchout In Self Service Procurement (Doc ID 1626210.1)
• Self Service Procurement Punchout Checklist/Diagnostic For Customers (Doc ID
1925547.1)
• How to Generate Electronic PO (cXML) For Punchout Supplier? (Doc ID 1983059.1)
• Where Is The Documentation To Configure Punchout Suppliers Within Fusion Self-
Service Procurement (Doc ID 1384564.1)
• https://www.unspsc.org/search-code for UNSPSC code lookup

© Copyright 2016. Apps Associates LLC. 70

 Wrapup
We talked about
• Punchout – definition, need, available models, how to choose
• Model 2a details
• Steps to configure Punchout / Catalog
• Steps to configure B2B
• OSN – how to login, get prod/test URL, register partners,
download cXML messages for debugging
• Lessons Learned
• Documentation Links

© Copyright 2016. Apps Associates LLC. 71

 Contact Info
• ANANYA PEDDU: ananya.peddu@appsassociates.com
• SRINI SAMY: srini.samy@appsassociates.com

© Copyright 2016. Apps Associates LLC. 72

Q&A
Thank You!