| # Requirements (tcuef0106m000) Use this session to define business requirements. A requirement serves to describe the modifications and the variations for an item expressed by the exceptions that are linked to BOM lines, E-BOM lines, routing operations, and so on. Requirements can indicate, for example, regulations: USA: USA regulations EUR: European regulations ASIA: Asian regulations Requirements can also, for example, concern an item’s model: LIGHT: Model with limited features NORMAL: Model with the normal features ADVANCED: Model with advanced features Related topics Overview of unit effectivity 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. Requirement The requirement's description. 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 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. 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 as well as 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. Text If this check box is selected, a text is present. Requirement - Effectivity Units Click to start the Requirement - Effectivity Units (tcuef0107m000) session. In this session you can determine all effectivity units for which a requirement is valid. Use this session if you apply unit effectivity according to the effectivity series approach. For more information, refer to Unit effectivity procedure 1 – series approach. Print Click to print requirements by means of the Print Requirements (tcuef0406m000) session, or to print effectivity units by requirements by means of the Print Effectivity Units by Requirement (tcuef0407m000) session. |