11g B2B Drops Inbound EDI Transactions When Multiple Transactions In One File And Sequencing Enabled
Last updated on FEBRUARY 11, 2013
Applies to:Oracle SOA Platform - Version 188.8.131.52.0 and later
Information in this document applies to any platform.
This affects : 184.108.40.206.0 version, B2B Engine
You have a scenario where you receive multiple inbound EDI transactions (either multiple STs in one ISA or multiple ISAs) into B2B via JMS listening channel. You need to maintain sequencing and hence you provide a JMS header “ACTION_NAME” with value “TARGET:BalaTest". You sent three EDI transactions in one ISA into B2B. B2B created 3 business messages as expected and marked all the three transactions MSG_COMPLETE. However, you received only the last transaction in the ISA into your back-end application; the first 2 transactions did not come thru. When you remove the sequencing header, all three transactions are coming to back-end application as expected.
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms