According to Oracle documentation3, Oracle's recommended method to define a chart of accounts that includes an intercompany segment when your customer plans to use segment value security rules for the Company segment is to share the same value set for the company and intercompany segments. Sharing the same value set enables you to use segment value security rules for both segments and ensures that the values in both segments are consistent. Therefore, option B is correct. Option A is incorrect because defining the intercompany segment with a default value does not enable segment value security rules for the intercompany segment. Option C is incorrect because defining the company segment and assigning both the primary balancing segment and intercompany segment labels does not enable segment value security rules for the intercompany segment. Option D is incorrect because creating two different value sets for the company and intercompany segments does not ensure that the values in both segments are consistent.

The process that allows you to change the qualifier back to cost center qualifier after a consultant accidentally designated the cost center segment as the natural account is to change and save the segment qualifier. You can change the segment qualifier using the Manage Chart of Accounts Structures task in Setup and Maintenance. You can only change segment qualifiers before deploying flexfield metadata changes for validation and activation. You do not need to create a new chart of accounts, as this is not necessary and will increase complexity and maintenance. You do not need to delete the segment and create a new segment with the correct qualifier, as this will affect existing values and journals. You do not need to delete the chart of accounts and create a new one, as this will affect existing structures and instances. Reference: Oracle Financials Cloud: General Ledger 2022 Implementation Professional Objectives - Define Chart of Accounts 12

According to Oracle documentation4, when you have a subsidiary company in a highly regulated country where there is a legal requirement to produce fiscal reports under local GAAP, you should configure the ledgers using these two ledger types: a primary ledger with the local accounting convention, and a secondary ledger with the IFRS accounting convention. A primary ledger represents your main accounting books that comply with local GAAP. A secondary ledger represents an alternative accounting representation that complies with IFRS. Therefore, options A and D are correct. Option B is incorrect because a reporting currency with the IFRS accounting convention does not represent an alternative accounting representation. Option C is incorrect because a primary ledger with the IFRS accounting convention does not comply with local GAAP. Option E is incorrect because a reporting currency with the local accounting convention does not represent an alternative accounting representation.

According to Oracle documentation3, the following statements are true regarding the Intercompany Reconciliation Report: This report can be run using an additional currency and conversion rate that converts all amounts into a common currency for comparison, and this report includes ledger balancing lines generated when the primary balancing segment value (BSV) is in balance, but either the second or third BSVs are not. The Intercompany Reconciliation Report enables you to reconcile your intercompany receivables and payables accounts, and identify any missing transactions. This report is automatically generated when you run the Prepare Intercompany Reconciliation Information process. Therefore, options B and D are correct. Option A is incorrect because you can drill down to the general ledger journal, subledger accounting entry, and source receivables or payables transaction. Option C is incorrect because this report displays both the reconciled and unreconciled transactions. You can use automatic reconciliation or manual reconciliation to reconcile the unreconciled transactions.

According to Oracle documentation2, when you want to achieve multi-step cascading allocations, you should use RuleSets. RuleSets enable you to group multiple allocation rules together and run them in a specific sequence. You can use RuleSets to perform cascading allocations, where the output of one rule becomes the input of another rule. Therefore, option A is correct. Option B is incorrect because formulas are used to define the calculation logic of allocation rules, not to group them together. Option C is incorrect because point of view (POV) is used to define the scope and context of allocation rules, not to group them together. Option D is incorrect because general ledger journal entries are used to record the results of allocation rules, not to group them together.
Reference:
html#FAIGL990115