Reduction keys (form) [AX 2012]

Updated: November 26, 2010

Applies To: Microsoft Dynamics AX 2012 R3, Microsoft Dynamics AX 2012 R2, Microsoft Dynamics AX 2012 Feature Pack, Microsoft Dynamics AX 2012

Click Master planning > Setup > Coverage > Reduction keys.

Use this form to create and set up reduction keys. You can use a reduction key to define how to reduce forecast requirements. Forecast reduction results in smaller forecasted quantities being transferred to master scheduling to calculate net requirements.

When you set up a reduction key, you define the time periods during which you want the reduction to occur. You can also define reduction percentages that you want to apply for each time period. When you use a reduction key, you must choose whether to reduce the forecast requirements by using actual transactions, or by using the pre-defined percentages.

TipTip

After you create and set up a reduction key, you can link it to a coverage group.

To use a reduction key to calculate forecast reduction during master scheduling, you must define this setting in the forecast plan or the master plan setup. See Create and use a reduction key for more information.

The following tables provide descriptions for the controls in this form.

Tab

Description

Periods

Set up the time periods and corresponding reduction percentages to apply when forecast requirements are calculated.

Button

Description

Wizard

Open the Reduction Key Wizard. You can use the wizard to create a reduction key and reduction key lines.

Field

Description

Reduction key

Enter a unique ID for the reduction key.

Name

Enter a name for the reduction key.

Fixed

When you select this field, the reduction key is valid from the date that you enter in the Opening date field. If the field is blank, the reduction key periods are valid from the current date (system date).

Opening date

The date from when the reduction key is valid. This field is used with the Fixed field, which you must select. If the field is blank, the current year, based on the system date, is used.

Change

This field is linked to the value in the Unit field and specifies the incremental change in the unit of time.

Example

If the Change field contains 30, and the Unit field specifies Days, the reduction key period is for 30 days.

Unit

Select the time unit for the reduction key period. The options are as follows:

  • Days

  • Months

  • Years

Percent

Enter a percentage by which the forecast requirements are reduced for the period. You can enter positive values to decrease requirements, or negative values to increase requirements.

Example

The forecast states requirements of 1,900 pieces every 30 days. If you use a reduction key of 10% for 90 days, the requirement is adjusted to 1,710 pieces.

If you create an additional reduction key line of -20% (indicating an increase) for a period of 120 days, the requirement is adjusted to 2,280 pieces (1,900 pieces + 20%) after 90 days.


Announcements: To see known issues and recent fixes, use Issue search in Microsoft Dynamics Lifecycle Services (LCS).

Community Additions

Show: