Error with a *LOOKUP in a script logic in 7.5 MS

Hello,
We have migrated to 7.5 MS from 5.1 version of BPC. Now we are working with SQL 2008 in the 7.5 MS SP05, but we have a script that doesn´t work now.
The script is:
/Reparto de la MW_INP a MW_AUX, PRIMA_INP a PRIMA_AUX, CAPEX_INP a CAPEX_AUX, FACTOR_INP a FACTOR_AUX y SUBVPOR_INP a SUBVPOR_AUX del año de proyección genérico al año proyección=año PEM
//*SELECT(%YEAR%,[YEAR],PEM,"APLICA='Y'")
*XDIM_MEMBERSET ACCOUNTL = MW_INP,MW_AUX,PRIMA_INP,PRIMA_AUX,CAPEX_INP,CAPEX_AUX,FACTOR_INP,FACTOR_AUX,SUBVPOR_INP,SUBVPOR_AUX
*XDIM_MEMBERSET CATEGORY = %CATEGORY_SET%
*XDIM_MEMBERSET CURRENCY=LC
*XDIM_MEMBERSET TECHNOLOGY = DESCENDANTS(.[RENOVABLES],99,LEAVES)
*XDIM_MEMBERSET PEM = DESCENDANTS(.[PEMTOT],99,LEAVES)
*XDIM_MEMBERSET TIME =
*LOOKUP ABAKON
*DIM YEAR_INICIO:ACCOUNTL="INICIO_INP"
*DIM YEAR_INICIO:TIME="TIME.INP"
*ENDLOOKUP
*WHEN TIME
*IS "TIME.INP"
     *WHEN ACCOUNTL
     *IS MW_INP
           *REC(ACCOUNTL="MW_AUX",TIME=LOOKUP(YEAR_INICIO) + .TOT,NOADD)
     *IS PRIMA_INP
           *REC(ACCOUNTL="PRIMA_AUX",TIME=LOOKUP(YEAR_INICIO) + .TOT,NOADD)
     *IS CAPEX_INP
           *REC(ACCOUNTL="CAPEX_AUX",TIME=LOOKUP(YEAR_INICIO) + .TOT,NOADD)
     *IS FACTOR_INP
           *REC(ACCOUNTL="FACTOR_AUX",TIME=LOOKUP(YEAR_INICIO) + .TOT,NOADD)
     *IS SUBVPOR_INP
           *REC(ACCOUNTL="SUBVPOR_AUX",TIME=LOOKUP(YEAR_INICIO) + .TOT,NOADD)
     *ENDWHEN
*ENDWHEN
*COMMIT
The problem is that in 5.1 MS it concatenated ok and
in 7.5 MS not (it does not understant the concatenate and does not
record anything in Time dimension)
With the REC we want to record the amount of MW_INP (accountl), 2008O
(pem), and TIME.INP (time) on MW_AUX, 2008O and 2008.TOT.
After doing some tests, we think the problem is that in 7.5 MS the LOOKUP is not reteiving
anything. (We have test without "+ .TOT", only with the lookup) But we do not see any error in the code.
Could anybody help with this issue?
Many thanks in advance.

This was a bug and fixed it in 7.5 SP6.
I just want to post it for others.
Regards,
James Lim

Similar Messages

Error with Combo Box, Executing CBTA Script

Dear Experts.
I am Using CBTA in solman 7.1 SP 12 to automate the testing with SAP ERP (SAP GUI) and CRM(CRM UI). We are creating the test script without problem, but at time to execute, it suddenly stop.
We were checking and found that always is failing with a Combo Box field.
do you know if exist any note to correct this behavior?
In CRM UI, the script recording create the following component to fill the combo box
But in the execution CBTA does not fill the field, just try focus in the field, show the values but does not select any.
At the end show the following error
IN SAP ERP
In ERP, the script recording create the following component to fill the combo box
But in the execution CBTA does not fill the field, just try focusing in the field show the values but does not select any.
Then the script execution fail and show a error, saying the field is read only.
Br.
Juan

Hi every One.
Finally i got the solution, the error was that i had set up in SAP GUI the option to view the key in the drop down list and the same happened in CRM UI i had set up the same option.
After shot down this option we record the escenario again, then we execute it and run without problem.
Best regards
Juan

