Oracle 1z0-1054-22 Dumps

According to Oracle documentation1, the following new features allow the segregation of duties of transferring journals to the General Ledger from the posting function: Uncheck the Enable Posting from the Manage Subledger Accounting Options task, and create separate user defined roles using the privilege XLA_CREATE_GENERAL_LEDGER_AND_SUBLEDGER_JOURNALS. Therefore, options A and C are correct. Option B is incorrect because journal entry spreadsheets are impacted by this new function. Users who create journals using spreadsheets must have the privilege XLA_CREATE_GENERAL_LEDGER_AND_SUBLEDGER_JOURNALS. Option D is incorrect because for previously scheduled automated processes, it is not recommended to cancel and reschedule the process for the option to be effective. The option will be effective for any new processes submitted after unchecking the Enable Posting option.

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.

According to Oracle documentation1, the reason why the general accountant is not able to see the cost center 110 in the List of Values for the Suspense Account is that the general accountant has a segment value security rule assigned which restricts access to that cost center. Segment value security rules enable you to control user access to specific segment values or ranges of values. Therefore, option B is correct. Option A is incorrect because the general accountant does not need the Financials Application administrator role assigned to update the cost center for the Default Suspense Account. Option C is incorrect because there is no primary balancing segment attached to the legal entity of the primary ledger. Option D is incorrect because there is no cross validation rule in place to prevent the resulting combination from being created.

 A secondary ledger is an optional ledger that is linked to a primary ledger for the purpose of tracking alternative accounting representations of the same transactions. A secondary ledger can differ from its primary ledger by one or more of the following attributes: accounting method, chart of accounts, accounting calendar, currency, and journal processing options. A secondary ledger is not used to meet local accounting requirements, as this can be achieved by using reporting currencies or subledger accounting rules. A secondary ledger is not used to maintain balances in a different currency only, as this can be achieved by using reporting currencies or revaluation. A secondary ledger is not used to maintain balances for processing performance, as this can be achieved by using ledger sets or data access sets. Reference: Oracle Financials Cloud: General Ledger 2022 Implementation Professional Objectives - Configure Secondary Ledgers 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.

According to Oracle documentation3, you can opt out of the period close checking feature for these three subledgers by using the lookup ORA_GL_INCLD_STRICT_PRD_CLOSE: Receipt accounting, Receivables, and Assets. The period close checking feature prevents you from closing a General Ledger period if there are any open subledger periods that exist for that ledger. You can opt out of this feature for specific subledgers by using the lookup ORA_GL_INCLD_STRICT_PRD_CLOSE and setting the Enabled flag to No for those subledgers. Therefore, options A, B, and D are correct. Option C is incorrect because Revenue Management is not a subledger that can be opted out of the period close checking feature. Option E is incorrect because Order Management is not a subledger that can be opted out of the period close checking feature.

The Default Date Rule determines how the encumbrance accounting date is derived for transactions that do not have an encumbrance accounting date. The actual accounting date option uses the invoice accounting date as the encumbrance accounting date1. In this case, the invoice accounting date was 4/20/19, so the encumbrance journal for liquidating the purchase order encumbrance was dated 4/20/19 as well.

The two options that allow access to the BI Catalog for creating an Oracle Transactional Business Intelligence analysis are Reports and Analytics and Enterprise Performance Management Workspace. Reports and Analytics is a tool that allows users to access, create, edit, and share reports and analyses using data from various sources, including Oracle Transactional Business Intelligence. Users can access Reports and Analytics from various pages in Oracle Fusion Applications or from Oracle Fusion Cloud Service Console. Enterprise Performance Management Workspace is a tool that allows users to access, create, edit, and share reports and analyses using data from various sources, including Oracle Transactional Business Intelligence. Users can access Enterprise Performance Management Workspace from Oracle Fusion Cloud Service Console or from a web browser. Universal Content Management Workspace is not an option that allows access to the BI Catalog for creating an Oracle Transactional Business Intelligence analysis, as this is a tool that allows users to manage documents and other digital content in Oracle Fusion Applications. Business Process Management Workspace is not an option that allows access to the BI Catalog for creating an Oracle Transactional Business Intelligence analysis, as this is a tool that allows users to monitor and manage business processes in Oracle Fusion Applications. Scheduled Processes is not an option that allows access to the BI Catalog for creating an Oracle Transactional Business Intelligence analysis, as this is a tool that allows users to submit, monitor, and manage scheduled processes in Oracle Fusion Applications. Reference: Oracle Financials Cloud: General Ledger 2022 Implementation Professional Objectives - Use Oracle Transactional Business Intelligence (OTBI) 12

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.

