1Z0-1054-24 Exam Dumps and Practice Questions

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.

You should define the default intercompany balancing rule at the legal entity level, because each ledger has one legal entity assigned to it and each legal entity is associated with one balancing segment value. This way, you can specify the intercompany receivables and payables accounts for each legal entity and ensure that the journals are balanced by legal entity or primary balancing segment values. A ledger-level rule would apply to all legal entities in the ledger, which may not be appropriate if they have different intercompany accounts. A primary balancing segment rule would apply to all ledgers that share the same chart of accounts, which may not be desirable if they have different intercompany rules. A chart of accounts rule would apply to all ledgers and legal entities that use the same chart of accounts, which may not be feasible if they have different intercompany segments or accounts.Reference:

Intercompany Balancing Rules, Section: Define Intercompany Balancing Rules

Overview of Intercompany Balancing Rules, Section: Define Intercompany Balancing Rules

Troubleshooting Guide For Intercompany Balancing, Section: 1. Journals and subledger accounting entries are not being balanced for intercompany activity

Implement General Ledger, Section: Intercompany Balancing

To use the Create Budgets in a Spreadsheet option, you need to have a budget scenario value and a scenario dimension member for your budget. A budget scenario value is a user-defined value that identifies a budget, such as FYXX Budget. A scenario dimension member is a member of the scenario dimension in the General Ledger balances cube that corresponds to a budget scenario value, such as FYXX_Budget. You can create budget scenario values and scenario dimension members using the Manage Budget Scenario Values task or the Create Scenario Dimension Members program. If you do not create these values and members, your budget will not appear in the Budget Name list of values in the spreadsheet. Therefore, the two reasons for your issue are:

A value for the budget scenario is not created: You need to create a budget scenario value for your budget using the Manage Budget Scenario Values task. This task enables you to define and maintain budget scenario values and their attributes, such as description, start date, end date, and status. You can also specify whether the budget scenario value is enabled for budgeting and reporting. You need to enable the budget scenario value for budgeting to use it in the spreadsheet.

The Create Scenario Dimension Members program has not been run: You need to run the Create Scenario Dimension Members program to create scenario dimension members for your budget scenario values. This program automatically creates scenario dimension members for all budget scenario values that are enabled for budgeting and do not have existing scenario dimension members. You can run this program manually or schedule it to run periodically. You need to run this program after you create or update budget scenario values to ensure that they are reflected in the scenario dimension.

Create Budgets in a Spreadsheet

Manage Budget Scenario Values

Create Scenario Dimension Members