To view high-level profit and loss results for each ledger in the Close Monitor, you need to associate a Financial Reporting Web Studio report with the ledger set. This report should be based on the General Ledger Balances cube and should include the Income Statement account group as a row dimension. The report should also have the ledger set as a point of view dimension and the period and currency as user prompts. This way, you can select the ledger set, period, and currency when you run the report from the Close Monitor and see the aggregated income statement results for each ledger and consolidation node in the ledger set hierarchy. References: Overview of Close Monitor, Using General Ledger, Close Monitor Issue

If you use insert in the spreadsheet to load the monthly historical rates by using FBDI, the existing historical rate for a specific ledger, currency, account combination, and accounting period will be replaced by the new rate. This is because the insert action will overwrite the existing rate with the new rate in the GL_HISTORICAL_RATES_INT table. If you want to preserve the existing rate, you should use update or delete actions instead. References:

How Historical Rates Import Data Is Processed, Section: Use the Historical Rates Import file-based data import (FBDI) template to import historical rates from external and legacy sources to Oracle General Ledger

Import Historical Rates, Section: Details

Entering Historical Rates, Section: Entering Historical Rates

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.