| To define user-specific constraints in unit effectivity |  |
| In the Requirements (tcuef0106m000) session you can use the Category field and the Exclusive Indicator field to specify constraints to apply requirements. Example Three requirements exist, HEAVY, NORMAL, and LIGHT, which denote three models. If you define the same categories and exclusive indicators for those requirements, you specify that only one of those requirements can be selected for a specific effectivity unit. To define more than one constraint The combination of category and exclusive indicator for an effectivity unit specifies only one constraint. Some customers want to define more than one (customer-specific) constraint. Therefore, customers can program their own constraints and actions in a set of predefined, empty functions, which are called by the tcuef007 DAL. The empty functions are located in tcuef.dll8007. The following functions exist: tcuef.dll8007.before.save.object tcuef.dll8007.before.destroy.object tcuef.dll8007.after.save.object tcuef.dll8007.after.destroy.object tcuef.dll8007.eopt.check tcuef.dll8007.effn.check To customize the dll, you must copy the dll to another VRC, after which you can make changes in the copy VRC. The reason for this is that during development in ERP LN, new functions could be added to the dll by ERP LN developers or ERP LN support. As a result, customizations in the original dll could be overwritten. If you copy the dll to a new VRC, you can extend the ERP LN logic without customizing the standard ERP LN program source code. Examples of potential use To add extra checks, which are executed if you insert a requirement for an effectivity unit. To automatically insert a requirement SAFETY_DEV if you insert a requirement ENGINE_3000 for an effectivity unit. Related topics Overview of unit effectivity |