1z0-1054-23 Practice Exam Questions with Answers Oracle Financials Cloud: General Ledger 2023 Implementation Professional Certification

The Intercompany Reconciliation report is a tool that helps you reconcile your intercompany transactions and identify any discrepancies between the provider and receiver sides. The report shows the entered or transaction amount of the accounting entries booked to the intercompany receivables and payables accounts for a pair of provider and receiver legal entities. The accounted amounts may be different when the conversion rates used for the intercompany receivables and payables are different. Therefore, you can run the report using an additional currency and conversion rate that converts all amounts into a common currency for comparison. This option helps you manage the currency risk and the conversion rate fluctuations for intercompany transactions. The report also displays the intercompany receivables and payables balances in summary for a period, and any differences between them. You can drill down on the links to view the balances by source and then by journal lines. You have full drill-down capabilities to the general ledger journal, subledger accounting entry, and source receivables or payables transaction. References:

• Intercompany Reconciliation
• Intercompany Reconciliation Reports

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.

According to Oracle documentation2, you should create a Data Access Set that allows access to the UK Ledger to allow users with the General Accountant job role to access the UK Ledger. A Data Access Set is a security feature that defines the ledgers and balancing segment values that a user can access. You can assign Data Access Sets to users or roles using the Manage Data Access for Users page. Therefore, option B is correct. Option A is incorrect because assigning the security context value of UK Ledger to the user/role combination does not enable access to the ledger. Option C is incorrect because assigning the General Accounting Manager role to those users does not enable access to the ledger. Option D is incorrect because assigning the UK reference set to the user/role combination does not enable access to the ledger.

The adjustment only level is the data conversion level that ensures only manual journals will be entered in the secondary ledger. This level means that no data is copied from the primary ledger to the secondary ledger automatically. Instead, the user can enter manual adjustments in the secondary ledger to reflect the differences between the two accounting standards. This level is suitable for scenarios where the accounting methods or charts of accounts are very close between the primary and secondary ledgers, and there is no need to maintain detailed journals or subledger transactions in the secondary ledger. References: Primary Ledgers, Secondary Ledgers, and Reporting Currencies, High Volume Data Migration Considerations for General Ledger, Reporting Currencies - Conversion Level Balance

 Intercompany processing will balance a journal using the accounts identified here for the UK Ledger when the journal is balanced by the primary balancing segment value (BSV) but not by second or third BSV. A BSV is a segment in the chart of accounts that identifies a legal entity or business unit for which financial statements are prepared and balanced. A primary BSV is required for every ledger and is used to balance journal entries within a ledger. A secondary or tertiary BSV is optional and is used to balance journal entries across different dimensions otherthan the primary BSV, such as fund or region. Intercompany processing is a feature that enables intercompany transactions between different legal entities or business units within the same enterprise. Intercompany processing uses intercompany balancing rules to generate intercompany receivables and payables accounts for cross-ledger or cross-BSV journals. Intercompany processing will balance a journal using the accounts identified here for the UK Ledger when the journal is balanced by the primary BSV but not by second or third BSV, as this indicates that there is an intercompany transaction between different legal entities or business units within the UK Ledger that requires intercompany balancing. Intercompany processing will not balance a journal using the accounts identified here for the UK Ledger when there is a many-to-many journal and you want to use a clearing company, as this is a scenario that involves multiple legal entities or business units across different ledgers that requires a separate clearing company ledger to perform intercompany balancing. Intercompany processing will not balance a journal using the accounts identified here for the UK Ledger when the journal is not balanced by the primary BSV, as this is an invalid scenario that violates the accounting rules and prevents posting of the journal. Intercompany processing will not balance a journal using the accounts identified here for the UK Ledger when the journal is balanced by second balancing segment value, as this is an incomplete scenario that does not specify whether the journal is also balanced by primary and third BSV. Reference: Oracle Financials Cloud: General Ledger 2022 Implementation Professional Objectives - Configure and Process Intercompany 12

Here are the steps you need to follow:

• In the Setup and Maintenance work area, go to the following:
• Select the chart of accounts that you want to create the alias for. In this case, it is the Corporate chart of accounts.
• Click on the Add Row icon to create a new alias. Enter the following information:
• Click on the Save and Close button to save the alias.

You have successfully created a shorthand alias for the US Chart of Accounts. For more information, you can refer to the following resources:

• Account Aliases
• Enter a GL Account Alias
• Short Hand Alias in Fusion Financials Key Flexfield
• How to Enable Account Shorthand Aliases

 Here are the steps you need to follow:

• In the Setup and Maintenance work area, go to the following:
• Select the source chart of accounts (UK) and the target chart of accounts (CA) that you want to map.
• Click on the Segment Rules tab to define the segment mapping rules. Enter the following information for each segment:
• Click on the Save and Close button to save the segment mapping rules.

You have successfully created a Chart of Accounts mapping for the given scenario. For more information, you can refer to the following resources:

• Overview of the Chart of Accounts Mapping Page
• Chart of Accounts Structures and Instances
• How To Create A Chart Of Accounts Mapping For A Secondary Ledger
• How To Bulk Upload The Mapping Rules In “Manage Chart of Accounts Mapping”
• Centralized Management of Chart of Accounts Configurations