Custom Measure in Script logic

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

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

Similar Messages

MEASURES in script logic

Hi All!
How can I use YTD measures in script logic? My aplication is PERIODIC ( YTDInput set to No) and I need in my script logic to use YTD values for some calculation. I tried following syntax
*REC(EXPRESSION=([C_ACCT].[PLM],[MEASURES].[YTD]))
but after validation error appears
http://screencast.com/t/q2gChPrqbVXy.
Please help, how to use measures dim in script logic??
Regards,
Justyna

Full script not it is working fine after change *XDIM_MEMBERSET MEASURES=YTD to *XDIM_MEMBERSET MEASURES=PERIODIC
*XDIM_MEMBERSET C_ACCT = VALCON_EN020
*XDIM_MEMBERSET MEASURES=PERIODIC
*WHEN_REF_DATA = MASTER_DATA
*WHEN C_ACCT
*IS VALCON_EN020
*REC(EXPRESSION=([C_ACCT].[PLM],[MEASURES].[YTD]))
*ENDWHEN
*COMMIT

Dimension Formula versus Script Logic that runs on default

Hi Experts,
Which is better to use dimension formula or script logic that runs on default? We have a lot of dimension formulas and when noticed that it has a huge impact in the performance of our AppSet. When we try to remove them, the performance seems better. We we're thinking of transforming these dimension formulas into script logic which will run by default instead. Right now I'm hesitant with two things, 1.) Will there be improvement in performance if I all these formulas are run at default via script logic? 2.) The maintenance seems to be much more complex for the user if we use script logic.
Thanks,
Marvin

Hi Marvin,
Actually you pointed very well the advantage and disantavage regarding dimension formula.
Dimension formula are executed into run time which means that value are not calculated. Of course this will have an impact regarding performances.
Usually our recommendation is to use dimension formula just when yoiu have KPI's to calculate which will be very difficult to be implemented into SQL scrip logic or when you have very simple calculation like Account A = Account B+ Account C.
For other calculation we advice our customer to use script logic.
But attention:
Default formula should not become very heavy because you will arrive into other issue with performances.
When you will send data if default formula script will be heavy you will arrive into situation to wait may be minutes just to send one figure and of course this will be not acceptable for users.
So you have to use script logic but you have to run into batch mode (schedule package) that script logic.
Into default formula you have to keep just minimum (you have to calculate just figures which have importance for user imediat, real time).
Also you have to be aware that moving dimension formula into scrip logic actually your fact table will grow a lot because the number of records generated will be probably 3-4 times bigger than number of records from fact table with dimension formula.
Maintenance of script logic is more complex than dimension formula and you pointed very well this.
So it is a balance and I tried o provide you suggestions or best practice when you have to use dimesnion formula and you have to avoid dimension formula.
I hope this will help you to arrive to best combination for your application.
Kind Regards
Sorin Radulescu

Use of MEASURES dimension in a RUNALLOCATION in a script logic

Hi everybody,
We are trying to use MEASURES dimension inside a RUNALLOCATION in a script logic, because we need to work with the information at a YTD element
Example:
It works:
*XDIM_MEMBERSET C_CATEGORY=%C_CATEGORY_SET%
*XDIM_MEMBERSET TIEMPO=%TIEMPO_SET%
*XDIM_MEMBERSET PRODUCT=BAS(TOT_PRODUCT)
*XDIM_MEMBERSET MARKET=BAS(TOT_MARKET)
*RUNALLOCATION
          *FACTOR=USING
          *DIM ACCOUNT     WHAT=Cost;          WHERE=Import;           USING=Units;
//        *DIM MEASURES    WHAT=PERIODIC;      WHERE=PERIODIC;         USING=YTD;
          *DIM CLIENT      WHAT=CLIENTE_NA;    WHERE=>>>;              USING=BAS(TOT_CLIENT);
