IBM RegTech Ideas Portal



Our team welcomes any feedback and suggestions you have for improving our offerings. This forum allows us to connect your product improvement ideas with IBM product and engineering teams.


For product documentation, see Knowledge Center.
Create and View Support Cases and Use the Discussion Forum here


Reminder: This is not the place to submit defects or support needs, please use normal support channel for these cases


The shorter URL for this site is:

IBMers, please visit the WFSS Internal Ideas portal


note: The IBM ICM IDEAS Portal is no longer available at this location. If you have reached this page, please look for a new link in the Varicent Administrator. Direct links are found under the "?" in the upper right corner.
A period of transition is likely to impact this service, while ICM becomes Varicent. Please contact Varicent support if you have additional challenges or concerns.

Inbound Transaction Hierarchy filter issues

Customer is asking to display all transactions for the bundle in case of
the control balancing, this is out of design scope.

We designed that filtering should apply to the transaction level based
on their own attributes. Unfortunately we do not propagate higher
parent's oob amount into the transaction level. So if bundle/segment has
OOB amount 100, such will not be used to filter in the transaction
Same was for the transaction balancing(We only filter the first item
within the transaction using OOB amount field).
OOB amount field is the logical attribute not physical attribute in the
item(or transaction level).

To satisfy the customer's need we have a function to find the next OOB

The way TCR should be used is to access the transmission hierarchy and
find next OOB, then perform an insert or update (The dialog display the
entire transaction in case of the transaction balancing). Balancing is
expected to occur sequentially not going back and forth..

I see the customer wants more than originally implemented but this
request seems more like the design change.
Please request if the customer can use the next oob finder as a work
around. Otherwise, this requires an RFE, not a PMR.
  • Avatar32.5fb70cce7410889e661286fd7f1897de Guest
  • Apr 5 2019
  • Reviewing
Component Usability
Priority High - Critical
  • Attach files