Can this planning layout format possible?

[Former Member]

Hi,

I'm wondering if I can achieve the following layout format.

I've 3 characteristics MATERIAL VERSION and STATUS and a KeyFigure DATA.

let'z say data is as follows.

MATERIAL VERSION STATUS DATA

============================

MATERAL1 Versin1 1 100

MATERAL1 Versin2 1 200

MATERAL1 Versin3 2 300

Status 1 means rejected and 2 means accepted.

Now, I need a layout that displays all accpted materials without displaying VERSION.

I'm looking for a layout with following informaiton.

MATERIAL STATUS DATA

====================

MATERAL1 2 300

I tried in 2 ways but not relevant as per my needs.

1. I didn't include VERSION characteristic in the planning level (LEVEL1).

drawback of this is, when I execute a planning function by updating DATA keyfigure, data is being updated correctly but VERSION field is blank for the new record (wrong) as VERSION is not included in LEVEL1.

I even tried by creating a backend level (LEVEL2) and included VERSION in this level.

so, when planning folder is executed, I look at LEVEL1 layout and included a Global Planning Sequence that runs on LEVEL2. but, still VERSION is blank in the new record.

if planning function changes DATA from 300 to 325,

planning cube is having following information.

MATERIAL STATUS DATA

====================

MATERAL1 2 300

MATERAL1 # 325

2. I did include VERSION in planning level and had put the same in dynamic data columns. it's giving correct data and no problem even if i execute planning funciton.

drawback of this is, it is creating DATA fields as many as entries in VERSION masterdata.

if i've 3 entries in VERSION master data, i'm getting following layout.

MATERIAL STATUS DATA1 DATA2 DATA3

====================

MATERAL1 2 300

where DATA1 = DATA for version1 etc..

hope it is clear. Appreciate any suggestions.

[Former Member]

then you just need to give a range or multiple single value for the version in planning level selection pushbutton, and hide in the header.

[Former Member]

you can incluse the version in the planning level, but put it in the header and hard code to 2.

[Former Member]

I can't put VERSION characteristic into header as it varies for each material.

So, Including VERSION into header is ruled out.

Material1 Can be accepted for Version 2

Material2 Can be accepted for Version 3

Material3 Can be accepted for Version 10 etc..