*ENDALLOCATION
*COMMIT
It doesn't work:
*XDIM_MEMBERSET C_CATEGORY=%C_CATEGORY_SET%
*XDIM_MEMBERSET TIEMPO=%TIEMPO_SET%
*XDIM_MEMBERSET PRODUCT=BAS(TOT_PRODUCT)
*XDIM_MEMBERSET MARKET=BAS(TOT_MARKET)
*RUNALLOCATION
          *FACTOR=USING
          *DIM ACCOUNT     WHAT=Cost;          WHERE=Import;           USING=Units;
          *DIM MEASURES    WHAT=PERIODIC;      WHERE=PERIODIC;         USING=YTD;
          *DIM CLIENT      WHAT=CLIENTE_NA;    WHERE=>>>;              USING=BAS(TOT_CLIENT);
*ENDALLOCATION
*COMMIT
How can we do it? Is possible to use Measures dimension?
Any idea out there?
Kind regards
Albert Mas

Hi Albert,
I believe you are correct that using MEASURES in this way is not possible. Depending on whether you have data in future periods, you may just be able to use the time dimension instead of the measures dimension:
*DIM TIME WHAT=2010.AUG; WHERE=2010.AUG; USING=2010.TOTAL;
You could also manually maintain a property and select on the property to do the same thing, which would allow you to exclude future periods.
Another option might be to make your Units account a balance sheet account, which should make it always behave as a YTD value, or create a second UNITS_YTD account as a balance sheet account and populate it with the Units YTD value using script logic before running the allocation, then use the UNITS_YTD account as your allocation driver.
Ethan

Execute custom script Logic from a package.

Hye!
I'm working with 7.0 NW.
I have a custom scriplogic and I would like to execute it from a package of Datamanager.
Is posible? Could you gime me an example code?.
Thanks.

Hi Martin,
This is feasible.
Once you have created a script logic, you need to create a process chain and the script logic will be linked with this process chain. Then you need to create the DM and link the process chain with this DM.
There is one document on SDN "How to Run a Top Down Allocation within BPC NW". Please refer to this. This will take you through the process of linking a script logic to a process chain and then to link the process chain to a DM.
Hope this helps.

Script Logic: Using a property in MDX *REC statement (BPC NW)

