Simple Script Logic Help - Unit Conversion

Hello Gurus, I am trying to prove some capability of BPC and need to write a Logic for doing it:
The scenario is like this:
I have a cube that will host Sales forecast information :
   Product: A
   Month:     MM01
   Unit :       X
   Signed Data :10
I have a property in the Product y that contains the conversion rate for converting values to another unit. In this case 0.5
What I need is :
1. Read Product Dimension and get the Conversion Rate.
2. Multiply Signed Data by COnversion Rate-
3. Generate a new record :
   Product: A
   Month:     MM01
   Unit :       Z
   Signed Data :(10 * Conversion Rate )
Could you provide a Sample code for this?
Thanks in Advance.
Sergio

Try:
*WHEN *
*IS *
REC(EXPRESSION=%VALUE%FLD(PRODUCT.Y), UNIT="Z")
*ENDWHEN
*COMMIT
You will have to make sure the correct records have been scoped.
Thanks,
John

Similar Messages

Simple Script Logic

Hi all,
Is it possible execute a script logic when i execute the import package? i added in the DEFAULT.LGF the code:
WHEN *
is *
REC(Expression=get(account="ccp0001")*get(account="ccq0001"), account="ccv0001")
endwhen
commit
The idea is calculate value = price * quantity and put in a new rec when i load the data.
value =ccv0001
price = ccp0001
quantity = ccq0001
i dont know whats wrong but thats calculate nothing.

Unfortunately you really don't exactly know if a scope is exactly right, unless you work out the tuples specific to each calculation and the define independent script calcs for each tuple set. A fancy way of saying, breaking down the calculation to each basic account by all the other dimension members that are to get together in a calculation.
There is a way of testing the script starting in version 7.0SP4 ithink, called the logic debugger. This process actually has you define some form of scope in order to test the calculations as a dry run, but not run based on an import, rather based on your request to run.
There are also various rules used during the logic calculation process, such as the engine will query all Accounts for values in the DB that match your inbound data set, or scope. Category, Time and Entity play an critical role in any caluclation, and the processing of values. And remember that logic that works in default may not look the same as when data is loaded, based onthe sets of data that are used during the passing of inbound detals to the engine for the logic processing.
hope this helps.

Calc script logic help needed urgently

Hello Gurus,
I am desiging a calc for Fringe Benefits account.
Longterm disability is calculated by multiplying cost pr employee per month ( constant hard coded number) with the % of Net Headcount
% of NetHEadcount is NetHeadCount(at lowest dept level)/Company Total Headcount(Highest Dept Level)
I have created accounts -- Netheadcount at lowest dept level
Is there a possibility that I calculate the %age of account level 0 to same account at highest level?
If not, please give me solution.
Also, I want to thank all the gurus that have helped me. Thanks to you...I am automated 90% of the process. THis is the last leg for this porject. My respect to all the gurus on Oracle FOrums

Hi
Struggling a little to understand exactly what you need...are you just asking if you can calculate "%NetHeadCount" account, based on "Headcount" account at differing department levels?
If so then I guess you just need something along the lines of...(assuming your fix is on level 0 members of your department dim)
NetHeadCount% = Headcount / Headcount -> TotalDepartmentLevel;
JB

Package with script logic CANCELLED

