Generate Aggregation Relationships (cprpd3211m000)

Field Information

Scenario

The scenario to which the main item belongs.

Family Item

The item to/from which LN must aggregate and disaggregate planning data.

If you zoom to the Items - Planning (cprpd1100m000) session, you can only select items for which the Item Type field is set to Family.

Plan Level

The plan level of the main item.

The plan level of the sub-item must at least be identical, but is preferrably lower than the plan level of the main item. You must define a plan items plan level in the Items - Planning (cprpd1100m000) session.

Channel

The channel to which the main item belongs.

You must first define the main items channel in the Plan Item - Channels (cpdsp5100m000) session.

Aggregation Type

Select the required aggregation type.

Select one of the following options:

• Aggregate from Sub-Item: LN aggregates planning data from the sub-items to the family item.
• Disaggregate to Sub-Item: LN disaggregates planning data from the family item to the sub-items.
• Both: LN both aggregates planning data from the sub-items to the family item, and disaggregates planning data from the family item to the sub-items.

Refer to online manual topic Aggregated planning for an example of aggregation types.

Percentage

Specify the percentage of the planning data that LN must aggregate or disaggregate.

If you specify Both in the Aggregation Type field, LN aggregates 100 percent of the planning data, and disaggregates the percentage that you define in the Percentage field. To overrule this type of aggregation, you must define a separate aggregation relationship for disaggregation.

In the Aggregation Relationships (cprpd3110m000) session, you can change the percentage for a specific aggregation relationship, or allow LN to calculate the planning percentage.

Effectivity Date

The date on which the aggregation relationships become valid.

You can define more than one aggregation relationship for a main item/sub-item combination. In that case, the aggregation relationships have different various effectivity dates and expiry dates, because the relationships cannot overlap. If the aggregation relationships do overlap, LN gives a warning. You can change the effectivity and the expiry date in the Aggregation Relationships (cprpd3110m000) session.

Sub Scenario

The scenario to which the sub-plan items belong.

Specify the same scenario as you selected in the Scenario field, if the main item and the sub-items belong to the same scenario, otherwise enter a different scenario.

Note: You cannot use this session to generate aggregation relationships between plan items in different logistical companies. You can only do so if you set up aggregation relationships manually in the Aggregation Relationships (cprpd3110m000) session.

From Plan Item

Specify the first of a range of sub-plan-items that LN must use to generate aggregation relationships.

Note: You must first define the item in the Items - Planning (cprpd1100m000) session.

To Plan Item

Specify the last of a range of sub-plan-items that LN must use to generate aggregation relationships.

Note: You must first define the item in the Items - Planning (cprpd1100m000) session.

From Channel

Specify the first of a range of channels to which the sub-plan-items must belong for which LN generates aggregation relationships.

You must first define the sub-items channel in the Plan Item - Channels (cpdsp5100m000) session.

To Channel

Specify the last of a range of channels to which the sub-plan-items must belong for which LN generates aggregation relationships.

You must first define the sub-items channel in the Plan Item - Channels (cpdsp5100m000) session.

Plan Level

The plan level of the sub-items.

The plan level of the sub-items must at least be identical to the plan level of the main item, but the level is preferrably lower. You must define a plan items plan level in the Items - Planning (cprpd1100m000) session.