Script logic using Dimension.Property

Hello, Gurus!
I have next problem with script logic:
Dimension Company
Company1
Company2...
Dimension Document
Document1
Document2...
Dimension Document has property PCompany, where there is Company ID.
I need to summation all data for Company=Company2 (for example).
How can I choose records from Dimension Document for PCompany=Company2 with BPC script logic?
Thanks!
Regards,
Svetlana.

Hello Gersh!
Thank you very much. It's worked.
I should clarify the question
I have several company which I choose with property of Company (for example, INTERCOMP=Y)
So, I have :
*SELECT(%COMPANY%,ID,COMPANY,INTERCOMP=Y)
*WHEN Document.PCompany
*IS %COMPANY%
*ENDWHEN
This construction doesn't work.
Regards,
Svetlana.

Similar Messages

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

Execute script logic using data manager

Hi all,
Could anyone explain me how to run a script logic using the data manager?
The only way I get it working is adding the script logic into the defaul.lgl file and running the default formulas package via data manager.
How can I run an specific script logic without using the default.lgf file?
Thanks and regards,
Ana

HI Ana,
You will have to create a SSIS package that will run the logic for you. A good example of this is the ICELIM package that comes standard with AppShell. The easiest is way for me is to copy the package and renaming it to what you want to call it in the following folder: C:\BPC\Data\Webfolders\<AppSet>\<Application>\DataManager\PackageFiles\System Files
You will then have to organize the package list and add the package and modify the advanced properties of the package and point it to the correct logic file. I always use the lgf file rather than the lgx file, but it is up to you.
Lemme know if you need more info.
Regards,
Andries

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

Row Axis using dimension property

Dear All,
I have a property on the Currency dimension, say "R_Acct", that identifies the R_Account ID each Currency memebr should post into. For example:
R_account:
ID Desc
UK UK Inflation
US Us Inflation
Eur Euro Inflation
Currency:
ID Desc R_acct
GBP Pound Sterling UK
USD US dollar US
Euro Euro CUrrency Eur
My requirement is to build an input sheet with the R_account and Currency dimensions expanded on the row axis. However, i want to fetch the corresponding R_acct for each currency member to replace the EPMOlapMemberO for the the R-Account dimension. Using the EPMMemberProperty only makes it a local member and does not make it an axis. And when i tried "EPMOlapMemberO(E19,"[R_ACCOUNT].[PARENTH1].[US]","US","","000") the first parameter does not move with the expansion. Kindly help me with this as am not sure which EPM function enables it.
I appriciate all your inputs. We are on EPM 10.0 SP 12 Patch 9
Regards
Seyi Obabiyi

Hi Seyi,
You dont require any local members.
First column will represent the CURRENCY dimension.
In the second column, get the R_ACCOUNT dimension. In the memberset of this dimension, select "Dimension Property", then select the dimension as CURRENCY, and then select the property as R_ACCT.
Hope this helps.

BPC : Using Dimension Property in Formula of a Conversion File

Hi,
I want to export data using Package Export from Fact Table. I have transformation and conversion files.
I want to use the property of a dimension in Formula Column of a Conversion file.
I want to lookup the property and based on property I want to either skip record or have internal value.
I am looking for something like follows..
=iif([%external%].TYPE = WBS,*SKIP,D2113)
So if my Dimension 's TYPE property is WBS , I would like to skip that record else I want the value from fourth column.
I am running the Export from Fact Table with various combinations in formula column , but it is only returning null in the export file.
Please let me know how I can make this work.
Thanks,
Sanjay

Sadi,
You can write if Statement in transformation not conversion.
Look at this docs,
How to Import Master Data and Hierarchies into SAP BusinessObjects BPC 7.5 from SAP NetWeaver BW
http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/c02d0b47-3e54-2d10-0eb7-d722b633b72e?QuickLink=index&…
Thanks

[ASK] Error in Script Logic Using WHEN

