The 'Remaining Cost' and 'Cost To Date' attribute calculations both include the values for today. If you add 'Remaining Cost' and 'Cost To Date' they will not equal Total Cost, because today is counted twice - once in Remaining Cost and once in Cost to Date. The sum of 'Remaining Cost' and 'Cost to Date' will be more than Total Cost by exactly one day.
Whenever a mashup is deployed the tables within that mashup will have record locking switched OFF with immediate affect. The side affects of not having record locking on are that multiple people can update the same record and also that pre-transition actions are run twice .
I'm using library type of DBB to accomplish my DB2 package binds. Whenever CMNDB2PL executes, it generates a duplicate set of bind control, causing the package to be bound twice .
