Exclude Logical Units from having Custom Fields

Due to architectural design decisions some logical units or some application forms may not be extended with Custom objects functionality. In such a case, such logical units and application pages should be explicitly excluded from Custom Objects logic so that a user will not be misguided.

The Excluded Logical Units page lists the manually registered logical units that due to architectural reasons cannot be extended. Reasons for this can be including, but not limited to:

• Performance impact. Custom fields adds a very small performance overhead when used on an LU. For particular LU's in heavy use, this overhead can add up to a performance problem.
• The design of an LU. IFS has implemented a particular LU such that it is impossible to use it with the custom fields framework, e.g. for performance reasons. This could be due to the design of both the client code or the server code.
• Join and union views. All records in a view must have a rowkey which correspond to a record in the base table to extend it with custom fields or information cards. There are views defined as joins or unions where that is not the case.

• Framework LU's. All LU's in the components FNDBAS and FNDCOB are excluded. Extending some of the framework LU's with custom fields is simply not possible, due to their nature and different use compared to normal business object LU's.

There is a possibility to add a description why the LU is not suitable to use together with custom objects framework.

Export

You can export the LU's that you don't want to be able to add custom objects to. You can either export all LU's or all LU's for one component. The file can be used to run during installation of IFS Applications in order to avoid custom objects on certain LU's.