Hello guys.
Script logic :
*XDIM_MEMBERSET CATEGORY = %CGY_PLAN%, %CGY_FORECAST%
*XDIM_MEMBERSET ACCOUNT = <ALL>
*XDIM_MEMBERSET ENTITY = <ALL>
*XDIM_MEMBERSET TIME = %YEAR_TTL%
*XDIM_MEMBERSET VEHICLE = <ALL>
*XDIM_MEMBERSET BUDGET_ACT = <ALL>
*WHEN CATEGORY
*IS %CGY_PLAN% // Error
*WHEN TIME
*IS %YEAR_TTL%
*REC(CATEGORY = %CGY_FORECAST%, TIME = %YEAR_TTL%)
*ENDWHEN
*ENDWHEN
*COMMIT
When i validate, it is error for statement : *IS %CGY_PLAN%.
But if that statement i change into : *IS %YEAR_TTL%; it isn't error.
Why is this happen ? How to correct it ?
Thank you.

Hi,
You have 3 variables in your script - CGY_PLAN, CGY_FORECAST, and YEAR_TTL.
Are you passing the values to these variables through DM package?

How to use dimension property in REC statement?

Hi,
In dimension ACCOUNT I have created additional property ZACC where I store "alternative" account numbers.
After I load actuals from BW to "regular" accounts I want to copy values to "alternative" accounts.
Regular accounts are hierarchy nodes and alternative are base members.
ACCOUNT dim values looks like that:
ID     ZACC
A1     A.1
A2     A.2
A.1
A.2
etc.
I wrote code below for that but when I validate I get message:
UJK_VALIDATION_EXCEPTION:Invalid dimension "ACCOUNT].[ZACC" in model ZXC
*XDIM_MEMBERSET TIME=2012.01
*XDIM_MEMBERSET ZKEYFIGURE=ZBALANCE
*SELECT(%ACC%,"[ID]",ACCOUNT,"[ZACC]<>' '")
*FOR %AC%=%ACC%
*WHEN ACCOUNT
*IS BAS(%AC%)
*REC(ACCOUNT=[ACCOUNT].[ZACC])
*ENDWHEN
*NEXT
Can you suggest me how to fix my code?
Thanks,
Andrzej
Message was edited by: A Ksik

Hi Andzej,
I will try to explain in details. If we are talking about target member override in REC like:
*REC(EXPRESSION=%VALUE%,SOMEDIM=TARGETMEMBER,...)
TARGETMEMBER can be:
1. Some fixed single member
2. Variable like %VAR%, but this %VAR% will get the value from FOR/NEXT loop (simply duplicating lines of code).
Something like:
*WHEN SOMEDIM
*FOR %VAR%=MEM1,MEM2,MEM3 //lines between FOR and NEXT are duplicated
*IS %VAR%
*REC(EXPRESSION=%VALUE%,SOMEDIM=PREFIX%VAR%SUFFIX)
*NEXT
*ENDWHEN
Where PREFIX%VAR%SUFFIX - is the target containing fixed prefix or suffix and contents of %VAR%
The result of code processing this code will be evaluated to:
*WHEN SOMEDIM
*IS MEM1
*REC(EXPRESSION=%VALUE%,SOMEDIM=PREFIXMEM1SUFFIX)
*ENDWHEN
*WHEN SOMEDIM
*IS MEM2
*REC(EXPRESSION=%VALUE%,SOMEDIM=PREFIXMEM2SUFFIX)
*ENDWHEN
*WHEN SOMEDIM
*IS MEM3
*REC(EXPRESSION=%VALUE%,SOMEDIM=PREFIXMEM3SUFFIX)
*ENDWHEN
This code is VERY slow and ineffective!
In you case the code can be:
*FOR %AC%=%ACC% //list of nodes
//or *XDIM_MEMBERSET ACCOUNT=BAS(%AC%)
*WHEN ACCOUNT
*IS BAS(%AC%) //or * if XDIM
*REC(EXPRESSION=%VALUE%,ACCOUNT="PREFIX%AC%")
*ENDWHEN
*NEXT
but you will need special coding for target to support PREFIX
3. Member property containing correct member ID, like
SOMEDIM.SOMEPROPERTY
In this case the member property of the current record of WHEN/ENDWHEN loop will be used as a target.
Hope it's clear!
B.R. Vadim

