Free Oracle Fusion Cloud Financials: General Ledger 2026 Implementation Professional 1Z0-1054-26 Exam Questions

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 view high-level profit and loss results for each ledger in the Close Monitor, you need to associate a Financial Reporting Web Studio report with the ledger set. This report should be based on the General Ledger Balances cube and should include the Income Statement account group as a row dimension. The report should also have the ledger set as a point of view dimension and the period and currency as user prompts. This way, you can select the ledger set, period, and currency when you run the report from the Close Monitor and see the aggregated income statement results for each ledger and consolidation node in the ledger set hierarchy.Reference:Overview of Close Monitor,Using General Ledger,Close Monitor Issue

The Journal Attachments Audit feature is intended to monitor journal attachments that are added through the journal user interface. This control is compliance-focused because journal preparers and approvers often attach supporting evidence, backup schedules, approval documents, or audit justification directly while creating or editing journals online. FBDI, ADFdi, and Journal Import are primarily data-load or integration methods for journal creation and are not the eligible source mode for this specific attachment audit behavior. The key point is that the audit feature is scoped to journals where attachments are maintained interactively in the UI. Therefore, the correct answer is journals created in the user interface. This is the only option that aligns with the functional purpose of Journal Attachments Audit in General Ledger compliance monitoring.

According to Oracle documentation, when there is a business requirement for a subsidiary company to report to the parent company on a monthly basis with different currencies and no requirement to have daily balances, you should recommend Balance level as the data conversion level. A Balance level data conversion level enables you to translate balances from one currency to another at month-end or quarter-end for reporting purposes. A Balance level data conversion level minimizes the data stored in the reporting currency because it does not store daily balances or journal details. Therefore, option D is correct. Option A is incorrect because a Subledger level data conversion level stores daily balances and journal details in the reporting currency. Option B is incorrect because a Journal Level data conversion level stores journal details in the reporting currency. Option C is incorrect because an Adjustment only level data conversion level does not translate balances from one currency to another. Option E is incorrect because a Spreadsheet level data conversion level does not exist.

Opening Balance Initialization is intended for scenarios where a new reporting currency or secondary ledger must begin with initialized balances rather than full transactional history. The feature is compatible with balance-oriented implementations because the objective is to establish beginning balances in the target ledger or reporting currency. Therefore, Balance level is compatible. Adjustment only level is also compatible because the secondary ledger is maintained through manual or adjustment entries rather than a full automatic transaction copy. Subledger level and Journal level involve detailed accounting transfer from the primary ledger or subledgers, which is not the purpose of opening balance initialization. Currency level is not a valid secondary ledger data conversion level in this context. This matches Oracle's ledger architecture for thin secondary ledgers and balance-based reporting currencies.

Here are the steps you need to follow:

In the Setup and Maintenance work area, go to the following:

Offering: Financials

Functional Area: Financial Reporting Structures

Task: Manage Shorthand Aliases

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:

Alias Name: RevDom

Account Template: 101-2000-400000-000-000-000

Description: Revenue Domestic for Supremo Fitness, Line of Business 2, and US Operations Cost Center

Enabled: Yes

Start Date: Today's date

End Date: Blank

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

According to Oracle documentation2, you enable invoicing for certain Intercompany transactions on the transaction type. The transaction type defines the characteristics of an intercompany transaction, such as whether it requires approval, whether it generates invoices, and what accounting rules apply. You can enable invoicing for a transaction type by selecting the Invoicing Options tab and choosing the invoice method, invoice source, invoice batch source, and invoice rule. Therefore, option D is correct. Option A is incorrect because you do not enable invoicing on the transaction batch. Option B is incorrect because you do not enable invoicing on the transaction category. Option C is incorrect because you do not enable invoicing on the transaction source.

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

The ledger option alone does not enforce the single-currency restriction for every journal source automatically. Oracle General Ledger applies this restriction at the journal source level. Since users are creating journals manually through the Create Journal task, the relevant source is the Manual journal source. Therefore, to stop users from entering multiple currencies in a manually created journal, the Limit Journal to the Single Currency option must be enabled for the Manual source. The category is not the controlling setup point, and the restriction is not enabled by currency value. Oracle documentation explains that single-currency enforcement is configured by journal source, and applicable journal sources must have the option enabled for the restriction to apply.