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.