Router issue in SAP HCI with 3 different receivers

[Former Member]

Hi All,

I am trying to Route the input to 3 different receivers depending upon a field value "ProcessingTypeCode" in SAP HCI. Source comes as wsdl to Router.So to achieve this I am using a Gateway.

Below is the condition which I am providing in ‘Condition Expression path’,.XML format.

Order       Route Name Condition Expression

1. abc ExternalSalesDocumentDataQuery_sync/ExternalDocumentRequest/ProcessingTypeCode = 'abc'
2. cde ExternalSalesDocumentDataQuery_sync/ExternalDocumentRequest/ProcessingTypeCode = 'cde'
3. fgi ExternalSalesDocumentDataQuery_sync/ExternalDocumentRequest/ProcessingTypeCode = 'fgi'
4. Default Route

When I trigger this using SOAP UI, instead of taking the proper route it takes the default value all the time (irrespective of the value provided in "ProcessingTypeCode" field in SOAPUI) and ends.

Can anyone suggest any solution to this issue? Looking forward to your help.

Thanks in advance.

Sradhanjali

[SergioG_TX · Accepted solution]

be aware that the routes go from more specific to more general.

see if you need to specify different routes.. or you could do a url rewrite rule (xsaccess file) based on the input.

hope this helps

[Former Member · Accepted solution]

Hi Sergio,

Thanks for your reply.

We have provided the routing conditions like this  :

In SOAP UI

May be we are missing the knowledge here on how should we specify the XPATH condition in the iFlow gateway. We have tried with all these XPATH conditions,

·//ExternalSalesDocumentDataQuery_sync/ExternalDocumentRequest/ProcessingTypeCode = ‘ZRQO’

·/ExternalSalesDocumentDataQuery_sync/ExternalDocumentRequest/ProcessingTypeCode = ‘ZRQO’

·ExternalSalesDocumentDataQuery_sync/ExternalDocumentRequest/ProcessingTypeCode = ‘ZRQO’

·/glob:ExternalSalesDocumentDataQuery_sync/ExternalDocumentRequest/ProcessingTypeCode = ‘ZRQO’

·/ExternalDocumentRequest/ProcessingTypeCode = ‘ZRQO’

But in all the cases instead of taking the Route 'ERP', its taking DEFAULT route all the time.

The incomming payload the ProcessingTypeCode  values comes as 'ZRQO' to HCI.

Regards,

Sradhanjali

[Former Member · Accepted solution]

Hi All,

I found the answer for this problem. Removing the Namespace just before the router solved the issue and worked as expected .

Thank you all for your help.

Regard,

Sradhanjali