Sign Flip  on UDA

Hi guys.
Could you guys please tell me if we can change the sign of a data(sign flip) as per UDA.
For example 4 would become -4 if UDA is A.
I know there is a option "Sign-Flip" in the rules file defination. But what if I want this for more than one UDA.
For example if the UDA is A or B, then what should be done..There is only one text field in the rules file.

Yep, it is one UDA per rule. Weirdly, the editor will accept e.g....
UDA1, UDA2...and validate the rule, but only UDA1 works.
You might be able to flip the sign in the source data itself, but if you have to do it in the rule the only sensible options I can think of are to use SQL (as John said) or create an additional UDA and apply it to all the accounts you want to flip.

Similar Messages

  • Data Load rule  Sign flip

    In this version of Essbase 11.1.2.2.100.2176
    the Data Load rule
    Data Load Settings
    DataLoad Values
    Sign flip
    On UDA
    SignFlip
    Dimension Accounts
    Doesn’t work.
    I've properly set up a UDA called SignFlip in the Accounts Dimension.
    I moved a data load rule from a working application in a prior version and it doesn't work in the new version.
    I've also started a new dataload rule from scratch.

    Used corrected Load rule.

  • Assigning Sign Flip on multiple UDA's

    On a data load rule is there any way to assign more than one UDA to perform a sign flip on accounts? I've tired separating the UDA's using a , ; : and a space and none of them seem to work. I can't find anything in the database admin guide about limiting the amount of UDA's that can be sign flipped on a data load. Can anyone give me some guidance on this or a possibility other than a calc script to perform a sign flip. Thanks

    Yep, it is one UDA per rule. Weirdly, the editor will accept e.g....
    UDA1, UDA2...and validate the rule, but only UDA1 works.
    You might be able to flip the sign in the source data itself, but if you have to do it in the rule the only sensible options I can think of are to use SQL (as John said) or create an additional UDA and apply it to all the accounts you want to flip.

  • Sign flip in Excel based on leading account number

    Hello All,
    I am currently creating Profiles in ERP Integrator that will be used for ARM. I am trying to utilize Excel to concatenate the account with the company and so on. My question is, if I have a range of accounts that need a sign flip (1XXXXX) can I do that in my Excel formula so that accounts beginning with 1 are negative?
    Currently I have:
    =CONCATENATE("#MULTIDIM UD2=[",D14,"]", " AND UD3=[",B14,"]",",",D14,"-",B14,",",D14,"-",B14,",")
    With an output of:
    #MULTIDIM UD2=[123456] AND UD3=[123],123456-123,123456-123,
    Thanks!

    Hi Guys,
    Please suggest me the any enhancement to solve my problem.
    is my question is understandable or not?
    is this question follows forms rules ?
    this is general question which i posted but no one is replyed.
    please suggest any thing wrong in questioning in posting sdn forms.
    Thanks in advance.
    kallam

  • Creating Logic for FDM Sign Flip Rule

    I am working through an implantation of FDM (11.1.2.2) for a Hyperion Enterprise environment and we have > 70 different locations to create. Some will share a common parent, but most will not. We were using HAL prior to FDM and HAL would allow us to utilize a Sign Flip Rule for the load to Enterprise, but FDM, as you're aware, works in a considerably different manner.
    For HAL we had a list of high-level accounts that we knew would need to have their sign flipped before loading to Hyperion, and we could use a wildcard to work for this account. For example, when "Accounts" = "CashEquiv*" then "0". Using this method, we were not required to specifically required to identify each individual sub account, rather we could just call out out the first-level account and say that anything that falls below that, should be flipped. Is there any way to do this in FDM? Would it possible to write logic to do this? Individually selecting each tick box for each account is going to take forever.

    There is no out of the box functionality to replicate what you want to do. I suggest you export the account mappings from FDM into excel, manage the sign flip there and re-import to FDM. This will be much faster than doing it via the web interface

  • ??? Sign flip on Attribute using report script ???

    We are using an Essbase report script to extract data that we then process with HAL. Since the system we are loading into uses natural balances, we need to flip the sign on a revenue accounts (have 'Revenue' attribute in Essbase).Is there a way to do the sign flip on data based on the value of an attribute? I could do it once the data is back in HAL, but it would be easier if we could do it on the data extract.Thanks,TomB

    I'm using example 4.
    This is what I have: 
    $UpdateUserAttributesArray = 'sn','givenName','initials','displayName','info','mail','departmentNumber','department','telephoneNumber','ipPhone','title','physicalDeliveryOfficeName','employeeType'
    Function StudentNameChange {
        $Attributes=BuildUserTable $UpdateUserAttributesArray
        Set-ADuser $User.sAMAccountName -Replace @{mail="$User.mail";targetAddress="$User.mail";proxyAddressess="SMTP:$User.mail";sn="$User.sn";cn="$User.sn + $User.givename"}
    $UpdateUserAttributesArray sets the value for the import file.
    StudentNameChange should set the updated value has needed.
    The script runs but no settings are changed.
    Set-AdUser $User.sAMAccountName  -mail $User.mail -surname $User.sn
    Like that.,
    Replace is only for optional attribute.
    Function does not specifi $user so that may also be missing.
    I think you need to spend some time learning the basics of PowerShell. It looks like you are just gluing things together thazt you have found with no understranding of how any of the bits work.
    Try just setting one user at a command prompt until you see how the CmdLet and PowerShell work.  Post single simple questions as you try each parameter.
    # build a test user object
    $user New-Object PsObject@{
    SamAccoutnName='somename'
    Mail='[email protected]'
    SN='lastname'
    GivenName='John'
    proxyAddresses='...<list of addresses>'
    #start like this and add items until you understand what is working.
    Get-AdUser $user.SamAccountName |
    Set-AdUser -Surname $user.sn -GivenName $user .GivenName -Replace @{Mail='$($user.Mail'}
    #use Rename-Object to change CN.
    You need to learn the simple bits before you try to do grand things.
    ¯\_(ツ)_/¯

  • How to Apply sign flipping applied in Bex Query in Web i report

    Hi,
    We have created a universe on top of Bex query and we have applied sign reversal to two of our rows in bex query,
    unfortunately when I run a report in webi the reversal of sign  is not getting reflected in web i report.
    Could any one please help me out in achieving the same  in web i
    Thanks in Advance,
    Any help is greatly appreciated.

    Hi,
    That BEX Property will not be surfaced to the OLAP API
    Same goes for Conditions, Scaling Factor etc.  Please take a look at Note 1387793 - BEx functionality features that are not supported or integrated in WebIntelligence
    Regards,
    H

  • Question about attributes, UDAs, Associations, etc

    Hello,
    In Essbase database (v 9.3.1), can someone tell me the usefulness/benefits of attributes, associations, and UDAs? What can they do/make it easier to do?
    Also in my information tab, I have some fields called variance reporting expense (could be true of false). I noticed that some members have this set to true or false. I wonder what this is for. I don't see the benefit of this extra property/information tied to the level 0 member.
    Thanks in advance.

    Attributes are wondereful things. I don't know if I can do it full justice but here are what I consider to be the highlights:
    1) Attributes come in two flavors: member and dimension. Member attributes are applied as a "flag" to specific members so that these members can be easily grouped in a method outside of the normal hierarchy itself. This is the primary purpose, to take an otherwise ungrouped set of members and give them a means to be readily associated as a group. Dimension attributes are a bit more formal, and should be applied to all members in the dimension (ideally). This applies to a given generation or level, of course. For instance, "all" level 0 members of the time dimension could have an attribute association for the day of week, assuming level 0 are the days of a specific year (or set of...). This would then allow you to say you want the entire Month of May as the time member, but then limit it to Fridays only through the "Day of Week" attribute dimension.
    2) There are some specific things that attributes do well, and some "not so much". For example, all attribute based retrieves are necessarilly done using a dynamic calculation -- there are no precalculated totals. On the previous example, to filter a single year to all Fridays would add the 52 Fridays in the year together at retrieval time to obtain the result. OUCH. However, when leveraged with other tools, this becomes a very powerful capability. For instance, an Organization structure could have an attribute for status (open/closed/etc.), type (center/overhead/field office/etc...), along with several other attributes. Now you can leverage these individually or in groups to "fine tune" your retrieve, by using these "optional dimensions" in a mix and match set which is not otherwise available within a single given dimension.
    3) Expense reporting is best looked up in the DataBase Administrators Guide (DBAG). There are a few easily understood but hard (for me to explain) reasons to use expense reporting, but it mostly boils down to the way expenses are handled for variance analysis purposes. Instead of needing if/then logic to deal with reporting good/bad news variances, expense account flags can make it all be perfectly understood by the finance team.
    I realize that a raw list of features doesn't easily translate into a "when/how/why would you use them", so here are some example scenarios that illustrate when/how/why these items may help:
    - If you need to make an alternate hierarchy based on subsets of members, perhaps UDA's are a better option here?
    - If you have multiple elements of information (attributes!) that relate to most/all of a single dimension, an attribute dimension will generally be better.
    - If you use partitions, attribute dimensions become an issue.
    - If you have a small subset of members that are spread throughout the dimension but need to be related in a different way, your options are pretty much UDA or Alternate Hierarchy.
    - If you do variance reports within the model, tagging expense accounts appropriately will automatically handle the sign flip associated with good news/bad news issues.

  • Generating .trn for mapping "Like"

    Hi guys,
    could you pleasen show me an example to generate a .trn to load mapping rules into an application in FDM? User's guide is not really useful. We need to create a file with the following features:
    Rule Name/     Rule Desc/     HFM Account/Rule Definition/-/Script
    Which are the ones you can find in FDM, to load the mapping scripts in FDM.
    Could you please provide an example?
    Thank you!
    Cheers,
    Lu

    While I won't vouch for every version of FDM, I do know that for 9.3.1 and previous, you absolutely can perform "Like" and "Between" mappings with Ledgerlink files (TRA / TRN).
    You can only specify a few options; however : Source account, destination account, and Description. To signify a sign flip, you put a - in front of the destination account. If you are doing a "Like" or "Between" type rule, the rule name is not specified in the TRA/TRN file, it is system created for you.
    Example as follows :
    1287-01-60-00;Patent; Patent Accumulated Amortization
    2100-01-50-00;-Cash; Cash Sign Flip
    2100*;Cash; Cash (Like Example)
    19??;COGS; Cost of Goods Sold (Like Example)
    1800>1850;Sales;Sales (Between Example)

  • Rollup of Subtraction of Child Entities

    Hello All,
    How can I achieve Roll up of Subtraction of two child entities into Parent Entity.
    for example I have
    A (Parent Entity)
       |--------A&B (Child 1)
       |--------B (Child 2)
    We want to upload summation of A&B trail in Child 1 and only B trail as Child 2 and want to calculate Parent A as Subtraction of both Child 1 & Child 2.
    what are the possible ways to achieve this, please share your views.
    Thanks & Regards.

    Hi,
    Suggest you do a sign flip of data loaded for child B so that when you consolidate A it will give you the required result.
    To still get data of B appearing correctly create reports for B with reverse sign flip in FR.
    Hope this helps.
    Regards,
    Darshana

  • Major differences between BW 2.1C, 3.0B

    Could some one throw some light on the major enhancements in 3.0B compared to 2.1 version of BW?
    Thanks in advance,
    Ram

    There are some of the adv..of 3.0 over 2.1C:
    XML support for reading and writing metadata and data.
    - Web application designer: graphically design and publish web reports and web applications.
    - Open Hub Service for distributing data to other tables/systems on a schedule.
       It supports selection, projection, and aggregation. Integrated into the BW monitor.
    - Process Chains and graphical scheduler for automating complex processes.
       Supports branching, condition testing, etc. Enables you to schedule all admin functions in a graphical, drag-and-drop
       fashion, including extracts, index drops and rebuilds, activating data, compressing, rolling up to aggregates, etc.
    - Transactional ODS objects with read/write API.
    - Transfer rules for hierarchies.
    - Subtree insert and subtree update for hierarchies.
    - Active attributes on hierarchies (sign flip, etc.)
    - Load, stage, and merge master data to ODS.
    - DB Connect Service allows BW to extract data from any DBMS supported by SAP R/3.
    - Formula editor in transfer and update rules to avoid ABAP coding.
    - Toolbox of standard transformations such as substring, look up data in a table, concatenate, offset and length, 
       arithmetic operations, etc.
    - Parallel loading into a single ODS object.
    - Secondary index maintenance for ODS objects built in to BW Admin Workbench.
    - Multiprovider: Use ODS objects, master data, and cubes in a multicube (now called multiprovider.)
    - New InfoSet Concept: join tabular data together and make it available for reporting. You can join ODS objects,
       master data tables, etc.
    - Archiving: Built-in tools to archive data on a schedule using selection criteria.
       Integrated into BW monitor; archived data deleted from InfoCubes and corresponding aggregates. 
       Support for re-loading data from archives as necessary.
    - BW Monitor includes all activities of process chains, open hub service, and archiving.
    - Use multiple hierarchies in a BW query.
    - Use a mix of hierarchies and characteristics on rows or columns in a BW query.
    - Use restricted key figures in a calculated key figure.
    - Generate static, offline web reports.
    - BEx Cell Editor: In queries with two structures, you can now reference cells at the intersections of rows and columns.

  • YTD Rollup in BPC

    Wanted to check with you guys whether measure ‘YTD’ is automatically calculated by the system or we need to write script logic. I am just wondering since we load the data periodically and system should rollup for YTD. To do this whether we need to do some settings?.
    I also read some documents which are talking about creating YTD application. It will not serve my purpose since this setting is required if we load YTD balances instead of periodic.
    Best Regards
    Shesh

    If the question is, is the YTD (and QTD) measure calculated automatically in the application the answer is yes.  All measures in the application are MDX expressions that calculate at runtime when the use requests data.  Normally, applications are periodic meaning the data is loaded monthly (or what ever the base time period is) and then aggregated.  You can create a YTD application where data is loaded YTD but we never do.
    As far as the mechanics, all data is loaded to the fact table as signed data.  That is, credits are negative and debits are positive.  The allows AS to aggreate the parent values by simple addition.  However, you never view signed data in the application.  At the presentation layer, you reference the calculated measures: periodic, QTD, and YTD.  ALL of these are calculated at query time.  For periodic, the measure simply multiplies the signed data value by -1 for accounts that have normal credit balances.  These are accounts that have an ACCTYPE property value ov INC (income) and LEQ (liability/equity).  This makes all numbers present positive if the account balance has a normal balance.
    For QTD and YTD, the calculated measure reference the periodic measure (for sign flip purposes) and then aggregates across time based on the time dimension hierarcy.

  • Importing mapping tables via txt-file

    Hi
    Is it possible to import mapping tables for some dimensions using txt- or csv-file instead of excel-template?

    Yes.
    There is a format called "Ledger Link" which is dirt simple. It is a CSV file that has Source, Target, and Description. If you have a sign flip, you put a - in front of the Target. If instead of explicit map, it is a like, Source is the rule.
    For example......
    110011,3rdPartySales,Third Party Sales
    110021,-ICSales,Intercompany Sales
    11003?,ServiceRevenue,Service Revenue for Accounts starting with 11003 with a length of 6 characters

  • Jexport results not reliable

    Hi,
    We like to use the jexport function to move data across our applications, but it does not appear to be completely reliable. To test - I moved one of our applications to the development environment and started running the same jexport script over and over (20 times only launching after the previous script finishes). Every so often - after maybe 5 or so runs - the export data set is missing some records or we have a record or two where the sign (debit/credit) is flipped. I have tested on different applications and see the same issue. The dataset being produced are pretty small (500k to 1mb) The results and pretty consistant - you get good data about 80% of the time, and about 20% of the time the data set is missing some records or you have a sign flip on a record or two. Has anyone ever seen this before and can you provide any suggestions on resolving? Our outlines are very large (cubes are huge - cube size over 100k) and reports scripts take a very long time to export slices of data where the jexport can run very fast. Any help would be appreciated.
    Thanks!

    I used jExport quite a bit on different versions and never had a problem with it. You might go to the EssbaseLabs blog and post the question there Matt and Toufic are primary contributors to that blog and Toufic created the jexport CDF. I'm am guessing you don't have a 100k cube was that supposed to be 100 gig? That would be a large cube. 100k would be tiny.

  • Variance Reporting problem in Planning

    Hi,
    I am facing an issue in variance reporting in Planning. I have a memeber X (dynamic calc, account type: saved assumption, variance reporting: non expense).   Now member formula of X is @sum(W,Y,-Z). W, Y & Z are expense members. Their variance reporting settings is expense. Now lets say W=5, Y=5, Z=5. So for actual scenario value of X is 5 and for variance scenario it should be 5. But it is coming as -5  because for variance scenario W Y & Z values are -5, -5 & -5. So as per formula X value is (-5-5+5)= -5
    So variance reporting settings of X is overwritten by member formula value. Is there any way to stop this?
    Regards
    SB

    I don't think that's the problem Rahul, it's a calculation order issue.
    I think the current calculation order is:
    1. Variance->W (sign flip occurs), Variance->Y (sign flip occurs), Variance->Z (sign flip occurs)
    2. Variance->X (no sign flip occurs)
    Net result, sign flip.
    What the OP wants is:
    1. Actual->X (no sign flip occurs), Budget->X (no sign flip occurs)
    2. Variance->X (no sign flip occurs)
    Net result, no sign flip.
    If X was a stored member this would 'just work'.  Another option would be to tag X as 'Expense' even though it really isn't.  This would flip the sign back for the Variance scenario only.
    Alternatively, 'roll your own' by writing the formula on 'X' to check for @CURRMBR("Scenario") and perform the extra sign flip when Variance is selected.

Maybe you are looking for