Generic condition in Receiver Determination

[Former Member]

hi,

in receiver determination, we can define a Condition, but in condition editor, under "context object", we have only some standard parameters of PI adapter like "FileName" like http://sap.com./xi/XI/System/file used in Dynamicconfiguration. I saw also some of seeburger... so...

How can we define our own "_generic_" condition ? Do I need to create an Adapter ?

Note: I do NOT want to define a context object (in ESR) and affect it to a field of a service service, because it's limited to one interface , and I want a generic context which could be used for all interfaces (already developped and to be developped).

Thanks.

Mickael

[stefan_grube]

> in receiver determination, we can define a Condition, but in condition editor, under "context object", we have only some standard parameters of PI adapter like "FileName" like http://sap.com./xi/XI/System/file used in Dynamicconfiguration. I saw also some of seeburger... so...

> How can we define our own "_generic_" condition ? Do I need to create an Adapter ?

If you want to have additional dynamic parameters, you have to create adapter metadata.

There is a blog from Michal Krawczyk about this topic. He posted it some years ago, maybe you can find it.

[Shabarish_Nair]

PS: Just saw your note. I dont think you can create such a generic context object as it is linked to a single interface

you will need to create a context object (http://help.sap.com/saphelp_nw04/helpdata/en/d6/e44fcf98baa24a9686a7643a33f26f/frameset.htm) to achieve this

Edited by: Shabarish Vijayakumar on Dec 5, 2011 4:57 PM

[Former Member]

hi Shabarish,

yes, the Context object is linked to an interface (I know), but not the "[predefined technical context|http://help.sap.com/saphelp_nw04/helpdata/en/6e/ff0bf75772457b863ef5d99bc92404/content.htm]", which are defined by SAP for SAP adapters, but I can see also some others for a Seeburger adapter that we have. So technically I think it's possible to define my "own predefined" technical context object. the question is how? (by creating an adapter, or just a module or ...).

Mickael

[Shabarish_Nair]

i wonder if it has something to do with the adapter metadata

[former_member189558]

I am not sure I understand the question correctly.. Context objects are tied to interfaces.. and that is the purpose.

There is something called "Receiver Rule", which you can create generically and apply to multiple receiver receiver determination.

Check the URL: [http://wiki.sdn.sap.com/wiki/display/XI/HowtouseReceiverRuleinPI+7.1]

Cheers,

Himadri

[Former Member]

hi Himadri,

thanks for your interest, but no, that's not my subject. I want neither a specific context object based on only one service interface (your blog) nor to define dynamically the receiver by using mapping functions... I would like to have my own predefined context in Context Objects like these of SAP, example: Filename from DynamicConfiguration of a FILE adapter.

I know my topic is a litle too technic... but it's a part of a more global solution (*) to do a pre-control on all my existing interfaces (!). so the solution should be as less intrusive as possible: I do not want to change in depth all my interfaces... supens...

Regards.

Mickael

(*) I'm studying different ways, and this topic is one of them