Hi,
Is it possible to use a Property in an MDX statement without using *LOOKUP() function? I have script successfully working but it takes 15 minutes to execute and would like to speed it up.
I understand that [DIMENSION].[MEMBER].Property is not valid syntax, and do not believe NW has any other functions to resolve the issue, except *LOOKUP which takes a long time.
Specific Example is below:
I have a piece of script that successfully splits JV Expense by customers. A Profit Share planning driver determines the percentage that each customer is entitled to. Typically this will be 100%, but could be 50% between two customers.
The PROFIT SHARE planning drivers records, and PARTNER_INCOME transactional records are below:
ACCOUNT
ENTITY
PARTNER
SIGNED DATA
PROFIT_SHARE
UK_001
PARTNER_A
0.5
PROFIT_SHARE
UK_001
PARTNER_B
0.5
PROFIT_SHARE
UK_002_PLANNING_DRIVERS
PARTNER_B
1.00
PARTNER_INCOME
UK_001
NO_PARTNER
$5,000
PARTNER_INCOME
UK_002
NO_PARTNER
$5,000
UK_001 has two partners that are each entitled to 50% of the $5,000 NET PROFIT.
For UK_002, one one single Partner is entitled to 100% of the $5,000 NET PROFIT.
Using script logic, you can scope the Profit Share account (PROFIT_SHARE) - , and use a *REC statement to multiply this by the driver. It would look like:
*XDIM_MEMBERSET ACCOUNT = PROFIT_SHARE
*WHEN ACCOUNT
IS *
*REC (EXPRESSION = %VALUE% * ([ACCOUNT].[PROFIT_SHARE],[PARTNER].[NO_PARTNER]), ACCOUNT = PARTNER_PROFIT_SHARE)
*ENDWHEN
This wouldn't be a problem if the Planning Driver is always stored on the same Entity that the Income is stored on, but for UK_002, the planning driver is stored on another Entity - which is stored in a the PLAN_DRIVER_REF property of the entity. It should use UK_002_PLAN_DRIVERS
ID (Entity)
PLAN_DRIVER_REF
UK_001
UK_002
UK_002_PLAN_DRIVERS
UK_002_PLANNING_DRIVERS
In this scenario, we need to switch out the Entity used in the MDX, however I do not believe you can use a property in MDX - can anyone confirm?
I have currently implemented the *LOOKUP functionality to loop through, changing each *LOOKUP partner for each loop.
Lookup:
*LOOKUP PLANNING_JV_US
*FOR %LOOP_ASLS% = %ASL_LOOKUP_LOOP_VARIABLE%
*DIM LOOK_%LOOP_PARTNERS%:ACCOUNT = "PROFIT_SHARE"
*DIM LOOK_%LOOP_PARTNERS%:PARTNER= %LOOP_PARTNERS%
*NEXT
*DIM ENTITY = ENTITY.PLAN_DRIVER_REF                   //   Use PLAN_DRIVER_REF Property of Entity
*ENDLOOKUP
Scope and *REC:
*XDIM_MEMBERSET ACCOUNT = PROFIT_SHARE
*WHEN ACCOUNT
IS *
*FOR %LOOP_PARTNERS% = %PARTNER_LOOKUP_LOOP_VARIABLE%      // 1000 Partners
*REC(EXPRESSION = %VALUE% * LOOKUP(LOOK_%LOOP_PARTNERS%), PARTNER= %LOOP_PARTNERS%, ACCOUNT = TCOJVSHAR_CALC, AUDIT_ID = PP_EXPENSE_BY_PARTNER)
*NEXT
*ENDWHEN
The problem with the above, is that because the Lookup is being generated for every single Partner, there are significant numbers of loops.
Does anyone know of another way this can be implemented in Script Logic? Otherwise we'll need to explore BAdI route.
Thanks,
Nick

Hi Nick,
Use property in LOOKUP - will dramatically speed up the calculation without FOR/NEXT.
Vadim

Greater Than Function in Script Logic File

BPC Experts,
I've got a pretty simple script logic file to calculate salary amounts, overtime, etc. The purpose of this logic is for forecasting. I have two referenced dimensions, TIME and SCENARIO, where TIME.MONTHNUM is equal to its relative month number (eg: Jan monthnum = 1), and SCENARIO.CURRMONTH is equal to the relative amount of actual months data, (eg Jan currmonth = 0, Feb = 1) because if you are completing a February forecast, you have one month of actual.
The ACTUAL scenario is never touched, but after a month closes, we copy the ACTUAL data to, for example, FEB_FCST. So, after January closes, its actuals are copied to the FEB_FCST scenario so we can complete an actual/forecast (one month actual, 11 months forecast).
Currently, the default logic skips anything in the ACTUAL scenario, by stating "*WHEN SCENARIO, *IS <> "ACTUAL" yada yada yada.
However, when the default logic runs on the forecast scenarios, it takes the same inputs from the months that are copied over from the ACTUAL scenario and adds to the original amount, essentially doubling the value--ultimately causing an incorrect actuals number in the forecast scenario.
My script right now looks like this:
*XDIM_MEMBERSET DATASRC=INPUT
*XDIM_MEMBERSET PRODUCT=NO_PRODUCT
*XDIM_MEMBERSET SHIFT=NO_SHIFTS
*XDIM_MEMBERSET MEASURES=PERIODIC
*WHEN SCENARIO
*IS <> "ACTUAL"
     *WHEN TIME.MONTHNUM
     *IS > SCENARIO.CURRENTMNTH
          *WHEN ACCOUNT
          *IS "SALARIED_MANPOWER"
               *REC(EXPRESSION=((([ACCOUNT].[SALARIED_AVG_WAGE] * (1 + [ACCOUNT].[SALARY_TIMEAHALF]))* [ACCOUNT].[SALARIED_MANPOWER])),ACCOUNT="01100")
          *ENDWHEN
