Financial Consolidation and Close

Get Involved. Join the Conversation.

Comments

  • Ligia Olguin

    Hi Mihajlo,

    We had this error in the past. Be sure that the Never Shared is the Data Storage property in Member Properties and Member Formulas.

    Hope this helps.

    Cheers.

    L.

  • Rich Wilkie

    Target is for early 2020 (safe harbor applies).

  • Erin Cerpa

    Hi

    I know this is an old post but what is the status of the enhancement 28405987 since it is now October and it has not been released?  

     

  • Antonio Barbaro

    Hi Elena,

    I used FY43 and FY44 (December Period).

    I verified and until FY38 December the loading process works correctly.

    Do you think that deletion and recreation of Years can solve the problem?

    Regards,

  • Elena Medrano

    Which period did you have previously?

  • Ezra Fishman

    Hi Antonio,

    Have you included the "FCCS_Balance" account in your alternate rollup?

    This account will hold a balance sheet plug once the balancing functionality is activated in your consolidation configuration.

    Additionally, make sure to enable the "Balance the Balance Sheet" system calculation under "Application"->"Consolidation".

    Thanks,
    Ezra

  • Antonio Barbaro

    Sorry,

    I read the log file and I saw that the problem is related to Period.

    I changed the period (from December 44  to January F19) and I have no problem.

    Do you have an idea?

  • Wayne Paffhausen

    Do you have a process details log?  Also maybe try a instance/service restart?  

  • Nouria Kehli

    Hi Antonio

    There is nothing attached

  • Antonio Barbaro

    I created a new hierarchy of Balance Sheet Under FCCS_Balance Sheet (see Attached file) but I have this problem..

    This is very urgent for us.

    Antonio

     

  • KI

    Thank you Wayne.  I had to reorder the SQL VALID_FLAG section and now it works.  It's such an old bug, would be great if it was fixed.

  • Wayne Paffhausen

    Hello Ki,

    It is most likely due to the valid flag not being set to Ignore.  As you have noted this was a bug and you did need to set the valid flag in the #SQL map.  The issue probably comes down to the #SQL not being properly written to make this happen.

    The criteria to set the VALID_FLAG to ignore is always going to be the same as what you used to apply the mapping.  For example:

    CASE WHEN ACCOUNT LIKE '%KI%' AND ENTITY LIKE '%FCCS%' THEN 'IGNORE' END,
    VALID_FLAG = CASE WHEN ACCOUNT LIKE '%KI%' AND ENTITY LIKE '%FCCS%' THEN 'I' ELSE VALID_FLAG END
    

    The VALID_FLAG line is a bit tricky depending on what dimension your map is on and everything else.  If you don't set it to I (for ignore) then you need to set it to the current value of VALID_FLAG.  If you assume any other value you could be also causing the problem you see.

    Hopefully this helps,
    Wayne

  • Ankit kumar Shrivastava

    Hi KI,

    Could you post the screenshot of your #SQL map as well as attach the log(level 5) please?

    Thanks

    Ankit Shrivastava

  • Belmond Facheu

    Thanks for the link Ezra!

  • Tom LeFebvre

    A user with the Power User role does not have any ability to reopen a task.  The Service Administrator is allowed to perform the reopen as they have few functional limitations.  The Schedule Owner is also able to reopen any task within the schedule.

    In system settings, the "Reopen" option allows the users within the task workflow (Assignees & Approvers) to reopen the task based on the task status.

    Is the user in question the schedule owner?