Electronic reporting (ER) framework allows to use application tables as data sources in ER model mappings. For each single table among with fields, table methods can be used as data source elements. Currently, table methods that either contain no parameters at all or contain only parameters that accept arguments specified as one of supported primitive data types (integer, real, string, etc.) can be used as data source elements. The problem is that ER designer shows for a selected table the only methods without parameters or with parameters in primitive data types to which the default argument’s value has been defined. All methods that have parameters in primitive data types to which the default argument’s value has not been defined are invisible in ER designer. Being entered manually in ER mapping expression, such methods are not recognized as existing for a selected table that causes validation errors for the designing model mapping.