RUN ALLOCATION

Hi All,
*RUNALLOCATION
*FACTOR=USING/100
*DIM ACCOUNT  WHAT=570927; WHERE=570999; USING=CRITERIA1
*DIM ENTITY WHAT=31400; WHERE=31300; USING<>31300
*ENDALLOCATION
This allocation works fine.But I would like to execute this for all accounts(source) in entity 31400,
so can i use <ALL> here,i mean
*RUNALLOCATION
*FACTOR=USING/100
*DIM ACCOUNT  WHAT=<ALL>; WHERE=570999; USING=CRITERIA1
*DIM ENTITY WHAT=31400; WHERE=31300; USING<>31300
*ENDALLOCATION
is the above code is not working, is it correct? or give me an alternate solution for this.
Thanks in advance

Your syntax of
*DIM ENTITY WHAT=31400; WHERE=31300; USING31300
needs an equal sign in the using, as follows:
*DIM ENTITY WHAT=31400; WHERE=31300; USING=31300
or
*DIM ENTITY WHAT=31400; WHERE=31300; USING=<<<
Also note, for the account=BAS(Something), while this works, it is a bit slower at logic execution time than using a member property to flag the set of accounts -- especially if you have an account dimension with many levels. The logic will recursively scan through each level, until it gets to all the base members. (Check the debug log closely to see this.) If you use a member property, it will find all the members in a single pass. There's a trade-off here between dim maintenace complexity and performance, but you'll want to consider both options.

