Oracle 1z0-1054-22 Oracle Financials Cloud: General Ledger 2022 Implementation Professional Exam Practice Test

According to Oracle documentation3, the attribute that needs to be set up on the Manage Values page for chart of accounts segment values so that you can run the Payables to General Ledger Reconciliation Report or Receivables to General Ledger Reconciliation Report is Third Party Control Account. The Third Party Control Account attribute enables you to maintain detailed balances by third party for an account combination. Valid third-party information must be associated with the journal line if the account is a third party control account. General Ledger prevents manual journal entries from posting to third party control accounts. Therefore, option B is correct. Option A is incorrect because Financial Category is not an attribute that affects the reconciliation reports. Option C is incorrect because End Date is not an attribute that affects the reconciliation reports. Option D is incorrect because Start Date is not an attribute that affects the reconciliation reports. Option E is incorrect because Reconcile is not an attribute that affects the reconciliation reports.

“When you publish a tree version, General Ledger creates a flattened version of the tree hierarchy and stores it in a table that Essbase can access. Essbase uses this flattened hierarchy to build dimensions in the balances cube.” Therefore, if the tree version is not published successfully, Essbase cannot access the tree hierarchy.

To achieve the requirement of only single currency journals being entered for this company, you should enable “Limit a Journal to a Single Currency” on both ledger options and journal sources. Ledger options are settings that apply to a specific ledger, such as journal processing options, currency options, and average balance processing options. Journal sources are identifiers that indicate where a journal originated, such as manual entry, subledger accounting, or import. You can enable “Limit a Journal to a Single Currency” on both ledger options and journal sources using the Specify Ledger Options and Manage Journal Sources tasks in Setup and Maintenance. This will enforce single currency journals for journals entered on the Create Journal page and for journals that are imported. You do not need to enable “Limit a Journal to a Single Currency” on journal lookup codes, as these are codes that indicate the status of a journal, such as Entered, Posted, or Reversed. You do not need to enable “Limit a Journal to a Single Currency” on journal category, as this is an attribute that classifies journals by purpose or function, such as Purchase Invoices or Allocations. You do not need to enable “Limit a Journal to a Single Currency” on profile option, as this is a setting that affects the behavior of an application or feature for a user or responsibility. Reference: Oracle Financials Cloud: General Ledger 2022 Implementation Professional Objectives - Define Ledgers 12

https://docs.oracle.com/cd/E25178_01/fusionapps.1111/e20375/F350915AN26721.htm

Oracle’s recommended approach to performing consolidations when you have three balancing segments for generating balance sheets and income statements at cost center segment and program segment levels is to use additional intercompany rules for the two additional balancing segments and additional intercompany balancing and clearing options. Intercompany rules define how intercompany transactions are accounted for across different balancing segments. Intercompany balancing and clearing options define how intercompany balances are eliminated or cleared during consolidation. Therefore, options A and B are correct. Option C is incorrect because you don’t need to run balance transfer programs for this scenario. Option D is incorrect because you don’t need to manually balance the journal entries across all balancing segments for this scenario.

When a purchase order is matched to an invoice, the purchase order encumbrance is released for the matched amount. In this case, the purchase order encumbrance of $2,500 USD will be reduced by $2,100 USD, leaving a balance of $400 USD. The system will not reserve funds for the invoice because it is matched to a purchase order that has already reserved funds. Funds reservation only happens for non-matched invoices or invoices that are matched to a purchase order with no encumbrance. Reference: Oracle Financials Cloud: General Ledger 2022 Implementation Professional Objectives - Process Budget Journals 12

 you need to define journal conversion rules that include subledgers in order to transfer subledger transactions when you set up a secondary ledger using the Manage Secondary Ledger task and selected a data conversion level of subledger. Journal conversion rules define how journal entries are converted from one ledger to another ledger. Therefore, option B is correct. You also need to assign a Subledger Accounting Method to the secondary ledger when you set up a secondary ledger using the Manage Secondary Ledger task and selected a data conversion level of subledger. A Subledger Accounting Method defines how accounting entries are generated for subledger transactions. Therefore, option D is correct. Option A is incorrect because you don’t need to ensure that the Accounting Calendar and Currency are the same as the Primary Ledger when you set up a secondary ledger using the Manage Secondary Ledger task and selected a data conversion level of subledger. You can have different Accounting Calendar and Currency for your secondary ledger. Option C is incorrect because you don’t need to define journal conversion rules that exclude subledgers when you set up a secondary ledger using the Manage Secondary Ledger task and selected a data conversion level of subledger. You need to include subledgers in your journal conversion rules. Option E is incorrect because you don’t need to define Supporting References with balances when you set up a secondary ledger using the Manage Secondary Ledger task and selected a data conversion level of subledger. Supporting References are used to store additional information for journal lines.

