My Oracle Support Banner

Applying a Patch With File icxprf.ldt Resets POR Proxy Profiles Incorrectly to Server and Port 80 Causing Punchout to Fail with 202 Error (Doc ID 1555953.1)

Last updated on JUNE 13, 2023

Applies to:

Oracle iProcurement - Version 12.1.3 to 12.2.6 [Release 12.1 to 12.2]
Information in this document applies to any platform.


The 'POR : Proxy Server Name' and 'POR : Proxy Server Port' profiles are seeded with an incorrect value and 80 respectively from icxprf.ldt.  Another incorrect seeded value is / 80 respectively

Customer applied 12.1 Patch 14665455:R12.ICX.B, which provides icxprf.ldt 120.30.12010000.9 (or applied 12.2 Patch 21974301:R12.ICX.D or similar which provides icxprf.ldt 120.35.12020000.6 through 120.35.12020000.14 )

... from the icxprf.ldt 120.30.12010000.9 file

It is not clear why the profile is seeded with this value.

Due to this issue, iProcurement users are not able to punchout to supplier, until the POR: Proxy Server Name profile value is manually updated and the oc4j (iAS/Apache) is bounced.  The punchout gets a 202 error.

1. Check that the POR : Proxy Server Name profile is set to the correct SITE level value.
2. Do punchout from iProcurement to a supplier and the punchout works fine.
3. Apply a patch that contains icxprf.ldt (Example: <Patch 14665455>:R12.ICX.B)
4. Check that the POR : Proxy Server Name profile is set to an incorrect value by the patch.
5. Try the punchout again from iProcurement to the supplier, and the punchout fails to connect because the profile has been set to an invalid value by the patch.

The workaround is to update the profile option 'POR : Proxy Server Name' at the SITE level to the correct value.



To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!

In this Document

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.