Script Logic like a function

Hi all,
I want to execute a load of data from a year and actual version to year + 1 and budget version based in some assumptions filled in another input schedule. I thought that is possible using a script logic, so i create the script and i don´t know how to call it, Just from de the DEFAULT.LGF but is not my idea for this, cause every change in the data will execute this calculation.... Thats is the scenario:
Input Schedule
Time 2011.JAN
========== Budget
Account% 5%
Real data Query
Time 2010.JAN
==========Actual
Account1____100
What i want
Time 2011.JAN
============BUDGET
ACCOUNT1 105
There is another way to do that? I
Thanks

Hi,
For executing a script logic, you need to follow few steps.
1. Create an SSIS package to call your script logic in business intelligence development studio (BIDS) - (please refer to the SSIS package for currency conversion)
2. Create a DM package to call the above SSIS package (please refer to the DM package for currency conversion)
You can run the above DM package to execute your script.
Hope this helps.

Similar Messages

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

SQL functions in Script Logic

I want to build a script logic but the dimensions that I am testing do not have the fields I want in the format I want. In my case I would like to test the "Start" property in the Employee dimension. The property represents the employee start date but is a var char in the format dd.mm.yyyy rather thna a date field. I want to test whether it is five years prior to the date being processed.
My time dimension has a year property and a monthnum property. Each of these are varchar. I can write SQL that would convert these to a date and compare them with the start property on the employee dimension.
Can I do iinsert SQL functions in the When statement. An example would be
*When convert(datetime, substring(employee.start,4,2) + '/' + substring(employee.start,1,2) + '/' + substring(employee.start,7,4))
Can I use SQL functions in the Is statement? An example would be
*Is <DateAdd(YY,-5 , convert(datetime, Time.Monthnum + '/01/'' + time.year)
Finally when I use such techniques and look at the log by using "show log" in the logic debugger I see no reference to the SQL I used. It is as if the generated SQL has not made use of my functions. Instead all I seee are the extract statements from the three fact tables. Is this normal? Is there a way to see what SQL is really being generated and run?
At the moment it seems my only option is to make changes, try running it and hope I get an output. If no records are written I can't be sure whether it is because embedding SQL function is not supported or because I have made some other error.

No, the "BPC SQL" script logic doesn't allow for this extensive use of real SQL within the scripting syntax. As a concept, it's best to think of "BPC SQL" script logic as, "this unique BPC logic syntax will generate real SQL code when it's executed."
There's very little real SQL that you can use within the syntax itself, and definitely not within the WHEN or IF statements. Nothing like cast, convert, substring, etc. (Except you CAN use these, a little bit, in a *SELECT statement. But I don't see how that will solve your current problem.)
Plus, when you consider how the logic engine processes a set of data, it's helpful to think of it in terms of selects & reading through a recordset. So in that regard, a SQL background can be helpful, in understanding the concepts. (Sort of helpful, except when it confuses you, or frustrates you since you don't have all the power you want.)
Anyway, to solve your problem, you might be able to restate the problem, and then use something like this code, which is valid syntax:
*WHEN TIME.TIMEID
*IS >= VERSION.FirstPlanMonthTimeID
In this case, FirstPlanMonthTimeID is set up in the version dimension as, for example, 20090400 (representing 2009.APR). This timeID is set by BPC automatically when processing the time dimension, and I need to ensure that my Version property value is set to match it.
A key point is that in BPC fact tables, the time dimension is stored as TIMEID (not ID, unlike all the other dimensions), and can be used for comparative evaluation in script logic WHEN/IF. The comparison property needs to be stored as an 8-digit integer value. If your time dimension has days in it (along with months), check the TIMEID after processing, and you should see the pattern for assigning values to TIMEID for days and months, etc.
Normally, TIMEID is assigned pretty sensible and stable values. If it doesn't meet your logic requirements, you can create another property (be careful of USERTIMEID, since that has a specific purpose in the system which I've never fully understood) and assign that whatever (integer) values make sense.

Math power function in script logic

Hello all!
Can anybody help me how I can do math "power" function in BPC 5.1 Script Logic?
Thanks

