Fixing at aggregate level & unfixing at detailed level.

[Former Member]

Hi,

Our requirement is as given below......

Our Demand Planning Process is Top-down process. Head Quarter will enter the demand at Territory, Channel and Product Group Level. These values are fixed and gets disaggregated to further planning level based on historical sales. The further planning levels are Sales Officer, Location & Product. Territory Manager can change the demand with in his targets across Sales officers (i.e. he should be able to change the targets of Sales officers without exceeding or reducing the Territory targets).

Can anyone suggest how to fix the keyfigures at Aggregate Level without fixing it at detailed level. We tried FIX_CALC macro, but could not resolve the issue.

Thanks in advance.

SP

[Former Member · Accepted solution]

You need to create AGGREGATES in your PLANNING OBJECT STRUCTURE, right click on POS and create the following aggregates

(1) ALL TERRITORY characteristics

Now you will be able to fix at the top level and still be able to change at the detailed level.

Read the following😘 Let me know if you have any questions*

Aggregate

Definition

The aggregates in APO are not the same as those in the Business Information Warehouse (BW), but they have the same purpose: to speed up data access and therefore increase performance. SAP recommends that you use aggregates in Demand Planning.

These aggregates are sometimes referred to as persistent aggregates, in particular when talking about detail and aggregate levels in interactive planning.

Use

An APO aggregate contains a subset of the characteristics in the master planning object structure. The creation and use of aggregates is optional. The data is always saved on the lowest level of detail. If aggregates exist, the system saves the planning data on the defined aggregate levels as well as on the lowest level of detail. The data is saved twice, but consistently; that is, the sum of the details equals the aggregate value.

SAP recommends that the aggregates you build in APO for planning data also exist in BW for actual data.

If you want to save fixed values at aggregate level ; that is not at detail level of the master planning object structure, in a planning book, you must create aggregates for this level. Otherwise the data is only saved at detail level.

You cannot form aggregates for navigational attributes

See also:

Fixing Key Figure Values

Aggregates are discussed in detail in OSS note 503363. SAP recommends that you read this note thoroughly before configuring your master planning object structures and aggregate hierarchy.

[Former Member · Accepted solution]

Hi Kumar,

Thanks for the reply.......

We donot want to use aggregates as business requirements (fixing levels) are changing every year. Hence we wanted to use macro to fix the values at aggregate level.

Regards,

SP