Aggregation Relationships (cprpd3110m000)

If the main item and the sub-item belong to the same scenario, you must enter same scenario in the Sub Scenario field as LN displays in the Scenario field. If not, you must define a different scenario in the Sub Scenario field.

In case of multicompany aggregation, you must define the scenario to which the sub-item belongs in the other company in the Sub Scenario field.

The first segment of the code is the planning cluster, the second is the project, and the third is the item.

You must define this channel in the Plan Item - Channels (cpdsp5100m000) session.

You can set up aggregation relationships between two different companies.

The company is used to determine the plan level.

Define the same scenario as in the Scenario field, if the main item and the sub-item belong to the same scenario. Define a different scenario, if the sub-item belongs to a different scenario.

If you want to (dis)aggregate between two different logistical companies, you must specify the scenario to which the sub-item belongs in the other company.

The plan level of the sub-plan item must be at least one level lower than the level of the main plan item.

You must define the subchannel in the Plan Item - Channels (cpdsp5100m000) session.

You can define more than one aggregation relationship for a specific main item/sub item combination. In that case you must define different effectivity and expiry dates, because the periods that you set must not overlap. If they do, LN gives a warning.

If no date is entered, the aggregation relationship remains valid.

Enterprise Planning disaggregates the production plan from the main item to the production plan of the subitem, if the subitem is not a channel item. If the subitem is a channel item, Enterprise Planning disaggregates the production plan of the subitem to the allowed demand of the subitem.

Enterprise Planning aggregates planned production orders of normal items to the scheduled production receipts of the family item, or disaggregates them to the allowed demand of the channel item. Enterprise Planning disaggregates planned production orders of a family item to the production plan of normal items.

Enterprise Planning does not disaggregate scheduled production receipts of a family item. Scheduled production receipts of a normal item are disaggregated to the allowed demand of the channel item.

If you selected Both in the Aggregation Type field, the percentage you specify only applies to disaggregation, and Enterprise Planning aggregates for 100%. To overrule this way of (dis)aggregation, you must set up a separate aggregation relationship for aggregation and disaggregation.

Enterprise Planning automatically updates the value of the Aggr. Perc. Prod. Plan/Orders/Receipts field, if you carry out the Calculate (Dis)Aggregation Percentages (cprpd3210m000) session.

Enterprise Planning disaggregates the purchase plan from the main item to the purchase plan of the subitem, if the subitem is not a channel item. If the subitem is a channel item, Enterprise Planning disaggregates the purchase plan of the subitem to the allowed demand of the channel item.

Enterprise Planning aggregates planned purchase orders of normal items to the scheduled purchase receipts of the family item, or disaggregates them to the allowed demand of the channel item. Enterprise Planning disaggregates planned purchase orders of a family item to the purchase plan of normal items.

Enterprise Planning does not disaggregate scheduled purchase receipts of a family item. Scheduled purchase receipts of a normal item are disaggregated to the allowed demand of the channel item.

If you selected Both in the Aggregation Type field, the percentage you specify only applies to disaggregation, and Enterprise Planning aggregates for 100%. To overrule this way of (dis)aggregation, you must set up separate aggregation relationships for aggregation and disaggregation.

Enterprise Planning automatically updates the value of the Aggr. Perc. Pur. Plan/Orders/Receipts field, if you carry out the Calculate (Dis)Aggregation Percentages (cprpd3210m000) session.

If the subitem is not a channel item, Enterprise Planning disaggregates the inventory plan from the main item to the inventory plan of the subitem.

If you selected Both in the Aggregation Type field, the percentage you specify only applies to disaggregation, and Enterprise Planning aggregates for 100%. To overrule this way of (dis)aggregation, you must set up separate aggregation relationships for aggregation and disaggregation.

Enterprise Planning automatically updates the value of the Aggr. Perc. Inventory Plan field, when you carry out the Calculate (Dis)Aggregation Percentages (cprpd3210m000) session.

Enterprise Planning aggregates the planned distribution orders of normal items to scheduled distribution receipts of the family item, or disaggregates them to the allowed demand of the channel item. Accordingly, Enterprise Planning disaggregates scheduled distribution receipts of normal items to the allowed demand of the channel item.

Enterprise Planning does not disaggregate scheduled distribution receipts of the family item.

If you selected Both in the Aggregation Type field, the percentage you specify only applies to disaggregation, and Enterprise Planning aggregates for 100%. To overrule this way of (dis)aggregation, you must set up separate aggregation relationships for aggregation and disaggregation.

Enterprise Planning automatically updates the value of the Aggr. Perc. Distr. Orders/Receipts field, if you carry out the Calculate (Dis)Aggregation Percentages (cprpd3210m000) session.

Enterprise Planning automatically updates the value of the Aggr. Perc. Demand Forecast field, if you carry out the Calculate (Dis)Aggregation Percentages (cprpd3210m000) session.

Enterprise Planning (dis)aggregates extra demand to (from) the extra demand of the subitem.

Enterprise Planning automatically updates the value of the Aggr. Perc. Extra Demand field, if you carry out the Calculate (Dis)Aggregation Percentages (cprpd3210m000) session.