Skip to Content

Problem with equalS after upgrade to PO 7.31 SP14

Hi,

we wanted to be early adopters of the SP14 for Process Orchestration.

We did an upgrade of our sandbox system that was on SP13 and imported content from our development system (SP08) and the first problem we encountered was that equalS is not working properly.

When there is a false value it should be suppressed but it issues a null result.

This error has ocurred also in the older SP but was fixed back then. Now we have encountered it again but can not apply the old patches since they are already in the SP14.

Problem is ticketed to SAP but they are kind-of stalling during the holidays and we have a pending upgrade on hold.

Is there anyone else that has started with SP14 and encountered this or any other problem?

Add comment
10|10000 characters needed characters exceeded

  • Get RSS Feed

4 Answers

  • Best Answer
    avatar image
    Former Member
    Mar 06, 2015 at 09:06 AM

    Hi Pontus,

    Yep. Same issue as we had faced and SAP came up with a parameter..This is mainly the handling of empty contexts in higher SPs

    Regards,

    Sriram

    Add comment
    10|10000 characters needed characters exceeded

  • Mar 06, 2015 at 08:03 AM

    Want to provide an upgrade to this post...

    The main problem was in our current SP8 (mabye also other SP's) an error made equalS to allow incorrect arrays of inputs create outputs that should not have been created in a normal function. Aka alowing the output to be correct without MapWithDefault or CopyValue.
    During our developers work and testing the mappings went well and arround 50 complete developments were deployed into production.

    Any change of productional interfaces will then trigger an extensive re-testing process so just easily do a mapping change has big impacts on the workload.

    SAP did release a solution, where an additional parameter can be introduced in the mapping that allows the equalsS work in this non-standard way.

    So in the end it will be a mapping change but there is no need to treat it as a new mapping (test cycle) but can be treated as a SP testing...

    Add comment
    10|10000 characters needed characters exceeded

  • avatar image
    Former Member
    Jan 08, 2015 at 09:59 AM

    Hi Pontus,

    We faced a similar issue while upgrading from PI 7.11 SP8 to SP13. The workaround was tweak in the mapping. SAP later on did come up with a patch for us. However i am surprised that similar issues is observed in later versions of PI as well, as SAP's contention was that the behaviour seen in PI 7.11 SP13 was the standard behaviour in all releases going forward.

    The standard behaviour is that o/p should be suppressed if its a null value at the i/p. For true condition it should process.

    Do let us know the outcome of your discussion with SAP.

    Regards,

    Sriram

    Add comment
    10|10000 characters needed characters exceeded

  • Jan 08, 2015 at 10:10 AM

    Hi Pontus,

    I believe this issue is happening only when the Input that you are trying to check is Absent in the Payload.

    As a workaround you can add MapWithDefault function for handling Absent Fields prior to doing EqualsS check.

    Regards,

    Azhar

    Add comment
    10|10000 characters needed characters exceeded