According to the Oracle documentation12, the Intercompany Reconciliation Report can be run using an additional currency and conversion rate that converts all amounts into a common currency for comparison (option C). The report also includes ledger balancing lines generated when the primary balancing segment value is in balance, but either the second or third balancing segment values are not (option B). Option A is incorrect because you can drill down to the general ledger journal, subledger accounting entry, and source receivables or payables transaction2. Option D is incorrect because the report displays the intercompany receivables and intercompany payables balances in summary for a period, and any differences between them1. Option E is incorrect because the report does not display clearing company balancing lines2.

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.

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.

According to Oracle documentation1, you should do the following things when you are implementing a multipillar implementation of both HCM Cloud and ERP Cloud: Deploy your chart of accounts, use HCM’s Enterprise Structure Configurator (ESC) first, and use file-based spreadsheet loaders using UCM to mass load and maintain chart of accounts segment values and hierarchies. Therefore, options A, B, and D are correct. Option C is incorrect because you should create your chart of accounts in the following order: value sets, COA structure instance, and then assign values to the value sets. Option E is incorrect because you should use the Rapid Implementation spreadsheet when creating your chart of accounts, not your enterprise structure.

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.

The process will create 3 ledgers based on the information entered in the Companies and Legal Entities tab of the Rapid Implementation Spreadsheet. The process will create one ledger for each unique combination of chart of accounts, accounting calendar, and currency. Since currency is left blank in the Ledger worksheet, the process will use the currency specified in the Companies and Legal Entities tab. The process will create one ledger for US1 with chart of accounts COA1, accounting calendar CAL1, and currency USD. The process will create another ledger for UK1 with chart of accounts COA2, accounting calendar CAL2, and currency GBP. The process will create a third ledger for FR1 and FR2 with chart of accounts COA2, accounting calendar CAL2, and currency EUR. The process will not create separate ledgers for FR1 and FR2 because they share the same chart of accounts, accounting calendar, and currency. Reference: Oracle Financials Cloud: General Ledger 2022 Implementation Professional Objectives - Define Chart of Accounts 12

According to Oracle documentation2, you enable invoicing for certain Intercompany transactions on the transaction type. The transaction type defines the characteristics of an intercompany transaction, such as whether it requires approval, whether it generates invoices, and what accounting rules apply. You can enable invoicing for a transaction type by selecting the Invoicing Options tab and choosing the invoice method, invoice source, invoice batch source, and invoice rule. Therefore, option D is correct. Option A is incorrect because you do not enable invoicing on the transaction batch. Option B is incorrect because you do not enable invoicing on the transaction category. Option C is incorrect because you do not enable invoicing on the transaction source.

General Ledger Cloud supports four methods for entering budget data: entering budget journals, using ADFdi, using file-based data import, and using source budget integration. Direct budget balance updates from a Financial Statement in Smart View is not a supported method for entering budget data. Smart View is a tool that allows you to view and analyze financial data in Excel, but it does not allow you to directly update budget balances. Reference: Oracle Financials Cloud: General Ledger 2022 Implementation Professional Objectives - Process Budget Journals 12

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.

The recommended approach to performing consolidations when all of your subsidiaries reside on the same application instance, but some of them require a different chart of accounts and/or accounting calendar and currency is to create separate ledgers for each subsidiary that shares the same chart of accounts, calendar, currency, and accounting method. Create a separate elimination ledger to enter intercompany eliminations. Then create a ledger set across all ledgers and report on the ledger set. This will allow you to maintain separate ledgers for each subsidiary with different reporting requirements and eliminate intercompany balances using the elimination ledger. The ledger set will enable you to report consolidated balances across all ledgers using General Ledger Cloud reporting tools. You do not need to translate balances to the corporate currency, create a chart of accounts mapping to the corporate chart of accounts, then transfer balances to the corporate consolidation ledger using the balance transfer program, as this is a complex and time-consuming process that involves multiple steps and data conversions. You do not need to translate balances to the corporate currency for ledgers not in the corporate currency, use General Ledger’s Financial Reporting functionality to produce consolidated reports by balancing segment where each report represents a different subsidiary, as this is not a reliable or accurate way to perform consolidations and does not address different charts of accounts or calendars. You do not need to use Oracle Hyperion Financial Management for this type of consolidation, as this is an external application that requires additional integration and maintenance. Reference: Oracle Financials Cloud: General Ledger 2022 Implementation Professional Objectives - Consolidate Balances 12

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

The Delete Translated Balances process deletes all previously translated balances for a given ledger, currency, and period range. After running this process, you must submit the Update General Ledger Balances Cube process to rebuild the balances cube and ensure that the translated balances are consistent with future translations. This process also updates the account hierarchies and dimension members in the balances cube. Reference: Oracle Financials Cloud: General Ledger 2022 Implementation Professional Objectives - Translate Balances 12

The Import Account Combinations process is used to create and/or modify account combinations using a file-based data import (FBDI). The appropriate upload steps are to insert rows into the GL_MULTI_COMBINATIONS_INT table using the FBDI template and then submit the Import Account Combinations process2.