My Oracle Support Banner

B2B Does Not Fire The Trigger For Batching, Though The Expire Time Has Passed (Doc ID 469848.1)

Last updated on MARCH 25, 2019

Applies to:

Oracle B2B 10g (Business to Business) - Version 10.1.2.0.2 to 10.1.2.3.0
Information in this document applies to any platform.
***Checked for relevance on 12-Oct-2010***


Symptoms

After setting the value of mergeMsgSize to 500, B2B seems to successfully process 5000 orders so
far which converts to a 10 MB file in EDI Native format. However it is observed that for a given
TP, if the BPEL/Back-end system continues to enqueue messages into B2B, though the Expire time
occurs B2B does not fire the trigger for batching, instead it continues to wait till the BPEL
completes the enqueuing which should not be the case. As soon as the expire time occurs B2B should
fire the batching with the existing records in queue.


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

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