3 Replies Latest reply: Aug 16, 2013 3:15 PM by JDN RSS

    Getting Invalid Intersection for Account with net 0 balance

    MarkSmith_FDM

      Hi FDM Gurus,

       

      We are getting an invalid intersection error for an account that nets to zero in the validate step, because the individual amounts that net to zero are coming in from the source system without an ICP member (hence mapping to ICP None).     The account in HFM is an "IsICP", so ICP None is invalid (is blocked for input by a rule).

       

      The individual amounts in the import section include 2 source accounts that are mapped to the same account, and also mapped to the exact same dimension members for that HFM account:

      E00210 B420199 [ICP NONE] NORF NOFUNC FDMLOAD NOC4 <ENTITY CURRENCY>    1000

      E00210 B420199 [ICP NONE] NORF NOFUNC FDMLOAD NOC4 <ENTITY CURRENCY>   -1000

       

      In the validate step, the data is condensed into 1 line, with a zero balance.

      E00210 B420199 [ICP NONE] NORF NOFUNC FDMLOAD NOC4 <ENTITY CURRENCY>   0

       

      Here is the invalid intersection report.   Interestingly, only 1 of the 2 offsetting accounts (one with the negative balance) shows up in the report:

      Detail Dimensions:

      FM Entity FM Account ICP NOE_RF Function DataType C4 Data Value Amount

      E00210 B420199 [ICP NONE] NORF NOFUNC FDMLOAD NOC4 <ENTITY CURRENCY>   -1000

       

      Does anyone know how to avoid this issue?   We tried to post a journal for each line item in which we tried to 'back out' the source system amount (offsetting entry) and  included another entry with a valid ICP member.   But we still get the invalid intersection error.

       

      Is there a way to fix this (short of doing something in the import script to prevent data from importing, which we prefer not to do)?

       

      Thanks,
      Mark

        • 1. Re: Getting Invalid Intersection for Account with net 0 balance
          JDN

          Since these source accounts are being mapped to an IsICP account in HFM wouldn't it be easiest to apply an ICP mapping to those two accounts and then it wouldn't kick out?

          • 2. Re: Getting Invalid Intersection for Account with net 0 balance
            MarkSmith_FDM

            Thanks for the reply.          Actually, in this situation, the source data is coming in with an ICP partner (999) that is mapped ato [ICP None].    It's an exceptional case where the source data in this account contained an ICP partner that we already have mapped to ICP None, and it was not possible to go back and change the source data. BUT the source account has to be mapped to an IsICP account in HFM (one-off situation).

             

            So we posted the journal to try to zero out the balance, and make additional entry in the journal to manually move the balance to an ICP partner.

             

            I would think if the balance is 0.00 in the account, it would not try to validate the intersection in HFM.   But it seems to be validating based on each individual source account, although they net out to zero in total for the HFM account.

             

            I'm not sure if there is much we can do here.  Just hoping maybe someone had run into the issue and could share how they resolved it...

            • 3. Re: Getting Invalid Intersection for Account with net 0 balance
              JDN

              Okay, that makes more sense as why a simple mapping won't fix this.  While I've never run into this the only two suggestions I might have to avoid writing a script would be on the account map to map these two source accounts to "Ignore" (that's assuming they will always net to 0 in the future).  And if that doesn't work, then maybe you would explore using logic accounts to aid in changing the ICP for mapping purposes.

               

              Regards,

              Jason