PRC:PO: Electronic Purchase Orders Are Not Transmitting From OSN / OBN
(Doc ID 2596769.1)
Last updated on OCTOBER 10, 2019
Applies to:
Oracle Fusion Purchasing Cloud Service - Version 11.13.19.07.0 and laterOracle Fusion Purchasing - Version 11.13.19.01.0 and later
Information in this document applies to any platform.
Symptoms
When a Purchase Order (PO) is approved, they should be transmitted to suppliers via Oracle Business Network (OBN) -- formerly Oracle Social Network (OSN), the following error occurs in B2B:
Error
======
Transport error: [IPT_HttpSendError] HTTP encounters send error :400 <?xml version='1.0'?><XHUB_HTTPSERVICE><RESPONSE TYPE="ERROR"><TEXT>"<![CDATA[CLIENT : [XHUB-174] An invalid user name was specified in the message envelope (Payload ID: XXXXXXXXXXXXXXXXX.PROD.doc-1)[XhubException:Err:174:Couldnt instantiate profile with Username and Password (username = XXXXXXX)]]]></TEXT></RESPONSE></XHUB_HTTPSERVICE>.
Steps to Reproduce:
1. Create and approve a Requisition.
2. Convert Requisition into a PO and Approve PO.
3. PO Automatically sent to Supplier.
4. PO Fails and does not make it to OBN.
5. PO fails in B2B with the above error.
Changes
OSN converted over to OBN.
Cause
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
| Symptoms |
| Changes |
| Cause |
| Solution |
| References |