cancel
Showing results for 
Search instead for 
Did you mean: 

TOP DOWN MANNUAL PLANNING

Former Member
0 Kudos

Hi All,

If anybody can give me some input that would be great help for me.

Presently the planning is happening by Extracting Flat file by using some zprogramme, this Zprogramme has restrictions

like based on companycode it has Sales offices and it extracting the same is loading to cube , this will be the

plan data for sales office according to the Division.

In the planning layout the aggregated sales office Plan data will get by this process by seeing this values and quantities for particular office and Division,

the ZBH will input the plan data for all the emloyees with in his office.

Now the requirement is

the sales planning is to be for 3 levels mentioned below as of now instead of 2 levels.

1 Sales head ( North & East ) or Sales Head ( west & South ) will put targets for respective

ZBH reporting to them.

2 All ZBH will enter targets of BOH

3 All BOH will enter targets of BM (Instead of BM it will be ASM/ASE/SO as on date)

4 All BM will enter targets of ASM. (Not applicable as of date due to no BM concept)

Accepted Solutions (0)

Answers (2)

Answers (2)

former_member5472
Active Contributor
0 Kudos

Hi,

As Indu said ,you can use a new characteristics or an existing one say 0version to control different levels..

Each version value can be used to differentiate a level.

Thanks

Pratyush

Former Member
0 Kudos

Hi,

Thanks for your valuable Answers,

As we have Sales office Characteristic, i can Add Zlevel characteristic and build hierarchy on sales office char is it ok and also do i need to maintain Characteristic relationship for sales office characteristic to Zlevel in characteristic relation please clarify my doubt.

Thanks

Deenu

Former Member
0 Kudos

Hi,

What master data you have maintained for sales office characteristic,if distinguish all three levels well then you can use the same one for planning.Need not maintain Zlevel as seperate char.

Even if you maintain you may not restrict in characteristic relationship ,rather use it in filter of query or modeler.It will be helpful.

Former Member
0 Kudos

Hi Indu,

Thanks a lot from your inputs

I have these characteristics in my Planning level BRAND, Base Unit, Company code, Country, Currency, Division, Fiscal year/period, Fiscal Year Variant, PRODUCT, SIZE. Sales District, Segment, Version

In Planning level for Sales District characteristic i have assigned Hierarchy(its having the Hierarchy from South/East/West/Region amd assogmed Related states under that related Offices. so i have assigned this hierarchy at planning level.

I created Mannual layout with Keyfigure in Datacoloumn Model and in Additional settings i choosed (All characteristics combination) and Selected Hierarchy Model with BPS Characteristics with Top Down Logic and enabled Check Entry.

In the Lead coloumn i choosed Brand, Sales District, Segment, Size, In the Datacoloumn keyfigure are quantity and value.

When i Execute its giving the Error : Characteristic 'Sales District' does not contain the initial value in the selection, i have searched in many ways to rectify this problem but i could not able to find, can you please suggest me what could be the problem.

Thanks for your help

Deenu

Former Member
0 Kudos

Hi ,

You can easily achieve this by adding one characteristic more in your cube.

Take this characteristic to differentiate all three levels of planning,say for example new characteristic is ZLEVEL.

1.Sales head ( North & East ) or Sales Head ( west & South ) will put targets for respective

ZBH reporting to them.with ZLEVEL - SH

2 All ZBH will enter targets of BOH with ZLEVEL - BH

3 All BOH will enter targets of BM (Instead of BM it will be ASM/ASE/SO as on date)with ZLEVEL - BM

4 All BM will enter targets of ASM. (Not applicable as of date due to no BM concept)with ZLEVEL - ASM

Then you can specify restrict ZLEVEL with specific values to get corresponding results.

For example to view the data at BOH ZLEVEL - restrict it wth SH and BH the rest will be aggregated at BM level.