Punchout through iProcurement
Punchout enables buyers to click a link that goes to a supplier’s catalog, search for items on the supplier’s site, and return those items directly to the buyer’s shopping cart. If punching out from Oracle Exchange, buyers add the supplier’s items to their shopping cart on Oracle Exchange. If punching out from Oracle iProcurement, requesters add the external items to their shopping cart in Oracle iProcurement.
Punchout offers seven models:
- 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)
In the example below, we will see how to implement Model 2a…
In the illustration above:
1. The requester logs on to Oracle iProcurement.
2. From Oracle iProcurement, the requester clicks a punchout link to the supplier site.
3. The supplier authenticates the requester and returns a response.
4. Oracle iProcurement redirects the requester’s browser to the supplier site for shopping.
5. When the requester finishes shopping, the supplier site returns the shopping cart items to Oracle iProcurement via the requester’s browser.
6. The requester completes the checkout process, and Oracle iProcurement processes the order.
Punchout Setup
Buyer Setup
1. Prerequisites
If the supplier’s site is secure, verify your access to secure sites.
a. Verify Access to Secure Sites
Certification Authorities List Accessing a secure site involves making sure the site is on the accessing application’s certification authorities list
For Models 2a and 2b: Punchout from Oracle iProcurement Directly to Supplier-Hosted Catalog (XML or cXML), the supplier’s certification authority needs to be on the ca-bundle.crt file in Oracle iProcurement
b. How To Add The Certificate To The Apache Certificate File For Punchout Suppliers Using HTTPS?
When a Punchout is attempted to a supplier, using https, in order to create a Secure connection between the Oracle E-Business Suite Middle Tier Server and the Punchout Destination, the certificate must be present in the certificate file that is used by the E-Business Suite Middle Tier – Apache Web Server.
1. Locate the punchout url that is being used in the Catalog definition in iProcurement.
***Initially catalog should be defined for url adress entrance.
iProcurement Catalog Administrator Responsibility > eContent Manager > Manage Content > Catalogs > Create
Select Punchout Catalog, then press Continue.
Define the type of external catalog by selecting a Source; Supplier and Access Method; Direct punchout (Oracle native XML), then press Continue.
Enter catalog information using the fields below and press Submit when you are finished.
*Indicates required field.
Supplier URL address is entered at punchout URL tab as you can see above. This is done in the iProcurement Catalog Administration in release 11.5.10. (above)
For release 12, it is in the Content Zones Section of iProcurement Catalog Administration. (See above)
2. Next, utilize the web browser to connect to the https url that was used in the Punchout.
In this example, Firefox browser is being used, which has a plugin installed called cert-viewer.
This Firefox plugin allows for viewing and saving a SSL certificate.
This Firefox plugin allows for viewing and saving a SSL certificate.
Double click the lock (Lower Right Hand Corner – Pictured Above) to view the certificate.
- Now choose the View Button – and the screen below will appear
- Now choose the View Button – and the screen below will appear
From this screen, choose Export – which then brings up a ‘Save’ screen (See below)
Choose the Format – X-509 Certificate with chain (PEM) – as seen above. Save it to the local PC
3. Now, it is necessary to confirm what certificate is being used by iProcurement.
This is done by logging into the application as System Administrator – and moving to Profile/System – to query on the Profile - POR : CA Certificate File Name
This is done by logging into the application as System Administrator – and moving to Profile/System – to query on the Profile - POR : CA Certificate File Name
Take note of the file location – this is the actual location on the middle tier Apache iAS server.
4. Upon confirming the location of the certificate, proceed to use a telnet program to access the middle tier – where the certificate resides.
Move to the directory where the certificate is located on the iAS middle tier server - and use vi or other text editor to open and add the contents from the certificate saved on the local PC – into the certificate that is on the middle tier server – which was referenced in the profile. It is best to back up the certificate file prior to making any changes – seen above. Highlight and copy the complete contents from the saved certificate file.
Adding the certificate just after the ## comment signs in the current certificate file is recommended. Cut and paste the complete contents from the Local PC text file into the certificate file on the server.
Save the newly modified certificate changes on the middle tier server.
Save the newly modified certificate changes on the middle tier server.
5. Restart the Apache iAS web server, and confirm that now connectivity is possible as the Apache iAS is now able to properly authenticate to the Supplier using https.
NOTE: It has been found that with release 12.X – a complete recycle of the middle tier may be required, and not just the Apache iAS
Retest and confirm that the Handshake is now properly taking place.
Note: If you use proxy authorization, you will get an time out error. For this reason proxy authorization should be bypassed for only Punchout connection.
2. Set Profile Options in Oracle iProcurement
POR: Proxy Server Name
Enter the proxy server (Web server) name if your Oracle iProcurement implementation has a proxy setup. The proxy server name is typically the same as the proxy server that is set up in people’s browsers in your company—for example www-proxy.company.com.
POR: Proxy Server Port
Enter the proxy server port on which the proxy server listens, if your Oracle iProcurement implementation has a proxy setup. The port is typically the same as the port that is set up in people’s browsers in your company—for example, 80.
3. Define Supplier Punchout in Oracle Procurement
We have already mentioned this step at prerequisite part.
After the supplier has set up punchout access to its Web store, use this step to create a punchout link in Oracle iProcurement to the supplier’s site.
Note: The setup in this step applies to all operating units.
To create a punchout link directly to the supplier’s site:
1. Log on to Oracle iProcurement using the Catalog Administration responsibility.
2. Click the “eContent Manager” link.
3. In the navigation bar at the left, click the “Manage Catalogs” link.
4. On the Manage Catalogs page, click Create.
5. On the Create Catalog page, select “Punchout catalog” and click Continue.
6. On the Create External Catalog page -
- Select a Source of Supplier.
- Select an Access Method of Direct Punchout (Oracle native XML) if you are setting up a Punchout to a supplier using XML
4.Add Catalog to Store
Any catalog you create must be assigned to a store to be searchable. Once your punchout catalog is ready for use, assign it to a store.
To add catalog to a store (required) and sequence it (optional):
1. Log on to Oracle iProcurement using the Catalog Administration responsibility.
2. Click the “eContent Manager” link.
3. In the navigation bar on the left, click the “Manage Stores” link.
4. On the Manage Stores page, do either of the following:
- Click a store’s Edit icon to add the catalog to an already-created store.
- Click Create to create your own store and add the catalog to it.
Follow the guidance online and in the Help icon if you need more help creating and editing stores.
5. Once you have selected the catalogs you want to include in the store, click Continue.
iProcurement Catalog Administrator Responsibility > eContent Manager > Manage Content > Stores > Create Store
After entering store name and description you should add catalog to store and click submit button.
5. Set Up Data Mapping in Oracle e-Commerce Gateway
Use Oracle e-Commerce Gateway to map the following values that the supplier sends to values you use in Oracle iProcurement:
- Supplier
- Supplier site
- Unit of measure (UOM)
- Category
Punchout and transparent punchout do not use currency mapping in Oracle e-Commerce Gateway, but recognize only the International Standards Organization (ISO) currency codes.
Supplier and Supplier Site Mapping
Example Mapping of XXX Supplier Catalog
Supplier site id information is entered EDI Location tab and catbuy side should be informed to entervalue 14915 and leave blank supplier name and site information in the XML file for XXX Supplier Catalog.
Unit Of Measure (UOM) Mapping
eCommerce Gateway Responsibility > Setup > Code Conversion > Define Code Conversion Values
You can see UOM comparison details between Catbuy and Oracle at below file.
Category Mapping
eCommerce Gateway Responsibility > Setup > Code Conversion > Define Code Conversion Values
Catbuy is sent generic code 99999999 for all catalog item’s category code. Category code (MISC.MISC.MISC.MISC.STANDARD) mapping has been done with generic code 99999999 as you can see below.
<category>
<categoryCode categoryCodeIdentifier=”">
</category>
Some useful Note-id’s from Metalink to Resolve Common Issues
Although every setup is done, there are chances of getting connection problem error. If you come across any connection issues, please refer to the below Metalink notes to resolve them.
- 399856.1: NullPoint Exception After Clicking On The Punchout Link
- 356128.1: How to Run the Punchout TEST Delivered With Oracle Applications?
- 344339.1: Punchout Fails With Error Code: 201 Unable To Reach Supplier Site
- 274816.1: Punchout Getting 201 Error – Unable To Connect To Supplier
0 comments