public class FldMatUseTransQuantity extends MboValueAdapter
mboValueTYPE_DOMAIN, TYPE_FIELDCLASS, TYPE_KEY, TYPE_UNKNOWNALLROWS, CHANGEDBY_USER, COUNT_ADDITIONS, COUNT_AFTERSAVE, COUNT_DATABASE, COUNT_DELETED, COUNT_EXISTING, DBCONFIG, DELAYVALIDATION, DELAYVALIDATIONONLY, DISCARDABLE, GOTCOMPLETEWHERE, HIDDEN, NO_RELATEDMBOS_OF_OWNERSCHILDREN_FETCH, NOACCESSCHECK, NOACTION, NOADD, NOCOMMIT, NODELETE, NONE, NOOVERWRITE, NOSAVE, NOSETVALUE, NOUPDATE, NOVALIDATION, NOVALIDATION_AND_NOACTION, NOVALIDATION_AND_NOACTION_ALLOWCROSSOVER, READONLY, REBUILD, REQUIRED, SAMEVALUEVALIDATION, SETBYPARENT, USER| Constructor and Description | 
|---|
| FldMatUseTransQuantity(MboValue mbv) | 
| Modifier and Type | Method and Description | 
|---|---|
| void | action()action()
 Update the fields affected by changing quantity
        Included in this list of affected fields is the QUANTITY field itself!!
        Indeed, changing the quantity itself should automatically trigger proper
        signing based upon issuetype
        NOTE: This allows programmer to make safe assumption as to the sign of the quantity
        value without checking issuetype each time quantity must be used in a calculation. | 
getAppLink, getIntegrationService, getList, getLookupName, getMatchingAttr, getMatchingAttr, getMboValue, getMboValue, getType, hasList, init, initValue, setType, setValueFromLookup, smartFill, smartFind, smartFind, validatepublic FldMatUseTransQuantity(MboValue mbv) throws MXException
MXExceptionpublic void action()
            throws MXException,
                   java.rmi.RemoteException
action in interface MboValueListeneraction in class MboValueAdapterMXExceptionjava.rmi.RemoteException