Inbound Transmission For GTM Contact Doesn't Match Number Of Contacts In XML From EBS Party Synchronization
(Doc ID 2713363.1)
Last updated on APRIL 04, 2025
Applies to:
Oracle Shipping Execution - Version 12.2.3 and laterInformation in this document applies to any platform.
Symptoms
ACTUAL BEHAVIOR
---------------
Inbound Transmission for GtmContact element doesn't match number of contacts in XML from EBS Party Synchronization.
When doing a Party Sync from Oracle EBS into GTM, there are 819 total sites.
Due to an EBS setting, the party synchronization is split into 2 separate XML messages sent to OTM/GTM. First transmission contains 500 and the other containing the remaining 319.
This is creating two inbound transmissions.
However, the first inbound transmission has 1078 GtmContact elements (not 500), whereas the second and smaller transmission has exactly 319 GtmContact elements, which exactly matches the XML.
EXPECTED BEHAVIOR
-----------------------
The expected results should show the following breakdown of messages:
1 XML message with 500 GtmContact elements
1 XML message with 319 GtmContact elements
Changes
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 |