null vs suppress

[Former Member]

In 7.1 if a value doesnt come, for the first time , it comes as null instead of suppress.

because of this my message mappings imported from 7.0 to 7.1 are not working as expected.

any clues?

thanks,

Venkat.

[Former Member · Accepted solution]

Hi Venkat,

Always for the first time , it comes as null, not as "SUPPRESS". if you want to replace yo need to build a UDF ...something like "Mapwithdefault".

Regards.

Ivan

[Former Member · Accepted solution]

Its not.

check the below URL

http://farm3.static.flickr.com/2496/3729755192_37b7711fce_o.png

This is the queue from 7.0 and imported mapping in 7.1 from 7.0, which is generating different outputs.

anyone who knows why?

This is for the third MM this is happening to me.

Ideally, we should not do MM for each version change.

FYI, MapWithDefault will not work here. If I map a mapwithDefault with SUPPRESS, it sends a string "SUPPRESS" not the empty context or just "" if we set empty mapWIthDefault

Thanks,

Venkat.

Edited by: Venkat A on Jul 17, 2009 10:49 AM

[Former Member · Accepted solution]

Hi Venkat A,

According I can see in the image, You are talking about the first value of the queue and It doesn´t mind because is only indicate the start of the queue...or your are getting the same value in other position?

Regards

Ivan

[Former Member · Accepted solution]

It does matter though it is in the first position of the Queue.

Check the following.

http://farm4.static.flickr.com/3484/3729754341_10534cde47_o.png

The SUPPRESS resulted in false for a exists check

<null> resulted in <null> in exists check.

Thanks,

Venkat.

[Former Member · Accepted solution]

Venkat,

I meant, It does not matter in your final result(target nodes). By the way...are you facing any problem with the final result?

Regards

Ivan

[Former Member · Accepted solution]

Yes Jose, This is because instead of false, true is being sent.

in 7.0 it is sending false and is sending true in the 7.1

Thanks,

Venkat.

[Former Member · Accepted solution]

Venkat,

I dont think it should be a problem. Can you give the mapping and the test payload you are using.

Regards,

---Satish

[Former Member · Accepted solution]

Satish and Jose,

This is the problem in 7.1 SP 06.

I have one more 7.1 with SP 04, it works there correctly there.

I will search for NOTE if I dont find one, I will raise a message with SAP. If anyone come across NOTE for this problem, do let me know.

Thanks,

Venkat.

[Former Member · Accepted solution]

Venkat,

Can you please check this note and see whether there are any issues as mentioned here:

1158484, 1053706

Regards,

---Satish

[Former Member · Accepted solution]

They do not apply in my case.

Anyone who faced similar problems?

thanks,

Venkat.

[Former Member · Accepted solution]

Hi Venkat,

Did you ever find a solution or OSS note that fixed this issue?

We have exactly the same issue after upgrading from PI 7.0 to PI 7.11 SP03.

The "null" is changing the behaviour and result of our mappings and we would like a quick fix if SAP have one, otherwise we will have pain modifying affected mappings.

We also are worried that we may not even identify all of the affected mappings without detailed testing of every mapping.

Thanks,

Brendan

[Former Member · Accepted solution]

Brendan,

Unfortuntely, No.

I had a mapping change done to work in both 7.0 and 7.1

but I have a doubt when I faced this issue, it was working in 7.1 system with SP4 and giving issues in a SP6 system.

Please check if your problem is similar to this one.

I think this is changed to null for ease of use in UDFs ( this is just my guess though )

Please update this post in case if you raise mesg with SAP on this .

Venkat.

[Former Member · Accepted solution]

Hi

Sorry, didn't check that the origin of the message was from july (where you actually said that you were going to send an issue to SAP)

regards Ole

Edited by: Ole on Nov 16, 2009 3:11 PM

[Former Member]

Hi Venkat A,

Even we are facing same issue when upgrading from SP4 to SP6. Did you find any OSS for this issue.

Thanks,

Rajeev Gupta