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

https://www.oracle.com/webfolder/technetwork/tutorials/tutorial/cloud/r13/wn/r13-2018-financials-wn.htm#F4376

you can use the General Ledger - Journals Real Time subject area to drill down from OTBI General Ledger Reports to a General Ledger journal. This subject area provides information about journal entries and journal batches. Therefore, option D is correct. Option A is incorrect because the General Ledger - Journal Transaction Balances Real Time subject area provides information about journal transaction balances by ledger, chart of accounts, and currency. Option B is incorrect because the General Ledger - Journal Balances Real Time subject area provides information about journal balances by ledger, chart of accounts, and currency. Option C is incorrect because the General Ledger - Summary Journals Real Time subject area provides information about summary journals by ledger, chart of accounts, and currency.

you can prevent the closure of the GL period if the corresponding subledger period is not closed by setting the relevant option on the Specify Ledger Options page. You can select the Prevent General Ledger Period Closure When Open Subledger Periods Exist option to enable this feature. Therefore, option B is correct. Option A is incorrect because there is no such option for the offering. Option C is incorrect because this option is not enabled automatically. Option D is incorrect because there is no such profile option.

you can use a report batch to run reports at a specific time to create a set of snapshot reports. A report batch is a collection of reports that you can schedule and run together. Therefore, option B is correct. You can also use Workspace to assemble multiple reports into a book that can be printed and viewed individually or as an entire book. A book is a collection of reports that you can organize into sections and chapters. Therefore, option C is correct. Option A is incorrect because BI Publisher is not an Oracle recommended way to create a month-end reporting package for an upcoming Audit Committee meeting. Option D is incorrect because Smartview is not an Oracle recommended way to create a month-end reporting package for an upcoming Audit Committee meeting. Option E is incorrect because OTBI is not an Oracle recommended way to create a month-end reporting package for an upcoming Audit Committee meeting.

To enable budgetary control for Requisitioning only on Procure-to-Pay Business Functions for business unit one, you need to enable control at purchasing and define the exceptions to only include requisitioning. This will allow budgetary control to check funds availability only when requisitions are created or modified. To enable budgetary control for Payable Invoicing only in Procure-to-Pay Business Functions for business unit two, you need to define control to disable control for Requisitioning, Purchasing, and Receiving. This will allow budgetary control to check funds availability only when invoices are created or modified. You do not need to define budgetary control at ledger level with Budgetary Control Exceptions for each business unit, as this is not a supported option. You do not need to enable control at Requisitioning and define the exceptions to only include invoicing for business unit two, as this will not achieve the desired result. You do not need to disable control for Purchasing, Payable Invoicing, and Receiving for business unit one, as this will not achieve the desired result. You do not need to define budgetary control at ledger level and only encumbrance control at the business units, as this is not a supported option. Reference: Oracle Financials Cloud: General Ledger 2022 Implementation Professional Objectives - Configure Budgetary Control 12

The two true statements regarding cross-validation rules are that you need to run the Cross-Validation Rules process to list and optionally disable combinations that violate rules, and that the rules will validate and apply to new and existing accounts. The Cross-Validation Rules process is a scheduled process that identifies existing account combinations that violate cross-validation rules and optionally disables them. You can run this process after defining or modifying cross-validation rules to ensure data integrity. The cross-validation rules will validate and apply to new and existing accounts, as they are enforced whenever an account combination is created or updated. The rules do not apply to new accounts only, as they also apply to existing accounts. There is no need to run the Cross-Validation Rule Violations process, as this is not a supported option. There is no need to create cross-validation rules if Dynamic Combination Creation Allowed is not enabled for your chart of accounts instance, as this is not a relevant factor. Dynamic Combination Creation Allowed is an option that determines whether users can create new account combinations on the fly or only use predefined combinations. Reference: Oracle Financials Cloud: General Ledger 2022 Implementation Professional Objectives - Define Chart of Accounts 12

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.

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.