*ENDWHEN
*ENDWHEN
*COMMIT
When it hits line 9 (*IS > SCENARIO.CURRENTMNTH) during validation, it errors. How can I use a "greater than" function to dictate whether or not a given scenario should run default logic on a specific month?
If not, is there a different/better way to do it?
Thank you!
ABF

Hi Alex
Take this sample logic, check the properties in your Time dimension to trouble shoot your issue.
*SELECT(%CAT_VAR%, "ID", CATEGORY, ID= PLAN_APRIL)
*XDIM_MEMBERSET CATEGORY = ACTUAL, PLAN, %CAT_VAR%
*SELECT(%CATMTH%, "STARTMTH", CATEGORY, ID= %CAT_VAR%)
*SELECT(%ACT_PERIOD%, "ID", TIME, MONTHNUM < %CATMTH% AND LEVEL = MONTH AND YEAR = 2010)
*SELECT(%PLAN_PERIOD%, "ID", TIME, MONTHNUM >= %CATMTH% AND LEVEL = MONTH AND YEAR = 2010)
*XDIM_MEMBERSET TIME= %ACT_PERIOD%
*XDIM_MEMBERSET CATEGORY=ACTUAL
*WHEN CATEGORY
*IS ACTUAL
*REC(EXPRESSION=%VALUE%, CATEGORY = %CAT_VAR%)
*ENDWHEN
*XDIM_MEMBERSET TIME= %PLAN_PERIOD%
*XDIM_MEMBERSET CATEGORY=PLAN
*WHEN CATEGORY
*IS PLAN
*REC(EXPRESSION=%VALUE%, CATEGORY = %CAT_VAR%)
*ENDWHEN
Thanks

Use of comments in script logic / BADI

Hi,
Does anyone knows whether one can read the comments entered in an input schedule in a script logic or BADI? Depending on the text entered in a comment, a certain planfunction has to be executed during save ...
the user should be able to easily change a dimension value in an input schedule:
Product    Product group    Key figure 1     Key figure 2
A             A1                     10                       30
-> the user easily needs to change the product group from A1 into B1 . When doing so the values of key figure 1 and 2 need to be copied to the new product group and the original values on A1 have to be removed. we cannot set up the product group as a propoerty since one should be able to compare multiple versions with different assignments ... So we were thinking to add an additional comment column in which the new value can be assigned to. When save, it should read the comment and perform the planfunction ... Would this be possible?
D

HI D-
Possible, but you would probably need to create a Badi to accomplish all the logic...
For a start, you would need to be able to find the comments...the naming convention for the dynamic comment table is:
/1CPMB/application_set_prefixapplication_prefixCMT
The two character application_set_prefix can be identified from the table UJA_APPSET_INFO, and the two character application_prefix can be identified from the UJA_APPL table.
Once the comment table is identified you could create a custom Badi to look up comment information to direct processing of specific records.
Regards,
Sheldon Edelstein

FOR loop in script logic