you can define intercompany balancing rules at various levels, such as primary balancing segment, legal entity, ledger, and chart of accounts. The rules are evaluated in the order shown, so the primary balancing segment rule has the highest precedence and the chart of accounts rule has the lowest precedence. Therefore, option B is correct. You can also create a rule for all sources and categories by selecting the source “Other” and the category “Other”1. Therefore, option A is correct. Option C is incorrect because you don’t need to define rules for every combination of specific categories and sources. If no rule is found for a specific combination, then the rule for all sources and categories is used1. Option D is incorrect because you don’t need to set up a chart of accounts rule for every chart of accounts structure. You can set up a rule for a specific chart of accounts or for all charts of accounts1.

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 use two different value sets for the company and intercompany segment because segment value security rules are at the value set level. This allows you to restrict access to specific values within a segment based on the value set assigned to that segment. Therefore, option D is correct. Option A is incorrect because you cannot qualify the same segment as both the primary balancing segment and intercompany segment. Option B is incorrect because you don’t need to define two different charts of accounts for this scenario. Option C is incorrect because you don’t want to share the same value set for the company and intercompany segments if you plan to use segment value security rules for the Company segment.

 When using budgetary control, an open purchase order for $500 USD will have a funds status of Reserved, meaning that funds are reserved for future spending. When an invoice for $300 USD is matched to the purchase order, the purchase order funds status will change to Partially Liquidated, meaning that some of the reserved funds have been liquidated by an invoice. The invoice funds status will be Reserved, meaning that funds are reserved for future payment. Reference: Oracle Financials Cloud: General Ledger 2022 Implementation Professional Objectives - Process Budget Journals 12

According to Oracle documentation3, the subcomponents of a Subledger Journal Entry Rule Set are Journal Line Rules, Account Rules, and Supporting References. A Subledger Journal Entry Rule Set defines how subledger journal entries are created for each event class and event type. A Journal Line Rule defines how subledger journal lines are created for each event class and event type. An Account Rule defines how accounts are derived for each journal line. A Supporting Reference stores additional information for journal lines. Therefore, options C, D, and E are correct. Option A is incorrect because Accounting Date is not a subcomponent of a Subledger Journal Entry Rule Set. Option B is incorrect because Chart of Accounts is not a subcomponent of a Subledger Journal Entry Rule Set.

The Journal Source attribute is used to set the automatic posting criteria for journals from subledgers. You can specify whether to post journals automatically or manually based on their source, such as Payables, Receivables, or Projects4.

you must assign the job role and data security context to each user after you submit the Accounting Configuration. This enables users to access the ledger and perform tasks based on their roles. Therefore, option D is correct. A Data Access Set with full read/write access to the ledger is automatically created after you submit the Accounting Configuration. This allows users to enter and post journals to the ledger. Therefore, option B is correct. Option A is incorrect because you don’t need to re-deploy the chart of accounts after you submit the Accounting Configuration. Option C is incorrect because you don’t need to define a Data Access Set to obtain full read/write access to ledgers in the Accounting Configuration. A Data Access Set is automatically created for you.

According to Oracle documentation1, the most efficient way to update your existing cross-validation rules when you have redesigned your chart of accounts is to use Cross-Validation Rules Import file-based data import (FBDI). FBDI enables you to import cross-validation rules from a spreadsheet template into General Ledger. You can use FBDI to create new rules, update existing rules, or delete rules. Therefore, option C is correct. Option A is incorrect because using the Manage General Ledger Security page does not enable you to update cross-validation rules. Option B is incorrect because creating Cross-Validation Rules desktop-integrated spreadsheet does not enable you to update cross-validation rules. Option D is incorrect because using the Manage Cross-Validation Rules page does not enable you to update cross-validation rules efficiently.

The two valid Data Access Set types are Full access and Read Only access. A Data Access Set is a security feature that defines the access level that users have to ledger data, such as balances, budgets, or journals. A Data Access Set type is an attribute that determines the type of access that users have to ledger data within a Data Access Set. The two valid Data Access Set types are Full access and Read Only access. Full access allows users to view and enter data for ledger data within a Data Access Set. Read Only access allows users to view but not enter data for ledger data within a Data Access Set. Full Ledger is not a valid Data Access Set type, but an option that determines whether a Data Access Set grants access to all balancing segment values in a ledger or only specific balancing segment values. Primary Balancing Segment Value is not a valid Data Access Set type, but an attribute that identifies the legal entity or business unit for which financial statements are prepared and balanced. Read and Write access is not a valid Data Access Set type, but an alternative term for Full access. Reference: Oracle Financials Cloud: General Ledger 2022 Implementation Professional Objectives - Define Ledgers 12

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.

To enable users of the income statement report to analyze the balances directly from the report, you should enable Drill Through in Grid Properties. This option allows users to drill down from summary balances to journal details and subledger transactions using Smart View or Financial Reporting Web Studio. You do not need to enable anything else, as all reports are drillable by default if Drill Through is enabled in Grid Properties. You do not need to enable Drill Down in Report Functions, as this option allows users to drill down within a report using different dimensions and hierarchies, but not to originating transactions. You do not need to enable Allow Expansion in Report Functions, as this option allows users to expand or collapse members within a report using different dimensions and hierarchies, but not to originating transactions. Reference: Oracle Financials Cloud: General Ledger 2022 Implementation Professional Objectives - Create Financial Reports 12