Dos and don’ts of authorization links
Authorization links can give rise to intensive database queries when the data is retrieved. Therefore, the following guidelines are recommended to avoid any performance issues when authorization links are used:
Filtering on a non-indexed field
Authorization links created between business objects with non-indexed fields, involved in the query, may have a performance penalty. In the Planon Software Suite, mostly all fields in relations (table) starting with FK_ are indexed. The code field is also indexed mandatorily. For example, the field Unit of length in the business object Spaces, with the table name FK_PLC_MEASUREMENT_SYSTEM.
Enabling filtering on a BO that is defined on a view
All relation (table) variables which start with PLN_VW_ are views in a database schema. An authorization link querying on a view created for relations with a complex relationship can have a performance penalty. For example, creating an authorization link on BaseMaintainenceActivityDefinition to BaseAssetRef. This link queries on the PLN_VW_ ASSET.
Making a user available in multiple user groups
An authorization link may result in a complex query, if a user is in multiple user groups. This can cause a performance penalty.
Making a long authorization link
If an authorization link is created on a business object, which in turn is a part of an authorization link of another business object and likewise, this may result in a slower performance.