BPC 10.0- Creating report using dimension property filter

Hi,
I created a new report in EPM addin for excel using the 'Filter Members by Properties' feature in the EPM Member Selector Window.
My requirement is as I add new members to my dimension with that property value , the report has to refresh and display the new member in the report.
The feature met my requirement and I saved the report.When I reopen the report, the filter that I had earlier used to create the report is hard coded with the members with those properties in the EPM selector Window.
As a result, when I add new Members to the dimension with that property , the report does not recognise that new member and my requirement does not meet.
Eg: I create report with Entity dimension across row axis and Product Dimension -filter on category = New across column axis
and save the report.
When I reopen the report, I see that in the EPM Member selector window, across column axis the members with Property Value Category= Y - Product A,Product B, Product E are hard coded and the filter has been auto removed.
So when I add a new member to my product dimension Product N with property Category= New, the report does not recognise this member.
Please help on how can I use this feature to meet my requirement.
Regards,
Sowmya

Hi,
It should work for newly created members which meets the requriement in member selector.
Member filtering by properties:
Select property, operator and Value and click Add Dynamic filter then in the right window you will be able to see as follows:
Member name Relation ship
<property>=<Value> Property
Hope it works,
Thanks,
Raju

Script Logic using when Condition

Hi,
Im working on BPC 7.5 SP04 MS and I cant figure out how to make this logic work:
1. Cuenta members (account) with the ivaacred property, are multiplied by a certain value and stored in the account 13010A
*WHEN TIEMPO
*IS 2009.Jan, etc etc.....
*WHEN CUENTA.IVAACRED
*IS "Y"
*REC(EXPRESSION=%VALUE% * GET(METRICAS="IND.IVA"),CUENTA="13010A")
2. When the data values for the cuenta 13010A are <= 0, then multiply them by zero and post them in the same account, else leave them the same way.
*WHEN CUENTA
*IS 13010A
IS <= 0
*REC (EXPRESSION = %VALUE% * 0, CUENTA="13010A")
*ENDWHEN
Thanx in advance
Velázquez

Hi Karthik,
The hierarchy you understood is correct
OUTSOURCING (Parent)
s_outsourcing (Son)
O_Gastos (Son)
This is an example of our report, what we look for in our script...
We want the calc to be applied to the parent values, instead of doing the roll up.
Area= s_outsourcing
Income = 100,000
Costs = 0
EBITDA = 100,000
ISR (30%) = 30,000
Area= O_Gastos
Income = 0
Costs = -50,000
EBITDA = -50,000
ISR = 0
Outsourcing
Income = 100,000
Costs = -50,000
EBITDA = 50,000
ISR = 30,000 --> WRONG!!!
Correct answer = EBITDA * 30% = 15,000

BPC Script Logic Multi-dimension REC Statement

Hi All BPC Experts,
The way that our data in the dimensions is setup, members in one dimension have properties that "point" to members in other dimensions.
In this case when I write the REC statement, whilst I'm just doing arithmetic on P_ACCT, when I write the final value, I also need to specifiy the members for the dimensions CUSTOMER, ENTITY, MINE, DESTINATION.
In the example below I hve hardcoded the CONTRACT and TIME dimension members, but going forward, this logic will be appllied to a number of CONTRACTS and TIMES so the members of the other dimensions need to be retrieved dynamically.
*XDIM_MEMBERSET P_ACCT = CAPACITY_REV,CAPACITY_RATE,FINAL_VOLUME
*XDIM_MEMBERSET CATEGORY=FORECAST
*XDIM_MEMBERSET P_DATASRC=Input
*XDIM_MEMBERSET CONTRACT=0005000001_10
*XDIM_MEMBERSET TIME=2009.JUL
*WHEN P_ACCT
      *IS CAPACITY_RATE
         *BEGIN
            REC(EXPRESSION=(%VALUE%[P_ACCT].[FINAL_VOLUME]),
                     CUSTOMER = CONTRACT.CUSTOMER,
                     DESTINATION = CONTRACT.DESTINATION_ID,
                     ENTITY = CONTRACT.HAUL_PC,
                     MINE = CONTRACT.MINE_ID,
                     P_ACCT = "CAPACITY_REV")
         *END
