Multi mapping in Extended receiver determination

[#1]

Hello Experts

I have a scenario where I want to keep operation mapping of Extended receiver determination common across multiple ICOs. One option we are trying is to make it N:1 where source will have multiple different Service Interfaces of multiple ICOs and receiver will have Receivers SI from SAP Basis component.

But this seems to be not working at runtime where I am getting error as No receivers found.

For testing purpose if I map constant value (receiver name) with receivers node in extended message mapping (instead of evaluating based on condition) then it works fine.

My doubts -

1. Is it possible to use multi mapping at extended Receiver determination step?

2. Is it because of the 'Messages' tab that is added for multi mappings? adding Java/XSLT map to insert messages tags will help ?

Can someone throw some light on this please?

Tried searching community forum for such configuration but didn't find relevant threads.

Thanks

Minal

[alex_bundschuh]

I don't think that this will work, for n:1 mappings you need to keep a state hence BPM is needed

Alex

[minal_vaidya2]

Thanks Alex.

Here the requirement is to keep receiver determination OM common as the conditions used for receiver evaluation are common for multiple sender interfaces ex. based on Company code/ sales org etc.

Is there any other way this can be achieved? We want to avoid creating individual receiver determination OMs and MMs (specific to Sender SI in each ICO) as much as possible.

[alex_bundschuh]

Hi Minal,

you may use receiver rules but since the sender interfaces differ usually you can only use header fields in your rules

An option which I however haven't validated is to define context objects within your sender interfaces and define your conditions based on the context objects, e.g., to stick to your example above define a context object salesOrg, however this would only work if all different sender interfaces have a sales org in the message format

Alex