Planning

Get Involved. Join the Conversation.

Topic

    Nicholas Mann
    Transfer Salary from OEP_WFP to OEP_FS GL Account - EPBCSAnswered
    Topic posted August 9, 2018 by Nicholas MannRed Ribbon: 250+ Points, tagged Financial Planning, Integration, Workforce 
    338 Views, 17 Comments
    Title:
    Transfer Salary from OEP_WFP to OEP_FS GL Account - EPBCS
    Content:

    Hi Everyone,

    Within EPBCS, we used our own Chart of Accounts and therefore need to map the accounts from WFP to FS, so that the data can transfer correctly.

    The Benefits, Earnings, and Taxes wizard allowed us to map each of those items to the respective GL Account via the Total Compensation Rollup which dictates the Financial Accounts Smart List.

    The question then becomes: how do we map the Salary account from WFP to our Salary GL Account in FS?

    One custom route could be to create a Data Map that aligns the salary account and other associated dimensions from WFP to the salary account in FS, but we wanted to see if there is an easier way to do this that we are simply not seeing.

    Thanks,

    Nicho

    Best Comment

    Tejas Patel

    Hi Nicho,

    Firstly, add the salary account as shared member under OFS_FinStmt Integration hierarchy.

    Secondly, create a new data map and push the "OWP_Basic salary" to the salary accounts.

    Please see attach screenshots.

    Thanks,

    Tejas

     

    Comment

     

    • Tejas Patel

      Hi Nicho,

      Firstly, add the salary account as shared member under OFS_FinStmt Integration hierarchy.

      Secondly, create a new data map and push the "OWP_Basic salary" to the salary accounts.

      Please see attach screenshots.

      Thanks,

      Tejas

       

      • Tejas Patel
      • Anthony Manfredi
         The new data map needs to be in the financials cube if you use this approach. Since the OOB data maps will use the mapping in the OWP_Financial Account to map the financial account. One other method I have done is write a simple rule to change the mapping in OWP_FINANCIAL Account. Run that rule before sending it over to the financial cube.
    • Mark Rinaldi

      It is a known issue that the out-of-box Data Maps from Workforce to Financials don't work when BYOCOA in Financials is used.  Use the workaround as suggest above.  Safe Harbor, this is on near-term road map to resolve.

    • Nicholas Mann

      Great, thank you both for the info!

      -Nicho

      • Arun Raj

        There is no need to have the Salary Account defined under OFS_Total Compensation Parent. This is because in the data map you are directly mapping OWP_Basic Salary to the Salary account in FS.

        For Taxes, Benefits and additional earnings you need to add the accounts under OFS_Total Compensation Parent.

        If you do add the Salary Account to OFS_Total Compensation Parent, make sure to run the data maps in the below sequence:

        • Taxes and Benefits 
        • Salary

        Thanks,

        Arun

         

    • Tino Tarantino

      I've encountered the same issue on my last two projects.  As Mark pointed out, the issue only occurs when BYOCOA is used in Financials.   On my project, I'm also using BYOCOA for Financials.  However,  I developed a different workaround to this issue that doesn't involve the use data maps.    My approach was to provided a way for the user to configure a Financial Account for base salary similar to the way users configure the financial accounts for other components of pay (via the Benefits and Tax Wizard).    The attached word doc contains the details of my workaround.

      • Anthony Manfredi

        This is interesting.  Grade to financial account is not what I would expect but I like it.  I have a client that uses employee type to dictate if the salary is mapped as part of margin or not on the financial pnl.  That is why the rule changing the mapping gave me the most flexibility.    

        Its great that we have 3 possible solutions, I would weigh the clients use case verse the number of customizations they feel comfortable with.

         

        Ultimately Mr. Rinaldi will have to evaluate what will be out of the box!!  No pressure! 

         

         

        • Mark Rinaldi

          Safe Harbor, we are likely aligning with the mapping approach using Salary "Grades" or whatever you load in that hierarchy.  We are working through some details now.  Stay tuned but I'm happy to hear if there is a consensus as to how the field wants the default behavior to work.

    • Tino Tarantino

      I choose Salary Grade because it provided a natural link to base salary.   Salary Grade is a good default option to establish the linkage to Financial Account.    However, as part the solution,  users should also be given a simply way to override this default.   This is why I extended the data load template for base salary to allow users to override the default Financial Account.    I think it's pretty common for the Salary Account to be driven by some type of employee, position, or job property.   If this is the case, users can simply provide the Financial Account as part of their data load.

    • Krishna Sangli

      Hi,

      I was trying to use the approach of adding the accounts under the parent "OFS_Workforce FinStmt Integration" but the "Add child" feature is disabled.

      Has anyone faced the same issue earlier.

      Thanks

       

       

       

       

      • Nicholas Mann

        Hi Krishna

        You'll have to add any children under the "OFS_Total Compensation" member (which is the child of "OFS_Workforce FinStmt Integration")

        Thanks,

        Nicho