BPC NW - Account Transformation

Hello,
I have defined the account transformation in the legal application, and copied the script logic given in the SAP documentation, which is validated OK.
However, when running the package (based on process chain /CPMB/RUNCALCACCOUNT), it is giving an error saying that no business rules have been defined.
Has anyone encountered the same problem?
Thanks&Regards
Begonia

HI  Begonia,
                  As you said that if you have done Modify Appl-->Selecting Business Rules..it should refelect in your application then you go the Those Rules and give the parameters then it will work..
If the rules are not reflecting in your application then you should think you hav't had Rules and problem continues..
Regards,
Naresh.K

Similar Messages

  • BPC NW - Error in Business Rule for Account transformation rule table

    hi
    I have given the Account transformation Rule to move Amount from Account A to Account B and then I have given the following script logic in the default script
    **RUN_PROGRAM CALC_ACCOUNT*
    *CATEGORY = Category*
    *CURRENCY = RptCurrency*
    *TID_RA = %TIME_SET%*
    *CALC=A*
    *OTHER = ENTITY=C1000*
    **ENDRUN_PROGRAM*
    But when I try to load data through Input schedule in Account A and expect amount to transfer to Account B, I m getting an error
    Book Name:Book4
    Application : PLANNING*
    Status : Failed*
    Submitted Count : 1*
    Accepted Count : 1*
    Rejected Count : 0*
    - Error Message -*
    Error running default logic (Business rules are not available)
    - Rejected record list -*
    Error converting records: The root element is missing.
    Can someone please advice me what to do ....

    hi Marcel,
    Lot of thanks for your answer.
    But I have used your logic after removing GROUPS as I dont have GROUPS dimension in my application.
    *RUN_PROGRAM CALC_ACCOUNT
    CATEGORY = %CATEGORY_SET%
    TID_RA = %TIME_SET%
    CALC=FX
    OTHER = [ENTITY=%ENTITY_SET%]
    *ENDRUN_PROGRAM
    This is the error I m getting
    Book Name:Book3
         Application     :     PLANNING
         Status          :     Failed
         Submitted Count     :     1
         Accepted Count     :     1
         Rejected Count     :     0
              - Error Message -
    Error running default logic (Business rules are not available)
              - Rejected record list -
    Error converting records: The root element is missing.
    Can you please advice
    a) Does it mean some issue with my client installation as I dont see these LGF files. I even dont see the data folder in which lgf files are supposed to be present
    b) Where to find information for this interface CALC_ACCOUNT? How did you decide to use 'FX' and how do you know which dimensions to use. Like I dont have GROUPS.
    Please give me your comments.
    regards
    Gaurav

  • .BPC NW 7.5 -  Account transformation Error

    I am trying to run Account Transformation Rules using data manager package. Every time I Run the Package I get error showing as Package "Cancelled". I am using the Standard RUNCALC Package to run the rules. Using the Following Script Logic:
    *RUN_PROGRAM CALC_ACCOUNT
          CATEGORY     = %P_CATEGORY_SET% 
          CURRENCY     = %RPTCURRENCY_SET% 
          TID_RA = %P_TIME_SET%
          CALC=MV
          OTHER = [ENTITY=%P_ENTITY_SET%]
    *ENDRUN_PROGRAM
    Request someone to please help.
    Regards,
    Vrushal

    Hi,
    'Cancelled' status would likely to give a dump in the backend. Have a look at the dump and analyse where the program is failing and it would be looking for a specific input. Could you please put the entity in square brackets in your code.
    *RUN_PROGRAM CALC_ACCOUNT
    CATEGORY = %P_CATEGORY_SET%
    CURRENCY = %RPTCURRENCY_SET%
    TID_RA = %P_TIME_SET%
    CALC=MV
    OTHER = [ENTITY=%P_ENTITY_SET%]
    *ENDRUN_PROGRAM
    And also. I beleive you are send the RPTCURRENCY vallue from your package. If not please hardcode as LC.
    Thanks,
    Sreeni

  • Account Transformation Business Rules: Apply to YTD is not working

    Hello Friends,
    I am using Account Transformation Rules for Re-classification of Accounts in MS version of BPC. And i am trying to use Apply to YTD. But it is not working and i am getting the same periodic values in YTD column also. For example if i am running a report for Dec 2009, i am getting the only Dec 2009 values under YTD also.
    I appreciate any ideas on resolving the issue.
    Regards,
    Mohan

    Hi Nilanjan,
    I observed the following:
    1. If I check the Apply to YTD in Account Transformation rules, it is always showing YTD only irrespective of what i choose in in Measures in CV.
    2. If i do not check the Apply to YTD in Account Transformation rules, it is showing only monthly values irrespectinve of what i choose in Measures in CV.
    YTD is working fine in the same Appset for other dimension members eg not used in the Account Transformation Rules.(for other reports).
    Thank you,
    Mohan

  • Calcaccount procedure - account transformation business rules

    Hi I have a question concerning the calcaccount procedure.
    I already made some Cashflow accounts
    I already filled in some lines in the account transformation business rules
    But now I was wondering how to run these business rules:
    I have made the following calcaccount logic, but when I run it I get nothing for the moment
    *XDIM_MEMBERSET INTCO=GLTOT     
    *XDIM_MEMBERSET GROUPS=C_WDP     
    *XDIM_MEMBERSET ENTITY=E_TOTAL     
    *IGNORE_STATUS     
    *RUN_STORED_PROCEDURE = SPRUNCALCACCOUNT([FINANCE],[%CATEGORY_SET%],[C_WDP],[%SCOPETABLE%],[%LOGTABLE%],[CF])     
    *COMMIT     
    I don't have a clue if this logic is even correct or not
    Please help me

    Hi Alwin,
    I tried this but it doesnt work
    *XDIM_MEMBERSET INTCO=GLTOT     
    *XDIM_MEMBERSET GROUPS=C_WDP     
    *XDIM_MEMBERSET ENTITY=E_TOTAL     
    *IGNORE_STATUS     
    *RUN_STORED_PROCEDURE = SPRUNCALCACCOUNT([FINANCE],[%CATEGORY_SET%],[C_WDP],[%SCOPETABLE%],[%LOGTABLE%])     
    *COMMIT     
    I have the following in the formula log:
    Start time --->3:36:33 PM  -  Date:9/24/2008  (build code:254)
    User:WDP\Administrator
    Appset:WDP_ONTWIKKELING
    App:FINANCE
    Logic mode:1
    Logic by:
    Scope by:
    Data File:
    Debug File:D:\BPC\Data\Webfolders\WDP_ONTWIKKELING\FINANCE\PrivatePublications\Administrator\TempFiles
    DebugLogic_7_.Log
    Logic File:D:\BPC\Data\WebFolders\WDP_ONTWIKKELING\FINANCE
    ..\AdminApp\FINANCE\Calcaccount.lgx
    Selection:D:\BPC\Data\WebFolders\WDP_ONTWIKKELING\FINANCE\PrivatePublications\Administrator\TempFiles\FROM_7_.TMP
    Run mode:1
    Query size:0
    Delim:,
    Query type:0
    Simulation:0
    Calc diff.:0
    Formula script:
    Max Members:
    Test mode:0
    Is Modelling:1
    Number of logic calls:1
    Call no. 1, logic:D:\BPC\Data\WebFolders\WDP_ONTWIKKELING\FINANCE
    ..\AdminApp\FINANCE\Calcaccount.lgx
    signeddata is YTD
    Building sub-query 1
    Query Type:0
    Max members:
    Executing SPRUNCALCACCOUNT [FINANCE],[ACTUAL],[C_WDP],[SPSCOPE_312035],[SPLOG_394894]
    SPRunCalcAccount Version 2.06
    2 Rows Calculated
    2 Rows Updated
    Time to run stored procedure:26.5 sec.
    call 1 completed and data posted in 26.7 sec.
    Run completed in 27.3 sec.
    End time --->3:36:59 PM  -  Date:9/24/2008
    As you can see he doenst post records to the cashflowaccounts..
    Do you know what is wrong?

  • Account Transformation with 13 periods

    Hi All,
    Has anyone had experience using the account transformation using 13 periods/months?  The Account Transformation business rules have properties for SourceYear and SourcePeriod.  These fields can hold either a specific value (2009, 2010, JAN, P01, etc) or a relative value (+1, -3, etc).
    The class that implements the transformations, CL_UJP_CALC_ACCOUNT, has a method, CALC_TIMESCOPE_P, that converts a relative SourcePeriod to an absolute SourcePeriod by first adding the relative number (example +2) to the period the transformation program is being run for (example monthNum 11) and the "rolling" years.
    We are using a fiscal year variant for 13 periods and the code appears to assume that a year has 12 months.  In the example above, Monthnum 11 + 2 = 13  ==>  Month 13 is treated as month 1 of next year.  We need it to be treated as "month" 13 of the current year.
    Any, and all, suggestions are appreciated.
    Thanks,
    Pam

    Opened message with SAP; scheduled to be an enhancement in a future BPC 7.5 NW service pack.

  • Account Transformation- Other Dimension..

    Hi all,
    As stated in the many Business Planning and Consolidation reading materials that i have read we can do account transformation on the account, data source, account flow and time dimensions. Is it possible to use account transformation having another dimension rather than the others that i have mentioned above?
    More power.
    Thanks,
    Benniejay

    Hi
    When i say SQL scripts these are the SQL scripts customised for BPC.
    you can just log into BPC for Administration.
    Go to manage applications in the explorer which would open the BPC administration screen.
    In the help of the administration you can get the SQL Script logic with detailed explanations, and then once you expand application/script logic/default.lgx u get an editor where you need to write the script or call other .lgf or .lgx file.
    if you go through the help you would get better information.
    Thanks and regards
    harish b ki

  • Account transformation accumulating values

    Hi Forum,
    A quick question is there an option for account transformations not to 'add' to values that exist in the bpc database already. I want to overwrite values in existing accounts but the account transformation seems to be accumulating the value.
    Thanks,
    Brian

    Hi..
    I'm working on CAPEX application. My problem is :- 1st time data loading, opening and closing are correct but the subsequent data uploading, opening and closing figure will accumulate. Please advice what coding should I include in my script logic.
    In my testing,
    1) I'll upload - Jan'2006 opening, Jan'2006 to Dec'2006 Movement
    2) use account transformation to calculate "opening + movement = closing" 
    3) use script logic for carry-forward monthly opening 
    Account Transformation business rule:
    Transf group   Source Acc  Source flow            Source d/source  Destination acc
    A                        1410220          FA_ExistDepr_OPE                                1410220
    A                        1410220          FA_ExistDepr                                         1410220
    A                        1410220          FA_AddDepr_OPE                                  1410220                 
    A                        1410220          FA_AdditionsDepr                                   1410220
    A                        1410220          FA_ADepr_OPE                                      1410220
    A                        1410220          FA_ADepr                                               1410220
    A                        1410220          FA_DispDepr_OPE                                  1410220
    A                        1410220          FA_DisposalDepr                                     1410220
    A                        1410220          FA_TranInDepr_OPE                                1410220
    A                        1410220          FA_TransferInDepr                                    1410220
    A                        1410220          FA_TranOut_OPE                                     1410220
    A                        1410220          FA_TransferOutDepr                                  1410220
    Dest. flow          Dest. d/source   Rev sign Source Period  AppytoYTD  Remark  LEVEL
    FA_ExistDepr_CLO                                                                         Y
    FA_ExistDepr_CLO                                                                         Y
    FA_AddDepr_CLO                                                                           Y
    FA_AddDepr_CLO                                                                           Y
    FA_ADepr_CLO                                                                               Y
    FA_ADepr_CLO                                                                               Y
    FA_DispDepr_CLO                                                                           Y
    FA_DispDepr_CLO                                                                           Y
    FA_TranInDepr_CLO                                                                         Y
    FA_TranInDepr_CLO                                                                         Y
    FA_TranOutDepr_CLO                                                                      Y
    FA_TranOutDepr_CLO                                                                      Y
    Default.lgf Script logic:
    *INCLUDE SYSTEM_CONSTANTS.LGL
    *SYSLIB  SYSTEM_LIBRARY.LGL
    // Default base level logic - applies to all base members in all dimensions
    //Move Net Income to Balance Sheet
    //ROLLTOBS( CYNI, CALCNI, FINSTMT, PL, DEC )
    // Perform Currency translation
    *INCLUDE FXTrans
    Perform ACCOUNT TRANFORMATION
    *RUN_STORED_PROCEDURE = SPRUNCALCACCOUNT([CAPEX],[%CATEGORY_SET%],[LC],'%SCOPETABLE%','%LOGTABLE%', 'A')
    *COMMIT
    //-- ACCOUNT TRANFORMATION END--
    TO CALCULATE MONTH OPENING
    *SELECT(%AccountList%, "ID", "CapAccount", "[Group] = 'Test1'")
    *xdim_memberset CapAccount= %AccountList%
    *xdim_memberset CapAcctDetail = FA_ExistDepr_OPE,FA_ExistDepr_CLO,FA_AddDepr_OPE,FA_AddDepr_CLO,FA_ADepr_OPE,FA_ADepr_CLO,FA_DispDepr_OPE,FA_DispDepr_CLO,FA_TranInDepr_OPE,FA_TranInDepr_CLO,FA_TranOutDepr_OPE,FA_TranOutDepr_CLO
    *When CapAcctDetail
      *IS FA_ExistDepr_CLO
      *REC(CapAcctDetail=FA_ExistDepr_OPE,TIME=NEXT)
      *IS FA_AddDepr_CLO
      *REC(CapAcctDetail=FA_AddDepr_OPE,TIME=NEXT)
      *IS FA_ADepr_CLO
      *REC(CapAcctDetail=FA_ADepr_OPE,TIME=NEXT)
      *IS FA_DispDepr_CLO
      *REC(CapAcctDetail=FA_DispDepr_OPE,TIME=NEXT)
      *IS FA_TranInDepr_CLO
      *REC(CapAcctDetail=FA_TranInDepr_OPE,TIME=NEXT)
      *IS FA_TranOutDepr_CLO
      *REC(CapAcctDetail=FA_TranOutDepr_OPE,TIME=NEXT)
    *EndWhen
    *COMMIT
    Please advice. Thanks.
    Regards,
    Clarissa Chung

  • Currency Translation and Account Transformation Business Rules Together?

    Hi I am fresh out of college and working on a BPC project. I have this working but fear down the road problems.
    We are using currency translation and struggling with getting our NetIncome to write the correct value to the Current Year Retained Earnings when it converts from LC to USD; USD value did not match Net Income in P&L.
    Initially, we did the Account Transformation first in our default logic only on LC, then FX runs and creates the corresponding USD value which does not match the Net Income.
    It looks like the logic is correctly summing the YTD value but it converts using the AVG rate for the period (as opposed to multiplying each month by that monthu2019s average rate) creating a variance.
    Weu2019ve moved the account transformation to run after FX and have it also running on USD. This currently works but seems like a workaround, and as we configure the remaining CTA rules will we run into problems?
    Have any experts run into this issue before and what should I do?
    Edited by: MichaelUCF2010 on Oct 12, 2010 10:18 PM

    Hi, perhaps this is my lack of accounting knowledge rearing itself.
    RE = BS = End (if you take into account translation adjustment for Net Income and Additions/Substractions & OB)
    However If you are talking about the RE Reserve (and computing that correctly)
    RE Reserve
    OB - Opening
    Inc - Avg
    Sub - Avg
    NI - Avg [I assume it is this line you are talking about - please try the apply periodic option for avg]
    CTA - calculated
    CB - End

  • Error while running Account Transformation...

    Hi Experts,
    I'm trying to run Account Transformation using the script logic below but unfortunately nothing gets calculated. When I check the package, it status is mark "CANCELED" though I did not cancel the execution of the package. Checking the detail of the status it only show the below info:
    Script Logic:
    *RUN_PROGRAM CALC_ACCOUNT
    CATEGORY = %CATEGORY_SET%
    CURRENCY = %CURRENCY_SET%
    TID_RA = %TIME_SET%
    OTHER = [COMPANY=%COMPANY_SET%]
    CALC = CALC_RE
    *ENDRUN_PROGRAM
    Package Detail Log:
    /CPMB/MODIFY completed in 0 seconds
    [Selection]
    (Member Selection)
    COMPANY: 1403
    CATEGORY: ACTUAL
    CURRENCY: LC
    TIME: 2005.JAN
    [Messages]
    Application: CONSOL Package status: SUCCESS
    By the way, I used the process chain for ALLOCATION, I put the code for Account Transformation in the ALLOCATION.LGF since it's the logic being called by the said process chain. Checking further using the TCODE ST22 it gives the following error:
    Runtime Errors: GETWA_NOT_ASSIGNED
    Short Text: Field symbol has not been assigned.
    What happened: Error in ABAP Application Program. The current ABAP program "CL_UJK_UTIL================CP" had to be terminated because it has come across a statement that unfortunately cannot be executed.
    Cheking "Information on where terminated" code is terminated here...
        READ TABLE <lt_mem> ASSIGNING <l_member> INDEX 1.
        ASSIGN COMPONENT 'TIMEID' OF STRUCTURE <l_member> TO <l_timeid>.
        MODIFY ct_timeid FROM <l_timeid>.
        "ASSIGN COMPONENT 'TIMEID' OF STRUCTURE <l_member> TO <l_string>.
    I checked the properties and the TIMEID property is existent. Was there anything wrong with my syntax? Any idea regarding this kind of error?
    Thanks,
    Marvin

    After checking all the dimension and using TCODE RSA1 to check the server side, I found that INTCO property is existent in the member worksheet but not in the server so I maintain the dimension properties and re-add INTCO property in the Entity dimension. After that package runs successfully.

  • Account transformation business rule

    Hi experts,
    I hace defined Account Transformation rule in the default.lgf file. and I have defined source and destionation account in the corresponding table.
    Now I am running the rule from Data manager package - Default formula.It is running successfully.
    But when I see Package log it is not executing SPRUNCALCACCOUNT at all.
    Would be great help if anyone can give some guidance.

    Can you post the exact logic script?
    Maybe a stupid guess, but did you put a *COMMIT directly after the *RUN_STORED_PROCEDURE logic statement?
    Regards,
    Joost

  • Business rules: Account transformation

    Hi everyone.
    I am trying to populate my cash flow statement using the Account Transformation. E.g For the changes in my inventories: I want the difference between the closing balance of DEC (of the previous year) and the closing balance of the current month.
    I thought I could use "Source Period" and "Source Year" in the account transformation. Any idea how they can be used? I want to use a property: u201CPrevious yearu201D to make the time dynamic. Is that possible?
    Thanks for your help
    Esther

    I would suggest using the dimension Account library functions and a dimension calculations or script logic calculations to create the value from the cube values, rather than during the data load process.Script Logic might look something like the following:
    INCLUDE SYSTEM_CONSTANTS.LGL
    *SYSLIB CONSOLIDATION_LIBRARY.LGL
    // MOVE INCOME STATEMENT ITEMS TO CASH FLOW STATEMENT
    RUNSUMMARIZE(ThisApp,CF_SUMM,%CATEGORY_SET%,%LC_RPT_CURR%)
    //CALCULATE BALANCE SHEET MOVEMENTS AND POST TO CASH FLOW STATEMENT
    *SELECT(%FROM_ACCOUNT%, "[ID]", "ACCOUNT", "[CF_TO_ACCT] <> ''")
    *XDIM_MEMBERSET ACCOUNT = %FROM_ACCOUNT%
    *XDIM_ADDMEMBERSET TIME = PRIOR
    *XDIM_MEMBERSET RPTCURRENCY=%LC_RPT_CURR%
    *WHEN TIME
          *IS %TIME_SET%
                *REC(ACCOUNT=ACCOUNT.CF_TO_ACCT)
          *IS PRIOR
                *REC(FACTOR=-1,ACCOUNT=ACCOUNT.CF_TO_ACCT,TIME=NEXT)
    *ENDWHEN
    *COMMIT
    But this will require a few properties on the accounts members to support the calculations. The idea for cash flow is to have the basic values in the accounts, and then provide the calculations to place values into another set of accounts that build the CAshFLow statement.  The most difficult part will be dealing with the exceptions, changes to the Cash Flow statement process a customer will need to work with each reporting period.  But Script logic generally works the best.

  • Business Rules for Account Transformation - Execute a Transformation Group

    Hello,
    when executing a package for account transformation, I want to select a specific transformation group
    only.
    The transformation group is the first column in the definitions.
    My question:
    Can I pass this to script logic as a parameter?
    What is it like?
    I think this should have a performance effect when using account transformation in default logic.
    Thanks for an answer
    Jochen

    Hi Jochen,
    Your best bet is the documentation at [http://help.sap.com/saphelp_bpc75_nw/helpdata/en/2b/8f059920de465b88be2893e2117fbe/frameset.htm], however in this case it does not do a very good job of explaining what is happening. Fortunately the CALC= property is just about the only one that you have control over for the account transformation business rules.
    The other option (and the only way to truly know what is going on) is to investigate the ABAP programs that actually execute the business rule logic in BW. You can find these programs in SE80, under the UJ package, in the UJP sub-package. You will be most interested in the classes available there. There tends to be one class per business rule group, as well as classes for allocations and validations.
    Cheers,
    Ethan

  • Account Transformation CALCACCOUNT.LGF returns 0 records

    Hi,
    Account transformation through CALCACCOUNT.LGF returning 0 records.
    Created a Account Transformation Business rule as follows -
    Transformation group Name - AST
    Source Account - CASH
    Category - ACTUAL
    Source Flow - NONE
    Source DatsSrc - SYSTEM
    Similarly maintained values for -
    Destination Account  - D_CASH
    Destination Category - ACTUAL
    Destination Source Flow - ENDBAL
    Destination DatsSrc - SYSTEM
    Source period = -1
    all other values like Source Year,Apply to YTD,Remark,Level, Forced into Member are left blank.
    Scrip Logic -
    *RUN_PROGRAM CALC_ACCOUNT
    CATEGORY = %CATEGORY_SET%
    CURRENCY = %RPTCURRENCY_SET%
    TID_RA = %TIME_SET%
    ENTITY=%ENTITY_SET%
    CALC=AST
    *ENDRUN_PROGRAM
    Script runs succesfully, however returns 0 records.
    RUN CALC_ACCOUNT
    0  SUBMITTED, 0  SUCCESS, 0  FAIL.
    SCRIPT RUNNING TIME IN TOTAL:1.94 s.
    LOG END TIME:2011-06-28 01:38:25
    Can some one please advise on the "checks" to be performed to run the script succesfully.
    I know out of experience even if a simple property is not set, script does not run.
    Inputs appreciated.
    Thanks.

    With this, one thing to be aware of is that if you have run an account transformation rule on a data set already, and you a re-running it yet the data has not changed - there will be 0 records generated.
    I recommend changing the data - do a simple zero and input data then save - then re-run, check if that works.
    Nick

  • Is there a limit for the Account Transformation Table?

    Hi Gurus,
             I am anxious to know is there a limit for the or any particular number for maintaing Account Transformation table. 2) If many rules are existing in the Table, will it cause any performance issue.
    Regards,
    KumarMG

    Hello Kumar,
    I endorse the view expressed by Lokesh. Yes, there is no limit to the number of Account Transformation Rules that you can maintain in the  Transformation Table. One way to limit this number is to use carefully maintained hierarchies instead of  specifying individual accounts in the Rule. However, this is not always possible - but will help limit the number of entries in the Account Transformation Table. To create Cash Flow Satatement, you have to anyway use the Account Transformation Rule and surely this would stretch the number of entries in the table. For a complex requirement, these might extend to a few hundred entries. Performance will be an issue, no doubt.
    Chakrapani