Similar Messages

  • Using a filter in RUN Allocation

    Does anyone know how to use a filter in the WHAT, WHERE clauses in RUN Allocation?
    I need to use something like WHERE=%STAT_ACCTS% AND [GROUP]<>"PL" but it dosen't work.
    On the contrary, is there a way to get the basemembers of a parent ID based on a filter?
    I could also use something like *XDIM_MEMBERSET ACCOUNT =BAS(STACCTS) AND [GROUP]<>"PL" but XDIM_MEMBERSET does not support conditions.
    Thanks in advance for help!

    Thanks for the replies... but my problem is still not solved... if either of the following could work that would solve this:
    a) have my xdim_memberset set to only those products which meet the condition [LEVEL]="seg" and are the bas members of the product i pick from the hierarchy. For this i would need a select statement which works like:
    *SELECT(%SKU%,[ID],"PRODUCT","[PARENTH1]=%PRODUCT_SET% AND [LEVEL]='SEG' ")
    OR
    b) a way to create a variable using xdim_filter that i can use anywhere else in my code
    c) put a condition in the WHERE clause of the allocation script so i could use something like:
    DIM PRODUCT WHAT=something; WHERE=BAS(%PRODUCT_SET%) AND [LEVEL]="SEG";
    but none of the above options are working

  • Run allocation based on condition matched

    Hi SAP friends,
    I need to run allocation based on condition matched, is it possible with IIF or another statement?
    the logical view is below (syntax is wrong):
    *RUNALLOCATION
    IIF(BAS(ACCOUNT_01)<>0,
    *FACTOR = USING/TOTAL
    *DIM ACCOUNT WHAT = ACCOUNT_52; WHERE=BAS(ACCOUNT_01); Using=BAS(ACCOUNT_01); TOTAL=BAS(ACCOUNT_01)
    *FACTOR = 1
    *DIM ACCOUNT WHAT = ACCOUNT_52; WHERE=ACCOUNT_10)
    *ENDALLOCATION
    thanks a lot.

    Hi Vadim,
    I am somehow getting doubled values, I have read some articles where when and REC can double values, but my case seems to be something different, do you have an idea?
    the code is below:
    *FOR %MONTH_PLUS% = 0,1,2,3,4,5,6,7,8,9,10,11,12
    *XDIM_MEMBERSET RPTCURRENCY     = LC
    *XDIM_MEMBERSET ENTRYTYPE          = INPUT
    *XDIM_MEMBERSET CLIENTSEG           = NA_CLS, GCIPZ
    *XDIM_MEMBERSET CUSTSEG              = C_INP, P_INP
    *XDIM_MEMBERSET ACCIDENTYEAR    = CAY
    *XDIM_MEMBERSET DISTCH                  = BAS(GI_TOTAL),ALL_OTHER
    *XDIM_MEMBERSET LOB                       = BAS(LOB_GI)
    *XDIM_MEMBERSET PARTNER_RU        = NA_PU
    *XDIM_MEMBERSET ZVIEW                   = MV_PROD,MV_REC
    *XDIM_MEMBERSET TIME                      = TMVL(%MONTH_PLUS%,%TIME_SET%)
    *XDIM_MEMBERSET VERSION               = %VERSION_SET%
    *XDIM_MEMBERSET RU                         = %RU_SET%
    *XDIM_MEMBERSET INSTYPE                = DIR_OWN
    *WHEN INSTYPE
    *IS DIR_OWN
    *REC(EXPRESSION=(([ACCOUNT].[IFRS_69011330_01],[VERSION].[A01],[TIME].[TMVL(%MONTH_PLUS%,$LAST_YEAR$)])==0) ? [ACCOUNT].[STAT_LOSS_52]:[ACCOUNT].[IFRS_69011330_10], ACCOUNT=IFRS_69011330_10)
    *ENDWHEN
    *NEXT
    many thanks, tomas.

  • BPC Run Allocation Logic

    Dear All,
    I am new in BPC world so i want ur help in solving one error
    when running allocation logic, it is not accepting more than 1 member in the denominator
    the factor i am using is 1/using
    can u pls help on this
    thanks.

    Can you please post the logic and the error you are getting?
    Thanks,
    John

  • Run allocation error

    Dear expert,
    I have run Allocation successfully but nothing saved in database. source script like this:
    *XDIM_MEMBERSET TIME=2013.01,2014.01
    *XDIM_MEMBERSET ACCOUNT = BS122
    *XDIM_MEMBERSET CATEGORY=Plan,Actual
    *XDIM_MEMBERSET ENTITY =$SOURCE$,$TARGET$
    *WHEN ENTITY
    *IS "Africa"
    *REC(EXPRESSION=$ASARENT$,TIME=2014.01,CATEGORY=Plan)
    *ENDWHEN
    *COMMIT
    *RUNALLOCATION
    *FACTOR=USING/TOTAL
    *DIM ACCOUNT  WHAT=BS122;                WHERE=<<<;               USING=<<<;         TOTAL=<<<
    *DIM ENTITY    WHAT=$SOURCE$;  WHERE=BAS($TARGET$);  USING=<<<;          TOTAL=<<<
    *DIM TIME     WHAT=>>>;                    WHERE=2014.01;      USING=2013.01;  TOTAL=<<<
    *DIM CATEGORY     WHAT=>>>;                   WHERE=Plan;      USING=Actual;  TOTAL=<<<
    *ENDALLOCATION
    *WHEN ENTITY
    *IS "Africa"
    *REC(EXPRESSION=0,TIME=2014.01,CATEGORY=Plan)
    *ENDWHEN
    *COMMIT
    Please show what I am wrong and how to correct it.
    thanks so much
    HUNGTH

    I have edited my script base on your comment like this:
    *XDIM_MEMBERSET TIME=2014.01
    *XDIM_MEMBERSET ACCOUNT=BS122
    *XDIM_MEMBERSET CATEGORY=Plan
    *XDIM_MEMBERSET ENTITY =$SOURCE$
    *WHEN_REF_DATA = MASTER_DATA
    *WHEN ENTITY
    *IS *
           *REC(EXPRESSION=$ASARENT$)
    *ENDWHEN
    *RUNALLOCATION
    *FACTOR=USING/TOTAL
    *DIM ACCOUNT  WHAT=BS122;                WHERE=<<<;               USING=<<<;         TOTAL=<<<
    *DIM ENTITY    WHAT=$SOURCE$;  WHERE=BAS($TARGET$);  USING=<<<;          TOTAL=<<<
    *DIM TIME     WHAT=>>>;                    WHERE=2014.01;      USING=2013.01;  TOTAL=<<<
    *DIM CATEGORY     WHAT=>>>;                   WHERE=Plan;      USING=Actual;  TOTAL=<<<
    *ENDALLOCATION
    *WHEN ENTITY
    *IS "ASA"
    *REC(EXPRESSION=0,TIME=2014.01,CATEGORY=Plan)
    *ENDWHEN
    But the same result

  • Error while running allocation: Driver stored in Rate Application

    Hi,
    I have the allocation driver stored in the Rate application.
    I have a custom application which has different dimensions than the Rate application. In the allocation logic I pick up the driver from the Rate Application -
    e.g.      *APP WHAT=MYPLANNING;         WHERE=MYPLANNING;           USING=RATE
    When I run the allocation I get the following error. Any inputs would be greatly appreciated.
    thx
    Sumangal
    ====================
    ExecuteBaseLogic::Incorrect syntax near ','. in:
    select [CATEGORY],[INPUTCURRENCY],[RATE],[RATEENTITY],[TIMEID],SIGNEDDATA
    into #941281
    from tblFactRATE
    where [RATE] = 'ALLOCFACTOR' and [TIMEID] in ('20050100','20050200','20050300','20050400','20050500','20050600','20050700','20050800','20050900','20051000','20051100','20051200')
    insert into #941281 ([CATEGORY],[INPUTCURRENCY],[RATE],[RATEENTITY],[TIMEID],SIGNEDDATA)
    select [CATEGORY],[INPUTCURRENCY],[RATE],[RATEENTITY],[TIMEID],SIGNEDDATA
    from tblFactWBRATE
    where [RATE] = 'ALLOCFACTOR' and [TIMEID] in ('20050100','20050200','20050300','20050400','20050500','20050600','20050700','20050800','20050900','20051000','20051100','20051200') and SOURCE = 0
    insert into #941281 ([CATEGORY],[INPUTCURRENCY],[RATE],[RATEENTITY],[TIMEID],SIGNEDDATA)
    select [CATEGORY],[INPUTCURRENCY],[RATE],[RATEENTITY],[TIMEID],SIGNEDDATA
    from tblFac2RATE
    where [RATE] = 'ALLOCFACTOR' and [TIMEID] in ('20050100','20050200','20050300','20050400','20050500','20050600','20050700','20050800','20050900','20051000','20051100','20051200')
    select ,sum(SIGNEDDATA) as amtTOTAL
    into #TOTAL_941281 from #941281 a
    group by
    drop table #941281
    ======================

    Hi ATW-
    Please repost this question in the forum for BPC, version for Microsoft:
    [SAP Planning and Consolidation, version for the Microsoft platform|SAP Planning and Consolidation, version for the Microsoft platform;
    Regards,
    Sheidon

  • Error when running allocation logic

    I am running the following allocation logic and get the following error:
    *RUNALLOCATION
    *FACTOR=USING/TOTAL
    *DIM P_ACCT WHAT=CE0004010; WHERE=CE0004020; USING=CE0004030; TOTAL=<<<
    *DIM ENTITY WHAT=A1000; WHERE=<<<; USING=<<<; TOTAL=<<<
    *DIM TIME WHAT=2009.JAN; WHERE=>>>; USING=BAS(2009.TOTAL); TOTAL=<<<
    *ENDALLOCATION
    UJP_RULE_EXCEPTION:Missing [] on property name: WHAT=CE0004010. I get this error when executing the script using the program "UJK_SCRIPT_LOGIC_TESTER". I also get a similar error when running it via the data manager package.
    Any thoughts on why this error is happening?

    Hi Sanjay,
    I think you are using formula property for any of the dimension member used in the Allocation logic.
    FYI Allocation will not work fine for the dimension members which is calculated using the formula written in the formula Property.
    There is no problem with your script it looks fine.
    Hope this might help you.
    Regards,
    G.Vijaya Kumar

  • Run Allocation Package - Execute formulasError- updated

    Hi Experts,
    I have the following allocation script logic:
    *RUNALLOCATION
    *FACTOR=USING/TOTAL
    *DIM COPAACCOUNT   WHAT=[EXPORT_ALLOC_BASIS]='Stat Cases';  WHERE=<<<;      USING=COPAVVSCA;   TOTAL=<<<;
    *DIM PRODUCT       WHERE=[CATEGORY]='%PRODUCT_SET%';   USING=<<<;   TOTAL=<<<;
    *DIM CUSTOMER      WHAT=ALC_CG_01;  WHERE=[SHPTO_LEVEL]='ALC_CG_01';   USING=<<<;   TOTAL=<<<;
    *DIM DATASRC       WHAT=11_INPUT;   WHERE=11_ALLOC;   USING=11_INPUT;   TOTAL=<<<;
    *ENDALLOCATION
    *COMMIT
    Now on my package I put the following input:
    Version: Actual
    Entity: EntityA
    Time: 2009.MAR
    Product: PROD_CAT_001,PROD_CAT_002,PROD_CAT_003,PROD_CAT_004,PROD_CAT_005
    After running the package, I get the following error:
    Execute formulasError
    Unclosed quotation mark after the character string 'PROD_CAT_001'. in:
    select [ID] from mbrPRODUCT where [CATEGORY]='PROD_CAT_001
    What could be causing this error??
    Notes:
    1. I don't encounter this error when I only select 1 product member.
    2. Actually, there are 500 product members that needs to be allocated. I let the users input the product members for allocation so that they would only input those with values.
    3. I tried using a FOR/NEXT which would read all the 500 product members, but my logic hangs when I validate and save it.
    Update:
    I see now the problem, my logic is processing all of my selection in the DM as one:
    WHERE=[CATEGORY]='PROD_CAT_001,PROD_CAT_002,PROD_CAT_003,PROD_CAT_004,PROD_CAT_005'
    instead of processing them one at a time. Is there a way to do so? I've tried using FOR/NEXT but it's making my logic hang when I validate and save it since I have to select 500 product members. Allocation logic is repeated 500 times. Is there a way to calculate each member without using FOR/NEXT?
    Hope you could help me,
    Marvin
    Edited by: Marvin Santos on May 26, 2010 4:43 PM
    Edited by: Marvin Santos on May 26, 2010 4:49 PM

    Hi Raman,
    Thanks for your prompt response.
    But I am still facing a couple of problems:
    1. First ASIARENT.INPUT is not a dimension member but a member, so I am not sure how to assign it to Expression. Could you please throw some light on it.
    2. Second, I haven't changed the ASIARENT.INPUT part, so may be the problem is because of this, but I am getting an error when I am running the DM Pacage. In the formula logic, its says - Missing file. So, please suggest if the package code is correct, esp. when I am calling the script logic.
    I would highly appreciate your help guys.
    Thanks
    Rahul

  • How to Run Allocation in Outlooksoft Everest 4.2 or SAP BPC 5.1

    Hello,
    Currently we use OS Everest 4.2 and we are in the Process of installing SAP BPC 5.1. We haven't used OS or BPC for allocation. I am trying to find a document that helps us guide through the process of creating a Allocation rules / formulas.
    We found a Allocation Manual in Old Outlooksoft Support site and tried using it but it doesn't work or may be I am doing something wrong.
    This is a Sample Allocation formula that we were just trying to see if it works.
    *RUNALLOCATION
    *FACTOR=USING/100
    *DIM ACCOUNTS  WHAT=AMOUNT; WHERE=<<<; USING = COUNT
    *DIM ENTITY  WHAT=EAST; WHERE=EAST;USING<>EAST
    *ENDALLOCATION
    *COMMIT
    It gives us  an error shown below when validating the Logic: shown below
    Update Excel file to Server
    Getting formulas
    Creating LGF file
    Validating logic
    *ValidateFormula: Invalid instruction: RUNALLOCATION
    Error occured
    If you have any documents that will show the step by step instructions on how ALLOCATION works and how to implement, please send it. I didn't find any thing in the helpfile. Its very difficult to figure out without any documentation.
    I would appreciate any help.. Thanks a lot !!!

    First of all, I am feeling for you. It is very hard situation that thousand of users has own local "MyDocument" folder in local PC.
    Folder structure between 5.1 and 4.2 is almost identical. Only difference is name of folder in My Documents. It was "Everest" in 4.2 but "OutlookSoft" in 5.1.
    And there is couple more differences but it is going to recover automatically. Something like dimension cache, appinfo archive.
    So, I like to suggest rename current "Everest" to "OutlookSoft" in My Documents. And do some test. I think biggest issue of here is report functionality between two versions.
    At least, simple rename procedure is much easier than copy all reports to correct path.
    I'm praying for your luck.

  • Run Allocation for integer values

    Hi experts,
    I am runnig an allocation for a HeadCount Account (all integer values) and I would like that the result of the allocation were also integer values, using a round instruction for example.
    Could I define in Account Dimension that Signed data must be integer? or using rounding logic?
    Regards

    Correct me if i am wrong:
    E.g.1
    *REC(EXPRESSION=int(%value%))
    E.g.2
    *RUNALLOCATION
    *FACTOR=USING
    *DIM ACCOUNTB          WHAT=BR030;                           WHERE=<<<;                                               USING=PR01;
    *DIM TIMEB                  WHAT=%YEAR%.TOTAL_D;       WHERE=[PARENTH1]= '%YEAR%.TOTAL';    USING=<<<;
    *ENDALLOCATION
    *COMMIT
    How could apply Int statement in a RUNALLOCATION?

  • RUN ALLOCATION PROBLEM

    hiiii
    i am working on runallocation concept ,when i exceute the package view status is showing empty not displaying anything .what might be the problem..?
    thanks in advance
    regards
    praveen

    Since you did not provide any information about which release and support package of BPC you are using I would have to guess and say you need to apply SAP note 1456024 which is included part of BPC 7.0 NW SP08.
    If that note is not applicable to your system, please come back with more details on the release information.  Also, does any packages show a status or is the issue only with the run_allocation package?
    Can you see the status files from UJFS or from SLG1?
    Best regards,
    [Jeffrey Holdeman|http://wiki.sdn.sap.com/wiki/display/profile/Jeffrey+Holdeman]
    SAP Labs, LLC
    BusinessObjects Division
    Americas Applications Regional Implementation Group (RIG)

  • Restricting the records in RUN ALLOCATION

    Hi ALL,
    *FOR %DESTIN%=32000,31400
       *RUNALLOCATION
       *FACTOR=USING/100
        *DIM ACCOUNT  WHAT=<ALL>; WHERE=<ALL>; USING=CRITERIA1
        *DIM ENTITY WHAT=31300; WHERE=%DESTIN%; USING<>31300
       *ENDALLOCATION
    *NEXT
    The above code fetches amount of all Accounts of Entity 31300 and adds to
    all accounts of destination Entity 32000,31400 according to the criteria1.
    Tha above code is working fine.Now i want to restrict the <ALL>in the where condition.
    say 31300 has only 1 account 'A'.,i want the amount of 'A' tobe calculated according to
    criteria1 and move to the destination entities 32000,31400.Finally the entities 32000 and
    31400 must have the 'A'(calulated according to criteria),but not all records of destination Entities
    getting modified.How can i restrict the <all> of where clause???

    Manasa,
    I may be way oversimplifying this, but you can use properties to restrict the where or simply specify the account if it is just a single account.
    Example:  GROUP is an account property and "A" is the property value.  Any account with that value will get applied.
    *FOR %DESTIN%=32000,31400
    *RUNALLOCATION
    *FACTOR=USING/100
    *DIM ACCOUNT WHAT=[GROUP]="A"; WHERE=<<<; USING=CRITERIA1
    *DIM ENTITY WHAT=31300; WHERE=%DESTIN%; USING31300
    *ENDALLOCATION
    *NEXT

  • For Next loop in allocations

    Request help in writing a allocation logic code.
    The current runs for 2600 Projects and 12000 customers. This causes memory issue and the code is aborted when run.
    Please suggest if this code can be run in a For/Next loop for each project..
    *XDIM_MEMBERSET CATEGORY = %CATEGORY_SET%
    *XDIM_MEMBERSET TIME = %TIME_SET%
    *WHEN ACCOUNT
    *IS "A1100001"
    *REC(EXPRESSION = ([ACCOUNT].[A1100001])*((%VALUE%)),ACCOUNT = "A3100001")
    *ENDWHEN
    *XDIM_MEMBERSET TIME = %TIME_SET%
    *XDIM_MEMBERSET ACCOUNT = BAS(MET-SAL.3.1)
    *XDIM_MEMBERSET P_PROJECT = BAS(AllProjects)
    *XDIM_ADDMEMBERSET P_PROJECT = NO_PROJECT
    *XDIM_MEMBERSET P_DEPARTMENT = ESG_Input
    *XDIM_MEMBERSET P_ENTITY = TTEU_INP
    *XDIM_MEMBERSET P_CUSTOMER = No_Customer
    *XDIM_ADDMEMBERSET P_CUSTOMER = BAS(AllCustomers)
    *XDIM_MEMBERSET P_ANALYSIS = BAS(AllAnalysis)
    *XDIM_ADDMEMBERSET P_ANALYSIS = NO_ANALYSIS
    *RUNALLOCATION
    *FACTOR = 1
    *DIM ACCOUNT WHAT = BAS(MET-SAL.3.1) ; WHERE = <<<;USING = <<<;TOTAL = <<<
    *DIM P_PROJECT WHAT = NO_PROJECT ;WHERE = <<< ;USING = <<<;TOTAL = <<< 
    *DIM P_DEPARTMENT WHAT = ESG_Input ;WHERE = <<< ;USING = <<<;TOTAL = <<< 
    *DIM P_ENTITY WHAT = TTEU_INP ;WHERE = <<< ;USING = <<<;TOTAL = <<< 
    *DIM P_ANALYSIS WHAT = NO_ANALYSIS ;WHERE = BAS(AllAnalysis) ;USING = <<<;TOTAL = <<< 
    *DIM P_CUSTOMER WHAT = No_Customer ;WHERE = BAS(AllCustomers) ;USING = <<<;TOTAL = <<<
    *ENDALLOCATION
    next

    I realized that while checking and have removed the section for recording expression.. and now only focusing to correct the Allocation logic. Based on your advice I have added the FOR/NEXT as below.
    The code is now only running for EDCTM-0007 but fails to generate any records for EDCTM-0014.
    *XDIM_MEMBERSET CATEGORY = %CATEGORY_SET%
    *XDIM_MEMBERSET TIME = %TIME_SET%
    *XDIM_MEMBERSET ACCOUNT AS %SAL% = BAS(MET-SAL.3.1)
    //*XDIM_MEMBERSET P_PROJECT = BAS(AllProjects)
    *XDIM_MEMBERSET P_PROJECT AS %PRJ% = EDCTM-0007, EDCTM-0014
    *XDIM_ADDMEMBERSET P_PROJECT = NO_PROJECT
    *XDIM_MEMBERSET P_DEPARTMENT = BAS(AllDepartments)
    *XDIM_MEMBERSET P_ENTITY = BAS(AllEntities)
    *XDIM_MEMBERSET P_CUSTOMER = BAS(AllCustomers)
    *XDIM_MEMBERSET P_ANALYSIS = BAS(AllAnalysis)
    *XDIM_MEMBERSET RPTCURRENCY = INR, CAD, EUR, GBP, KRW, MXN, SGD, THB, USD
    *FOR %PRJ% = EDCTM-0007, EDCTM-0014
    *RUNALLOCATION
    *FACTOR = 1
    *DIM ACCOUNT WHAT = %SAL%; WHERE = <<<; USING = <<<; TOTAL = <<<
    *DIM P_DEPARTMENT WHAT = ED_Input; WHERE = ED16; USING = <<<; TOTAL = <<<
    *DIM P_ENTITY WHAT = PUN_C; WHERE = <<<; USING = <<<; TOTAL = <<<
    *DIM P_CUSTOMER WHAT = No_Customer; WHERE = C100700; USING = <<<; TOTAL = <<<
    *DIM P_PROJECT WHAT = NO_PROJECT; WHERE = %PRJ%; USING = <<<; TOTAL = <<<
    *DIM P_ANALYSIS WHAT = NO_ANALYSIS; WHERE = TM_S; USING = <<<; TOTAL = <<<
    *ENDALLOCATION
    *COMMIT
    *NEXT
    log..
       FILE:\ROOT\WEBFOLDERS\ENVIRONMENTSHELL1\ADMINAPP\Planning_TTL\CP_RAVINNINE.LGF
    USER:RAVINDRA.S
    APPSET:ENVIRONMENTSHELL1
    APPLICATION:Planning_TTL
    FACTOR:1
    ALLOCATION DATA REGION:
    CATEGORY:Budget,
    P_PROJECT:NO_PROJECT,
    P_DEPARTMENT:Admin_Entity,Admin_Group,BRT_Entity,CEO_Entity,CEO_Group,COO_Entity,COO_Group,CSR_Entity,CSR_Group,ED01,ED02,ED03,ED04,ED05,ED06,ED07,ED08,ED09,ED10,ED11,ED12,ED13,ED14,ED15,ED16,ED_Input,ESG01,ESG02,ESG03,ESG04,ESG05,ESG06,ESG07,ESG08,ESG09,ESG10,ESG_Input,Finance_Entity,Finance_Group,GDO_Entity,HR_Entity,HR_Group,IT_Ent_Apps_Entity,IT_Ent_Apps_Group,IT_Ops_Infra_Entity,IT_Ops_Infra_Group,Legal_Entity,Legal_Group,Mktg_Entity,Mktg_Group,NO_DEPT,OSM_Entity,OSM_Group,PL01,PL02,PL03,PL04,PL05,PL06,PL07,PL08,PL09,PLM_P_Input,PLM_P_Services_Input,PLM_S_Input,PP01,PP02,PP03,PP04,PP05,Products_Autodesk,Products_Dassault,Products_IBM,Products_IKS,Products_MSC,Products_Others,Products_UGS,Quality_Entity,Quality_Group,VP01,VPD01,VPD_Input,
    P_ENTITY:BLO_C,BLO_Input,BLO_NC,BLR_C,BLR_Input,BLR_NC,BOM_C,BOM_Input,BOM_NC,BRG_C,BRG_Input,BRG_NC,BRZ_C,BRZ_Input,BRZ_NC,CAN,DEL_C,DEL_Input,DEL_NC,GER,GIP,HNJ_C,HNJ_Input,HNJ_NC,JSE_C,JSE_Input,JSE_NC,JSR_C,JSR_Input,JSR_NC,LKQ_C,LKQ_Input,LKQ_NC,MEX,NLD,PNQ_C,PNQ_Input,PNQ_NC,PUD_C,PUD_Input,PUD_NC,PUN_C,PUN_Input,PUN_NC,SAS,SIG,SKR,THD,THE,TTCN_INP,TTEU_INP,TTL_INP,TTMX_INP,TTPL_INP,TTTH_INP,TTUS_INP,UKG_Input,UKG_J,UKG_N,USA,
    P_CUSTOMER:C000001,C000002,C000003,C000004,C000005,C000006,C000007,C000008,C000009,C000010,C000011,C000012,C000013,C000014,C000015,C000016,C000017,C000018,C000019,C000020,C000021,C000022,C000023,C000024,C000025,C000026,C000027,C000028,C000029,C000030,C000031,C000032,C000033,C000034,C000035,C000036,C000037,C000038,C000039,C000040,C000041,C000042,C000043,C000044,C000045,C000046,C000047,C000048,C000049,C000050,C000051,C000052,C000053,C000054,C000055,C000056,C000057,C000058,C000059,C000060,C000061,C000062,C000063,C000064,C000065,C000066,C000067,C000068,C000069,C000070,C000071,C000072,C000073,C000074,C000075,C000076,C000077,C000078,C000079,C000080,C000081,C000082,C000083,C000084,C000085,C000086,C000087,C000088,C000089,C000090,C000091,C000092,C000093,C000094,C000095,C000096,C000097,C000098,C000099,C000100,C000101,C000102,C000103,C000104,C000105,C000106,C000107,C000108,C000109,C000110,C000111,C000112,C000113,C000114,C000115,C000116,C000117,C000118,C000119,C000120,C000121,C000122,C000123,C000124,C000125,C000126,C000127,C000128,C000129,C000130,C000131,C000132,C000133,C000134,C000135,C000136,C000137,C000138,C000139,C000140,C000141,C000142,C000143,C000144,C000145,C000146,C000147,C000148,C000149,C000150,C000151,C000152,C000153,C000154,C000155,C000156,C000157,C000158,C000159,C000160,C000161,C000162,C000163,C000164,C000165,C000166,C000167,C000168,C000169,C000170,C000171,C000172,C000173,C000174,C000175,C000176,C000177,C000178,C000179,C000180,C000181,C000182,C000183,C000184,C000185,C000186,C000187,C000188,C000189,C000190,C000191,C000192,C000193,C000194,C000195,C000196,C000197,C000198,C000199,C000200,C000201,C000202,C000203,C000204,C000205,C000206,C000207,C000208,C000209,C000210,C000211,C000212,C000213,C000214,C000215,C000216,C000217,C000218,C000219,C000220,C000221,C000222,C000223,C000224,C000225,C000226,C000227,C000228,C000229,C000230,C000231,C000232,C000233,C000234,C000235,C000236,C000237,C000238,C000239,C000240,C000241,C000242,C000243,C000244,C000245,C000246,C000247,C000248,C000249,C000250,C000251,C000252,C000253,C000254,C0002
    P_ANALYSIS:FB_M,FB_S,NO_ANALYSIS,TM_M,TM_S,
    RPTCURRENCY:CAD,EUR,GBP,INR,KRW,MXN,SGD,THB,USD,
    ACCOUNT:WHAT:MET-SAL.1.1,MET-SAL.5.1, MET-SAL.1.2,MET-SAL.5.2, MET-SAL.1.3,MET-SAL.5.3, MET-SAL.1.4,MET-SAL.5.4, MET-SAL.1.5,MET-SAL.5.5, MET-SAL.1.6,MET-SAL.5.6, MET-SAL.1.7,MET-SAL.5.7, MET-SAL.1.8,MET-SAL.5.8,WHERE:<<<,USING:<<<,TOTAL:<<<
    P_DEPARTMENT:WHAT:ED_Input,WHERE:ED16,USING:<<<,TOTAL:<<<
    P_ENTITY:WHAT:PUN_C,WHERE:<<<,USING:<<<,TOTAL:<<<
    P_CUSTOMER:WHAT:No_Customer,WHERE:C100700,USING:<<<,TOTAL:<<<
    P_PROJECT:WHAT:NO_PROJECT,WHERE:EDCTM-0007,USING:<<<,TOTAL:<<<
    P_ANALYSIS:WHAT:NO_ANALYSIS,WHERE:TM_S,USING:<<<,TOTAL:<<<
    --Read WHAT region
    [P_DEPARTMENT] =ED_Input
    [P_CUSTOMER] =No_Customer
    [P_PROJECT] =NO_PROJECT
    [P_ANALYSIS] =NO_ANALYSIS
    [CATEGORY] =Budget
    [RPTCURRENCY] =CAD,EUR,GBP,INR,KRW
    --Time to load WHAT :0.2066 second(s).
    WHAT data:1680 records.
    --Apply factor
    WHERE=WHAT *1
    --Time to apply factor :0.003074 second(s).
    --Read destination and calculate difference
    [P_DEPARTMENT] =ED16
    [P_CUSTOMER] =C100700
    [P_PROJECT] =EDCTM-0007
    [P_ANALYSIS] =TM_S
    [CATEGORY] =Budget
    [RPTCURRENCY] =CAD,EUR,GBP,INR,KRW
    --Time to read destination and calculate difference :0.14611 second(s).
    --Records succeeded to write back :1680
    --Records failed to write back
    --Time to run Allocation :0.390015 second(s).
    FACTOR:1
    ALLOCATION DATA REGION:
    CATEGORY:Budget,
    ACCOUNT:WHAT:MET-SAL.1.1,MET-SAL.5.1, MET-SAL.1.2,MET-SAL.5.2, MET-SAL.1.3,MET-SAL.5.3, MET-SAL.1.4,MET-SAL.5.4, MET-SAL.1.5,MET-SAL.5.5, MET-SAL.1.6,MET-SAL.5.6, MET-SAL.1.7,MET-SAL.5.7, MET-SAL.1.8,MET-SAL.5.8,WHERE:<<<,USING:<<<,TOTAL:<<<
    P_DEPARTMENT:WHAT:ED_Input,WHERE:ED16,USING:<<<,TOTAL:<<<
    P_ENTITY:WHAT:PUN_C,WHERE:<<<,USING:<<<,TOTAL:<<<
    P_CUSTOMER:WHAT:No_Customer,WHERE:C100700,USING:<<<,TOTAL:<<<
    P_PROJECT:WHAT:NO_PROJECT,WHERE:EDCTM-0014,USING:<<<,TOTAL:<<<
    P_ANALYSIS:WHAT:NO_ANALYSIS,WHERE:TM_S,USING:<<<,TOTAL:<<<
    "LC" has been added as default currency in allocation.
    --Read WHAT region
    [P_DEPARTMENT] =ED_Input
    [P_CUSTOMER] =No_Customer
    [P_PROJECT] =NO_PROJECT
    [P_ANALYSIS] =NO_ANALYSIS
    [CATEGORY] =Budget
    [ACCOUNT] =MET-SAL.1.1,MET-SAL.1.2,MET-SAL.1.3,MET-SAL.1.4,MET-SAL.1.5
    --Time to load WHAT :0.060259 second(s).
    WHAT data:0 records.
    --Apply factor
    WHERE=WHAT *1
    --Time to apply factor :0.000028 second(s).
    --Read destination and calculate difference
    [P_DEPARTMENT] =ED16
    [P_CUSTOMER] =C100700
    [P_PROJECT] =EDCTM-0014
    [P_ANALYSIS] =TM_S
    [CATEGORY] =Budget
    [ACCOUNT] =MET-SAL.1.1,MET-SAL.1.2,MET-SAL.1.3,MET-SAL.1.4,MET-SAL.1.5
    --Time to read destination and calculate difference :0.05125 second(s).
    --Records succeeded to write back
    regards, Prashant

  • Allocation Question -- Selecting Non-zero Dimension Members?

    Hi experts,
    (BPC 7.5 NW)  During an Allocation process, if you have a dimension, such as COSTCENTER for which only some members have data (in my case, about 400 of 700), which is not the driver dimension and you'd like to have the Allocation write back to those same members, while leaving the blank ones blank, is there some special process?
    In this example, you can see it selecting the CC's which are <> NO_COSTCENTER, but USING the Allocation rate, which as a stat account is stored in NO_COSTCENTER.
    So, it all works, except that the logic function writes a percentage to all three CC's specified in the *XDIM_MEMBERSET, even if there were initially values in only one or two.  Is there any way to have it write only to the ones that were initially populated/non-zero?
    ===================================================================================
    *XDIM_MEMBERSET ACCOUNTGL=A54442000,A54443000,A59989000,ALLOC_0702
    *XDIM_MEMBERSET COSTCENTER=CC01000,CC01004,CC01027,NO_COSTCENTER
    *XDIM_MEMBERSET CATEGORY=ACTUAL
    *XDIM_MEMBERSET CO_CODE=C001
    *XDIM_MEMBERSET TIME=2007.APR
    *RUNALLOCATION
    *FACTOR=USING
    *DIM COSTCENTER WHAT<->NO_COSTCENTER; WHERE<->NO_COSTCENTER; USING=NO_COSTCENTER
    *DIM ACCOUNTGL WHAT=A54442000,A54443000; WHERE=A59989000; USING=ALLOC_0702
    *ENDALLOCATION
    *COMMIT
    Edited by: Garrett Tedeman on Nov 4, 2010 6:59 PM
    Edited by: Garrett Tedeman on Nov 4, 2010 7:24 PM
    Update -- Just discovered that the "AMOUNT" keyword, which was used on the MS version, will not validate on BPC 7.5 NW.

    Hi Garrett,
    I'm not sure I understood what is the problem here: is it that allocation overrides some existing values on those Cost centers and Account A59989000 or you just don't like those records with zeroes?
    If it's the last one, that just run light optimization and check that zero elimination is turned on. It will delete your records with zeros.
    If it's the first one, that common practice is to use additional Dimension (DATASRC for example) and populate it with some value for all Cost centers from which you taking data (INPUT for example); than include it in allocation with WHAT = INPUT. You have to define additional member in that dimension (RESLT for example) and put WHERE = RESLT in allocation. By using this technique you achieve at least two benefits:you don't override existing values and you can run allocation as many times as you want without deleting results of previous allocations. You don't have to use that dimension in your reports and data will be just summarized across that Dimension.
    Please let me know if you had something different in mind.
    Regards,
    Gersh

  • Doing an Allocation

    Hello experts!
    I need to do an allocation and I don't know how.
    I have one dimension (CUSTOMER) with one parent and four childs that these childs has values when I choose one KPI of another dimension. I need sum of these values and then each value divided for total of four.
    Exemple:
    I choose DIM.KPI=Quantity and I can see next values in DIM_CUSTOMER:
    DIM_CUSTOMER.Child1: 55
    DIM_CUSTOMER.Child2: 15
    DIM_CUSTOMER.Child3: 20
    DIM_CUSTOMER.Child4: 5
    TOTAL----
    > 95
    I need to do sum of this childs and divided for total and put in KPI=result_alloc
    So with this allocation I should to see when I choose KPI=result_alloc:
    DIM_CUSTOMER.Child1: 57
    DIM_CUSTOMER.Child2: 15
    DIM_CUSTOMER.Child3: 21
    DIM_CUSTOMER.Child4: 5
    TOTAL----
    > 100
    *RUNALLOCATION
         *FACTOR=USING
         *DIM CUSTOMER                WHAT=S_CLIENT;                    WHERE=[Child]="Y";         USING=<<<
                          *DIM KPI                      WHAT=quantity;              WHERE=result_alloc;     USING=quantity
    *ENDALLOCATION
    *COMMIT
    This allocation doesn't work. Anybody has an idea???
    Thanks!!!

    I try this run allocation but all quantity doesn't sum 100 else 92... I don't know how.
    *RUNALLOCATION
                *FACTOR=USING
                *DIM CUSTOMER            WHAT=parent;                      WHERE=BAS(parent);        USING=<<<; TOTAL=<<<
                *DIM INDICATORS         WHAT=quantity;              WHERE=result_alloc;     USING=quantity; TOTAL=<<<
    *ENDALLOCATION
    Original values are:
    Child1: 54
    Child2 :12
    Child3: 20
    Child4: 10
    It shows with this run allocation:
    Child1: 51,84
    Child2 :11,52
    Child3: 19,20
    Child4: 9,6
    And the correct result should be:
    Child1: 56
    Child2 :13
    Child3: 21
    Child4: 10
    Any idea???
    Thanks!!!

Maybe you are looking for

  • Filter on Master Detail tables

    Hi, I've just created a simple Master Detail view (both tables) on my jsf page. I would like to add a filter above all the master table columns but I can't. I have set all the properties linked to Filtering I've seen to "true" (for the table and the

  • Unable to Boot from OSX -- Get Strange Schematic

    Hello - A friend forgot her password on her iBook. Using this forum, we found out that she can access and change the password by booting from the OSX disk (Tiger) and opening the "Utilities" on the installer. So we inserted the disk and restarted the

  • Can't drag vector taken with Shape into illustrator...

    For some reason I cannot drag into a document a vector I created using the new Adobe Shape app from the Creative Cloud panel window.  When I double click the vector I get the pop up seen below.  I watched a few official Adobe videos on this app and t

  • Problems with video previews: image freezes when scrubbing (CS6)

    I just installed CS6 on my computer after working with CS5.5 and I encountered a strange problem with my EOS5D Mk 2 and also Ixus 100IS footage in Bridge CS6 (actually this happens with every video). In CS5.5 I was able to preview my mov files and sc

  • Collect idocs and send to receiver?

    Hello All, Can any one send document or blogs related to the collecting all the IDOCs and at the end of the i need to send it to receiver side. Thanks and Regards, Chinna