Oracle Cloud offers a broad portfolio of software as a service applications, platform as a service, and social capabilities, all on a subscription basis. Oracle Cloud delivers instant value and productivity for end users, administrators, and developers alike through functionally rich, integrated, secure, enterprise cloud services.
 Get a Free Magzine ...Profit:The Executive's Guide to Oracle Applications

Subscribe to the OracleAppsHub to receive notifications when there are new posts:

 get RSS feed
 Oracle Fusion Applications (OFA) is a portfolio of next generation suite of software applications from Oracle Corporation. It is distributed across various product families; including financial management, human capital management, customer relationship management, supply chain management, procurement, governance, and project portfolio management
 Get a Free Magzine ...Profit:The Executive's Guide to Oracle Applications

Guide to Punch Out : When To Use Punchout

Posted on January 17th, 2013 by Sanjit Anand ||Email This Post Email This Post

Have you tried OracleappsHub in ipad/iphone/smart Phone? Don't wait. try it today

This is very common question , you might think and try to under stand , when to use PunchOut ?

Punchout is particularly useful for products that are configurable or include highly variable or dynamic items and pricing. These products are difficult and costly to maintain in a buyer hosted catalog.

In last post , you have observed various model of punchout models thats provide you with the flexibility to pick the model that best works for you.

  • Model 1: Punchout from Oracle iProcurement to Oracle Exchange ( XML)
  • Model 2a: Punchout from Oracle iProcurement Directly to Supplier-Hosted Catalog (XML)
  • Model 2b: Punchout from Oracle iProcurement Directly to Supplier-Hosted Catalog(cXML)
  • Model 3a : Punchout from Oracle Exchange to Supplier-Hosted Catalog (XML)
  • Model 3b: Punchout from Oracle Exchange to Supplier-Hosted Catalog (cXML)
  • Model 4: Punchout from Oracle iProcurement to Supplier-Hosted Catalog via Oracle Exchange (XML)
  • Model 5: Punchout from Oracle iProcurement to Supplier-Hosted Catalog via Oracle Exchange (cXML)

OPTING YOUR NEED: SELECTING A PUNCHOUT MODEL

iProcurement and Exchange support various punchout models.

It is important for both buyers and suppliers to decide on the model they want to use before implementing the punchout. The following table compares the punchout models:

Model /Options Buyer Benefits Suppliers Benefits

Model 1:

Punchout from Oracle iProcurement to
Oracle Exchange (XML)

  • iProcurement requesters have access to all supplier catalogs defined on Exchange.
  • They can comparison shop among suppliers on Exchange. They
    have a similar user interface experience as in iProcurement.
  • Suppliers load their catalog items once on Exchange and reach many iProcurement customers in addition to the buyers already registered on Exchange.
  • The Exchange catalog supports features such as buyer pricing , price breaks,and price effective dates

Model 2 (a), 2(b)

Punchout from Oracle iProcurement
Directly to Supplier-Hosted Catalog
(XML)/(cXML)

  • This model offers a unique,point-to-point solution between the
    buyer and supplier
  • Supplier closely manages the content.
  • Supplier can control access by allowing only certain buyers to access the site.

Model 3 (a) , 3(b)

Punchout from Oracle Exchange to
Supplier-Hosted Catalog (XML or cXML)

  • Buyers have access to a centralized collection of punchouts simply by registering with Exchange.
  • Purchasing Managers on Exchange can control buyer access to specificpunchouts using the Control Punchout Access page.
  • Suppliers only have to define their punchouts on Exchange once, rather than configuring punchout separately for each iProcurement customer.
  • Suppliers can control the visibility of their punchout definitions by publishing or unpublishing the punchout on Exchange.

Models 4 and 5


Punchout from Oracle iProcurement to
Supplier-Hosted Catalog via Oracle Exchange (XML or cXML)

  • iProcurement requesters have access to a centralized collection of punchouts.
  • iProcurement administrator does not have to configure a punchout for each supplier, but can just download the supplier’s punchout definition from Exchange.
  • The punchout’s passing via Exchange is transparent to the requester.
    Exchange translates cXML to XML seamlessly.
  • Suppliers only have to define their punchouts on Exchange once, rather than configuring punchout separately for each iProcurement customer.
  • Suppliers can control the visibility of their punchout definitions by publishing or unpublishing the punchout on Exchange.
  • Suppliers already maintaining cXML catalogs can continue to use those

The figure below shows the process for deciding which model to use.

Opting for PuncxhOut Model

For all models, make sure of the following prerequisites:

  • Make sure the supplier supports the punchout.
  • If the supplier’s site is secure, verify your access to secure sites.
Related Posts

Posted in Oracle Purchasing | No Comments »Email This Post Email This Post |

Have you tried OracleappsHub in ipad/iphone/smart Phone? Don't wait. try it today
Leave a Comment

Please note: Comment moderation is enabled and may delay your comment. There is no need to resubmit your comment.