You transact in 50 different currencies and you need to define a high volume of revaluation definitions. Which two methods are Oracle recommended best practices
for streamlining this process?
A.
Define separate revaluation definitions for each class of accounts, currency, and different rate types.
B.
Use hierarchies and parent values in your revaluation definition.
C.
Share revaluation definitions across ledgers that share the same chart of accounts.
D.
Define one revaluation definition for all accounts (assuming all ledgers share the same chart of accounts) and simply change the parameters at run time.
Explanation:
http://docs.oracle.com/cd/E15586_01/fusionapps.1111/e20374/F494861AN18482.htm
B,C
B,C
Bakr Reference: Hierarchies and flexible account selection criteria, such as usage of parent values from your account hierarchy, streamlines maintenance of revaluation definitions. The parent values can be selected for the primary balancing and the natural account segments using the is a last descendant of operator. Leveraging hierarchy versions extends your revaluation definitions during organizational changes. Adjust account selection criteria monthly to retrieve the accounts that need to be revalued for the current accounting period.
Share revaluation definitions across ledgers that have the same chart of accounts to reduce maintenance.
B,C
I agree. B, C correct answer
B.
Use hierarchies and parent values in your revaluation definition.
C.
Share revaluation definitions across ledgers that share the same chart of accounts.