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

Wierd Behaviour of IF then ELSE standard function

$
0
0

Hi All,

 

I am facing a very wierd behaviour of the IF then ELSE function in a mapping.

 

Condition to be checked:   if GDS_id = 1, then (condition 1 -  RFC lookup ) ElSE (condition 2 - JDBC Lookup followed by an RFC  lookup).

 

 

Issue:  The input payload is 0-unbounded with a possibility of a different GDS_id values.

 

Case 1 :

As shown below, in case the input payload has 3 repitions of the RECORD, with the Fit set having GDS_ID = 01, the mapping runs perfectly fine . All the If then Else branches are getting executed.

 

Case 2:

Where as iF the first GDS_ID != 01 (not 01) , thenthe target value is not getting populated properly .

 

I have tried all the possibilities and combinations but i am unable to resolve this. Please help.

 

Attached the screen shot of the message mapping, and sample test results of both the use cases.

 

 

---------------------------------------------------------------------

For instance, below is a sample payload:

----------------------------------

<?xml version="1.0" encoding="UTF-8"?>

<ns0:mt_EMERGO_common xmlns:ns0="http://sabreEMERGO_common.com">

 

<Record>

      <booking_date>08012013</booking_date>

      <iata_code>2325540</iata_code>

      <gds_id>01</gds_id>

      <pos_code>RD3A</pos_code>

      <gds_code>01</gds_code>

      <net_booking>11</net_booking>

   </Record>

<Record>

      <booking_date>08012013</booking_date>

      <iata_code>2325540</iata_code>

     <gds_id>02</gds_id>

      <pos_code>54S8 </pos_code>

      <gds_code>02</gds_code>

      <net_booking>11</net_booking>

</Record>

  </ns0:mt_EMERGO_common>

----------------------------------


Viewing all articles
Browse latest Browse all 7030

Trending Articles