*ENDWHEN
*COMMIT
My Question is twofold:
- Can anyone see any problems with the above code, ie is this a valid way of writing the REC statement?
- Can anyone suggest another way of writing this code?
Best regards
Mark Rodrigues

Just repostoing the logic as "Code"
*XDIM_MEMBERSET P_ACCT = CAPACITY_REV,CAPACITY_RATE,FINAL_VOLUME
*XDIM_MEMBERSET CATEGORY=FORECAST
*XDIM_MEMBERSET P_DATASRC=Input
*XDIM_MEMBERSET CONTRACT=0005000001_10
*XDIM_MEMBERSET TIME=2009.JUL
*WHEN P_ACCT
*IS CAPACITY_RATE
    *BEGIN
        REC(EXPRESSION=(%VALUE%P_ACCT.FINAL_VOLUME),
                                        CUSTOMER = CONTRACT.CUSTOMER,
                                        DESTINATION = CONTRACT.DESTINATION_ID,
                                        ENTITY = CONTRACT.HAUL_PC,
                                        MINE = CONTRACT.MINE_ID,
                                        P_ACCT = "CAPACITY_REV")
    *END
*ENDWHEN
*COMMIT

Script Logic - REC Statement

Hi,
Can we use dimension property value in REC statement?
*REC(EXPRESSION = %value%/[TIME].CURRENTMEMBER.PROPERTIES("ACCTHRS"),ACCT_PROJECT="FTE_DIRECT_BASE")
WHEN I PROCESS THE SCRIPT LOGIC I AM GETTING AN ERROR "INVALID LINE IN LOGIC SECTION: *REC........"
THANKS

Hi,
In this case, you can use LOOKUP. For instance,
*LOOKUP XXX
*DIM AAA:TIME=TIME.ACCTHRS
*ENDLOOKUP
*REC(EXPRESSION = %value%/LOOKUP(AAA),ACCT_PROJECT="FTE_DIRECT_BASE")
Hope this helps.
Regards,
YH Seo
====================================================================================================
Hi,
Can we use dimension property value in REC statement?
*REC(EXPRESSION = %value%/TIME.CURRENTMEMBER.PROPERTIES("ACCTHRS"),ACCT_PROJECT="FTE_DIRECT_BASE")
WHEN I PROCESS THE SCRIPT LOGIC I AM GETTING AN ERROR "INVALID LINE IN LOGIC SECTION: *REC........"
THANKS

Rounding up in script logic

Dear all,
I am using BPC 7.0 MS
I tried to perform rounding up in script logic using Round and a negative number, but it didn't work.
Any other suggestions?
Cheers,
Lip Chean

So in this case you might need to use division instead of multiplication, for example:
(int(28/100)+1)*100
In my previous example I was assuming that you might need to get rid of two decimals and round to the full currncy unit.
cheers,
Madis
Edited by: Madis Udam on Mar 17, 2010 9:30 PM
Edited by: Madis Udam on Mar 17, 2010 9:31 PM

Calling multiple script logics from a single package

Team- How do i call multiple script logics from a single DM package...?
I know its possible and have seen a prototype but cant recollect or find it on sdn...
Thanks for your time.
Vishal.

Hi,
You can create a master script logic which will include all the other script logics using the *INCLUDE command and call this master script through your DM package.
Another way is to have multiple tasks in the process chain which is calling a script logic. You can pass separate script logics to each of the tasks.
I would prefer the first option
Hope this helps.

Script Logic EDI

Hi!
Does anyone know if there is script logic (sap bpc) EDI?
Thankxx!!

HI,
I don't know what is EDI.
But SAP BPC has a script logic used to create calculation for aggreate members.
Regards
Sorin Radulescu

Script logic using Dimension.Property

Similar Messages

Maybe you are looking for