Error in Content based Routing from wrong xpath

 

Issue:-  Error faced while executing the EDIOutBound Relationship where the wrong XPath is defined in EDI Outbound Data Source after enabling content-based routing.

 

Error:- The error faced in such scenario is:-

Error while executing 
Xquery.Encountered "data" at line 2, 
column 10. Was expecting one of: 
"and" ... "div" ... "=" 
... "except" ... "eq" 
... "ge" ... "gt" ... 
"le" ... "lt" ... "ne" 
... ">=" ... ">>" ... 
">" ... "idiv" ... 
"intersect" ... "is" ... 
"<=" ... "<<" ... "<" 
... "mod" ... "*" ... 
"!=" ... <OPERATOR_ORDER_BY> 
... <OPERATOR_STABLE_ORDER_BY> 
... "or" ... "return" 
... "to" ... "union" 
... "|" ... "where" ... 
<OPERATOR_INSTANCE_OF> ... 
<OPERATOR_CASTABLE_AS> ... 
<OPERATOR_CAST_AS> ... 
<OPERATOR_TREAT_AS> ... <FOR_$> 
... <LET_$> ... "[" ... 
"," ... "outer-merge" ... 
"outer-nested" ... "#)" ... 
"merge" ... "cartesian-product" 
... "join" ... "nested-loop" 
... "+" ... "-" ... "/" 
... "//" ... . For more 
error details, refer to audit logs. 
O

 

Cause:- This issue is caused when we wrongly define the Application ID/XPath as '/ORDERS05/IDOC/EDI_DC40/RCVPRN/' instead of '/ORDERS05/IDOC/EDI_DC40/RCVPRN' for the same input file. In this case, EDI Outbound Source has the different name and Xpath. As an example, Source1 has correct XPath as '/ORDERS05/IDOC/EDI_DC40/RCVPRN' and Source2 has the wrong XPath as '/ORDERS05/IDOC/EDI_DC40/RCVPRN/' due to which all the relationships which are using correct/wrong EDI Outbound source fails.

 

Solution:- This issue will be resolved once you will define correct XPath like '/ORDERS05/IDOC/EDI_DC40/RCVPRN' instead of '/ORDERS05/IDOC/EDI_DC40/RCVPRN/' in every EDI OutBound Source for the same input file.

 

Have more questions? Submit a request

0 Comments

Article is closed for comments.