Business partner selection based on unit effectivityGeneral In LN, you can use unit effectivity to adapt the standard business procedure for items, and model exceptions that originate from specific customer requirements. The unit effectivity concept supports situations in which customers have specific requirements concerning the features of the products they order. You can link requirements to effectivity units and vice versa, and you can define exceptions that you can link to the business aspect that is impacted by the exception. In this way, you can model small deviations from the standard product configuration. Before you can define exceptions, you must first set up a unit effectivity structure for the item involved in the Unit Effectivity (UEF) module of Common. For more information about the use of unit effectivity, refer to To set up unit effectivity, the online manual topic. Next, you can define exceptions for the following business aspects:
Note For more information on defining exceptions for BOM lines, routings, operations, and sourcing strategies, view the online Help in the corresponding sessions. This online manual topic only refers to the selection of specific item - purchase business partner combinations based on unit effectivity. Item - Purchase business partners In the Items - Purchase Business Partner (tdipu0110m000) session, the following unit effectivity related check boxes are available:
Both check boxes are used to:
If the Standard Configuration check box is selected, the item - purchase business partner combination is valid unless it has exceptions attached that define the combination as not valid. If this check box is selected, and the purchase order has no effectivity unit linked to it, the purchase business partner is considered as valid. If the Standard Configuration check box is cleared, Enterprise Planning considers the item - purchase business partner combination as not valid, unless it has exceptions attached that define the combination as valid for the effectivity unit of the purchase order. If the Exceptions present check box is selected, the item - purchase business partner combination has exceptions attached that can overrule the standard configuration settings. Note The standard configuration determines whether an item - purchase business partner combination is valid or not, but the standard configuration can be overruled by exceptions. Exceptions With an exception you can specify whether an item - purchase business partner combination is valid for a specific effectivity unit or a requirement. Example 1 A sales order line is created for Item RADAR to which effectivity unit 232 is assigned. The sold-to business partner has made the following specifications for the item:
As a result, you must link the following requirements to effectivity unit 232 in the Requirement - Effectivity Units (tcuef0107m000) session, or the Effectivity Unit (tcuef0102m000) session:
You can model exceptions for requirements, which usually takes place when you set up the master data. With these exceptions, you can define the validity of a BOM line, routing, operation, sourcing strategies, or an item - purchase business partner combination. Assume the BOM and the routing contain valid exceptions for requirements USA and LIGHT. As a result, the generated purchase orders and production orders for the RADAR and its part are tailored to the LIGHT Model for the USA market. To define Advanced Electronics Inc. as the only valid purchase business partner for the item part X-DEVICE, you must take the following steps:
Example 2 If you take the same example but you want the Item RADAR to be sold to the German market only, you must take the following steps:
As a result, during the approved business partner selection process of Enterprise Planning, Enterprise Planning only retrieves the German purchase business partners for the item RADAR. After Enterprise Planning has retrieved valid business partners, the planned purchase orders are converted to actual purchase orders and the effectivity unit is transferred to the Effectivity Unit field of the Purchase Order Lines (tdpur4101m000) session. Note
| |||