1z0-1054-22 Oracle Financials Cloud: General Ledger 2022 Implementation Essentials Questions and Answers

To add a global branding logo and more predefined transactional attributes to the journal approval email notification, you should copy (or customize) and edit the layout template and the data model. The layout template is a file that defines the appearance and content of the notification, such as text, images, tables, or charts. The data model is a file that defines the data sources and queries that provide data for the notification, such as predefined transactional attributes. You can copy (or customize) and edit the layout template and the data model using Oracle Analytics Publisher reports. You do not need to copy (or customize) and edit the output type, as this is a setting that determines the format of the notification output, such as HTML or PDF. You do not need to copy (or customize) and edit the data source, as this is a component of the data model that specifies where data for the notification comes from, such as an SQL query or an XML file. You do not need to copy (or customize) and edit the sub template, as this is a file that contains reusable content or logic that can be referenced by multiple layout templates. Reference: Oracle Financials Cloud: General Ledger 2022 Implementation Professional Objectives - Configure Workflow Approvals and Notifications 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.

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

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.

cross-validation rules only test new account combinations being inserted into the table. They ignore any invalid account combinations already existing in the table. Therefore, option C is correct. Option A is incorrect because deactivating the value will not prevent further usage of the invalid account combination. Option B is incorrect because cross-validation rules are not assigned to the end user role. They are defined at the chart of accounts level. Option D is incorrect because cross-validation rules do not automatically disable that account code combination.

The Calculation Manager is a tool that enables you to create and manage allocation definitions that can be used to automate the process of creating eliminating entries for intercompany balances. You can use the Calculation Manager to define allocation rules, formulas, drivers, and conditions for your eliminating entries. You can also schedule the allocation definitions to run every period or on demand1.

To add a global branding logo and more predefined transactional attributes to the journal approval email notification, you should copy (or customize) and edit the layout template and the data model. The layout template is a file that defines the appearance and content of the notification, such as text, images, tables, or charts. The data model is a file that defines the data sources and queries that provide data for the notification, such as predefined transactional attributes. You can copy (or customize) and edit the layout template and the data model using Oracle Analytics Publisher reports. You do not need to copy (or customize) and edit the output type, as this is a setting that determines the format of the notification output, such as HTML or PDF. You do not need to copy (or customize) and edit the style template, as this is a file that defines the styles and formatting of the notification elements, such as fonts, colors, or margins. You do not need to copy (or customize) and edit the sub template, as this is a file that contains reusable content or logic that can be referenced by multiple layout templates. Reference: Oracle Financials Cloud: General Ledger 2022 Implementation Professional Objectives - Configure Workflow Approvals and Notifications 12

According to Oracle documentation2, the option you should use to view the supporting reference balances is General Ledger inquiries and reports. Supporting reference balances are maintained at the account combination level for each supporting reference that you define. You can view these balances using General Ledger inquiries and reports, such as Account Inspector, Account Monitor, Smart View, Financial Reporting Studio, and OTBI. Therefore, option D is correct. Option A is incorrect because an Account Group is not an option to view the supporting reference balances. Option B is incorrect because an OTBI analysis is not an option to view the supporting reference balances. Option C is incorrect because a SmartView analysis is not an option to view the supporting reference balances.

 Essbase balances are updated on three occasions: every time you run the batch program called “Update Essbase Balances”, every time you open a new period, and every time journals are posted to the general ledger. The Update Essbase Balances program updates the balances cube with the latest account balances from General Ledger Cloud. You can run this program manually or schedule it to run periodically. When you open a new period, Essbase balances are updated automatically with the opening balances of the new period. When journals are posted to the general ledger, Essbase balances are updated automatically with the posted journal amounts. Essbase balances are not updated every time the tree version is published, as this does not affect account balances. Essbase balances are not updated at report run-time, as this would affect performance and accuracy of reporting. Reference: Oracle Financials Cloud: General Ledger 2022 Implementation Professional Objectives - Use Oracle Transactional Business Intelligence (OTBI) 12

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

, “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

According to the Oracle documentation2, “Control budgets are always absolute to generate encumbrance accounting.” Therefore, this is a true statement regarding the creation of a control budget.

According to the Oracle documentation3, “You can associate a control budget with a different calendar than your accounting calendar.” Therefore, this is also a true statement regarding the creation of a control budget.

According to Oracle documentation2, when defining your AutoPost Criteria to automatically post journal batches imported from subledger sources, you should consider the following aspects: Use the All option for category and accounting period to reduce maintenance and ensure that all imported journals are included in the posting process, and include all of your subledger sources in the AutoPost Criteria. Divide up criteria sets by subledger source only if you need to schedule different posting times. Therefore, options A and C are correct. Option B is incorrect because you should create your AutoPost criteria using as many sources and categories as needed. Option D is incorrect because you can schedule your AutoPost Criteria set to run at any time, not only during off-peak hours.

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 the Oracle documentation34, account hierarchies are defined in Oracle Fusion applications using tree functionality. Each account hierarchy is defined as a tree with one or more versions. You can have only one version of a hierarchy published to the Essbase cube at any time (option A). Child values in these hierarchies can belong to only one parent (option D). Option B is incorrect because hierarchies for reporting and allocations must be published to Essbase cubes5. Option C is incorrect because it contradicts option B.