Forum Stats

  • 3,837,857 Users
  • 2,262,302 Discussions


Import columns from TB for mapping only?

mb1824 Member Posts: 148
edited Jan 24, 2018 3:38AM in Planning and Budgeting


My Source TB has [Account] (usually numeric) and [AccountName] (usually a string).

Sometimes I want to use [AccountName] to map source data to target dimension [Reporting Account] while for other [Reporting Account], I would like to use [Account]

Is this possible? If so, please explain steps.

Thank you in advance!



  • USER1211
    USER1211 Member Posts: 3,104
    edited Jan 24, 2018 1:06AM

    What version of Hyperion(including patch level) are you on or are you cloud?

    What have you design or what is currently in place?

    Also providing an sample example what exactly you are seeking to do allows folks to provide more reasonable recommendations.

  • mb1824
    mb1824 Member Posts: 148
    edited Jan 24, 2018 1:57AM


    Thanks for the comment. I am using Cloud PBCS.

    This is what I have currently done (I didn't know if this would work, I just tried it):

    1. Import Format: I added both [AccountName] & [Account] from the Source TB as columns that target [Account] (note in my original question, I renamed the target [Account] as [Reporting Account]

    PBCS_import format.JPG.

         2. This concatenates [AccountName] & [Account] to give Source-AccountName

    PBCS_data load workbench.JPG

         3. Data Load Mapping: I use type Like, e.g.

        • C/S PARTS WARRANTY*  maps to Warranty C/S
        • *485 maps to Internal C/S

    This gives the right outcome, but any better ideas would be appreciated?

  • JohnGoodwin
    JohnGoodwin Member Posts: 30,471 Blue Diamond
    edited Jan 24, 2018 3:38AM

    That is one way of going about it, alternatively you could create a lookup dimension for account name and then use a multi dimension mapping on account to define whether to use account or account name.



This discussion has been closed.