Data validation on extension version

[ArnoldWarhonowicz]

Hi,

We have a standard version and an attached extension version. We use this extension version for currency rate simulations, meaning that in the extension version we only use slightly different currency rates but we do not change / enter any other data. The extension version does not allow LC, TC, QTY changes.

In our validation method we have a rule that checks whether the amount on an fs item across all document types is >= 0. We use this validation rule both for local currency data (task 1080) and group currency data (task 1180). We do this because we have manual posting, i.e. certain document types, in local currency but also in group currency.

We have now come across a case as follows.

The reported (flat file import) amount on a specific fs item in local currency is 100 in the standard version. The converted amount in group currency is 120. On the same fs item we also have a manual journal posted in group currency only of -118. 
=> in the standard version both the local currency and the group currency validation is fine as both amounts are greater than zero (100 in local and 2 in group currency).

In the extension version we have the same reported data and the same manual journal in group currency. However, due to the difference in exchange rate, the 100 local currency are converted to 117 in group currency.
=> in the extension version the validation in converted currency shows an error as the total of reported amount and manual journal is -1 and hence not equal to or greater than 0.

Ideally we would like to disable this validation for the extension version,  is that possible? Or how else could we deal with this situation in order to not receive an error in the data monitor for task 1180?

[lucapaccagnini]

Hi Arnold,

I recommend creating a second validation method by duplicating the one used in the standard version. In this new method, remove any validation rules that are incompatible with the Group Currency Extension version.

Next, open the Assign Validation Method app. First, select the standardized validation task. Then, at the top of the screen, choose your Group Currency Extension version in which you want to change the assigned method. Finally, assign the newly created validation method to that version.

I hope this approach resolves the issue.

Best regards,
Luca

[Eduardo_Lombard]

Hi Arnold,

Just to complement Luca’s approach. To assign different validation methods to different consolidation versions it will be necessary to create a Data Entry Special Version and assign it to your Extension Version

Best Regards

Eduardo

[Eduardo_Lombard]

Hi Arnold, Just to complement Luca’s approach. To assign different validation methods to different consolidation versions it will be necessary to create a Data Entry Special Version and assign it to your Extension Version Best Regards Eduardo

[Eduardo_Lombard]

Hi Arnold,

Just to complement Luca’s approach. To assign different validation methods to different consolidation versions it will be necessary to create a Data Entry Special Version and assign it to your Extension Version

Best Regards

Eduardo

[ArnoldWarhonowicz]

I am not sure I understand this.

[ArnoldWarhonowicz]

I am not sure I understand this. I have my standard version Y10 and the extension version W10. Y10 uses data entry special version Y10, and currently W10 uses the same data entry special version. If I now create a new data entry special version to be used by version W10, would version W10 still show the same local currency values as version Y10?