Professional Documents
Culture Documents
1 Page 1 of 1
In this Document
Purpose
Troubleshooting Steps
References
APPLIES TO:
Oracle Fusion Self Service Procurement Cloud Service - Version 11.1.4.0.0 and later
Oracle Fusion Self Service Procurement - Version 11.1.1.5.1 and later
Information in this document applies to any platform.
PURPOSE
This note was created to help Customers to diagnose what the underlying punchout issue might be in a
customer environment.
TROUBLESHOOTING STEPS
Please always run the Punchout Diagnostic Test (What Diagnostic Tests Are Available For Fusion Procurement
(Doc ID 1331902.1) ) , provide results and collect Appslogger log if an SR is necessary after you read this
document.
Below are the main things in the Appslogger log that will help us diagnose the issue. See end of page for an
example of what we are looking for in Appslogger log.
Note: Even though Punchout Diagnostic test might pass, it doesn't mean punchout will work. Our Punchout
Diagnostic test only tests the Login Request and Response part. Getting a status code 200 only means we can
communicate with the supplier successfully. However, if there are other issues like authentication issue, actual
punchout will still fail.
https://support.oracle.com/epmos/faces/DocumentDisplay?_adf.ctrl-state=158omf6smk_310... 3/8/2017