Oracle 1z0-1054-23 Exam Dumps - Valid Questions Answers

If you use insert in the spreadsheet to load the monthly historical rates by using FBDI, the existing historical rate for a specific ledger, currency, account combination, and accounting period will be replaced by the new rate. This is because the insert action will overwrite the existing rate with the new rate in the GL_HISTORICAL_RATES_INT table. If you want to preserve the existing rate, you should use update or delete actions instead. References:

• How Historical Rates Import Data Is Processed, Section: Use the Historical Rates Import file-based data import (FBDI) template to import historical rates from external and legacy sources to Oracle General Ledger
• Import Historical Rates, Section: Details
• Entering Historical Rates, Section: Entering Historical Rates

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 becausehierarchies for reporting and allocations must be published to Essbase cubes5. Option C is incorrect because it contradicts option B.

According to Oracle documentation1, the following statements are true regarding intercompany accounting for Financials Cloud, Projects, Inventory, and SCM: Each product has its own Intercompany Accounting feature that needs to be configured separately, and Intercompany Balancing Rules are defined centrally and applied across Financials and Projects. Intercompany accounting is the process of recording transactions between related entities within an enterprise or between groups in the same legal entity. Each product has its own Intercompany Accounting feature that enables you to create, process, and reconcile intercompany transactions. Intercompany Balancing Rules are used to generate balancing entries for journals that are out of balance by legal entity or primary balancing segment values. Intercompany Balancing Rules are defined in General Ledger and applied across Financials and Projects. Therefore, options A and C are correct. Option B is incorrect because Intercompany Balancing Rules are not used to balance cross-ledger allocation journals. Option D is incorrect because Intercompany balancing rules in General Ledger do not need to be mapped with the intercompany configuration in each product.