IBM Sterling Ideas

Submit new product ideas for IBM Sterling solutions. Before you submit, please review existing ideas; if an idea close to yours already exists, it's better to add comments or vote on the existing idea. We will review your ideas and use them to help prioritize our product development. Best of all, the portal will automatically update you when the status of your idea has been changed.

IBM is transforming its request for enhancement (RFE) process. The purpose of the transformation is to provide a more consistent experience for you to submit requests and to enable IBM product owners to respond to your requests more quickly. For more information click here.

Connect with IBM experts and your peers on the Supply Chain Collaboration Community and the Order Management Interest Group

Improve performance of SERIESTOTEXT function

Currently the SERIESTOTEXT function does not distinguish the type of an object when the same field from the type tree is passed at different level.

To make things clear, below is an example of a typical ANSI X12 type tree and the 'X12 Segment' is a simple blob type field in the type tree.

The same field is being passed as different type of an object under the header & Message group.

Assuming the Header occurs 3000 times and the Message occurs 300,000 times in the input file , the SERIESTOTEXT function currently gets evaluated for 303,000 times for SERIESTOTEXT(X12Segment:Header)

When executed 3000 times, the run time of the rule is less than a second and when executed 303,000 times the rule completion time is around 55 seconds.

The current product behavior is that the SERIESTOTEXT(X12Segment:Header) & SERIESTOTEXT(X12Segment:Message) gets evaluvated 303,000 times as they share the same field .

Eventhough the right output is produced, the idea is to change the behavior so the SERIESTOTEXT takes the type of the object into account instead of just the name.

Typical X12 Message Type tree

==========================

X12

- ISA Segment

- Header (0:1)

-> X12 Segment (s)

- Functional Group (s)

- GS Segment

- Message (s)

-> X12 Segment (s)

- GE Segment

- IEA

  • Avatar32.5fb70cce7410889e661286fd7f1897de Guest
  • Aug 21 2020
  • Under Consideration
How will this idea be used?

The idea will improve the map performance to a great extent under all circumstance when SERIESTOTEXT function is used.

Currently we are ensuring that each field in the type tree has got a unique name to avoid issues. Changing the behavior would save lot of time and allows faster transformation.

What is your industry? Automotive
What is the idea priority? Urgent
  • Attach files
  • Admin
    Luke Raiano commented
    21 Aug 05:18pm

    Develpment to review