cancel
Showing results for 
Search instead for 
Did you mean: 

Custom Measure in Script logic

Former Member
0 Kudos

Hi,

We have a custom measure created which is more or less the same as the YTD, but it starts not at the beginning of the year, but instead it starts at a given month.

The measure creation was ok and we can use it perfectly well in reports and input shedules and the cumulation of data is ok.

However, if we want to use this measure in a script logic it does not work.

- Validating the script in the admin console goes fine

- Executing the script gives the error:

- Root element is missing

- validating in UJKT gives the erro:

- UJK_VALIDATION_EXCEPTION:Invalid Measures value: "T_232"

The script we try to use is below. If we change the LTD (our custom measure) by YTD it works perfectly fine:

*XDIM_MEMBERSET BUILDSTATE=NABS

*XDIM_MEMBERSET BUSAREA=V1

*XDIM_MEMBERSET CATEGORY=FCSTCUR

*XDIM_MEMBERSET DATASRC=INPUT

*XDIM_MEMBERSET ENTITY=201

*XDIM_MEMBERSET MARKSEGM=NAMS

*XDIM_MEMBERSET ORIGIN=OBOOK

*XDIM_MEMBERSET PRODUCT=ELEVATORS

*XDIM_MEMBERSET PROFCENT=201251

*XDIM_MEMBERSET RPTCURRENCY=LC

*XDIM_MEMBERSET SALESORG=SO_201

*XDIM_MEMBERSET TECHPLATF=NATP

*XDIM_MEMBERSET TIME=2010.OCT

*XDIM_MEMBERSET TYPE=T_PLAN0

*XDIM_MEMBERSET NEBACCOUNT =BAS(T_232)

*XDIM_MEMBERSET MEASURES=PERIODIC

[NEBACCOUNT].[#A232]=([MEASURES].[LTD],[NEBACCOUNT].[T_232])

*COMMIT

Thanks for any input on this. We want to avoid going via a BADI!

Kind regards,

Christophe Posson

Accepted Solutions (0)

Answers (1)

Answers (1)

Former Member
0 Kudos

Hi Christophe,

I'm in a similar position to you and wish to avoid use of a BAdI if we can - despite the MDX parser engine being pretty pathetic at handling YTD or custom measures.

Did you get a resolution to this? If so, could you please share it with everyone?

As much information as possible would be apprecaited. Our next move is to contact SAP for confirmation that there is no possibility of using custom measures in Script Logic.

Many thanks,

Nick