Oracle 1z0-1054-24 Oracle Financials Cloud: General Ledger 2024Implementation Professional Exam Practice Test

Here are the steps you need to follow:

Navigate to the Setup and Maintenance work area and search for the task Manage Chart of Accounts Structures.

Click on the Create icon to create a new Chart of Accounts Structure. Enter the following information:

Structure Code: 07COA

Structure Name: 07 Chart of Accounts

Description: Chart of Accounts for candidate 07

Number of Segments: 5

Click on the Next button to define the segments. Enter the following information for each segment:

Segment Number: 1

Segment Name: Company

Value Set Code: 07Corporate Company

Value Set Name: 07 Corporate Company

Maximum Size: 3

Balancing: Yes

Segment Label: Company

Segment Number: 2

Segment Name: Cost Center

Value Set Code: 07Corporate Cost Center

Value Set Name: 07 Corporate Cost Center

Maximum Size: 4

Balancing: No

Segment Label: Cost Center

Segment Number: 3

Segment Name: Account

Value Set Code: 07Corporate Account

Value Set Name: 07 Corporate Account

Maximum Size: 8

Balancing: No

Segment Label: Natural Account

Segment Number: 4

Segment Name: Product

Value Set Code: 07Corporate Product

Value Set Name: 07 Corporate Product

Maximum Size: 3

Balancing: No

Segment Label: Product

Segment Number: 5

Segment Name: Intercompany

Value Set Code: 07Corporate Company

Value Set Name: 07 Corporate Company

Maximum Size: 3

Balancing: No

Segment Label: Intercompany

Click on the Next button to review the summary and click on the Save and Close button to save the Chart of Accounts Structure.

Navigate to the Setup and Maintenance work area and search for the task Manage Chart of Accounts Structure Instances.

Click on the Create icon to create a new Chart of Accounts Structure Instance. Enter the following information:

Structure Code: 07COA

Structure Name: 07 Chart of Accounts

Description: Chart of Accounts for candidate 07

Chart of Accounts Structure: 07COA

Enabled: Yes

Allow Dynamic Inserts: Yes

Click on the Next button to review the summary and click on the Save and Close button to save the Chart of Accounts Structure Instance.

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

Chart of Accounts Structures and Instances

Chart of Accounts Components

Minimum Steps For Financial Enterprise Structures Configuration

Overview of Creating and Configuring Chart of Accounts Structure and Instances

 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 Chart of Accounts Mapping

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:

Segment Number: 1

Segment Name: Company

Mapping Type: Value

Source Value: *

Target Value: *

Segment Number: 2

Segment Name: LoB

Mapping Type: Value

Source Value: *

Target Value: *

Segment Number: 3

Segment Name: Account

Mapping Type: Range

Source From Value: 1000

Source To Value: 1999

Target Value: 11101

Mapping Type: Range

Source From Value: 2000

Source To Value: 2999

Target Value: 22100

Mapping Type: Range

Source From Value: 3000

Source To Value: 3999

Target Value: 34000

Mapping Type: Range

Source From Value: 4000

Source To Value: 4999

Target Value: 42000

Mapping Type: Range

Source From Value: 5000

Source To Value: 99999999

Target Value: 51100

Segment Number: 4

Segment Name: Cost Center

Mapping Type: Value

Source Value: 0

Target Value: Balance Sheet

Mapping Type: Value

Source Value: 000

Target Value: Balance Sheet

Mapping Type: Value

Source Value: *

Target Value: 610

Segment Number: 5

Segment Name: Product

Mapping Type: Value

Source Value: *

Target Value: *

Segment Number: 6

Segment Name: Intercompany

Mapping Type: Value

Source Value: *

Target Value: *

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

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 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.

Geography validation is a feature that enables you to validate the address information entered for a location against the geography hierarchy defined for a country. You can set the Geography Validation for Country option to one of the following values:

No Validation: No validation is performed on the address information.

Warning: A warning message is displayed if the address information does not match the geography hierarchy, but the user can still save the address.

Error: An error message is displayed if the address information does not match the geography hierarchy, and the user cannot save the address until the error is corrected. To ensure that only valid addresses are entered in the system, you should set the Geography Validation for Country option to Error. This will prevent users from saving erroneous address data and enforce data quality and accuracy. References:

Oracle Financials Cloud: Enterprise Structures with General Ledger Implementation, Chapter 2: Define Geographies, Section: Geography Validation

Oracle Financials Cloud: Implementing Enterprise Structures and General Ledger, Chapter 2: Define Geographies, Section: Geography Validation

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 issuitable 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

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 isincorrect because Order Management is not a subledger that can be opted out of the period close checking feature.

To modify the journal approval notification, you need to copy (or customize) and edit the layout template and the data model of the Analytics Publisher report. The layout template defines the appearance and content of the notification, such as the text, fields, tables, and images. The data model defines the data sources and queries that provide the data for the notification, such as the journal attributes, amounts, and statuses. You can use Template Builder for Word to edit the layout template and Analytics Publisher to edit the data model. You also need to download the Workflow Notification Subtemplate, which is a common subtemplate that contains the header and footer of the notification. You can preview the modified notification using the subtemplate and the data model. References:

Modify Journal Approval Notifications with Analytics Publisher

[Creating Analytics and Reports for Financials Cloud]

The two true statements for the resulting revaluation run are that you have an unrealized exchange gain recorded and you have an unrealized exchange loss recorded. Revaluation is a process that adjusts foreign currency balances to reflect current exchange rates at period end. Revaluation creates journal entries to record unrealized exchange gains or losses on foreign currency balances based on revaluation rates defined for each currency. In this scenario, you have a balance on the Accounts Payable Liability Account of 100,000 Euros which is equivalent to USD 136,550 at month end. The month end exchange rate for revaluation is 1 Euro = 1.3755USD. Therefore, after revaluation, your balance on the Accounts Payable Liability Account will be USD 137,550 (100,000 x 1.3755). This means you have an unrealized exchange gain of USD 1,000 (137,550 - 136,550) on your Accounts Payable Liability Account because your liability in foreign currency has decreased in terms of your ledger currency due to exchange rate fluctuations. Revaluation will create a journal entry to debit your Accounts Payable Liability Account by USD 1,000 and credit your Unrealized Exchange Gain Account by USD 1,000 to record this gain. The original journal entry in Euros is not updated by revaluation, as revaluation only creates new journal entries to adjust foreign currency balances in terms of ledger currency based on revaluation rates. There is no unrealized exchange gain or loss calculated by revaluation, as revaluation does calculate unrealized exchange gains or losses on foreign currency balances based on revaluation rates. 

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