Procurement - EBS (MOSC)

MOSC Banner

Punchout - XML Gateway - HTTP Bad Request Error

in Procurement - EBS (MOSC)

Hi Team,

We are experiencing issues when connecting to HTTP web from XML Gateway. Below is the error summary.

Can someone pls review and help on this issue ?

ECX_OXTA_LOGMSG- Gives the OTA status message for this Outbound Transaction

STATUS RESULT_CODE RESULT_TEXT TRANSACTION_TYPE PROTOCOL_TYPE PROTOCOL_ADDRESS EXCEPTION_TEXT BEGIN_DATE COMPLETED_DATE

COMPLETED 3000 Bad Request PO HTTP http://XXXXX.com:8080/HTTP?Format=cXML&HTTPInterface=syncReply Response: HTTP/1.1 400 Bad Request Content-Type: text/html Content-Length: 836 Date: Fri, 09 Nov 2018 09:09:01 GMT Connection: close Server: BIS6.5.2SP52

SEEBURGER HTTP Controller

400: 400 - ERROR: Empty File.

09-NOV-2018 01:08:59 09-NOV-2018 01:09:01

COMPLETED 3000 Bad Request PO HTTP

Tagged:

Howdy, Stranger!

Log In

To view full details, sign in to My Oracle Support Community.

Register

Don't have a My Oracle Support Community account? Click here to get started.

Category Leaderboard

Top contributors this month

EBS Procurement Tags

Instructions for posting

×

1. Select a discussion category from the picklist.


2. Enter a title that clearly identifies the subject of your question.


3. In the body, insert detailed information, including Oracle product and version.


Please abide by the Oracle Community guidelines and refrain from posting any customer or personally identifiable information (PI/CI).


Cloud / Fusion customers - Our Cloud community has moved! Please go to Cloud Customer Connect .


New to My Oracle Support Community? Visit our Welcome Center

MOSC Help Center