| # Requirement - Effectivity Units (tcuef0107m000) Use this session to link requirements to an effectivity unit to configure the effectivity unit. Example A requirement with the name GER represents the safety features for the German market. The safety features are reflected in adjustments of BOMs, routings, and so on, indicated by exceptions, which are linked to requirement GER. By linking the requirement GER to an effectivity unit, the German safety features apply to the effectivity unit. If the German safety features change, you must only change the appropriate exception linked to requirement GER, after which the change applies to all effectivity units with requirement GER. On the View menu, you can select how to display the session: Effectivity unit by requirement Requirements by effectivity unit If you click New on the toolbar or on the File menu to define a new requirement for an effectivity unit, you can select a requirement in one of the following sessions: The Requirements (tcuef0106m000) session, in which you can select a requirement from all existing requirements. The Item - Requirements (tcuef0108m000) session, in which you can select one of the requirements that is linked to the effectivity unit's item. Import requirements To import default requirements that you defined for a specific item in the Item - Requirements (tcuef0108m000) session, click (Re-)Import Requirements on the appropriate menu. Note that you can define default requirements with identical categories and exclusive indicators in the Item - Requirements (tcuef0108m000) session, and you can also import them into this session, you cannot save them in this session. All requirements that are selected for a specific effectivity unit must have a unique combination of category and exclusive indicator. Note This session can be part of the Effectivity Unit (tcuef0102m000) session. On the Requirement tab of this session, you can view, maintain, and select requirements for a specific effectivity unit. Related topics Overview of unit effectivity Unit effectivity procedure 1 – series approach Effectivity Unit A reference number, for example a sales order line or a project deliverable line, that is used to model deviations for a unit effective item. End Item An item that is ready to be delivered to a warehouse. An end item is produced at the end of a dangle routing (co-products and by-products) or a main routing. Effectivity Series Code A code that represents a group of one or more effectivity units that applies to the same unit effective item. Sequence Number The sequence number of the effectivity unit in the effectivity series. Configuration Ready If this check box is selected, all desired requirements are selected for the unit effective item. Requirement The business reason that you define to describe exceptions used in unit effectivity. A requirement can be, for example, a specific market, model, or customer. Category A code to group requirements. Examples of categories are: CUSTOMER, MARKET, MODEL, SIZE, COLOR, and so on. If you define a code in the Exclusive Indicator field in the Requirements (tcuef0106m000) session in addition to a category, you have a means to determine which requirement can be linked to an effectivity unit. Related topics To define user-specific constraints in unit effectivity Exclusive Indicator A code to indicate that for a specific effectivity unit, a requirement cannot be combined with another requirement having the same category and exclusive indicator. You can define exclusive indicators and categories in the Requirements (tcuef0106m000) session. The following is an example of the usage of the category and the exclusive indicator.
Data in the Requirements (tcuef0106m000) session:
Requirement | Category | Exclusive Indicator
--- | --- | ---
HEAVY | MODEL | A
NORMAL | MODEL | A
LIGHT | MODEL | A
W16 | MODEL | B
W32 | MODEL | B
BLUE | COLOR | A
RED | COLOR | A
The table shows that the requirements HEAVY, NORMAL and LIGHT have the same category and exclusive indicator. This means that only one of those requirements can be assigned to a specific effectivity unit. The same goes for the requirements BLUE and RED. Only one of the two requirements can be assigned to a specific effectivity unit. Related topics To define user-specific constraints in unit effectivity Upgrade Price A price that is defined for a requirement in Unit Effectivity (UEF). If the requirement is used in an effectivity unit's configuration, the upgrade price is added to the effectivity unit's sales price. Upgrade prices can be positive or negative. If the upgrade price is negative, you can consider it as a discount. Currency The currency in which balances of entities shared by all the companies of a financial company group are expressed. For example, LN uses the reference currency for business partner balances. Note The reference currency is the common base currency of the companies in a multisite structure. For currency systems other than the standard currency system, the reference currency is a company's base currency for all calculations with currencies. per The physical quantity in which an item or good is managed. For example, a quantity of wood can be expressed as a length by using the unit of one meter, or as a volume by using the unit of one cubic meter. (Re-)Import Requirements Click to import the default requirements that you defined for the unit effectivity item in the Item - Requirements (tcuef0108m000) session. Print Starts the Print Effectivity Units by Requirement (tcuef0407m000) session. Add Range In the effectivity units by requirement view, click to start the Add or Remove Range (tcuef0207m000) session. You can add a range of effectivity units for a specific requirement in one go. Remove Range In the effectivity units by requirement view, click to start the Add or Remove Range (tcuef0207m000) session. You can remove a range of effectivity units for a specific requirement in one go. |