Maybe you are looking for

  • Application working under NetBeans but not as a *.jar file

    Hello, recently I found a little problem. I wrote application that shows all available ports in my computer. When I am running this applications under NetBeans it works with no problem - finds all available ports. Then I am building it to the *.jar f

  • Updating a managed metadata column from choice column value

    I am trying loop through all lists in a web, and for each list,  1. create a managed metadata column->Working 2. Pull value from choice column->Working 3. Move choice column value to managed metadata column->Not Working Point number 3 is not working.

  • Error : DB Mapping does not exist for the Host in iSetup

    Hi Experts, We configured iSetup for migrating data from source to target, while configuring instance mapping has been completed successfully but while extracting data from source to target is showing below error : Error : DB Mapping does not exist f

  • Quality of Keynote widget in iBooks Author

    Dear All, I am working on an iBook with many Keynote widgets. The keynotes are already made and connected to my iBook, but when i publish it to my iPad3 everything is unsharp. I played around with many resolutions and sizes but nothing helps. So i di

  • Viewing 3D .PDF on MAC 10.9.2

    Hello, I have a 3D .PDF created on a Windows 7 machine that I need to be able to view on the MAC... unless I am opening a can of worms with this question (am a new MAC user who is only beginning to begin to be aware of the Apple/.PDF issue...) is the