Solution: When designing the MBO, map it's load parameter to a corresponding
attribute with "Propagate to Attribute". If there is no corresponding
attribute, add one, then map it. For example, the Customer MBO has this
definition:
SELECT id,
fname,
lname,
address,
city,
state,
zip,
phone,
company_name FROM sampledb.dba.customer
WHERE state = :state
Map
the Customer MBO's state load argument to the state "Propagate to Attribute"
from the Load Arguments tab.