Engineering Change Management Parameter Effectivity

The standard SAP system supports the effectivity types DATE (date interval) and SERNR (serial number interval) only. Since it is not possible to construct all variants based on effectivity conditions in the standard SAP system, you can create more effectivity types with the parameters you require in Customizing for Engineering Change Management.

You can, for example, define the effectivity type AIRLINE (Airline) that has the parameter DEBIT (customer) as a single value.

In the SAP system, the following values exist in the database table for the customer master:

• A (Airline A)
• B (Airline B)
• C (Airline C)

When you assign values to the effectivity parameter CUST in the change master record you can choose from among these three customers.

In the BOM for an airplane, you can enter several components for different seat covers, and define exactly which component (seat cover) is effective for which airline.

You create two change numbers with the effectivity type AIRLINE and set values for the parameter DEBIT (customer) for the first change number the value A and for the second change number the value B. When you then want to add the seat cover material for each airline company in the BOM you process the BOM of the seat cover in relation to the matching change number.

When you process an object (such as a BOM item) using a particular change number for the first time, the system generates a new processing status ( change state ). If your organization does not use parameter effectivity, these changes simply have time-related validity, which means that a change state’s validity extends from its valid-from date to immediately before the valid-from date of the change state following.

However, if you douse parameter effectivity, you can also make a change state’s validity dependent on other criteria, such as serial number or customer.

Prerequisites

In Engineering Change Management Customizing you have set the Parameter effectivity indicator in Setup control data. You have made settings for Parameter Effectivity according to your requirements. This may have included defining effectivity parameters and types for your organization if required.

Process Flow

You create a change master record with parameter effectivity.

• In the change master record you define the effectivity criteria, according to which you want the changes you make with reference to this change master record, to be effective. For more information, see Creation of Change States with Parameter Effectivity.

You process one or more objects with reference to this change master record.

• For each object (such as a BOM item) you process for the first time, with reference to a particular change master record, the system generates a new change state. For more information, see Object Processing.

In various operational areas (such as when you create a sales order) you assign values to the effectivity parameters. For more information, see Assignment of the Effectivity Parameters.

• Other processes, such as planning runs, take the parameter variant you entered in the sales order into account. The system determines the valid change state, for all objects you create with reference to change master records with parameter effectivity. For more information, see Effective Change State Selection.

Change Master Record

Change number generated with parameter effectivity in CC01 transaction

Master Data BOM Update

With reference to change number bill of material master data change with parameter values.

Sales Order Creation

While creating sales order parameter value to be updated based on change master values.

MRP Run

MRP run generated planned order (planned order quantity created based on a customer order or project).

Production Planning and Execution

Planned order components updated based parameter change value in BOM.

Same parameter value information transfer to production order for execution.

Additional Information

https://help.sap.com/erp_hcm_ias_2012_03/helpdata/en/f0/8951e68ae611d3b491006094b9d648/frameset.htm

Best Regards,

Lingaiah