Let's say you have a source account FOO and you want to calculate FOO to the 5th power, posting the result to FOOFIVE.
In BPC SQL scripting, there are no mathematical functions to play with (powers, roots, sine, cosine, etc.) except for add, subtract, multiply and divide -- plus you can round results in your Factor or Expression. So that means, we must use multiplication.
You could certainly do this using a bunch of intermediate accounts, one each for foo squared, foo cubed, foo to the 4th, and foo to the 5th. That would require *GO in between each *WHEN/REC block, and could be slow.
I haven't tried this, but I think this should work, all in one statement:
*XDIM_ACCOUNT = FOO
*WHEN *
*IS *
REC(Factor=GET(Account="FOO")GET(Account="FOO")GET(Account="FOO")GET(Account="FOO")*GET(Account="FOO"),Account=FOOFIVE)
*ENDWHEN
If you want FOO to the 50th power, copy & paste.
If you want square root of FOO, that could be a real challenge. I think to use straight BPC SQL logic it wouldn't be possible. I would probably write a stored procedure using SQL's SQRT(), and call that from the BPC logic file. Likewise for any other geometric functions, complex algebra, etc.
There also may be a way to calculate powers in MDX -- that's more mathematically straightforward -- but as a BPC on MS person, I really never ever use MDX due to performance.
Regards,
Tim

Need Example for AVG() function in script logics...

Hi Everyone,
I need to calculate average for all the account members ...
so if anybody worked with this AVG() in Script logics please share with me...................

What do you mean by calculate average? Average for the period or for some other parent or..? Where do you want to store this average? How do you want to use this average???

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

Use of LEFT in Script Logic

I am having one doubt reagrding usage of excel function like LEFT, MID, RIGHT in script logic of SELECT Statement.
Let me know with example if its possible.
I tried the below statement:
*SELECT(%EQACC%,"ID","ACCOUNT","LEFT(ID,6)='BE9001' AND CALC='N' AND ID<>'BE9001010'")
But it throw the error as "invalid select statement"
Anurodh

Anurodh,
what you are trying to do is not supported. As a workaround you can try to create a new property in the dimension (for example IDSHORT), putting in this filed just the first 6 characters of the ID and you can filter on it like in the following example:
*SELECT(%EQACC%,"ID","P_ACCT","IDSHORT='CE0004' AND CALC='N'")
Regards,
Simmaco

Script Logic: How to test the sign of data

Hi Forum,
I'm looking for a function to test if the amount of an account is positive or negative.
This test is necessary to choose the target account where transfer the amount.
In MS version there is the TEST_WHEN function, but doesn't work in NW (not implemented).
I'm trying to use an algorithm but I don't know the sintax in BPC of Square Root.
I'm working with BPC NW S04.
Have someone suggestion about it.
Thanks a lot in advance.
Gianluca Orlandi

Hey Gianluca,
Looks like this is a known issue and is not supported in NW....
check this thread...
Script Logic: chek the sing of the amount of an account
Hope this helps...

Multiple script logics in default logic... can you control execution ?

Hi Gurus,
My default logic consists of two .LGF files both of which do two different Logics functions e.g. A and B
For one input template when the user saves the data I would like Logic A be run and not Logic B.
For the second input template I would like the Logic B to be executed and not Logic A.
Is there a way to achieve this ?
thanks

Hi Daniel,
The point is that his question not seems related to the data itself but to the screen, maybe a special operation for a screen?
First scenario where the data itself have the reference of the operation. He might be then be able to distinguish even in a scriptlogic.
Second scenario: The calculation is driven by the screen itself. Then he have several oportunities.
          1) Add extra information if possible in one unused dimension for the purpose of this calculation and use this information to distinguish the operation
          2) trigger the calculation on the default script logic of another application and bypass the calculation with a change of destination_app
          3) In a routing schema in a BADI you will still need to implement one of the two above points or as you know drive the operations through the dimension file ;).
Best regards,
Philippe
Edited by: Martin, Philippe on Mar 30, 2010 3:45 PM

Script Logic choice SQL or MDX in NW release?

