ADDITION USING SCRIPT LOGIC

Hi All,
Under 'INCOME' i have 3 accounts.
account1
account2
account3
i want to add the value of these 3 account then i want to multiply with 3
the result i want to display in "account4"
What is the required script logic for this?
Regards,
Phanikumar.

Hi Phani Kumar,
BPC 7.0 NW doesnt support GET, so you cannot have the script as
*WHEN ACCOUNT
*IS "ACCOUNT1"
   *REC(EXPRESSION=(%VALUE% + GET(ACCOUNT="ACCOUNT2") + GET(ACCOUNT="ACCOUNT3"),ACCOUNT="ACCOUNT4")
*ENDWHEN
Instead you can modify the script to
*WHEN ACCOUNT
*IS "ACCOUNT1","ACCOUNT2","ACCOUNT3"
   *REC(FACTOR = 3, ACCOUNT="ACCOUNT4")
*ENDWHEN
If you want to go with MDX, then you can use as suggested earlier
[ACCOUNT].[#account4]=([ACCOUNT].[account1]+[ACCOUNT].[account2]+[ACCOUNT].[account3])*3
Hope this helps.

Similar Messages

  • How to copy applications using script logic with conditions

    Hi,
    I have two copy data between application A to application B, but only i want to copy the March's Data of Application A. Dimensions are the same in both applications
    I'm going to use this script logic, ¿this script will work?
    *WHEN TIME
    *IS "2009.MAR"
    *DESTINATION_APP=B
    Thanks in advance
    Regards,
    Juan

    Hi all,
    Finally I solved the issue, the problem was that i haven't add this line in the script logic:
    TASK(Execute formulas,USER,%USER%)
    But now i need to pass in the script logic as an input: entity and time. Below is the code I prepare, it has no error but it doesn't work. ¿any idea?
    Thanks in advance
    Regards,
    Juan
    *SSIS PACKAGE *
    'DEBUG(ON)
    PROMPT(RADIOBUTTON,%CHECKLCK%,"Select whether to check work status settings when running logic.",1,{"Yes, check for work status settings before running logic","No, do not check work status settings"},{"1","0"})
    PROMPT(SELECTINPUT,,,"Please select entity and time to copy data from LegalAppNceu to LegalApp",%ENTITY_DIM%%TIME_DIM%)
    TASK(Execute formulas,USER,%USER%)
    TASK(Execute formulas,APPSET,%APPSET%)
    TASK(Execute formulas,APP,%APP%)
    TASK(Execute formulas,LOGICFILE,%APPPATH%..AdminApp%APP%CopyApplication.lgx)TASKTASK(Execute formulas,RUNMODE,1)
    TASK(Execute formulas,LOGICMODE,1)
    TASK(Execute formulas,CHECKLCK,%CHEKCLCK%)
    SCRIPTLOGIC
    *DESTINATION_APP=LEGALAPP
    *SKIP_DIM= COSTCENTER
    *WHEN ENTITY
    *IS "%ENTITY_DIM%"
    *WHEN TIME_DIM
    *IS "%TIME_DIM%"
    *REC(FACTOR=1)
    *ENDWHEN
    *ENDWHEN
    *COMMIT

  • Exclude records using script logic.

    I have created a script logic to exclude records but it does only exclude few records.
    Example:-
    *SELECT(%SHARED%,"[ID]","ENTITY","CLUSTER<>'SHARED_SERVICES' AND CLUSTER <>'CENTRAL_MANAGEMENT'")
    *XDIM_MEMBERSET ENTITY = %SHARED%
    Please advice which other logic I can use to exclude records.
    Thanks.

    Thanks but when I change it to OR statement it still does not exclude them.
    Please check the example provided.
    ID     EVDESCRIPTION     PARENTH1     CLUSTER
    7901     TOTAL TRANSACTIONAL BNKG     7910     CORPORATE
    4243     CORP SHARED SERV & NIS     7910     CORPORATE
    7920     NEDBANK CAPITAL                          7800     CAPITAL
    3064     NEDBANK WEALTH                          7800     WEALTH
    8037     CENTRAL MANAGEMENT                          7800     CENTRAL_MANAGEMENT
    3113     BALANCE SHEET MANAGEMENT     8037     CENTRAL_MANAGEMENT
    4236     CAPITAL CENTRE                          3113     CENTRAL_MANAGEMENT
    7455     GROUP ALCO                          3113     CENTRAL_MANAGEMENT
    1119     TREASURY FUNDING UNIT NB     3113     CENTRAL_MANAGEMENT
    1999     CORPORATE FUNDING UNIT NB     3113     CENTRAL_MANAGEMENT
    3505     TOTAL NBG CAPITAL MANAGEMENT     3113     CENTRAL_MANAGEMENT
    7479     IMPERIAL INCL ALCO CHARGE     4237     CENTRAL_MANAGEMENT
    6050     NEDBANK LTD ELIMINATIONS     7800     ELIMINIATIONS
    7937     SHARED SERVICES                          7800     SHARED_SERVICES
    7940     GROUP TECHNOLOGY                          7937     SHARED_SERVICES
    3247     GT NEDBANK INCL EX IBL                          7940     SHARED_SERVICES
    4109     SWISSCARD                           7940     SHARED_SERVICES
    7513     GRP TECH INIT D9095 NB                           7940     SHARED_SERVICES
    7792     GROUP TECH AC133 F VAL NB     7940     SHARED_SERVICES
    3400     TOTAL FINANCE                          7937     SHARED_SERVICES
    8154     FINANCE - SHARED SERVICES     3400     SHARED_SERVICES

  • 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 MEASURES dimension in a RUNALLOCATION in a script logic

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

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

  • How to use total elements in a script logic?

    Hi All,
    I am using BPC 7.0 MS. I need to create a calculation using script logic as follows:
    The application name is GYP and it is composed by the following dimensions:
    PL (Account type) in this dimension are the units
    Time
    Category
    Entity
    Product
    RptCurrency
    I would like to make a calculation like this:
    UNITS of any product (base element) and any entity (base element) for the BUDGET category and LC currency divided by UNITS of TotalEntity.
    Also, I would like to check before the calculation if UNITS have any value to proceed with that calculation.
    Best Regards,
    Luisana

    Hi Robert,
    Thank you for your reply.
    Let me explain better what i would like to do. I have an application called GYP, it is composed for the following dimensions:
    PL (Account type)
    Time
    Category
    Entity
    Product
    RptCurrency
    In the PL dimension i have an element called UNITS and another one called UNITSBYX. I would like to get a calculation like this:
    For the BUDGET category and LC currency.
    UNITSBYX = UNITS for each ENTITY / UNITS for ALL_ENTITIES
    Let's say I have three entities:
    Units for Entity1 = 50
    Units for Entity2 = 100
    Units for Entity3 = 300
    Units for All_Entities = 450
    The calculation should be like this:
    UNITSBYX = Units for Entity1 / Units for All_Entities
    UNITSBYX = 50 / 450
    UNITSBYX = 0.11
    UNITSBYX = Units for Entity2 / Units for All_Entities
    UNITSBYX = 100 / 450
    UNITSBYX = 0.22
    I hope you get my point.
    Kind regards,
    Luisana

  • Changing Work Status using data package or script logic

    Is it possible to set Work Status using Script logic, or an SSIS package.
    I know status is kept is an SQL table, is it possible to just update the locking table with a new record, or is there more to changing the work status.
    Thanks for you help

    Thanks for your reply. This would be a nice enhancement.
    Although the work status does help with the audit trail of who and what locks the data, doing it automatically will allow the system to automatically unlock the period when it is opened before auto-loading the current closing balances. It will need to be carefully used in order to maintain proper audit trail of the data. When done automatically, the system userid would be used in the lock table witha  timestamp.
    I am needing to know if there are anyother steps involved in locking data other than writing to the SQL lock table. Is usppose this is especailly relevant when locking a parent and pushing the status to the children.

  • Can we calculate difference of  dimension properties values in script logic

    HI
    I have 3 products, whose manufacturing process starting perod and end periods are different for three products. Now I want
    to distribute total  manufactuing cost to those periods only for each product.  how will write script logic  for this senario.
    My system is BPC nw7.5
    Mahi

    Hi,
    So, you want to find the difference between the dates and distribute the cost among them. I dont think this will be feasible using script logic. My suggestion would be use BADI. Script logic cannot do manipulation on the properties. BADI will be much easier. In addition to this, you need to think what should be the destination of the result. Every record is going to generate few records (depending on the number of months).
    Hope this helps.

  • Calculations in Script Logic

    Dear Experts,
    I am trying to do some calculations using script logic.
    Foe example: In account dimension I have three members A, B & C.
    Now i want to do A = B multiply C using script logic.
    I will insert data for B and C. The B, C should get multiply and insert in to A.

    hello experts,
    i am newbie to bpc & scriptlogic, i am, me too, trying to do some calculations using scriptlogic.
    i've created a dimension S_GOSTERGE with members SATISTUTARI, SAT_Fiyat, SAT_Miktar
    i want to calculate SATISTUTARI = SAT_Miktar * SAT_Fiyat
    so i've writed the script below.
    *XDIM_MEMBERSET S_GOSTERGE = SATISTUTARI
    *XDIM_MEMBERSET S_GOSTERGE = SAT_Fiyat
    *XDIM_MEMBERSET S_GOSTERGE = SAT_Miktar
    *WHEN S_GOSTERGE
    *IS SAT_Miktar
        *REC(FACTOR = GET(S_GOSTERGE ="SAT_Fiyat") , S_GOSTERGE = SATISTUTARI)
    *ENDWHEN
    *COMMIT
    when i click ''validate'' i get the error message : cannot find dimension ""SAT_FIYAT")"
    please, can you help me to solve this?
    thanks in advance.

  • 7.0NW: script logic to post data to another cube

    Hi,
    On the 7.0NW we have a FINANCE cube (8 dimensions) and a FINANCE_DETAIL (12 dimensions) cube. I was hoping that someone could advise on how to transport data using script logic from FINANCE_DETAIL to FINANCE, knwoing that the SQL logic for the MS-platform is no longer applicable (DESTINATION_APP statement) on the NW-platform.
    Thx&Rgrds
    Bjorn

    BPC7Nw supports ABAP development through script logic. You can use the keyword 'call custom logic' to execute the BADI that you developed. With SP01, you can also pass parameters to this BADI. Here are step by step instructions to do the same.
    https://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/20f4252d-98ca-2b10-e689-f85085ae2d12
    Regards
    Pravin

  • Dimension Formula versus Script Logic that runs on default

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

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

  • 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

  • How Acumulated Value in a script Logic

    Hello,
    We facing a problem here, that we cannot acumulated value using  script Logic.
    We need to calculated a account where we need the value to this account in the previous month
    Like That
                                JAN        FEB       MAR       APR        MAY
    ACCOUT
    A                          10           40          45         45            45
    B                           7            30          20         
    C                           3                        -15                  
    In this case we need to save the acumulated value to all months, until the end of the year, even if we dont input value in this months.
    Anyone facing this problem? 
    Best Regards

    You can't use a date display pattern on a text field, it has to be a date field.
    The only way around that is to use scripting to format the date and then put the date in a text field - I've done this using util.printd() (I think - going off the top of my head at the moment) and there's a way to do it with FormCalc too.
    Patterns work well once you get the hang of them. Display is how you want the data to look. Edit is the different ways you allow the data to be entered (multiple date, phone number patterns, etc.). Validate will validate that the Display pattern has succeeded. Data is the format to export.
    I haven't had a chance to look at your new file but if you use 2 date fields with patterns you would just need: dateField2.rawValue = dateField1.rawValue; with dateField2 having date.long{} as the display pattern. Come to think of it you could use Global binding and give the fields the same name and you wouldn't have to do any scripting.
    Radzmar has a good explanation of using multiple edit patterns for dates (English text is part way down): http://thelivecycle.blogspot.de/2011/10/date-patterns.html

  • Use of comments in script logic / BADI

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

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

  • How to use the current view in script logic - %DIMENSIONNAME_SET% not work

    Hello,
    I have the requirement to use the values from the current view in the script logic. User would like to use the members which were selected from the current view in the calculation.
    We are using SAP BPC 7.0 SP06
    I have prepared the following scrpit:
    *XDIM_MEMBERSET TIME=$YEARS001$.NA
    *XDIM_MEMBERSET ACCOUNT=BAS(PLVEH_EXP)
    *SELECT(%CBU%,ID,BUSINESSAREA,[ID]='%BUSINESSAREA_SET%'")
    *SELECT(%CIO%,ID,INTERNALORDER,[ID]='%INTERNALORDER_SET%'")
    *RUNALLOCATION
    *FACTOR=USING
    *DIM BUSINESSAREA WHAT=BANA;WHERE=%CBU%;USING=<<<
    *DIM INTERNALORDER WHAT=IONA;WHERE=%CIO%;USING=<<<
    *DIM INDICATORS WHAT=INVEHPRI;WHERE=INPXQ;USING=INVEHQUA
    *ENDALLOCATION
    I have read in the sdn that it is possible to get the current values using %DIMENSIONNAME_SET% variable and use it but it returns all the members that were selected in the datapackage.
    I would like to know if there is any special consideration regarging the use of variable or if there is another way to solve it.
    Thanks in advance.

    Hi,
    If you want the code to be executed for the current view selected, you can place the code in Default logic which executes the logic for what ever current view values you send the data through Input schedule.
    The key word you have mentined is for script running through Data Manager which gets the value selected through user promt.
    Hope this helps,
    Regards,
    G.Vijaya Kumar.

Maybe you are looking for