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.

Similar Messages

  • Business Rules: Account transformation and the source YEAR / PERIOD

    Ladies and gents,
    lets assume you have an amount of 100 on account A everymonth for 2 years.
    in my business rules, account transforamtion, i put those sales to be transfer to an  account B.
    When i put DEC in period and -1 in year, then it will post the previous year cumulated amount of A to B. So be will have 1200
    Now, lets assume  I put 9 in period and -1 in year then it will bring me the total of previous year October if i am in january Y1, or previous year November if i am in february... But then in march, april, ... until the end of the year it will bring previous year December.
    Now, when i put -3 in period and no change in year, for january, it brings january, for february it brings february, for march it brings march... But on April it brings january as expect...
    I want it to come with 0 for the first 3 month... and only start in april!! Why does it do that considering that it for the previous example +3 after march always brings december... why then -3 in january doesnt bring nothin!!
    Nic

    You can greatly improve your chance of receiving a helpful answer to your question if you state the version (MS or NW) and the release (5.1, 7.0, 7.5) of BPC which you are using.
    Also notice the sticky [note|Please do not post BPC, SSM or FI/CO questions here!; at the top of this forum whereby we announced new dedicated forums for BPC which are the proper place to post your questions regarding BPC in the future.
    Thanks and best regards,
    [Jeffrey Holdeman|http://wiki.sdn.sap.com/wiki/display/profile/Jeffrey+Holdeman]
    SAP BusinessObjects
    Enterprise Performance Management
    Regional Implementation Group

  • Why not allow Business Rule Design Transformer to overwrite existing BRDDs

    Hi,
    It can be quite annoying during development to continually having to remove the BRDD Trigger and PL/SQL Definition when running the BR Design Transformer reveals missing information in the BR Analysis definition. It seems that it would be practical to have at least the option to have the Business Rule Design Transformer overwrite an existing Business Rule Design Definition.
    You could think of an additional parameter in this utilily labeled "Overwrite existing BRDD?" with allowable values Y(es) and N(o) with No as default (so that the default functionality is the same as before).
    Below you find the code that can be added to the HSU_BRTR package to realize such a functional improvement. Maybe you can consider it for a next release...?!
    best regards,
    Lucas Jellema
    AMIS Services BV
    code to add to HSU_BRTR to provide a parameter that allows the user to specify whether or not the HSU_BRTR is allowed to overwrite an existing BRDD:
    in the revision history:
    09-jan-2003 Lucas Jellema
    6.5.2.3AMIS1.1 Added new parameter and supporting code that allows user to indicate
    whether existing Business Rule Design Definitions may be/should be overwritten
    at the end of procedure install
    hsu_install.add_parameter
    ( PACKAGE_NAME -- package name
    , 40 -- sequence
    , 'Overwrite existing BRDDs?' -- prompt
    , 'N' -- default value actual
    , 'No' -- default value displayed
    , 'Y' -- mandatory
    , 'N' -- allow multi-select
    , 'N' -- include shared elements
    , '' -- element type short name
    , '' -- sql expression actual
    , '' -- sql expression displayed
    , null -- where clause
    , null -- synchronize with
    , null -- foreign key column
    , -- help text
    'Choose whether you want this utility to overwrite existing Business Rule Design Definitions.'
    hsu_install.add_allowable_value
    ( PACKAGE_NAME -- package name
    , 40 -- parameter
    , 1 -- sequence
    , 'Y' -- actual value
    , 'Yes' -- displayed value
    hsu_install.add_allowable_value
    ( PACKAGE_NAME -- package name
    , 40 -- parameter
    , 2 -- sequence
    , 'N' -- actual value
    , 'No' -- displayed value
    --------6.5.2.3AMIS1.1
    Just before procedure transform_stage2
    procedure delete_brdds
    ( p_tbl_id in ci_table_definitions.id%type
    , p_br_name in varchar2
    -- Purpose Delete existing Business Rule Design Definition
    -- Usage from run procedure
    -- Remarks Find PL/SQl Module Definition based on Business Rule Label
    is
    cursor c_brdd
    ( b_tbl_id in ci_table_definitions.id%type
    , b_br_name in varchar2
    is
    select trg.id trg_id
    , trg.name name
    , plm.id plm_id
    from ci_database_triggers trg
    , ci_plsql_modules plm
    where trg.table_definition_reference = b_tbl_id
    and trg.plsql_module_reference = plm.id
    and plm.name = b_br_name
    begin
    -- loop over journalling busrules of this application
    <<brdd>>
    for r_brdd in c_brdd(p_tbl_id, p_br_name) loop
    -- delete busrule (delete of trigger is since 6i not enough anymore, so
    -- explicitly delete PL/SQL module also)
    bllog.write
    ( 'Deleting trigger '||r_brdd.name||' and PL/SQL module '
    ||hsu_name.get_name_and_path(r_brdd.plm_id)
    ||', a new business rule design definition overwrites this old one.'
    , bllog.information
    bltrg.del(r_brdd.trg_id);
    blplm.del(r_brdd.plm_id);
    end loop brdd;
    end delete_brdds;
    inside procedure transform_stage2
    (just before the comment: -- check if BRDD with this plm_name already exists)
    if p_overwrite_br = 'Y'
         then
    delete_brdds
    ( p_tbl_id => g_trg_tbl(i).tbl_id
    , p_br_name => l_plm_name
         end if; -- find_trg and overwrite =Y
    A new parameter in procedure transform_br_fun
    procedure transform_br_fun
    , p_overwrite_br in varchar2 default 'N' -- 6.5.2.3AMIS1.1
    use the parameter p_overwrite_br in the call to transform_stage2
    transform_stage2
    ( p_fun_id => p_fun_id
    , p_fun_label => r_fun.fun_function_label
    , p_fun_short_definition => r_fun.fun_short_definition
    , p_msg_prefix => p_msg_prefix
    , p_msg_language => p_msg_language
    , p_rule_type => l_rule_type
                   , p_overwrite_br => p_overwrite_br -- 6.5.2.3AMIS1.1
    new parameter p_overwrite_br in the procedure run
    NOTE: in both PACKAGE SPECIFICATION and BODY
    , p_overwrite_br in varchar2 default'N' -- 6.5.2.3AMIS1.1
    use the parameter p_overwrite_br in all calls to transform_br_fun inside procedure run
    transform_br_fun
    ( p_fun_id => r_fun_tree.id
    , p_msg_prefix => p_msg_prefix
    , p_msg_language => p_msg_language
    , p_create_att_usages => p_create_att_usages
    , p_overwrite_br => p_overwrite_br -- 6.5.2.3AMIS1.1

    Among the alternatives not mentioned... Using a TiVo DVR, rather than the X1; a Roamio Plus or Pro would solve both the concern over the quality of the DVR, as well as providing the MoCA bridge capability the poster so desperately wanted the X1 DVR to provide. (Although the TiVo's support only MoCA 1.1.) Just get a third-party MoCA adapter for the distant location. Why the hang-up on having a device provided by Comcast? This seems especially ironic given the opinions expressed regarding payments over time to Comcast. If a MoCA 2.0 bridge was the requirement, they don't exist outside providers. So couldn't the poster have simply requested a replacement XB3 from the local office and configured it down to only providing MoCA bridging -- and perhaps as a wireless access point? Comcast would bill him the monthly rate for the extra device, but such is the state of MoCA 2.0. Much of the OP sounds like frustration over devices providing capabilities the poster *thinks* they should have.

  • Business Rule Design Transformer fails with ORA-00001

    I'm stuck with the Business Rule Design Transformer Utility of Headstart. After running this utility over one BR it is impossible to run it over other BR's because of violation of the unique constraint HST65.QMS_MSP_PK (table QMS_MESSAGE_PROPERTIES). The problem is that the utility tries to insert a record (message, specified in the Notes property of Designer) into QMS_MESSAGE_PROPERTIES with the code "ABI-10000", that was already created by running the utility for the first time.
    Exact error message: "Activity aborted with ORACLE internal errors.
    -1 ORA-00001: unique constraint (HST65.QMS_MSP_PK) violated"
    I'm using Designer 6i (6.5.52.1.0) and Headstart 6.5.1.3
    If someone has any clue about this I would be very grateful
    Cheers,
    Dimce

    Jan,
    The name of the business rule is already in the CONSTRAINT_NAME of the QMS_MESSAGE_PROPERTIES table.
    I already tested by deleting the records in the two tables, QMS_MESSAGE_PROPERTIES and QMS_MESSAGE_TEXT, and ran the utility, but it didn't help either. I can run the utility for one rule, but when I want to run it again at some later point, it fails with this error.
    But, I managed to create rule definitions using the HSU Create Business Rule Design Definition, rule by rule. I only had to add references in the business rule to the used module.
    Dimce

  • ORA-06502 in Business Rule Design Transformer

    For a specific business rule we got the following error: ORA-06502: PL/SQL: numeric or value error: character string buffer too small. It appears that it is caused by a long entity relation name. See the detailed logging below. Bij reducing the length of the entity relation name involved the utility worked file.
    Relationship: afstand rechtsmiddel gedaan bij namens verdachte door is included as Usage for entity: GGRL/ RELATIE
    Relend usage is found with name: technisch ttz gevoegd bij and id: 1497077058224033627321119385618562861
    Relationship: TECHNISCH TTZ GEVOEGD BIJ->STRAFZAAK is not found to be part of AFSTAND RECHTSMIDDEL GEDAAN BIJ NAMENS VERDACHTE DOOR->RELATIE
    Triggering event UPDATE UITSPRAAK.AFSTAND RECHTSMIDDEL G0 found.
    bltext.get_lines_from_repository, p_text_type=CDIDSC
    bltext.get_line_containing
    Activity aborted with ORACLE internal errors.
    -6502 ORA-06502: PL/SQL: numeric or value error: character string buffer too small

    Jan,
    The name of the business rule is already in the CONSTRAINT_NAME of the QMS_MESSAGE_PROPERTIES table.
    I already tested by deleting the records in the two tables, QMS_MESSAGE_PROPERTIES and QMS_MESSAGE_TEXT, and ran the utility, but it didn't help either. I can run the utility for one rule, but when I want to run it again at some later point, it fails with this error.
    But, I managed to create rule definitions using the HSU Create Business Rule Design Definition, rule by rule. I only had to add references in the business rule to the used module.
    Dimce

  • Consolidation Business Rules

    Hi
    Can someone tell me the main purpose for each of the following business rules:
    Account transformation
    Currency conversion rule
    Intercompany booking
    Automatic adjustments
    Automatic adjustments details
    Carry-forward rules
    US Elimination
    Validation rules
    Validation rules details
    Would really appreciate the help. Also, would be great if anyone can send me some document specifically on consolidation rules and methods.
    Thanks
    Mav

    Hi Mav,
    Unfortunately there is no current documentation on Business Rules for 5.1.  The only documentation that is out there is the Admin User Guide, which you can download from SAP.  There is also the Consolidation Engine Referecnce guide for version 4.2 SP3, which goes into more detail regarding business rules.  I can send you a copy of this.  Just send me a note.
    Michael

  • TYPELIM and DIMLIST properties cannot be used in business rules

    Hello All,
    We are implementing BPC V5.1.
    We are facing a problem while using properties such as TYPELIM or DIMLIST in "Automatic Adjustments detail" business rules.
    According to the documentation, there are 4 colums where we can use account properties in this business rule :
    - ACCOUNT where we give the account used to trigger the elimination.
    In this field we are able to use account ID, TYPELIM or DIMLIST properties and it works perfectly.
    - ALL_ACC, GROUP_ACC or MINO_ACC where we give the accounts we want to change.
    In these fields, we are supposed to be able to use account ID, TYPELIM or DIMLIST properties. If we use the account ID, it works fine. If we use the TYPELIM property that has been used in the account field to trigger the elimination, it works fine.
    Howewer, we cannot use TYPELIM or DIMLIST if they have not been used previously in the account field to trigger the elimination.
    Has anybody faced the problem before ?
    Is there a workaround (except typing all the IDs of the accounts we want to eliminate) ?
    Thanks in advance.
    Regards
    Romain

    Hello All,
    We are implementing BPC V5.1.
    We are facing a problem while using properties such as TYPELIM or DIMLIST in "Automatic Adjustments detail" business rules.
    According to the documentation, there are 4 colums where we can use account properties in this business rule :
    - ACCOUNT where we give the account used to trigger the elimination.
    In this field we are able to use account ID, TYPELIM or DIMLIST properties and it works perfectly.
    - ALL_ACC, GROUP_ACC or MINO_ACC where we give the accounts we want to change.
    In these fields, we are supposed to be able to use account ID, TYPELIM or DIMLIST properties. If we use the account ID, it works fine. If we use the TYPELIM property that has been used in the account field to trigger the elimination, it works fine.
    Howewer, we cannot use TYPELIM or DIMLIST if they have not been used previously in the account field to trigger the elimination.
    Has anybody faced the problem before ?
    Is there a workaround (except typing all the IDs of the accounts we want to eliminate) ?
    Thanks in advance.
    Regards
    Romain

  • Headstart Business Rule IN parameter changes value

    I've created a Business Rule (CEV rule � triggered by create) with following code:
    IN parameters: p_datum_van, p_cat and p_prest
    cursor c_cap is select datum_tot
    from cew_cat_prest
    where . . .
    and p_datum_van between datum_van and datum_tot
    and datum_tot is not null;
    l_datum_tot cew_cat_prest.datum_tot%type;
    begin
    dbms_output.put_line('BR5 p_datum_van '||p_datum_van);
    open c_cap;
    fetch c_cap into l_datum_tot;
    if c_cap%found then
    dbms_output.put_line('BR5 eerste controle p_datum_van '||p_datum_van);
    update cew_cat_prest
    set datum_tot = p_datum_van - 1
    where cat = p_cat
    and prest = p_prest
    and datum_tot = l_datum_tot;
    dbms_output.put_line('BR5 tweede controle p_datum_van '||p_datum_van);
    update cew_cat_prest
    set datum_tot = l_datum_tot
    where cat = p_cat
    and prest = p_prest
    and datum_van = p_datum_van;
    dbms_output.put_line('BR5 derde controle p_datum_van '||p_datum_van);
    The updates are not executed correctly since p_datum_van changes !!!
    Eerste controle: p_datum is correct
    Tweede controle: p_datum has changed its value
    What we do:
    Record 1: van (from) 01/01/2003 tot (to) 31/01/2003
    Record 2: van 01/02/2003 tot <null>
    Add new record: van 15/01/2003
    What we want:
    Record 1: van 01/01/2003 tot 14/01/2003
    Record 3: van 15/01/2003 tot 31/01/2003
    Record 2: van 01/02/2003 tot <null>
    Eerste controle: parameter p_datum_van = 15/01/2003
    Tweede controle: parameter p_datum_van = 01/01/2003
    Remark: if we use the TAPI procedure ups instead of updates, we have the same problem
    How is it possible that an IN parameter changes its value during execution of a procedure ???

    Tim,
    Headstart should be able to check out any tables you need.
    We think we have the user settings
    done correctly, but there may be something that we
    have missed. How can we get Headstart to
    automatically check-out the table(s) for which we
    want to run the Business Rules design transformer?The user settings you need are (see also pages 5-7 and 5-10 in the Headstart User's Guide):
    - Under 'Process the following objects', choose 'Checked out by anyone'
    - Also check the check box '... also Checked In objects'
    - Choose whether you want to automatically check out with or without lock
    If this does not help, please run the utility with log level 'Debug Detailed' (can also be set in the User Preferences) and report the last few lines of the log messages. They should give an indication of why the check out does not succeed.
    Hope this helps,
    Sandra Muller

  • Problem using "Create Business Rule Design Definition" utility

    Hi everyone,
    I tried to create a business rule with Headstart Utilities - Create Business Rule Design Definition (Revision 6.0.0.20) and I got the following errors :
    Errors
    Message
    Combination of Message Prefix and Message Number (SGM-ENG) does not match format AAA-NNNNN.
    Activity aborted with ORACLE internal errors.
    -1400 ORA-01400: cannot insert NULL into ("HST50"."QMS_MESSAGE_TEXT"."LANGUAGE")
    I suppose that the utility concatenate the message prefix and the language to build the error message.
    Our Oracle Designer version is 6.0.3.9.0, Headstart 2.1.2 with patch 12.4 and Developper is 6.0.5.35.3
    Any patch available?
    Regards,
    Jerome Couture

    Tim,
    Headstart should be able to check out any tables you need.
    We think we have the user settings
    done correctly, but there may be something that we
    have missed. How can we get Headstart to
    automatically check-out the table(s) for which we
    want to run the Business Rules design transformer?The user settings you need are (see also pages 5-7 and 5-10 in the Headstart User's Guide):
    - Under 'Process the following objects', choose 'Checked out by anyone'
    - Also check the check box '... also Checked In objects'
    - Choose whether you want to automatically check out with or without lock
    If this does not help, please run the utility with log level 'Debug Detailed' (can also be set in the User Preferences) and report the last few lines of the log messages. They should give an indication of why the check out does not succeed.
    Hope this helps,
    Sandra Muller

  • Headstart Business Rule Design Xformer utility

    When using the Headstart Business Rule Design Transformer to generate Business Rules, the table is required to be checked out. In previous releases, we have been told that an automatic check-out is performed on the table(s), but ours forces us to manually check-out the table definition, or it does not continue. We think we have the user settings done correctly, but there may be something that we have missed. How can we get Headstart to automatically check-out the table(s) for which we want to run the Business Rules design transformer? Or is this a bug in the current release? We are using Headstart release v6.5.2.3 (HSU_BRTR). Thanks.

    Tim,
    Headstart should be able to check out any tables you need.
    We think we have the user settings
    done correctly, but there may be something that we
    have missed. How can we get Headstart to
    automatically check-out the table(s) for which we
    want to run the Business Rules design transformer?The user settings you need are (see also pages 5-7 and 5-10 in the Headstart User's Guide):
    - Under 'Process the following objects', choose 'Checked out by anyone'
    - Also check the check box '... also Checked In objects'
    - Choose whether you want to automatically check out with or without lock
    If this does not help, please run the utility with log level 'Debug Detailed' (can also be set in the User Preferences) and report the last few lines of the log messages. They should give an indication of why the check out does not succeed.
    Hope this helps,
    Sandra Muller

  • 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

  • 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

  • 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 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

  • 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

Maybe you are looking for

  • NFe xml versao 2.0 - Dados de importacao DI

    Boa Noite ! Alguem poderia me dar uma dica de como resolver o erro que estou tendo no envio de um XML de Importacao ? Os dados da DI estao sendo preenchidos na BADI, inclusive consigo ver quando debugo no R3, porem quando envio para o GRC, está me re

  • Incomplete print jobs with HP Officejet v40 and Windows 7

    I've seen this problem posted but no solution yet.  I have upgraded my laptop to a Windows 7 and my trusty old HP Officejet v40 will not print a complete page.  It worked great with XP.  The drivers are supposedly updated.  Please help! Thanks.

  • Error occured while creating purchase info record in mm

    sir, while creating purchase info record  an error occured while inserting net price. it said NOT POSSIBLE TO DETERMINE A CONDITION TYPE FOR A PRICE when it attempted to generate the time dependent condition for the price you entered the systeem was

  • Ship-To Address for Business Partner

    Hi, I have two records related to the same partner in the table CRMD_PARTNER. Where each record has a different address number (field ADDR_NR). One address is about Location (Partner func. = 75) and other is about Ship-To (Partner func. = 27). I took

  • Photos Keep Disappearing

    Hi, I've only recently started using iPhoto '08, and twice within the last week I've lost my library. As in, all the thumbnails are there, but when I click them I get that big exclamation point. So I'm now in the process of rebuilding the library aga