Hi experts,
I have encountered some opposite arguments in forum. Please can you clarify NW release script logic choice should be as MS release?
In [Script Logic BPC MS (SQL) vs. NW (ABAP); Tim Klem states
- "Write the logic using BPC SQL script logic syntax (not MDX) for performance reasons" but this opinion based on MS version. How about NW release is it really smarter to select SQL Script rather than MDX.
There is another statement in [Re: BPC 7 NW; Deppak mentions that:
- "In BPC 5.1 the script formula approach suggests to use SQL based logic instead of MDX.
Whereas in Teched,08, I learnt that MDX & ABAP (using BADIs) would be used for it. Thats why I am slightly confused...."
But second statement is far beyond NW relase date and I am sure this is not true but I would like you to confirm that.
If you were a project responsible and want that all scripts will be held in one language, what would you choose??
Thanks in advance,
ergin ozturk

Hi Ergin,
I can understand your approach not to use ABAP hence you miss the skills witin your project team.
However, you (or you client) has chosen the NetWeaver version for whatever reason. I'm sure a thorough decisions process has lead to this decision. In choosing the NetWeaver version with SAP BI you will sooner or later come to the point that you will have to use ABAP if you like it or not. Especially when you start using further capabilities within NetWeaver and the BI solutions. So from my point of view ABAP knowledge is an essential skill you need in a project based on SAP NetWeaver anyway.
Additionally I heared some statements that MDX is causing some performance issues on the NetWeaver version. This may have been fixed in the meantime with some SPs.
As the SQL within the NetWeaver verison does not have the full functionality than it has in MS Version SQL is not an option for me.
I do also not see the cost impact hence someone need to do the support anyway. In case of MDX you need an MDX developer, in case of ABAP and ABAP developer. Or a technical BPC consultant able to do the development (which I would recommend you should have in your project team anyway).
So coming back to your original question, I would recommend to do as much as possible using ABAP BADIs.
Cheers,
Steffen

[ASK] Get One Row of Property Value From Dimension in Script Logic

Hello, i need help about how to get one row of property value from dimension in script logic.
Let say there is CATEGORY dimension and the members are like this :
ID                                                  YEAR   Status
PLAN_2011                                   2011        A
PLAN_2011_V1                            2011        I
ACTUAL_2011                              2011        I
FORECAST_2011                         2011        I
FORECAST_2011_V1                  2011        A
PLAN_2012                                  2012        A
PLAN_2012_V1                           2012        I
ACTUAL_2012                             2012        I
FORECAST_2012                         2012        I
FORECAST_2012_V1                  2012        A
If i scope CATEGORY like this :
*XDIM_MEMBERSET CATEGORY = [CATEGORY].PROPERTIES("YEAR") = "2011"
Then i will get member scope like this :
PLAN_2011                                   2011        A
PLAN_2011_V1                            2011        I
ACTUAL_2011                              2011        I
FORECAST_2011                         2011        I
FORECAST_2011_V1                  2011        A
Question :
In script logic, how can i read the second record of scope and move it to variable ?
Ex. : I read second record, so i can get the data of second record (PLAN_2011_V1, 2011, A).
Is there any function to read all record that had been scope ? So i can read all those 5 records.
Is there any substring or offset function in script logic ? How to use it ?
Thank you.

Hi,
Firstly, when we scope the logic, it doesnt fetch the entire record from the member sheet. It just fetches the ID.
Secondly, we dont have the feasibility to read only the second ID and skip the others. However, one alternative is that you use the SELECT statement to store all the IDs in a variable, and then use a FOR loop. But this will loop through all the 5 IDs, as per your example. If you want to skip all the IDs except one, you should maintain some property, so that all the IDs are neglected which doesnt have a particular property value.
Hope you got the idea.

Script Logic examples

Are any script logic examples available anywhere which I can refer to? (like Fox Formula examples in BPS).
Is there any book that I can refer to?
Please let me know.
Thanks.

The central notes for each of the BPCNW Support Pack releases contain helpful information on a variety of topics, as well as information on specific script logic functionality. Please review notes: 1306898, 1349538, 1349538, and 1366582.
http://help.sap.com/saphelp_bpc70sp02/helpdata/en/a1/532226947C49A5B2E2BD32450CB2D1/frameset.htm
Business Planning and Consolidations (BPC) Tips -3 u2013 Sheldon Edelstein
/people/sheldon.edelstein/blog/2008/04/21/business-planning-and-consolidations-bpc-tips-3
/people/sheldon.edelstein/blog
/people/sheldon.edelstein/blog/2008/04/23/business-planning-and-consolidations-bpc-tips-4
SAP Library BPC Administration Guide
https://websmp108.sap-ag.de/~form/sapnet?_SHORTKEY=01200252310000085368&_SCENARIO=01100035870000000112&_OBJECT=011000358700001123512008E
****How to Use BPC Scripting Logic
http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/80ffae4b-99d5-2a10-4e9f-96149969aabb?quicklink=index&overridelayout=true
SAP BUSINESS PLANNING AND CONSOLIDATION SCRIPT LOGIC, PART 2
http://www.sdn.sap.com/irj/scn/index?rid=/library/uuid/a066c75e-3077-2b10-c6a6-b8af14b91775
http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/a066c75e-3077-2b10-c6a6-b8af14b91775?quicklink=index&overridelayout=true
SAP BUSINESS PLANNING AND CONSOLIDATION SCRIPT LOGIC, PART 3
http://www.sdn.sap.com/irj/scn/index?rid=/library/uuid/50c75047-3077-2b10-61b2-9a1b9373b0ee
http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/50c75047-3077-2b10-61b2-9a1b9373b0ee?quicklink=index&overridelayout=true
HOW TO... PASS DYNAMIC PARAMETERS TO SCRIPT LOGIC
http://www.sdn.sap.com/irj/scn/index?rid=/library/uuid/d01ce779-f1b2-2b10-07ba-da3734013245
http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/d01ce779-f1b2-2b10-07ba-da3734013245?quicklink=index&overridelayout=true
You can go to and check under "article library"
http://www.sdn.sap.com/irj/scn/advancedsearch?query=bpc+nw

Script logic debugger

When I try to run a script logic in my production environment there are nothing posted when I use the Show Log functionality.
Running the same script in a test environment show a fine log. Only diffens between environments are the produktion system divided on two servers - (web/ APP - DB) - while the test system is on a single server installation (Both Microsoft 2003 server).
Has anyone experienced something like this?

Hello,
Did you find an issue for your problem.
We have the same problem on our 3 environments (dev, rec, prod).
The 3 env. are multi-server.
BPC 7.0 SP7
one server for App BPC
one server for Sqlserv
Best regards

Include within Default.lgf Script Logic does not run

Dear Gurus,
I wrote a WHEN function in Script Logic which is supposed to multiply a input % (INP01) value (growth) with the absolute figure of the previous year. I works fine in the Backend Debugger. Then I put it in the default logic because I want it to run everytime somebody sends data. However it doesn't run? Has anybody had a problem like this?
When running the default formulas out of the data manager it works just fine.
default:
*INCLUDE CALCULATE_KPI.LGF
Calculate KPI:
*XDIM_MEMBERSET ULOB=D00000
*XDIM_MEMBERSET UCHANNEL=VD0001
*XDIM_MEMBERSET RPTCURRENCY=EUR
*WHEN TIME
*IS "2008.SUM"
*WHEN CATEGORY
*IS "ACTUAL"
*WHEN P_ACCT
*IS "I001"
REC(EXPRESSION=%VALUE%(1+([P_ACCT].[INP01],[ TIME].[2010.INP],[CATEGORY].[PLAN])),CATEGORY=V302,TIME=2010.INP,P_ACCT=I0000001)
*ENDWHEN
*ENDWHEN
*ENDWHEN
Thank you so much in Advance
Edited by: Cora Boettger on Oct 19, 2009 3:59 PM

Hi Cora,
Are you sure that your default logic isn't running and that the *WHEN just isn't being triggered? This has happened to me when members used in *XDIM_MEMBERSET or *WHEN are not base-level. I'm a bit suspicious about 2008.SUM with regards to this.
You can test by replacing what you have with something like
*WHEN CATEGORY
*IS *
*REC(FACTOR=1.1)
*ENDWHEN
If this results in your written back values being multiplied by 1.1 into the TEST category, then your default logic is running and your issue is that the *WHEN is not getting triggered. At that point your should be able to head into the script logic tester and keep trying different scripts until you find one that works.
Good luck!
Ethan

Problems with "GET" in a Script Logic

Hi,
I created a Script Logic in BPC NW with the following code:
*WHEN *
*IS *
   *REC(GET(CONCEPTO=M30121),CONCEPTO=M213)
*ENDWHEN
And I click "Validate and Save" and I get this error:
Validation Error
Unknown Dimension Name in Keyword: "*:
What's happening?
Regards,
Miguel.

Thanks, but my problem is with "GET" function in Script Logic. You don't look at what I do with the code because it's an example. The problem is that the GET function doesn't work.
I created a Script Logic in BPC NW with the following code:
*WHEN CONCEPTO
*IS M30121
   *REC(FACTOR=GET(CONCEPTO=M213),CONCEPTO=M30121)
*ENDWHEN
And I click "Validate and Save" and I get this error:
Validation Error
Unknown Dimension Name in Keyword: "M213):
And if the code is like this:
*WHEN CONCEPTO
*IS "M30121"
   *REC(FACTOR=GET(CONCEPTO="M213"),CONCEPTO=M30121)
*ENDWHEN
The error is this:
Validation Error
Unknown Dimension Name in Keyword: ""M213"):
Regards,
Miguel.

Script Logic like a function

Similar Messages

Maybe you are looking for