Hi everybody,
I am trying to implement a very simple script logic that removes negative values from the Units account.
*XDIM_MEMBERSET C_CATEGORY=%C_CATEGORY_SET%
*XDIM_MEMBERSET TIEMPO=%TIEMPO_SET%
*XDIM_MEMBERSET MERCADO=%MERCADO_SET%
*XDIM_MEMBERSET ORG_VENTAS=%ORG_VENTAS_SET%
*XDIM_MEMBERSET CUSTOMER=BAS(TOTALCUSTOMERS)
*XDIM_MEMBERSET PRODUCT=BAS(00001)
*XDIM_MEMBERSET P_DATASRC=DRIVER
*XDIM_MEMBERSET ACCOUNT_SIM=Unit
*XDIM_MEMBERSET TIPO_CLIENTE=BAS(TOTAL_TOP)
[ACCOUNT_SIM].[#Unit]=IIF(([ACCOUNT_SIM].[Unit])*(-1)<0, 0, [ACCOUNT_SIM].[Unit])
*COMMIT
When I execute it with the Data Manager the result of the package is "Cancelled". I have one large dimension ("Customer" with more than 2000 elements) but there are not too many records in the database now. However, when I restrict the number of elements, the package works fine. It seems like a memory issue, I don't know... We are using SAP BPC NW 7.0 SP5
Any idea out there? Is our logic not 'optimized' for BPC?
Thanks a lot,
Mr. Albert Mas

Hi Albert,
I think you're running into a dimensionality limit. I believe this was fixed in SP06.
In any case, it's easy to fix. Just add
*XDIM_MAXMEMBERS CUSTOMER = 1
after your other *XDIM statements.
You should be able to up this number a fair amount, depending on the number of members in other dimensions. In the script logic evaluation, there is code that multiplies the number of members in your memberset in each dimension and then attempts to assign the result to an INT datatype. I don't remember the size of the INT, but if you look at the short dump in ST22 of the SAP GUI, you'll see the code.
Hopefully that helps.
Ethan

BPC 7.5 NW SP 4 - ERRORVALIDATION SCRIPT LOGIC WITH PROGRAM CURR_CONVERSION

Hi Gurus
I´m copying script logic for currency conversion for consolidation application, but when I want to validate this code
*RUN_PROGRAM CURR_CONVERSION
*ENDRUN_PROGRAM
the system generate this error "run program error, message number:""
is very strange because when i run without "N" or any other letter, the validation is correct, for example:
**RUN_PROGRAM CURR_CONVE
*ENDRUN_PROGRAM
is sensitive when I write CURR_CONVERSION
do you have any idea what happend with this?
thanks in advance

Lucio,
This is not a valid currency conversion call:
*RUN_PROGRAM CURR_CONVERSION
*ENDRUN_PROGRAM
You need to provide the necessary argument parameters. I assume that it is validating "correctly" when you remove letters because it can't find the program and just assumes that it will show up at runtime. These other permutations won't work either.
Please search the forum and take a look at help.sap.com for examples of currency conversion. There are a lot of good examples out there.
Ethan

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

What is a logical storage unit in a database can anyone help me in a better

what is a logical storage unit in a database can anyone help me in a better
Thank u

Do you have something specific in your mind? Do you want to clarify something you did not understand in the documentation? If so please provide the document you are reading.
For example, a tablespace is a logical storage unit where datafiles are physical files. Did you read the concepts manual?

Help in script logic

Hi Experts,
We are using SAP BPC 7.5 NW Version SP08. We are using a script logic that calculates the opening value of inventory(ASSTCAINVAMO) for each month except the 1st month of financial year for which the value is entered from an input schedule. The opening value of inventory of each subsequent months are calculated when the parameters for production(e.g. OSDA) are entered from a separate input schedule. The following script logic is written for the calculation:
*FOR %TIM_MEM%=%TIME_SET%
*XDIM_MEMBERSET TIME =%TIM_MEM%
*WHEN P_ACCT2
*IS "OSDA",
REC(EXPRESSION=[P_ACCT2].[ASSTCAINVAMO]+[P_ACCT2].[RDPA][P_ACCT2].[EFFA][P_ACCT2].[OSDA]-[P_ACCT2].[CONVAMUR][P_ACCT2].[RDPU][P_ACCT2].[EFFU][P_ACCT2].[OSDU]-([P_ACCT2].[SALQAMBC]+[P_ACCT2].[SALQAMM]),P_ACCT2="ASSTCAINVAMO",TIME=TIME.NEXT)
*ENDWHEN
*COMMIT
*NEXT
The loop works fine, but it seems the list of time values are not coming in proper sequence. For example, the loop is running for 2011.NOV before it iterates for 2011.OCT. So when it iterates for 2011.NOV, it is not getting the opening value for the month and consequently 2011.DEC's opening value is calculated assuming 2011.NOV's opening value to be 0. In the input schedule the months are in proper sequence.
Is there any way out so that the months come in proper sequence in the logic as well?
Thanks in advance for any help.

We had similar issue . we changed TIME members from Monthnames to numbers . i.e changed 2011.JAN to 2011.01 . Then you get correct result as you are expecting . Issue when using month names in combination of TMVL is that , instead of getting 2011. MAY for TMVL(1,2011.APR) , it gets 2011.FEB . TMVL function some how takes alphabetical order instead of taking month order . Not sure if this behavior is with service pack . But never saw any thread reporting this issue .
Anyways ,you can wait for other responses as i am too curious to know if any one faced this issue and how did they resolve.

Script Logic Syntax Help

Hello,
Like for example I have two dimension like P_ACCT ve PRODUCT.
In P_ACCT dimension I have two members like ACCOUNT1 and ACCOUNT2, and in PRODUCT dimension I have a one members called PER_1100.
I want to update PRODUCT.PER_1100 with ACCOUNT1 / ACCOUNT2 * 100 value.
Example =
ACCOUNT1 = 50
ACCOUNT2 = 200
PRODUCT.PER_1100 = ACCOUNT1 / ACCOUNT2 * 100 = 50 / 200 * 100 = 25
I wrote a script like below but it doesn't work.
*WHEN P_ACCT
*IS ACCOUNT1
    *REC(FACTOR=[P_ACCT].[ACCOUNT2]*0.01,PRODUCT="PER_1100")
*ENDWHEN
*COMMIT
Regards,
Burak

Hello,
I didn't face any problem about this script logic. It works fine. You can use it. I developed this script.
*WHEN P_ACCT
*IS KFNETCIRO
    *WHEN PRODUCT
    *IS TOT_BUD_10
    *REC(EXPRESSION=%VALUE%*0.01*([P_ACCT].[KFORANLAR],[PRODUCT].[NC_1101]),P_ACCT="KFNETCIRO",PRODUCT="1101")
    *REC(EXPRESSION=%VALUE%*0.01*([P_ACCT].[KFORANLAR],[PRODUCT].[NC_1102]),P_ACCT="KFNETCIRO",PRODUCT="1102")
    *REC(EXPRESSION=%VALUE%*0.01*([P_ACCT].[KFORANLAR],[PRODUCT].[NC_1103]),P_ACCT="KFNETCIRO",PRODUCT="1103")
    *REC(EXPRESSION=%VALUE%*0.01*([P_ACCT].[KFORANLAR],[PRODUCT].[NC_1104]),P_ACCT="KFNETCIRO",PRODUCT="1104")
    *REC(EXPRESSION=%VALUE%*0.01*([P_ACCT].[KFORANLAR],[PRODUCT].[NC_1105]),P_ACCT="KFNETCIRO",PRODUCT="1105")
    *REC(EXPRESSION=%VALUE%*0.01*([P_ACCT].[KFORANLAR],[PRODUCT].[NC_1106]),P_ACCT="KFNETCIRO",PRODUCT="1106")
    *REC(EXPRESSION=%VALUE%*0.01*([P_ACCT].[KFORANLAR],[PRODUCT].[NC_1107]),P_ACCT="KFNETCIRO",PRODUCT="1107")
    *REC(EXPRESSION=%VALUE%*0.01*([P_ACCT].[KFORANLAR],[PRODUCT].[NC_1108]),P_ACCT="KFNETCIRO",PRODUCT="1108")
    *REC(EXPRESSION=%VALUE%*0.01*([P_ACCT].[KFORANLAR],[PRODUCT].[NC_1109]),P_ACCT="KFNETCIRO",PRODUCT="1109")
    *REC(EXPRESSION=%VALUE%*0.01*([P_ACCT].[KFORANLAR],[PRODUCT].[NC_9900]),P_ACCT="KFNETCIRO",PRODUCT="9900")
    *ENDWHEN
*ENDWHEN
*COMMIT
[#KFBRUTKAR] = [KFNETCIRO] - [KFSMM]
[#KFURBRKAR] = [KFNETCIRO] - [KFSMM] - [KFISKARTA]
[#KFMAGBRKAR] = [KFNETCIRO] - [KFSMM] - [KFISKARTA] - [KFAMBALAJ]
*COMMIT
I hope it helps to you.
Regards,
Burak

Help in script logic - problem in FOR loop

Hi Experts,
We are using BPC 7.5 SP08. I have written a FOR loop in script logic default.lgf which is as follows:
*FOR %TIM_MEM%=%TIME_SET%
*XDIM_MEMBERSET TIME =%TIM_MEM%
*WHEN P_ACCT2
*IS "OSDU"
REC(EXPRESSION=[P_ACCT2].[ASSTCAINVURO][P_ACCT2].[COGSUPRVIPSA]/[P_ACCT2].[ASSTUPRVTAQTY],P_ACCT2="COGSUIPSAO")
*ENDWHEN
*COMMIT
*NEXT
As per my requirement, all this members: [ASSTCAINVURO], [COGSUPRVIPSA], [ASSTUPRVTAQTY] exists for months September to next year's August. But in my input schedule, the months are from August to next year's July(which is the company's fiscal year). Consequently the loop runs for month August to next year's July while I need to run the loop 1 month late(i.e. September to next year's August). This was achieved earlier by hard-coding the time members which we cannot afford as this requires to update these hard-coded member IDs every year.
We have also tried using the "NEXT" property of TIME dimension as follows:
*XDIM_MEMBERSET TIME =%TIM_MEM%.NEXT
but %TIM_MEM%.NEXT doesn't get the month in 'NEXT'.
Please suggest if there is any way out to solve this problem.
Thanks in advance.

Hi Appu,
Even if you restrict the scope using the XDIM statement, your script will just run the number of times as per the for loop. Actually, in reality, the same calculation is happening again and again, in your code; since your calculation is not based on the time member.
To use the for loop effectively, you need to incorporate the time member in your calculation.
Please look at the below sample code:
*XDIM_MEMBERSET TIME = %TIME_SET%
*FOR %TIM_MEM%=%TIME_SET%
   *WHEN P_ACCT2
   *IS "OSDU"
      *REC(EXPRESSION=<CALCULATION>,P_ACCT2="COGSUIPSAO")
   *ENDWHEN
*NEXT
And in your calculation, you can use statements like
([P_ACCT2].[ASSTCAINVURO],TMVL(1, [TIME].[%TIM_MEM%]))
This will ensure that everytime (as per the for loop), the calculation works on separate set of data.
Hope you got the idea.

Please help me to write a simple script.

I wonder to tell a application named "Alien BBS", to input "right key" then wait for 5 seconds to input "left key".
How can I do that by using a simple script ?
tell application "AlienBBS"
activate
input ?
end tell
Please do me a favor to write~ cause I don't have any computer language background. Thanks in advance.

Hi Tim,
When you run an application it becomes a process. You can do stuff with the process. One thing is ui scripting which means that you're interacting with the user interface of tghe process. Some Processes don't have the same name as the application it was launched from, but usually they're named the same. You can try this:
tell application "AlienBBS"
activate
end tell
tell application "System Events"
tell process "AlienBBS"
keystroke (ascii character 29) -- right key
delay 5
keystroke (ascii character 28) -- left key
end tell
end tell
You need to test it out and adjust.
gl,

Simple Script - won't run - please help

I've written a very simple script to check to see if a volume is mounted and then copy a directory to that volume if it is mounted:
#!/bin/sh
# check to see if network space mounted by looking for known folder
if [ -d /Volumes/backupvolume ]; then
cp –R /Users/username/Documents/foldertobebackedup /Volumes/backupvolume/username
fi
I made sure the cp command works by running it in the terminal - no trouble there.
According to what I see in Xcode, all the syntax is correct and there are no errors.
I then run the test on the script (per the Bombich instructions):
sudo u+x /Users/user/backupscriptingtests/190520100730.sh
I'm then required to enter the password (which I do and it accepts it)
The next thing that happens though is the following error appears:
sudo: u+x: command not found
Any ideas on what I'm entering incorrectly here? Eventually, this script will be a logout hook to copy files for a user as a backup. This process seems like it should be very simple, which is why I'd rather do it this way instead of buying a backup program.
Thanks!
FYI: The -d command has brackets, left bracket with space at the beginning and space with right bracket just before the ;
Message was edited by: mcguirek
Message was edited by: mcguirek

You need to include the actual backup volume name and home folder name where backupvolume, username, and user are. If the backup volume name contains spaces or other special characters, precede them with backslashes or put the whole path in single quotes.
(53087)

From where i can run script logic file.

Dear All,
I am new to BPC.
I have a code for currency translation in my Script logic (Default.lgf).
From where i should run this file. Can any help me.
thanks a lot in advance,
Regards,
Satish.

Typically the Currency rates are stored in the "RATE" application. This application is what the script logic or Business rule will call during the conversion process. The rates are only stored by MONTH and by TYPE in a typical planning application. If you need more granular rate details, then you may need to make you time dimension by weeks or days, or add more "TYPES" that are assigned to ACCOUNTs in th ecorressponding account dimension.
But in a simple planning world, most companies will use a monthly rate, one for an AVG and one for END account types, enter this into the RATE application, and run the Defualt logic on submission of data to compile the FX value. Whne you wish to view the results, make certain that you select the correct REPORTING CURRENCY in the report. Many time users forget that data is "normally" entered to an ENTITY,, the ENTITY defines the currency it assumes data is entered, so the plan is loaded to the "LC" member, and converted to USD; or entered in LC, and converted to RS.
But the RATE application will store all the rates required and you may need to open the INPUT template in that application to load the data at the correct intersections.
Hope this helps.

An error in Script Logic

Hi Experts,
I have a problem with one of the FXTranslation logicu2019s in one of my report can u please help me on that.
The logic works fine for 2 reports out of 3, for the 3rd report I donu2019t know why itu2019s not doing the translation to USD. As far as the design of the report goes the 2 reports for which translation works fine comprises of 2 logics one for percentage allocation and other for translation from LC to USD, whereas the 3rd report needs only translation but doesnu2019t need the allocation logic to be run.
The conversion for the 3rd report happens if I comment out the allocation logic. Both these logics are mapped to Default.LGF file. I am unable to figure out what could be the error.
Below is the Script Logic for Aloocation and Translation:
//Budget Allocation
*SELECT(%CURR%,"[ID]","RPTCURRENCY","[CURRENCY_TYPE]='L' OR [CURRENCY_TYPE]='R'")
*XDIM_MEMBERSET RPTCURRENCY=%CURR%
*RUNALLOCATION
*FACTOR=USING/1
*DIM ACCOUNTB WHAT=[IS_ALLOC]='Y'; WHERE=<<<; USING=ALLOCPER
*DIM PRODUCTM WHAT=NOPRODUCT; WHERE<>NOPRODUCT; USING=<<<
*ENDALLOCATION
*COMMIT
// Currency Translation
*SELECT(%REPORTING_CURRENCIES%, "[ID]", "RPTCURRENCY", "[REPORTING] = 'Y'")
*SELECT(%FX_RATES%, "[ID]", "RATE", "[GROUP] = 'FX RATE'")
// Load the rates from the RATE cube
*LOOKUP RATE
            *DIM CATEGORY="BUDGET"
     *DIM RATEENTITY="GLOBAL"
     *DIM RATE=ACCOUNTB.RATETYPE
     *DIM SOURCECURR:INPUTCURRENCY=LEGALENTITY.CURRENCY
     *FOR %CURR%=%REPORTING_CURRENCIES%
          *DIM %CURR%:INPUTCURRENCY="%CURR%"
     *NEXT
*ENDLOOKUP
// define the translation rule
*WHEN ACCOUNTB.RATETYPE
*IS "NOTRANS"
     // skip
*IS %FX_RATES%
           // translate
     *FOR %CURR%=%REPORTING_CURRENCIES%
          *REC(FACTOR=LOOKUP(%CURR%)/LOOKUP(SOURCECURR),RPTCURRENCY="%CURR%")
     *NEXT
*IS "COPYLC"
     // take as is
     *FOR %CURR%=%REPORTING_CURRENCIES%
          *REC(RPTCURRENCY="%CURR%")
     *NEXT
*ENDWHEN
*COMMIT
// Default
// FX Translation
*include FXTranslation.lgf
// Budget Allocation
*include BudgetAllocation.lgf

Hi Naresh,
One thing that helped me solve the problem was I needed to use different set of Dimension members/property in the Logic i.e What, Where and Using to trigger off the Curency Translation.
But please make sure that you use try to understand a unique dimension (member/property) used and use that to trigger off the translation or anything for that matter. My other two translations were working fine as the parameters i used were unique for them whereas the remaining one needed alteration in the logic only in the parameters used in What, Where and Using, so had to add one more set of Translation Logic for this exclusively.
Another point you need to check in your Rate Application is whether you have your Reporting Currency as value 1, say for eg USD is your reporting currency then the value in Rate Application for USD must be 1, if u by mistake cleared of this value when using the Clear Data Manager Package so the multiplication with 0 results in no conversion.
These were the two points that helped me solve my issue. I hope it helps.
Rgds,
Rizwan
Edited by: Rizwan Mustaffa on Jul 13, 2009 12:09 PM

Concatenation in script logic

Hi,
I am using BPC 7.0 MS and i have a problem with the script logic.
I have a combination of dimension, i.e. account=price, entity=big_state; and i have another combination of dimension, i.e. account=unit,sales , entity=country. The 'country' entity has a property called 'property1', and assuming one of the property member is 'state'.
in a nutshell, i need to do a unit*price=sales, but they have different entities which are related through the property.
below is what i have tried, and it's unsuccessful, i.e.my input schedule will always include combination of account=price,unit ; entity=big_state,country
*xdim_memberset account=price,unit
*when account
*is unit
rec(expression=%value%get(account=price,entity= big_ + entity.property1), account=sales)
*endwhen
i think it's the concatenation, i.e. entity=big_+entity.property1 that's making my script logic fail.
any suggestions?
Cheers

Hi,
You can try using something like:
*WHEN CATEGORY
*IS FACT
*REC(FACTOR = 20, CATEGORY = FORECAST)
*ENDWHEN
Hope this helps.

Simple Script Logic Help - Unit Conversion

Similar Messages

Maybe you are looking for