Dear Gurus,
This is the logic I am working with:
*FOR %MONTH% = 2008.FEB,2008.MAR,2008.APR,2008.MAY,2008.JUN,2008.JUL,2008.AUG,2008.SEP
//CHECK IF THE VALUE OF THE ACCUMULATED DEPRECIATION IS GREATER THAN THE CAPITALIZED ASSET VALUE//
[ACCOUNT].[#AccumDepr] = (([ACCOUNT].[AccumDepr]+[ACCOUNT].[Depreciation])>[ACCOUNT].[EQUIPMENT1]? [ACCOUNT].[EQUIPMENT1] : ([ACCOUNT].[AccumDepr]+[ACCOUNT].[Depreciation]))
*NEXT
I am trying to execute the above script logic, but the system is throwing an error that says
"Duplicate formula found: [ACCOUNT].[#AccumDepr] = (([ACCOUNT].[AccumDepr]+......."
Any idea why this is happening?
Also, could you please suggest a better way of writing the above code?
Thanks,
Vijay.

As a testing scenario, I have calculated the depreciation in a different part of the same logic. Here it is:
//This logic calculates the accumulated depreciation amount for the time period specified in the logic
//NOTE: This logic is not very dynamic and is only valid for the accounts specified in the logic
//A FUTURE ENHANCEMENT TO THIS LOGIC WOULD BE TO MAKE THE "LIFE" OF THE ASSET A $DATAMANAGER VARIABLE$
//AND WRITE A CUSTOM SCRIPT LOGIC
//BEGIN SCRIPT LOGIC FILE//
//CONSTANTS
*XDIM_MEMBERSET CATEGORY=ACTUAL
*XDIM_MEMBERSET ACCOUNT=Depreciation,AccumDepr,NBV_EQUIPMENT1,EQUIPMENT1
*XDIM_MEMBERSET ENTITY=STORE1
*XDIM_MEMBERSET TIME=2008.JAN,2008.FEB,2008.MAR,2008.APR,2008.MAY,2008.JUN,2008.JUL,2008.AUG,2008.SEP
//BEGIN: POPULATE NET BOOK VALUE FROM CAPITALIZED ASSET VALUE //
*WHEN ACCOUNT
*IS EQUIPMENT1
     *WHEN TIME
     *IS 2008.JAN
          *REC(FACTOR=1,ACCOUNT="NBV_EQUIPMENT1")
     *ENDWHEN
*ENDWHEN
*COMMIT
//END: POPULATE NET BOOK VALUE FROM CAPITALIZED ASSET VALUE   //
//BEGIN: CALCULATE DEPRECIATION //
*WHEN ACCOUNT
*IS EQUIPMENT1
     *REC(EXPRESSION=(%VALUE%/6),ACCOUNT="Depreciation")
*ENDWHEN
*COMMIT
//END: CALCULATE DEPRECIATION   //
//BEGIN: CALCULATE ACCUMULATED DEPRECIATION AND NET BOOK VALUE //
*FOR %MONTH% = 2008.FEB,2008.MAR,2008.APR,2008.MAY,2008.JUN,2008.JUL,2008.AUG,2008.SEP
//CHECK IF THE VALUE OF THE ACCUMULATED DEPRECIATION IS GREATER THAN THE CAPITALIZED ASSET VALUE//
*WHEN CATEGORY
*IS ACTUAL
*REC(EXPRESSION=IIF((([ACCOUNT].[AccumDepr] + [ACCOUNT].[Depreciation])>[ACCOUNT].[EQUIPMENT1]), [ACCOUNT].[EQUIPMENT1], [ACCOUNT].[AccumDepr]+[ACCOUNT].[Depreciation]))
*ENDWHEN
*NEXT
//*FOR %MONTH% = 2008.FEB,2008.MAR,2008.APR,2008.MAY,2008.JUN,2008.JUL,2008.AUG,2008.SEP
//CHECK IF THE NET BOOK VALUE OF THE ASSET IS LESS THAN ZERO//
//*[ACCOUNT].[#NBV_EQUIPMENT1] = (([ACCOUNT].[NBV_EQUIPMENT1]-[ACCOUNT].[Depreciation])>0? ([ACCOUNT].[NBV_EQUIPMENT1]-[ACCOUNT].[Depreciation]) : 0)
//*NEXT
*COMMIT
//END: CALCULATE ACCUMULATED DEPRECIATION AND NET BOOK VALUE   //
//END SCRIPT LOGIC FILE//
Please let me know if there is a better way to write this code.
Thanks for all your help.

Raise an ERROR message from Script logic

Hi All
Here i have developed a custom copy funtion im not using standard copy functionality.
I am trying to copy from working version to another version ex: V01 to V02. I have scoped these two versoins in script logic.
But when user runs DM package for a different version other than v01 and v02 then user has to get the error message.
Can i achive this by including some code in the script logic. i dont want to use the security options on user level.
is there any function to raise error??
Please suggest thanks in advance.
Regards
AK

Hi AK,
As I understood from your question, you want to copy always from V01 to V02. No other versions will be used other than these 2. So, it will be better to have them hardcoded in your script logic, instead of keeping error messages for the user. Anyways, you dont want the user to enter anything other than V01 and V02.
Hope this helps.

Validate my script logic: reference erro LOOKUP is not defined

Dear all,
i want write one script logic. It use LOOKUP using FOR/NEXT.
But when i check stament in my script logic: messesage erro: reference erro LOOKUP is not defined.Can you help me?
My script logic
*XDIM_MEMBERSET ACCOUNT=BS221
*XDIM_ADDMEMBERSET CATEGORY = Actual
*XDIM_ADDMEMBERSET ENTITY = CSO
*SELECT(%TIME%,"[ID]",TIME,"[ID]>=2006.01 AND [ID]<=2006.02")
*XDIM_MEMBERSET TIME = %TIME%
*LOOKUP Rates
*DIM CATEGORY ="Actual"
*DIM R_ACCOUNT ="AVG"
*DIM R_ENTITY ="Global"
*DIM INPUTCURRENCY="USD"
*DIM MEASURES ="PERIODIC"
*FOR %T% = %TIME%
*DIM RATE_%T%: TIME =%T%
*NEXT
*ENDLOOKUP
*WHEN ACCOUNT
*IS "BS221"
*FOR %T1% = %TIME%
*REC(EXPRESSION=LOOKUP(RATE_%T1%),TIME=%T%)
*NEXT
*ENDWHEN
*COMMIT
Thanks,
Hungth

Dear Vadim,
I want test LOOKUP statement using FOR/NEX, then get value per member for member in LOOKUP.
in excel add-in of Rates Model:
Actual - Actual
Average Rate
Global Entity
2006.01 - Jan 2006
31
2006.02 - Feb 2006
30
2006.03 - Mar 2006
30
2006.Q1 - Q1 2006
30
I want run my script logic above to get value from Rates Model ( 2006.01: 31, 2006.02 : 30, 2006.03: 30 ) to current model , to calculate in crurrent model.
BS221 - Long Term Debt
2006.01 - Jan 2006
2006.02 - Feb 2006
2006.03 - Mar 2006
Actual - Actual
31
30
30
How i can write my script logic? My script logic statements is correct??
Thanks,
hungth

Lookup Script Logic

Dear Freinds,
I am trying to write script logic for learning LOOKUP fuction of script logic and written the below code in BPC 7.5 NW its not working. Please let me know my mistake .
*XDIM_MEMBERSET TIME =2009.APR
*XDIM_MEMBERSET P_ACCT=CE0004010
*XDIM_MEMBERSET CATEGORY=ACTUAL
*LOOKUP RATE
*DIM TIME="2009.APR"
*DIM CATEGORY="ACTUAL"
*DIM R_ACCT="AVG"
*DIM R_ENTITY="GLOBAL"
*DIM RATEEUR:INPUTCURRENCY="INR"
*DIM MEASURES="PERIODIC"
*ENDLOOKUP
*WHEN P_ACCT
*IS "CE0004010"
*REC(EXPRESSION=%VALUE%/LOOKUP(RATEEUR), RPTCURRENCY="INR")
*ENDWHEN

below is the UJTK log but I am not getting result. Please help me .
LOG:
FILE:\ROOT\WEBFOLDERS\BPC_Demo \ADMINAPP\MGT_CONSO\TEST.LGF
USER:PARAGONDNS\BPC_CON
APPSET:BPC_Demo
APPLICATION:MGT_CONSO
[INFO] GET_DIM_LIST(): I_APPL_ID="MGT_CONSO", #dimensions=8
CATEGORY,MEASURES,P_ACCT,P_ACTIVITY,P_CC,P_DATASRC,RPTCURRENCY,TIME
#dim_memberset=3
TIME:2009.APR,1 in total.
P_ACCT:CE0004010,1 in total.
CATEGORY:ACTUAL,1 in total.
REC :%VALUE%/LOOKUP(RATEEUR)
CALCULATION BEGIN:
QUERY PROCESSING DATA
QUERY TIME : 1535.45 ms. 2 RECORDS QUERIED OUT.
QUERY REFERENCE DATA
QUERY LOOKUP DATA FROM APPLICATION: RATE
QUERY TIME : 416.49 ms. 1 RECORDS QUERIED OUT.
CALCULATION TIME IN TOTAL :123.38 ms.
1 RECORDS ARE GENERATED.
CALCULATION END.
SCRIPT RUNNING TIME IN TOTAL:2.42 s.

Handling Ranges in Script Logic

Hi Experts
Is it possible to put logic to check a range of values in Script Logic.
For example, if I need to check if the value in Quantity Account is between 200 and 800, then only some Quantity Discount is calculated against this.
What command should one use for this
Any input would be very helpful.
Regards
Krishnendu

Hi Krishnendu,
I believe that you can use MDX or a BADI to do this. Using MDX, for example, the following should write 100 to the QUANT_DISC account in the event that QUANTITY is greater than 200 and less than 800:
[ACCOUNT].[QUANT_DISC] = IFF(([ACCOUNT].[QUANTITY]) > 200,IIF(([ACCOUNT].[QUANTITY])<800,100,0),0)
This is just example MDX code - you'll have to adapt and test yourself. I suggest using the script logic tester to speed the process. Performance may be less than ideal, and you can certainly implement this in a BADI in that event.
It would be nice if it were possible to do this using WHEN/IS statements in script logic, but at present conditional logic based on measure values is not supported in that context.
Ethan

Substring in script logic

Hi,
We have a customer dimension, where we can extract a lot of information. However the information depends on the sales organization.
Since the client currently have 30 sales organization and we can deduct information like: billing currency, sold-to-country and profitcenter from the combination of sales organization and customer this means I have to create 90 properties to hold this information (30 salesorg * 3 informations pr salesorg).
Therefore I would like to concatenate the information in 1 property per sales organization. This however means I have to be able to make a substring on the property, e.g. in a select statement to retreive the relevant information (it is not possible to do it in the report, since the properties hold information I need to save the data).
Does anyone know if this is possible?
Thanks,
Lars

Hi Lars -
Sorry, string manipulation commands are not available in script Logic. You will need to call a BAdI from script logic and use the rich string manipulation tools available in ABAP.
Regards,
Sheldon

Custom Measure - Unable to Submit Data Using Input Schedule

We have an application that requires storage of data on a job-to-date basis. To accommodate this, the application was changed to a YTD application and 3 custom measures were added:
JTD (base data)
YTD_JOBS (offsets current period against last month of prior period)
PERIODIC_JOBS (offsets current period against prior period)
Everything is working and the measures resolve to the correct values. The system also completes logic (advanced and dimension) properly. Data may also be submitted through an Import process.
However, we are unable to submit data using an input schedule. We consistently get a "no data to refresh" error message. When the same schedule is used in the older, periodic version of the application, the submission works as expected.
I suspect the problem is the naming of the custom measures is the root cause. I have been unable to find documentation (BPC 5.1M) related to custom measures for 5.1. Any help resolving this issue and/or tracking down custom measures documentation for v5.1 is much appreciated.
Cheers,
Jeff

Joost,
I believe what you are describing is the root of the issue. The application is set to YTD as the data input type both in the web admin section and in the database table. The problem is that JTD is the input member for this application -- we are loading job-to-date values instead of year-to-date.
It seems that BPC does not understand JTD as a "base level" measure fort the input method. I have not been able to find a table in the database that defines PERIODIC and YTD. My hope was to add JTD to the settings.
Unless someone else has made something like this work, I suspect that I'll have to use YTD as the ID of the base member and restructure the custom measures. We did not start this way since the user community thinks in terms of JTD data.

Custom Measure in Script logic

Similar Messages

Maybe you are looking for