Best Practices for User-Defined Objects

As you create user-defined objects, follow these performance guidelines:

• Limit the amount of data returned by user-defined objects, or by models or controls that consume them, to as few rows as possible. Add filters during model-logic definition to ensure acceptable performance.

• The smaller the number of business objects joined to a user-defined object, the better the performance. (For example, you might relate a user-defined object to only one or two business objects.)

• When applying the Related to (join) filter condition, use the most unique (or primary) attribute for better logic processing. Examples of primary attributes in transaction business objects include Invoice ID in Payables Invoice and Expense Report Identifier in Expense Report Information.

• For reusability, keep user-defined objects as generic as possible. However, don't allow this approach to result in an excessively large data set.

• Be sure to select only key attributes in the model used for a user-defined object. For example, select those required to establish join relationships, to create attributes, or to be returned as results. The number of selected attributes can impact performance. The recommended limit for result attributes is 50, including derived attributes.