Quantcast
Viewing all articles
Browse latest Browse all 8623

Re: Number Limitation in XPath condition of Interface Determination

Hi Nabendu,

It is great to see you again in the SCN, we miss your posts. I think like you, to maintain to much conditions in the condition editor can be hard task. I was wondering and it not easy to solve, i have thought the next:

1. First possible solution

you could use a web service lookup in this way i think in this:

1. First scenario. You actual scenario but with only two conditions to determine one or another scenario. This will be called in the lookup.

2. Second scenario. The scenario visible for your client, this will be used to determine the value to choose one or another condition, for this you can use a value mapping to determine the set that the company code belongs.

It is no easy solution as well, but there is not exists a "value mapping conditions".

 

2.Second possible solution

To use cross-reference calls betwenn mappings. Use a first mapping to detemine which second mapping call. Check this document http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/f03df013-289f-2e10-acb9-d1fcf782ae5d?QuickLink=index&…

 

3. Third possible solution.

Another option could be to make one only mapping and to decide with value mapping what to do, but im afraid you dont like this workaround, me neither.

 

Hope i can give you any idea.

 

Regards.


Viewing all articles
Browse latest Browse all 8623

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>