Error with Mapping Lookup API using JDBC

All,
I have an interface that uses a JDBC lookup user defined function. Occassionally we get the following message:
<i>Problem when calling an adapter by using communication channel myJDBCLookup (Party: , Service: myJDBCdbase, Object ID: 0cdb888150ee36638cbfb100ff2e7161) XI AF API call failed. Module exception: 'Error ACK handling failed: java.lang.NullPointerException'. Cause Exception: (No information available)</i>
The only way I can duplicate this error is if I deactivate the myJDBCLookup communication channel and re-run the interface. In this case I get the same exact error. I know the commchannels were active when I ran and got the errors. Typically what I do is just restart the erred message and it runs fine.
I'm thinking I may be running into a timeout problem on the Oracle end of my call and XI is "timing out" or something like that.
My questions are:
1) whether or not XI has some timeout setting that I could increase that would hopefully mitigate this issue (I'm not an XI admin)?
2) would using a different Conflict Resolution (JDBC adapter config) or Number of Retries of Database Transaction on SQL error (JDBC Advanced adapter config) setting help?
3) Is there something altogether different I should be looking at?

Hi,
This blog may help u on to optimize the lookup-
/people/sap.user72/blog/2005/12/06/optimizing-lookups-in-xi
/people/sap.user72/blog/2005/10/15/jdbc-adapter-execution-mode-chained-or-unchained
ALso check the Adapter Engine about time out parameters-
hope this helps,
Regards,
moorthy

Compiler Error with simple vi using MatLab script nodes

While attempting to build a simple vi to test the capabilities of LabView's interface with MatLab, I received a compiler error message that said I should report the problem to National Instruments Tech Support. The error said, "reference to undefined label from: refPC=0x41C." I've attached the vi that created the error. I am using LabView 7.0 on a PC running Windows 98.
Attachments:
Compliererror.vi ‏11 KB

I don't know if this will help your problem, but there is a fix for some problems with LabVIEW 7.0 and Matlab:
http://digital.ni.com/public.nsf/websearch/4475BC3CEB062C9586256D750058F14B?OpenDocument
Good luck,
-Jim

Script logic error - Invalid object name 'tblStatus'

