ITM Party Synchronization Fails With Process_flag=2 For Customers With Large Site Count
(Doc ID 2611008.1)
Last updated on JUNE 25, 2020
Applies to:Oracle Shipping Execution - Version 12.1.3 to 12.1.3 [Release 12.1]
Information in this document applies to any platform.
On : 12.2 version, Intl Trade Mgmt Integration
Observe that Party Synchronization fails record with process_flag = 2 for customers with large number of sites/locations.
This causes the orders for these customers to get stuck.
Below is the error messages for this record from the WSH_ITM_RESPONSE_HEADERS table.
ERROR_CODE = 101
ERROR_TEXT = Response XML document is unavailable
The thread worker logs show a "502 Proxy Error" in 2 logs: thread0 and thread1.
The Proxy Error also has this:
The proxy server could not handle the request
Reason: Error reading from remote server
==> The failed Party Sync occurs for customers with a large number (1000's) of sites/locations.
==> Each time party sync happens for the customer, it is sending over all thousands of records.
It is believed that the size of the transmission is just finally getting too large and the record is stuck.
==> The failure also produces "agent failure" emails from GTM. Inbound transmissions exist in GTM.
However, GTM gave an error "Process released to free resources (process=36794929/OPEN/Process Agent)".
Some or all of the data was transferred into GTM but it is possible that GTM didn't send an acknowledgement back to EBS.
But the orders cannot be processed because the specific Ship To party that the orders reference is not created in GTM.
The issue can be reproduced at will by running the Party Sync for a customer that has thousands of sites/locations
The issue has the following business impact:
Due to this issue, users cannot process the new sales order as party synch is failing.
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