These are some of the objectives that must be considered when designing the chart of accounts, according to Oracle documentation1. Anticipating growth and maintenance needs as organizational changes occur helps to design a flexible and scalable chart of accounts that can accommodate future business requirements. Effectively managing an organization's financial business requires a chart of accounts that can provide accurate and timely financial reporting and analysis. Considering implementing a single, global chart of accounts can simplify consolidation and standardization across multiple ledgers and currencies.

According to Oracle documentation2, what happens to funds available when you cancel an invoice that requires budgetary control is that the budget and funds available will increase by the invoice amount. When you validate an invoice, the budget and funds available are reduced by the invoice amount. When you cancel an invoice, the budget and funds available are restored by the invoice amount. Therefore, option D is correct. Option A is incorrect because funds available will change when the invoice is canceled, not when it is approved. Option B is incorrect because the funds reserved for the purchase order are not affected by the invoice cancellation. Option C is incorrect because the budget will increase by the invoice amount, not decrease by it.

, "Encumbrance accounting is a method of accounting for funds that have been reserved for specific purposes. Encumbrance accounting enables you to track funds that have been committed but not yet spent." When a purchase order is created and reserved successfully, an encumbrance is created on the purchase order and reduces the funds availability. The encumbrance created on the purchase order can go back to the budget or funds

you can override the default accounting attribute assignment at the journal line rule level. A journal line rule defines how subledger journal lines are created for each event class and event type. Therefore, option C is correct. Option A is incorrect because a journal entry rule set defines how subledger journal entries are created for each event class, not how accounting attributes are assigned. Option B is incorrect because an event type defines a business operation that triggers accounting, not how accounting attributes are assigned. Option D is incorrect because a journal entry defines a set of subledger journal lines that are created for an accounting event, not how accounting attributes are assigned. Option E is incorrect because an event class defines a category of business transactions that have similar accounting impact, not how accounting attributes are assigned.

To configure the Intercompany Provider and Receiver distribution accounts to be created automatically for all intercompany transactions, you should configure the intercompany transaction type default accounts. Intercompany transaction types define the default accounts for intercompany receivables and payables for each combination of provider and receiver business units. You can also specify other attributes such as tax classification codes, payment terms, and invoice options for intercompany transactions. You do not need to configure a Provider and Receiver distribution set, as this is not a supported option. You do not need to configure the AutoAccounting Definition, as this is a feature that determines how revenue and receivable accounts are derived for Receivables transactions. You do not need to configure the Transaction Account Definition, as this is a feature that determines how subledger journal entry accounts are derived for subledger transactions. Reference: Oracle Financials Cloud: General Ledger 2022 Implementation Professional Objectives - Configure and Process Intercompany 1