Hi all,
Running BPC 5.1 SP5 on SQL 2005.
Has anyone ever seen this error message before? I only get the error message when choosing the run-time option in the package, to honor work status settings. This problem just appeared in the last few days, and I believe that a month or two ago, users were running the same logic (with the same yes-honor-work-status option selected).
We did recently upgrade from 5.1 SP3 to 5.1 SP5, and I'm wondering if this may be a cause? That's just a hypothesis though.
Invalid object name 'tblStatus'. in:
select distinct d.VERSION,d.ENTITY,d.TIMEID
from #RESULT_333729 d where signeddata<>0
and exists (select * from tblStatus s where [APP]='CONSOL' and d.VERSION=s.CATEGORY and d.ENTITY=s.ENTITY and d.TIMEID=s.TIME and [STATUS]>0)
I understand what it means, and of course there is no table in the appset database tblStatus. Work status locks are kept in tblConsolLock (where Consol is my app name). And in that table, the field name is StatusCode, not Status. So it appears that this is some vestige of code from an earlier version of BPC / O'soft.
This error occurs in a piece of script logic, that includes both basic SQL WHEN/IS/*REC's and also a *RUNALLOCATION. The error is thrown within the RUNALLOCATION code block. The complete run-up to the error message is shown below.
-- Calculate difference
insert into #DIFF_333729 ([ACCOUNT],[AFFILIATE],[CURRENCY],[DATASRC],[ENTITY],[PRODHIER],[TIMEID],[VERSION],signeddata)
select [ACCOUNT],[AFFILIATE],[CURRENCY],[DATASRC],[ENTITY],[PRODHIER],[TIMEID],[VERSION],amtWHERE as signeddata
from #WHERE2_333729
select [ACCOUNT],[AFFILIATE],[CURRENCY],[DATASRC],[ENTITY],[PRODHIER],[TIMEID],[VERSION],sum(signeddata) as signeddata
into #RESULT_333729 from #DIFF_333729
group by [ACCOUNT],[AFFILIATE],[CURRENCY],[DATASRC],[ENTITY],[PRODHIER],[TIMEID],[VERSION]
--Time to calculate and count differences (45459 found):2.5 sec.
select distinct d.VERSION,d.ENTITY,d.TIMEID
from #RESULT_333729 d where signeddata<>0
and exists (select * from tblStatus s where [APP]='CONSOL' and d.VERSION=s.CATEGORY and d.ENTITY=s.ENTITY and d.TIMEID=s.TIME and [STATUS]>0)
call 1 completed and data posted in 23.6 sec.
Run completed in 23.7 sec.
End time --->11:01:05 AM - Date:1/16/2009
Invalid object name 'tblStatus'. in:
select distinct d.VERSION,d.ENTITY,d.TIMEID
from #RESULT_333729 d where signeddata<>0
and exists (select * from tblStatus s where [APP]='CONSOL' and d.VERSION=s.CATEGORY and d.ENTITY=s.ENTITY and d.TIMEID=s.TIME and [STATUS]>0)
Here is the original script logic (from the LGX file -- the LGF file has a whole bunch of variables in it that would only confuse the matter more). It works just fine when the
*RUN_ALLOCATION @A_1||
USING/TOTAL|
ACCOUNT WHAT=659210,659310,659320,659410,659510,659610,659620,659630,659710,659810,659820,659910; WHERE=<<<; USING=PCAYTD510000; TOTAL=<<<|
PRODHIER WHAT=PRODHIERL1A;WHERE=[PRODHIERLEVEL]='5'; USING=<<<; TOTAL=<<<|
DATASRC WHAT=PCAASSESSSTAGE1,PCAASSESSSTAGE2; WHERE=PCAASSESSALLOC1; USING=INPUTCONSOL; TOTAL=<<<|
ENTITY WHAT=[COMPANYCODE]='7470' AND [PCAASSESSDRIVERBP]='PCAYTD510000' AND
([PCAASSESSMETHODBP] = 'ALLOCAUTO' OR [PCAASSESSMETHODBP] = 'ALLOCMANUAL');WHERE=<<<;USING=7470.BASE;TOTAL=<<<|
Anyone experience this same error message? I searched for SAP support notes and found nothing to do with tblStatus or similar.
Thanks for your help,
Tim

Hi Sorin,
Thanks, you've confirmed what I suspected.
Yes, we always process & save apps & dims on any upgrade.
We've reproduced the problem in all 3 of the environments with the customer's appset. I haven't yet reproduced in ApShell, but will do so & report it as a bug.
And just out of curiousity -- was the other message you saw here in this EPM forum? Before I posted my question, I searched both here, and in the support notes, for "tblStatus" and a few other terms about work status lock errors, etc., and came up with 0 results.
Thanks again,
Tim

Getting an error message while running FX script logic

We are getting the following error message, while running the FX script logic - RUN_LOGIC:MDX statement error:"Value (Entity value) for characteristic /CPMB/U8D5FIT". Any help is truly appreciated. We are using the standard FX logic scrip *RUN_PROGRAM CURR_CONVERSION

Hi,
Hope all the required currency configuration settings are followed in Entity, Input currency, Category, Account correctly. Also reporting currency indicates the right reporting currency with the 'Reporting' propert set to 'Y' to the currency that you want to report in.
For the period that you are running the currency trans, could you also maintain rates for the reporting currency as 1.
Check your rate data. And please post your currency conversion script here.
Thanks,
Sreeni

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.

How to create a script logic using two applications and some conditions?

Hi All,
I am using BPC 7.0 MS
I have two applications, one called RATE (Dimensions: Category, InputCurrency, Rate, RateEntity, Time) and one called GYP (Dimensions: Category, Entity, PL, Producto, RptCurrency, Time. In the GYP application for Revenues. I have the followings products:
Product code
1-808-912-433
3-208-345-542
11-869-789-946
13-456-786-890
I need to calculate a discount using the first digits to identify the product: 1, 3, 11 and 13, based on some percentages that are in the RATE application.
I have an element in the RATE application for each one of them.
DPC1
DPC3
DPC11
DPC13
What I am trying to do in the script logic is:
*XDIM_MEMBERSET PL=Revenues
*XDIM_MEMBERSET PRODUCTO=<ALL>
*XDIM_MEMBERSET ENTITY=<ALL>
*XDIM_MEMBERSET CATEGORY=Budget
*LOOKUP RATE
*DIM D1:RATE ="DPC1"
*DIM D11:RATE ="DPC11"
*DIM D3:RATE ="DPC3"
*DIM D13:RATE ="DPC13"
*DIM RATEENTITY="Global"
*DIM INPUTCURRENCY="VEB"
*ENDLOOKUP
*WHEN PL
*IS Revenues
*REC(FACTOR=LOOKUP(D1), PL=Discount)
*ENDWHEN
*COMMIT
In the WHEN area, i would like to create some condition to identify the product and assign the correct percentage to it but i don't know how to do it?
Do you have any suggestions?
Also, because i need to key the values in the RATE application for the discounts, the logic should be run from this application?
Using RUNLOGIC like this:
*RUNLOGIC
*APP GYP
*LOGIC Discounts
*ENDRUNLOGIC
Best regards,
Luisana

Hi Nilanjan,
Thanks for your prompt reply.
The special characters ("-") cannot be used. The product codes use the special character ("_").
I understand what you said about the property for the dimension Product but not for the dimension Rate. I have the lookup that has the four elements (DPC1, DPC11, DPC3, DPC13). It is not supposed to get the data from those elements directly when using the lookup?
The script logic is still not working. I created the dimension property in the product dimension and the new script logic is as follows:
*XDIM_MEMBERSET PL=Revenues
*XDIM_MEMBERSET PRODUCT=<ALL>
*XDIM_MEMBERSET ENTITY=<ALL>
*XDIM_MEMBERSET CATEGORY=Budget
*LOOKUP RATE
*DIM D1:RATE ="DPC1"
*DIM D11:RATE ="DPC11"
*DIM D3:RATE ="DPC3"
*DIM D13:RATE ="DPC13"
*DIM RATEENTITY="Global"
*DIM INPUTCURRENCY="VEB"
*ENDLOOKUP
*WHEN PRODUCT.TYPE
     *IS 1
          *REC(FACTOR=LOOKUP(D1), PL=Discount)
     *IS 11
          *REC(FACTOR=LOOKUP(D11), PL=Discount)
     *IS 3
          *REC(FACTOR=LOOKUP(D3), PL=Discount)
     *IS 13
          *REC(FACTOR=LOOKUP(D13), PL=Discount)
*ENDWHEN
*COMMIT
Could you let me know what i am doing wrong?
The calculation i would like to get is: Discount = Revenues(GYP) X DPCx(RATE)
Also, when I sent the data from the rate application I get the message "ExecuteBaseLogic::invalid application:*APP GYP". I am using a RUNLOGIC in the application RATE with the following code:
*RUNLOGIC
*APP GYP
*LOGIC Decto_en_vtas_pilot
*ENDRUNLOGIC
Kind Regards,
Luisana

Transport Script Logic not posting zero's

Hi Guys,
I have a piece of transport logic that is supposed to transport data from the TRAVEL cube to the Finance cube. The problem is that in some months the users do not have people travelling and only a zero should be transported across to Finance and clear the data that is sitting there. Unfortunately the zero's are being transported across
I even force the accounts to be zero before populating them, but that doesn't work
Here follows my code, please let me know if you can spot anything:
Edited by: Gert Andries van den Berg on May 29, 2009 3:37 PM

In theory, *clear_destination should work across applications, and I've successfully used it that way once or twice. But it's always been a challenge for me to figure out exactly what scoping instructions are required. Plus, I've needed to play with the *calculate_difference option, not sure if it should = 0 or 1, to get the expected results.
Plus, the behavior seems to have changed somewhere along the way, between versions 5.0 and 5.1 SP8.
I may be wrong, but I don't think that the NOADD specifically is going to solve the problem where a zero value in the source app isn't being properly updated to a zero value in the destination app. I've found this problem is a lot easier to resolve if the transfer is being done in the source app's default logic, since that somehow includes the scoping of that zero-value account in the transfer logic. When the transfer logic is run as a batch process (after the value has already been set to zero), it's impossible sometimes to get the logic to generate that zero-value record.
So instead, I've played around with ideas such as a script logic in the destination app, that just clears out the entire region of data that is to be transferred, and then re-transfer everything. I'm sure that this is horribly inefficient, and I'm not really happy with that design, but I haven't come across a better solution.
Regarding the *select's: Correct, these are not "by commit". The commit clears the source data region that was scoped out and was read into memory from the fact tables, during the logic run-time. The select, however, is evaluated at logic validation-time (along with any for/next loops), and the variables are replaced then.
It's not possible to assign some variable %foo% one value "2009" in a select (on line 10), then use it (on line 15), and then assign the same variable a second value "2010" (on line 20), and use it (on line 25). I've never bothered to test this out, but I'm certain that both lines 15 and 25 will see the variable replaced with the same value. My guess is that both would have the value of 2010, the final select.

Error with Script logic

Hello friends,
I am getting an error with running currency conversion in an app, the error says Invalid dimension "C_Category". Here is the script logic, I dont see C_Category anywhere. For the record, the name of dimension is category.
*RUN_PROGRAM CURR_CONVERSION
      CATEGORY     = %C_CATEGORY_SET%
      GROUP = %GROUPS_SET%
      TID_RA = %TIME_SET%
      RATEENTITY = GLOBAL
      OTHER = [ENTITY=%ENTITY_SET%]//For More than one other scope parameters: OTHER = [ENTITY=%ENTITY_SET%;INTCO=%INTCO_SET%...]
*ENDRUN_PROGRAM

Hello,
Variable %C_CATEGORY_SET% means set of members selected for Dimension C_CATEGORY. So, if you want to use CATEGORY instead replace it with %CATEGORY_SET%, but if are running Consolidations I think you need C_CATEGORY Dimension.
Regards,
Gersh

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

Script Logic error when trying to Calculate P*Q

I am new to MDX and Script Logic and need some help.
I am trying to calculate Price * Qty. Prices are stored in an Account called Unit_Price, and Qtys are stored in Accounts as well. We have a Service property called "DRIVER" that points to the Account that holds the Q for that Service, but I can't seem to refer to it in Script Logic. So, for each Service, I want to find the corresponding Unit_Price, lookup the Driver for that service and then use that to find the corresponding Quantity. However, I'm having trouble with the portion that points to the Quantity.
Can someone please help?
This is the error that I get when I try to run it in the Logic Debugger:
"Warning no. -2147467259 reading cell 0; The hierarchy '[SERVICE.DRIVER]' was not found in the cube when the string, [ACCOUNT].[SERVICE.DRIVER],was parsed. "
Here is my Script Logic:
*MEMBERSET(%BILL_ENTITY%,FILTER(DESCENDANTS([ENTITY].[547],99,LEAVES), [ENTITY].CurrentMember.Properties("BILLED_ENTITY")="X") )
*XDIM_MEMBERSET ENTITY = %BILL_ENTITY%
*MEMBERSET(%PQ_SERVICE%,FILTER(DESCENDANTS([SERVICE].[TOTAL_SERVICE],99,LEAVES), [SERVICE].CurrentMember.Properties("ALLOC_METHOD")<>"") )
*XDIM_MEMBERSET SERVICE=%PQ_SERVICE%
*XDIM_MEMBERSET CATEGORY = %CATEGORY_SET%
*XDIM_MEMBERSET TIME = %TIME_SET%
*XDIM_MEMBERSET DATASRC = INPUT
*FOR SERVICE.ALLOC_METHOD = "PQ"
[ACCOUNT].[#16404ZZZ] = ( [ACCOUNT].[UNIT_PRICE], [TIME].currentmember) * ([ACCOUNT].[SERVICE.DRIVER], TIME].currentmember)
*NEXT
*COMMIT

1. completely uninstall all the nokia PC Suite products with this http://nds1.nokia.com/files/support/global/phones/software/Nokia_PC_Suite_Cleaner_7_1_1.exe, and also uninstall all OVI Suite products
2. reboot pc
3. download & Install a fresh copy of PC Suite
4. it will then have you download and install a new version of the software installer after you connect your e90
it should be fine after that. i had to do the same thing a while back.
re: no able to sync the calendar with ovi suite:
go to the Sync drop down and then select Sync Calendar.
hope that helps

Lookup total value in logic script

hi experts,
is it possible to lookup with same criteria that returns many row and fetch the total of all returning rows ? if it is possible, how ?
you can see at attached picture, i try to lookup with same criteria (row 3 & row 5), the different only at column 3. what i want is fetch the total value of row 3 & row 5 = 1000 + 10000 = 11000
but what i get is 1000 which means only fetch the first row (row 3).
the code that i using in my logic script:
*XDIM_MEMBERSET ACCOUNT = 551010
*XDIM_MEMBERSET METRIC = PERCENTAGE
*XDIM_MEMBERSET RPTCURRENCY = LC
*XDIM_MEMBERSET SUBITEM1 = NO_SUB1
*XDIM_MEMBERSET MEASURES = PERIODIC
*XDIM_MEMBERSET SUBITEM3 = NO_SUB3
*XDIM_MEMBERSET BUAREA = NO_BUAREA
*XDIM_MEMBERSET ENTITY = %ENTITY_SET%
*XDIM_MEMBERSET CATEGORY = 2014Q3
*XDIM_MEMBERSET AUDITTRAIL = Input, OFFSET
*XDIM_MEMBERSET INTERCO <> NO_INTERCO
*XDIM_MEMBERSET TIME = 2014.07
*LOOKUP Finance
*DIM EXP_Input:AUDITTRAIL = Input
*DIM EXP_Input:METRIC = AMOUNT
*ENDLOOKUP
thank you.

Hi Yoki,
Please, read How To: Ask questions about Script Logic issues
Point 9! and other...
In general it's possible to use LOOKUP to get a value of the parent node, but it's not clear what total do you want to get.
Vadim

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

Error Script Logic FXTrans

Hi All,
Under script logic section under my application, I have maintain
*RUN_STORED_PROCEDURE=SPRUNCONVERSION('%APP%','%CATEGORY_SET%','','GLOBAL','%SCOPETABLE%','%LOGTABLE%')
and added below it the following
*INCLUDE SYSTEM_CONSTANTS.LGL
*INCLUDE SYSTEM_LIBRARY.LGL
*SYSLIB MULTICURRENCYTRANS.LGF
I receive the following error, " Application: FINANCE
Logic file: FXTrans.LGF
Validation status of executable file: Failed
- missing file:D:\PC_MS\DATA\WebFolders\BSB\AdminApp\FINANCE\SYSTEM_LIBRARY.LGL
Validation status of syntax: Failed
- Invalid syntax found; see statements in red"
The Red ones are
- SYSTEM_LIBRARY.LGL
- MULTICURRENCYTRANS.LGF
Could anyone advise me how do go about on this
Thanks
Zan

Hi,
I'd like to clarify first that SPRUNCONVERNSION and MULTICURRENCYTRANS.LGL do the same thing using different methods. The first requires you to maintain appropriate business rule table called Currency Conversion and the latter is Script Logic-based functinality. Typically you do not need to maintain bot as SPRUNCONVERSION is pretty robust and should fulfil all your needs unless you have to do some truly exotic variation of the business calculation.
So to conclude you probably only need the following in your script logic:
*RUN_STORED_PROCEDURE=SPRUNCONVERSION('%APP%','%CATEGORY_SET%','','GLOBAL','%SCOPETABLE%','%LOGTABLE%')
*COMMIT
and also maintain rates in the rate application. Please refer to user guide section Business Rule Management for further details: [http://help.sap.com/saphelp_bpc75/helpdata/en/b1/f5839e6ba74a22aa4ce9470179c854/content.htm]
In order to use script logic you will need to write the logic yourself or to use the one supplied with the system (in the SYSTEM_LIBRARY).
The logic library is stored in the file on the server %APPSET%\System Library\Logic Library\SYSTEM_LIBRARY.LGL
IN your script logic you need to include the library to use in your logic:
*SYSLIB SYSTEM_LIBRARY.LGL (SYSLIB tells the system to look at the specific place in the appset folder and LGL is the extension for appset-level logic files)
After this you need to call appropriate subprogram from that library and pass some parameters to it:
RunFX(%APP%,%CATERGORY_SET%)
*COMMIT
for example.
Hope this helps,
Madis

Error with a *LOOKUP in a script logic in 7.5 MS

Similar Messages

Maybe you are looking for