| bernardH 2005-03-03, 5:53 pm |
| We have too the same issue but I do not like the proposed turn-around. We
are posting transactional stuff and won't like the risk of loosing a
transaction by getting through a file.
I would recommend to post the XML-IDOC to the message box where additional
orchestration instances do subscribe, got activated, and pick them up to
finish posting to the SAP adapter within a clean non-looping-and-ending
context each time... We suspect something to occur on orchestration exit
that closes the transaction with SAP and which is not invoked when
looping.... I think it's a shame to be forced to do so!
Some more bits of our own experiences:
We successfully fed SAP with thousand IDOCs of exactly the same brand (I
mean, same EDI_DC40 IDOC header, SAP gateway params and all stuff) without
loosing a single one provided they got posted each by a different
Orchestration instances. But in a loop construct within the same
orchestration..the result is random in SAP, sometimes we got them all,
sometimes some fail with a timeout condition on SAP side! sometimes no
trace at all...
We tried playing around send port parameters with no success.
It's called a BUG!
|