Financial Consolidation and Close

Get Involved. Join the Conversation.

Comments

  • Girish Joshi

    Under "Exchange Rate Form - Multi Period" you can change the POV as per the your requirement and when you move the SEK to POV then at EUR you have to input 10.6315. I am not sure why the  translation is not working as per the updated FX rate.

    Do you have any SR raised with Support? If yes, can you let me know the SR number, I would take a look.

  • Luis

    You should be able to use ismbr to identify the year within the rule is running.

    E.g.:

    IF(@ISMBR("FY19"))

    /* rule applied in 2019 */

    ELSE

    /* rule applied in other years */

    ENDIF

     

    Check on @RSIBLINGS / @LSIBLINGS functions so you can create a IF that supports your scenario.

     

    Regards,

    Luis

  • Carolina Silva

    I already tried this. I only deployed this specification rule, all the others were undeployed.

    I have the same issue. So the problem is in this rule.

  • Joona Knuuti

    Thanks for the suggestion, but if I enter the exchange rates to "Exchange Rate Form - Multi Period" with SEK in the page and EUR in the rows, the system translations do not seem to function even after running the ComputeRates. EOM rate entered to the form this way would be 10.6315, which is what we would like wish to be able to input as the rate. Translations seem to function only if rates are entered with EUR in the page and other currencies in the rows.

  • Keith Glide

    This issue is expected to be fixed in the 19.11 release, subject to successful QA testing (all usual caveats apply).

  • Dishil Shah

    Hello,

    Can you check when you don't deploy any rules then how much it is getting eliminated? Because here it may possible that whatever you are specifying in rules are addition to the same. So without deployed rules it is already eliminating 20 and now after the rules it is eliminating 500 more to the same.

  • Girish Joshi

    You can change the POV of the "Exchange Rate Form - Multi Period" to achieve it. For example: if you want to enter the FX EUR 1 = SEK 10.6315 than EUR should be at POV and SEK in page and enter 0.106315 rate in EOM as I believe this is EOM rate which you want to load/update. For "Single period" form, FX rates always targeted to application currency for example: if the default application currency is EUR, than the default POV at the back-end always set to EUR.

     

    .

  • Carolina Silva

    The SR number is: 

    SR 3-20978954471 : Error: Intercompany Source cannot be empty when Partner Factor/Condition is defined

    Thanks,

  • Keith Glide

    Thank you, please advise of the SR number.

  • Carolina Silva

    Thanks for the help.

    I already created a SR and updated it with this information.

     

     

  • Keith Glide

    This issue has already been identified internally and is being worked on. When you raise your SR, please refer the Support Analyst to bug 30302533 - FCCS - INVALID MEMBER(S) FOUND IN RULESET - INTERCOMPANY CANNOT BE EMPTY WHEN PARTNER USED AS FACTOR.

  • Luis

    Hi,

    Translation replacement with a redirection should give exactly this feature. On the configurable consolidations you should be able to do it also using the eliminations to transfer this amount.

    With the logic that you seems to be implementing you may have to change the logic.

    With restricted members you can use it on the right side of the formula but not on the left side as well.

    So something like bellow code should work.

     

    FIX (/*DIM:Account*/"240000"
    /* your other fixes should be added here */
    )
    "New_FX_movement"(
    "New_FX_movement" = "FCCS_Mvmts_FX_Movement" * -1

    )
    )

    ENDFIX

    FIX (/*DIM:Account*/"24DC"
    /* your other fixes should be added here */
    )
    "New_FX_movement"(
    "New_FX_movement" = "240000"->"FCCS_Mvmts_FX_Movement"

    )
    )

    ENDFIX

    Note that use the features like the translation override should work better depending on your scenario as there are some restrictions on the execution of custom rules when doing the translation for reporting currencies. (it is not executed when there is no translation for the a parent - e.g.: children USD, Parent USD while doing a reporting translation for the children to GBP as reporting currency, currently FCCS does not support customizations for this kind of translation)

     

  • Luca Scarpa

    Hi Mihajlo

    Not exactly sure as to why, but I have had similar issues before. Have you tried clearing the Exchange Rates for RSD to EUR, re-type it in, save and Compute Rates.

    Your SER050 entity should get impacted at Entity Currency. Consolidate first and then Translate to EUR.

    Alternatively, you could enter a small number into a cell for that entity at Entity Currency, then Consolidate and Translate.

    Give it a try.

    Luca

     

  • Luca Scarpa

    Hi Iqbal

    Please check your scenario settings and makes sure Start Year and End Year fields include the time range you need, i.e. FY18 to FY30.

    The issue also could be related to the Entity Approval status on Not Started. Go into Manage Approval and make sure your entity is on Unlocked status.

    Regards

    Luca

     

  • Keith Glide

    Carolina,

    When the Partner Consolidation % is selected as the factor, the system needs to ensure that there is a partner in each source data-point from which to look-up the information. However, your Inter-company dimension consolidation string filter should prevent any data-points without a partner from being included in the data being processed so this looks like a bug.

    Please raise an SR with Support with a reproducible use-case and we will have the developers take a look.