According to Oracle documentation1, the following statements are true regarding the Translation process:
Any resulting offset from the translation is entered in the Cumulative Translation Adjustment account, and if necessary, before submitting the Translation process, the Revaluation process should be completed. The Translation process enables you to translate balances from one currency to another for reporting purposes.
The Translation process calculates any difference between the translated balance and the entered balance and posts it to the Cumulative Translation Adjustment account. The Revaluation process enables you to adjust balances denominated in foreign currencies to reflect current exchange rates. The Revaluation process should be completed before the Translation process to ensure that the balances are accurate. Therefore, options A and B are correct. Option C is incorrect because the Translation process should be run after posting Period Close adjustment entries. Option D is incorrect because the Translation process can be used for translating the balances of primary ledgers, secondary ledgers, and reporting currencies. Option E is incorrect because the Translation process can be used to translate both balance sheet accounts and income statement accounts.

According to Oracle documentation3, when using FBDI template to load Chart of Account Mapping Rules for their Primary and Secondary ledgers, you can create, update, and delete account rules for a chart of accounts mapping, and you can create, update, and delete segment rules for a chart of accounts mapping. FBDI enables you to import chart of accounts mapping rules from a spreadsheet template into General Ledger. You can use FBDI to manage both account rules and segment rules for a chart of accounts mapping. Therefore, options C and D are correct. Option A is incorrect because you can download the template from other pages besides the Manage Chart of Accounts Mappings page. Option B is incorrect because FBDI does not support external integration using REST services.

According to Oracle documentation1, the most efficient way to update your existing cross-validation rules when you have redesigned your chart of accounts is to use Cross-Validation Rules Import file-based data import (FBDI). FBDI enables you to import cross-validation rules from a spreadsheet template into General Ledger. You can use FBDI to create new rules, update existing rules, or delete rules. Therefore, option C is correct. Option A is incorrect because using the Manage General Ledger Security page does not enable you to update cross-validation rules. Option B is incorrect because creating Cross-Validation Rules desktop- integrated spreadsheet does not enable you to update cross-validation rules. Option D is incorrect because using the Manage Cross-Validation Rules page does not enable you to update cross-validation rules efficiently.
According to Oracle documentation2, you should create a Data Access Set that allows access to the UK Ledger to allow users with the General Accountant job role to access the UK Ledger. A Data Access Set is a security feature that defines the ledgers and balancing segment values that a user can access. You can assign Data Access Sets to users or roles using the Manage Data Access for Users page. Therefore, option B is correct. Option A is incorrect because assigning the security context value of UK Ledger to the user/role combination does not enable access to the ledger. Option C is incorrect because assigning the General Accounting Manager role to those users does not enable access to the ledger. Option D is incorrect because assigning the UK reference set to the user/role combination does not enable access to the ledger.

A primary ledger is the main ledger for a legal entity or business unit that records all accounting transactions and maintains the accounting balances. A secondary ledger is an optional ledger that is associated with a primary ledger and maintains accounting balances in a different accounting representation. A reporting currency is an optional currency that is associated with a primary ledger and maintains accounting balances in a different currency. In this scenario, the subsidiary company needs to produce fiscal reports under local GAAP and local currency, as well as report to the parent company using IFRS and not local currency.
Therefore, the subsidiary company should configure a primary ledger with the local accounting convention and local currency, and a secondary ledger with the IFRS accounting convention and not local currency. A reporting currency with the local accounting convention or the IFRS accounting convention would not meet the requirement, as it would only maintain balances in a different currency, not a different accounting representation. A primary ledger with the IFRS accounting convention would not meet the requirement, as it would not comply with the local GAAP. References:
Oracle Financials Cloud Implementing Enterprise Structures and General Ledger, Chapter 2: Ledgers, Primary Ledgers, Secondary Ledgers, and Reporting Currencies Oracle Financials Cloud Using General Ledger, Chapter 1: Introduction, Ledgers and Subledgers, Primary Ledgers, Secondary Ledgers, and Reporting Currencies