<Insert Picture Here>

Punchout from iProcurement to Supplier

Oracle Support Services and the Proactive Support Delivery Team Clarina Allen and Linda Johnston

Why We Are Here?

The purpose of this presentation is to provide an understanding of:

The various punchout models

Basic setup steps

Troubleshooting steps

To help you prevent and resolve issues.

PREVENT

RESOLVE

Agenda

• Review of Models

• Setup - Profiles

• Certificates

• Mapping

• Demo - iProcurement Punchout

• Punchout to Purchase Order Process

• Troubleshooting

• Documentation and Notes

• Q&A

Discover More

4

Punchout Models

The Punchout Models available are:

• 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)

Punchout Models

• 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)

Transparent Punchout Models

• Transparent Punchout is used when you don’t want the user to see the actual supplier site. The system will search the supplier site and bring the item into the iProcurement search results page, along with the local items.

• The Transparent Punchout Models available are:

• Model 1: Transparent Punchout from Oracle iProcurement to Oracle Exchange (XML)

• Model 2: Transparent Punchout from Oracle iProcurement to Supplier-Hosted Catalog (XML)

Profile Setup

• POR : CA Certificate File Name: <full path and file name> In general this is set to $ORACLE_HOME/sysman/config/ b64InternetCertificate.txt

• In 11.5.10 or lower: file is ca_bundle.cert

• POR : Proxy Server Name: <set if using proxy server> Example: proxy.company.com • POR : Proxy Server Port: <set if using proxy server> Example: 80

Certificates

• If any supplier site involved in the Punchout process is using certificates which is not included in the b64InternetCertificate.txt (or the file from profile POR :CA Certificate File Name), append it in the file if SSL handshake errors is occurring.

• If the certificate has a chain, add all the certificates from the chain in the correct order.

• Bounce the middle tier after adding the certificates.

• Demonstration on the steps to copy the certificates to a text file.

Mapping Setup

• The mapping for Punchout is defined in the E-Commerce Gateway responsibility.

• Mappings are defined for UOM, Categories and Suppliers (For details see questions 16,17 and 18 from NOTE:206646.1 - Punchout FAQ)

• Suppliers are mapped, only for OAG XML and is optional.

• Demonstration steps to map UOM, categories and suppliers.

Punchout to the Supplier

• Model 2a: Punchout from Oracle iProcurement Directly to Supplier-Hosted Catalog – XML

• Model 2b: Punchout from Oracle iProcurement Directly to Supplier-Hosted Catalog – cXML

• Demonstration on steps to setup and punchout directly to the supplier from iProcurement

Punchout to PO Process

• A very common process is the buying organization after executing the Punchout and creating the requisition which turns to a PO, is to send the PO XML/cXML message to the supplier.

• The approval of Purchase Order (PO) generates cXML or OAG XML message according to the setup.

• PO cXML is sent directly to the supplier or…

• OAG XML is sent directly to the supplier or through OSN (Oracle Supplier Network) which will send the OAG XML or convert to cXML depending on the supplier setup.

Troubleshooting • Check the debug.log to see the XML message returned from

supplier. Sample of debug log.

• Refer to (Doc ID 290614.1) on how to get the debug.

• If file versions are current, certificates are in place, and the setup and profiles are correct, the issue could be on the supplier side:

. Can the supplier see the XML request in their server?

. Which access validation is done by the supplier system? (check if it matches with what is being sent by the XML/cXML request)

Manuals:

The Punchout models and the DTD for the XML/CXML messages are documented in the following manuals:

• Oracle Procurement Buyer's Guide to Punchout and Transparent Punchout

• Oracle Procurement Supplier's Guide to Punchout and Transparent Punchout

• DOC ID 109924.1 has links to these manuals

The documentation is the same for 11.5.10 and release 12. There is no specific manual for release 12.

Documentation and Notes

Notes:

• Note: 1177725.1 - Punchout White Paper - Release 12 (Doc ID 1177725.1)

• Note:206646.1 - Punchout FAQ

• Note:1390278.1 - How To Synchronize Exchange Punchout Suppliers

Documentation and Notes

16