Quantcast
Channel: SCN : All Content - Process Integration (PI) & SOA Middleware
Viewing all articles
Browse latest Browse all 7030

Number Limitation in XPath condition of Interface Determination

$
0
0

Hi Experts,

 

I have an existing interface with scenario:

 

Web Service (Sync) ->> PI ->> RFC 1 (Sync).

 

Now we have a requirement to call RFC 2 on the basis of <Company Code> (Receiver would be same for both the cases: SAP ECC) when Sender is the also the same Web Service.

 

Now we have introduced the XPath condition (Company Code == 111) in the Interface Determination and we are successfully able to separate these two RFC flow Mappings for the same Receiver on the basis of  <Company Code>. Now they are asking the same for 170 different company codes.


We are not sure if we maintain 170 Codes as Routing Rule in Interface Determination, whether it could create performance issue.

 

Note: We want to avoid BPM in this case

 

Important Point: We are using single Receiver but want to call different Mappings at Runtime.

 

Please suggest.

 

Regards,

Nabendu.


Viewing all articles
Browse latest Browse all 7030

Trending Articles



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