Entering content frame

This graphic is explained in the accompanying text Aggregated Lifecycle Planning with Like Profiles - Examples Locate the document in its SAP Library structure

A planning object structure contains the following characteristics and characteristic value combinations:

 

Sales org.

Location

Product

Color

Size

1 (historical data)

1000

N0001

P1

Red

Medium

2

1000

N0001

P2

Red

Medium

3

1000

N0001

P3

Red

Medium

4

1000

N0001

P1

Green

Medium

5

1000

N0001

P1

Black

Medium

6

1000

N0001

P1

Black

Large

7

1000

N0001

P1

Black

Small

8

1000

N0001

P1

Black

Extra Large

9

1000

N0001

P2

Black

Medium

10

2000

N0001

P1

Red

Medium

11

1000

S0002

P1

Black

Extra Large

Historical data only exist for the first combination.

The basic settings for the planning area specify that the characteristics product, location, color, and size are relevant for lifecycle planning. The Aggregated Lifecycle Planning with Like Profiles indicator has been set.

Example 1

You create the following like profile for characteristic product:

Product1

Ref. values

Action

a/b (%)

P1

S

100

and make the following assignment:

Product

Location

Color

Size

Profile

P2

*

Red

*

Product1

You select the highest possible aggregate level (all characteristic combinations) and make a forecast. The system finds the historical data for combination 1at aggregate level. It determines that one characteristic combination exists to which a like profile has been assigned (combination 2). It determines the historical data for this combination using the profile – it replaces the characteristic value P2 with P1, this corresponds to combination 1 for which historical data exist. The aggregated historical data now comprises of data from two combinations, in this case the historical data is now double as large as initially. As a result the aggregate forecast is also double as large.

Example 2

You change the assignment to:

Product

Location

Color

Size

Profile

P2

*

Red

*

Product1

and carry out a forecast for the same assignment as above. The system finds two characteristic combinations to which like profiles have been assigned. However the result is exactly the same as above. The combinations are:

Combination

Product

Location

Color

Size

2

P2

N0001

Red

Medium

9

P2

N0001

Black

Medium

In both cases product P2 is replaced with P1 so that the modified combinations are:

Combination

Product

Location

Color

Size

1

P1

N0001

Red

Medium

5

P1

N0001

Black

Medium

However historical data only exists for combination 1, so that historical data is only generated for the first combination.

Example 3

You create a new characteristic value combination for the planning area:

 

Sales org.

Location

Product

Size

Color

12

1000

N0001

P2

Yellow

Medium

and carry out a forecast as above. The system issues an error message to the effect that it cannot carry out a forecast because there is no historical data. If you look in the messages log, you see that it has found three combinations to which like profiles have been assigned:

Combination

Product

Location

Color

Size

2

P2

N0001

Red

Medium

9

P2

N0001

Black

Medium

12

P2

N0001

Yellow

Medium

It replaces P2 with P1.

Combination

Product

Location

Color

Size

1

P1

N0001

Red

Medium

5

P1

N0001

Black

Medium

 

P1

N0001

Yellow

Medium

The last combination does not exist in the planning area. The system stops processing and issues the error message.

Note

This is one reason why you should not use large selections in aggregated lifecycle planning with like profiles. Particularly when using batch processing it is preferable to execute several smaller jobs with restricted selections than few large jobs. If the above situation occurs, less selections are affected.

Example 4

You create a new like profile.

Product2

Ref. values

Action

a/b (%)

P1

S

50

and make the following assignment

Product

Location

Color

Size

Profile

P3

N0001

Red

Medium

Product2

You now select Product P3 without specifying any other characteristic values and execute the forecast. The system does not use aggregated lifecycle planning. However a forecast is carried out. In the message log a message appears telling you that lifecycle planning is active. No further messages are displayed. If you then go to the Settings tab page, you see that Like profile Product2 has been used. This is a special case; only one characteristic value combination exists and therefore aggregated planning is not necessary, the system automatically reverts to normal lifecycle planning with like profiles.

Example 4a

Now create a further characteristic value combination containing product P3 and execute the forecast as above. Aggregated liefycle planning is carried out and the message log contains the relevant messages.

Example 5

You make the following selection: Sales org = 2000, Product = P1 and carry out a forecast. The system is unable to make a forecast and issues a message that it could not find historical data. No messages appear regarding lifecycle planning.

Since there is only one characteristic combination for this selection aggregated lifecycle planning is not started (see Example 4). No historical data exists for this combination and none of the like profile assignments meet the selection.

In this case it is not possible to use like modeling to generate historical data for the selection. The characteristic Sales org. was not included in the basic settings.Therefore it is not possible to use this characteristic to select a like profile. It is only possible to carry out a forecast if historical actually exists for sales org 2000, for instance for caharacteristic value combination 10.

Leaving content frame