GLCRVL Revalue Balances Completes with "No Revaluation Journal Entries Were Created" (Doc ID 457032.1)

Last updated on DECEMBER 31, 2022

Applies to:

Symptoms

Revaluation was run and it completed normally. The batch created from the first run was reversed, new activity was entered, and then Revaluation run a second time, which completes with the following warning.

ERROR

Output: 
No revaluation journal entries were created. Balances have already been converted at the revaluation rate.

OR, for R12: 

No revaluation journal entries were created. Balances may have already been converted at the revaluation rate, or you may have insufficient access to the ledger, balancing or management segment value you are attempting to revalue.

Logfile: 

ORA-01403: no data found

CRVL0015: No revaluation records were found.

STEPS TO REPRODUCE
The issue can be reproduced at will with the following steps:
1. Navigate to responsibility pointing to primary set of books/ledger
2. Navigate to concurrent requests.
3. Run GLCRVL Program - Revalue Balances, for a period, for a range of accounts.
4. Post the batch.
5. Reverse the batch.
6. Post the reversal.
7. Enter new transaction activity in a different currency in the primary set of books/ledger
8. Run GLCRVL Program - Revalue Balances again.

When there is activity, i.e. new journals posted to a code combination ID or the exchange rate for the period changes, or the existing revaluation journal is reversed and the reversal is posted, then the the translated_flag on gl_balances for that code combination gets set to 'R'. This means that the code combination can be picked up again by the revaluation program.

Changes

Cause