15.8.6 Use and Execute the Balance Revaluation Retrospective Management Ledger Process
AFCS will support retrospective revaluation. A retrospective revaluation is one in which the accounting/effective date for which revaluation is performed is prior to the as-of date on which such execution is requested.
To enable this, AFCS revaluation process will accept the following runtime parameters: effective date, as of date, ledger, rule and rate date.
Please note that when revaluation is performed retrospectively, all process pipelines as necessary should also be executed such that the refreshed set of balance figures are reflected and accessible from Results.
Alongside this ability to perform revaluation retrospectively, AFCS will also support multiple executions of revaluation with a given set of runtime parameters. This is intended to ensure that exceptions that necessitate such repeat executions can be supported without any error in Management Ledger outcomes - balance and related movement information.
Considering that change to balance information itself, scope or actions required by rule configuration and rates to be applied collectively determine the set of data that should be processed upon any given execution of revaluation, it is recommended that such re-execution be limited to exceptional circumstances.
AFCS will also support revaluation of a ledger with another as basis, if so configured in Financials Cloud GL and instructed by revaluation metadata obtained by AFCS from said service.
Note:
More than one Balance Revaluation Retrospective Management Ledger process should not be simultaneously executed with the same set of runtime parameters. Refer below table for the list of runtime parameters supported.Note:
When Revaluation Type parameter in Balance Revaluation Retrospective Management Ledger Process is selected as "Revised Balances":- Ensure that revaluation rules in ERP are not modified after the end of prior period until that prior period's adjustment period has concluded.
- Ensure that the exchange rates(as per Rate Date and Rate Version input parameters) used for prior period revaluation is not modified after the end of prior period until that prior period's adjustment period has concluded.
- Ensure that for a given Extraction Date- Effective Date-Ledger-Revaluation Rule Name combination, the remaining input parameters are not changed between multiple intraday executions.
If any of the above conditions are not or cannot be met, for accurate results of revaluation, please select Revaluation Type parameter as "All Balances" in Balance Revaluation Retrospective Management Ledger Process.
- When revaluation is performed on a ledger with another as the basis, AFCS will consistently follow the instructed basis in such metadata irrespective of relative values of Entered and Functional currency codes within basis and revalued ledgers or across the two.
- AFCS will not skip any balance data based on Entered Currency value when revaluation rule metadata advises user configuration of ‘ALL’ currencies for a given rule.
- Multiple revaluation rules for a given ledger should NOT be concurrently executed. Attempts to do so may result in incomplete or incorrect outcomes that may not be reversible.
- Revaluation should only be performed for rules completely configured in the Financials Cloud service instance that AFCS is deployed with.
- Revaluation should be invoked with the Rule Name exactly as configured in the Financials Cloud service instance that AFCS is deployed with.
- Revaluation should be invoked with the following parameters: Ledger, Rule Name, Effective Date, As of Date, Rate Date, Rate Version and Revaluation Type.
- Not more than one revaluation rule for a given ledger should be executed at the same time - as in, if there are three rules for Ledger A, rule 1, rule 2 and rule 3 should be executed strictly in sequence. Not more than one rule per ledger should be executed at any point in time.
- Revaluation may optionally be invoked with a list of Rule Names relevant to a given ledger.
- When invoked with a set of Rule Names the rules will be executed in the sequence they are listed.
- Note that Financials Cloud does not stop revaluation rules for a ledger being configured with overlaps in ranges of code combinations to be revalued.
- Revaluation may also be executed specifically for balance information that has
been revised since immediately prior execution. When attempting this, the
following should be observed:
- Given that this is that amount to re-execution, invocation to achieve this should be with identical run-time parameters.
- The run-time parameter 'Revaluation Type' should be set to 'Revised Balance'.
- All other guidelines for invocation of revaluation also apply when executed solely for balance information that has been revised since immediately prior execution".