Conceptual advice required for file receiver scenario

Question

Hi,
My scenario is to read 3 sets of data from SAP ERP and write files on the receiver system, one per data set.
I could create 3 service interfaces and set up Integration Builder configuration for each one but this seems messy.
Alternatively, if I create one service interface with 3 operations to group them, it is not possible to create the required files unless I add mapping and use dynamic configuration to determine the filename from the payload and set this in the receiver communication channel.
It seems to me that I would have benefited from the ability to define a rule in the receiver determination to define a different communication channel per operation where the specific filename could be specified.
It is only possible to bind a service interface to one communication channel in the receiver agreement.
What would you recommend as the cleanest and best approach to meet this requirement - 1 or 3 service interfaces, use of mapping or are there any alternatives?
Thanks in advance.
Alan
Edited by: Alan Cecchini on Aug 4, 2011 7:02 PM
Edited by: Alan Cecchini on Aug 4, 2011 7:02 PM

Answer 1

Basically your requirement is many to many mapping.  Please decide based on the sender system requirement. If your sender system sends different message structure then you can break into three diff interfaces and keep the interface simple.
You can route to three diff recievers based on the condition setting in the receiver determination or you can do in the mapping too. That is not the whole point. you need to think about how do pick the three different interfaces.  You might also consider using ccbpm for this. 
Refer the pattern that comes in the PI standard installation under SAP BASIS  SWCV.
BPMPatternSerializeMultipleTrigger or BPMPatternSerializeOneTrigger