Messages in multi-message format can only be sent to one Adapter Engine

[Former Member]

Hi,

Using XI 7.0 SPS 12 I have a scenario Single Flat File->XI->Multiple Messages to ECC.

Due to an annoying limitation/bug in ECC we have to send workorders in to be processed as individual transactions. This means generating seperate calls to ECC from PI.

I've adjusted my message map (No BPM) to split the source messages out, but when it calls the XI adapter to send them to ECC I get the following:

<!-- Technical Routing -->
<SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" 
xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" 
SOAP:mustUnderstand="">
	<SAP:Category>XIServer</SAP:Category>
	<SAP:Code area="OUTBINDING">CO_TXT_MMF_ENGINETYPE</SAP:Code>
	<SAP:P1/>
	<SAP:P2/>
	<SAP:P3/>
	<SAP:P4/>
	<SAP:AdditionalText/>
	<SAP:ApplicationFaultMessage namespace=""/>
	<SAP:Stack>
	Messages in multi-message format can only be sent to one Adapter Engine
	</SAP:Stack>
	<SAP:Retry>M</SAP:Retry>
</SAP:Error>

I am generating multiple structures under

messages/message1/xx_my_structure_repeated_at_this_level

which gives the correct amount of payloads in moni.

I believe this error is because the http/idoc adapters dont go through the AE and it is the AE that splits the multiple messages into individual calls. Is there a clean workaround which doesnt involve BPM or intermediate writing to disk etc?

Thanks

James.

Points awarded where appropriate.

[Former Member · Accepted solution]

Legg,

This is not possiable with out BPM for formation look into Jins Blog at the end

/people/jin.shin/blog/2006/02/07/multi-mapping-without-bpm--yes-it146s-possible

Regards

Sreeram.G.Reddy

[prateek]

<i>I believe this error is because the http/idoc adapters dont go through the AE and it is the AE that splits the multiple messages into individual calls.</i>

Perfectly correct

<i>Is there a clean workaround which doesnt involve BPM or intermediate writing to disk etc?</i>

May be writin a module.

Otherwise to avoid other development time, go for BPM.

Regards,

Prateek