How can we decrease the number of 202 and 403 error messages occurring in RSSP?
Summary:
Since going live on RSSP we have seen an increase in 202 and 403 error messages occurring in Oracle. Does Oracle have any suggestions on how to eliminate or limit the connection issues to PunchOut suppliers?
We do have a suspicion that these errors increase during our high order volume timeframes during the day (9 a.m. and 2 p.m. CST).
Please note these errors occur for users who do have access, and the connection works most of the time.
Content (please ensure you mask any confidential information):
202 - (The punchout site that's defined in the iShopSmart catalog couldn't be reached. Contact the Procurement application administrator. (POR-2010064) Details: There is no response from the punchout site. The error code is 202.)