OBN - Receiver Is Unable To Receive The HTTP POST Request via Amazon Web Services (AWS) (Doc ID 3067484.1)

Last updated on JANUARY 21, 2025

Applies to:

Symptoms

Oracle Business Network (OBN) receiver is unable to receive the HTTP POST request and it was noticed there were failures occurring while receiving invoices from Amazon Web Services (AWS) through to OBN.

Below is the error message in OBN Monitor screen:

ERROR
-----------------------
Receiver is unable to receive the HTTP POST request. Receiver site may be unavailable.
502 {"message": "Internal server error"}

 "Activity" Cause Control Number Date Error Code Error Message Possible Remedy
-----------------------------------------------------------------------------------------------
OBN To TP Receiver is unable to receive the HTTP POST request. Receiver site may be unavailable. 20241220.201507515.PROD.doc-1 12/20/2024 20:15 261 HTTP POST Exception No action needed. The message will continue to be retried for 72 hours from time of first delivery attempt.
OBN To TP(HTTPS URL Connection) 20241220.201507515.PROD.doc-1 12/20/2024 20:15

STEPS
-----------
1. From Trading Partner an invoice is transmitted to OBN
2. Invoice files gets transferred via https post to AWS.  This step in the process is when the reported error occurs intermittently
3. Normally a custom program pulls the files from AWS to EBS custom staging table
4. Wrapper program parses the xml files and then write the data into AP_INVOICES_INTERFACE and AP_INVOICE_LINES_INTERFACE tables
5. Payables Open Interface Import is run to import the invoices

Changes

 Implemented AWS custom interface to utilize directly OBN in lieu of XML Gateway.

Cause

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