Free 1Z0-1055-26 Practice Test Questions and Answers (2026) | Cert Empire Practice Questions

To add new transactional attributes to a workflow notification, you must modify both the data source and the presentation layer. In Oracle Business Intelligence (BI) Publisher, which manages these notifications, the Data Model defines the SQL query that fetches the data. The Layout Template controls the visual presentation and layout of that data in the notification. Therefore, you must customize the data model to include the new attributes and then edit the layout template to display them.

C. The Original Source is a vague term; the specific BI objects that need modification are the Data Model and the Layout Template.

D. The Output types (e.g., PDF, HTML) define the format of the generated report, not the data content or its layout within the notification.

1. Oracle Fusion Cloud Financials

Implementing Expenses

23D

Chapter 6: Configure Expense Approval Rules. Section: "How You Configure Workflow Notifications in BI Publisher". This section explains that notifications use BI Publisher templates and data models.

2. Oracle Fusion Cloud Financials

Creating and Administering Analytics and Reports for Financials

23D

Chapter 3: Use BI Publisher. Section: "Components of a Report". This document explicitly states a report consists of a data model and a layout template.

The ability to create a supplier is controlled by specific job roles and their associated privileges. The "Create Supplier" task is granted by the POZCREATESUPPLIERPRIV privilege. This privilege is a key component of the "Supplier Manager" job role, which is designed for users responsible for managing the supplier lifecycle, including onboarding and profile maintenance. A Payables Analyst or Procurement Agent role does not inherently include this privilege. Therefore, the user cannot see the task because they lack the required Supplier Manager role.

A. The Procurement Administrator role is primarily for managing procurement application setups and configurations, not for day-to-day supplier data management.

C. While the Supplier Administrator role also has supplier creation privileges, the Supplier Manager role is the primary functional role for managing supplier relationships and data.

D. The Procurement Requester role is for creating purchase requisitions and does not include privileges for creating or managing suppliers.

1. Oracle Fusion Cloud Financials Documentation

"Security Reference for Oracle Financials Cloud

" Chapter: "Job Roles and Duty Roles

" Section: "Supplier Manager Job Role." (Lists the privileges and duties

including supplier creation).

2. Oracle Fusion Cloud Financials Documentation

"Security Reference for Oracle Financials Cloud

" Chapter: "Job Roles and Duty Roles

" Section: "Payables Analyst Job Role." (Shows that this role lacks supplier creation privileges).

3. Oracle Fusion Cloud Financials Documentation

"Using Procurement

" Chapter: "Define Suppliers

" Section: "Supplier Model." (Describes the roles involved in supplier management).

The installment selection in a Payment Process Request (PPR) is governed by the 'Pay Through Date' and the 'Date Basis'. In this scenario, the 'Date Basis' is 'Due Date'. The PPR will only select installments with a due date on or before the 'Pay Through Date'. The installment's due date is July 31, 2022, which is after the specified 'Pay Through Date' of July 30, 2022. Consequently, the installment is not selected for payment in this payment run. Discount availability is only evaluated for installments that have been selected.

A. The installment is not selected because its due date is after the Pay Through Date.

B. The installment is not selected. Even if it were, the discount would be $50, but the primary selection criteria failed.

C. The installment is not selected. The first discount date has already passed based on the payment date.

E. Installment selection is based on the 'Date Basis' (Due Date in this case), not on the discount dates.

1. Oracle Financials Cloud

Implementing Payables Invoice to Pay

24A

Chapter: Payments

Section: "Submit a Payment Process Request". The guide explains

"Pay Through Date: The date through which you want to select invoices for payment. Payables selects all invoices with a due date or discount date on or before the pay through date

depending on the date basis you select."

2. Oracle Financials Cloud

Using Payables Invoice to Pay

24A

Chapter: Payments

Section: "Payment Process Requests". This section details the parameters

confirming that the Pay Through Date acts as a cutoff for installment selection based on the chosen Date Basis.

When configuring account derivation rules (ADRs) for Payables invoices sourced from Oracle Lease Accounting, the accounting rule engine can use specific attributes from the original lease transaction. Oracle predefines several source attributes for this purpose. These include the "Right-of-use" (ROU) flag, which is a critical attribute for lease accounting standards, and descriptive flexfield (DFF) values captured on the lease asset. These attributes allow for granular accounting rules based on the specific nature and user-defined characteristics of the leased asset.

B. While DFFs are available sources, the documentation specifically calls out DFFs on the lease asset (header level), not necessarily the payment schedule level, as predefined sources for Payables ADRs.

C. The lease preparer is typically an audit or transactional attribute and is not a standard predefined source for creating accounting derivation rules.

E. Lease location may be stored in an asset DFF but is not itself a distinct, predefined source attribute for these specific accounting rules.

1. Oracle Fusion Cloud Financials

Implementing Leases

Release 24B

Chapter: Set Up Leases

Section: "Create Account Rules for Leases". This document outlines the available sources for creating custom account rules for leases

explicitly mentioning "Right-of-use" and asset-level DFFs.

The customization feature in BI Publisher is designed to be upgrade-safe. When a predefined report is customized, a copy is saved to a separate /Custom folder. The application is configured to use this custom version. When Oracle provides patches or updates, they are applied to the original reports in the standard directory, leaving the customized version in the /Custom folder untouched and operational. Furthermore, the BI Publisher layout editor is a primarily visual tool, allowing users to create and modify report layouts without writing complex code.

A. Report output is sent to an e-commerce site: This is a report delivery option, not a benefit specific to the customization feature itself.

C. You do not need any special roles to access this feature: Incorrect. Customizing reports requires specific BI roles, such as BI Administrator or BI Author.

D. A backup copy of the report is automatically saved in my folders: The copy is saved in the shared /Custom folder, not a user's personal "My Folders," to ensure it's available to the application.

1. Oracle Fusion Cloud SCM

Creating and Administering Analytics and Reports for SCM

24B

Chapter: Customize Reports. The "Overview of Customizing Reports" section states

"Your customizations are preserved during updates and patches."

2. Oracle Fusion Cloud Financials

Creating and Administering Analytics and Reports for Financials

24B

Chapter: Customize Reports. This guide explains that customizations are saved to the /Custom folder in the BI Catalog

ensuring they are not overwritten by updates. It also highlights the use of the visual layout editor.

Oracle Fusion Cash Management provides specific predefined reports to monitor cash positions. The Cash to General Ledger Reconciliation Report identifies discrepancies by listing subledger transactions accounted in the General Ledger but not yet reconciled in Cash Management. The Bank Statement Report provides exact balance and transactional data for specified bank statements, aiding in granular statement verification. The Cash in Transit Report identifies funds that are in process by securely listing transactions remitted to the bank but not yet cleared. Finally, the Bank Statement Analysis Report provides a broader analytical view, displaying the bank statements utilized to analyze overall balances and transaction details. These functions correspond directly to official Oracle Cloud Financials parameters.

Oracle Help Center. "Cash to General Ledger Reconciliation Report", Oracle Fusion Cloud Financials (Release 26A). (Confirms the GL vs. Cash Management unmatched transaction mapping).

Oracle Help Center. "Oracle Fusion Cash Management Predefined Reports", Oracle Fusion Cloud Financials (Release 26A), Chapter: Financial Reporting and Analysis. (Defines Cash in Transit Report and Bank Statement Analysis Report mappings).

Oracle Corporation. "Oracle Financials Reports List (Financials-Reports-R10.xls)", Document ID: R10, Tabs: Cash Management & Reports and Analyses. (Verifies the definition for Bank Statement Report vs Bank Statement Analysis Report).

for Step- by-Step Solution. Explanation: Task 1: Create an Expense Report Template for the US1 Business Unit The following configurations need to be implemented: Effective Start Date: The current date. Hotel Expense Type: Requires itemization with Internet, Room Rate, and Dinner. Expense Type: Associated with the respective GL account. Card Expense Type Mapping: Not enabled. Receipts Policy: Users can indicate missing receipts, and a warning should be displayed. Expense Fields: All fields should be optional. Step-by-Step Solution Step 1: Navigate to Expense Report Templates Log in to Oracle Financials Cloud with the Expense Manager or Financial Administrator role. Navigate to Setup and Maintenance. In the Search Bar, type "Manage Expense Report Templates". Click on Manage Expense Report Templates. Step 2: Create a New Expense Report Template Click Create New Template. Enter the following details: Name: "US1 Business Unit Expense Report" Business Unit: US1 Business Unit Effective Start Date: (Set to current date) Enable for Use: (Check this box) Click Save. Step 3: Define the Expense Type – Hotel with Itemization Navigate to the Expense Types tab. Click Add Expense Type. Enter the following details: Expense Type Name: "Hotel" Expense Category: "Lodging" Requires Itemization: (Check this box) Under Itemization, click Add Itemization Categories: Internet Room Rate Dinner Click Save. Step 4: Associate Expense Types with GL Accounts Click on Edit Expense Type "Hotel". Go to the Accounting section. Select the appropriate GL Account for lodging expenses. Repeat this process for other required expense types. Click Save and Close. Step 5: Disable Card Expense Type Mapping Navigate to the Corporate Card Expense Mapping tab. Ensure the "Enable Corporate Card Mapping" checkbox is unchecked. Click Save. Step 6: Configure Receipts Policy Navigate to the Receipts tab. Under Receipt Handling, set: Company Policy: Employees must provide receipts. Allow users to indicate missing receipts? (Check this box). Action for Missing Receipts: Raise a Warning (so that expense submission is not blocked). Click Save. Step 7: Set Expense Fields as Optional Navigate to the Fields Setup tab. Ensure all Expense Fields are set to Optional. Click Save and Close. Step 8: Validate and Activate the Template Review all configurations. Click Submit and Activate. Run the Validate and Deploy Expense Templates process to ensure all settings are applied. Step 9: Testing the Expense Report Template Simulate an Expense Report Submission: Select Hotel Expense and enter details. Verify if the system requires itemization (Internet, Room Rate, Dinner). Submit without a receipt to check if a warning is displayed. Ensure all fields remain optional. Verify no corporate card expense mapping applies. Expected Outcome: The Expense Report Template is successfully created for US1 Business Unit. Hotel expenses require itemization into Internet, Room Rate, and Dinner. Receipts are required, and a warning is displayed for missing receipts. GL Account mapping is correctly applied to each expense type. Card Expense Type Mapping is disabled. All fields are optional, allowing flexible data entry. Conclusion By following these steps, we have successfully created and configured an Expense Report Template that meets all business requirements for the US1 Business Unit.

for Step-

by-Step Solution.

Explanation:

Step-by-Step Solution: Configuring Expense Policies by Expense Category in Oracle Financials Cloud

To implement the expense policy for meals in Oracle Financials Cloud, follow these steps:

Step 1: Navigate to the Expense Policies Setup

Log in to Oracle Financials Cloud with the appropriate Expense Manager or Financial Administrator

role.

Go to the Setup and Maintenance work area.

Select Manage Policies by Expense Category (Task Name: Manage Expense Policies by Expense

Category).

Select the US1 Business Unit to ensure the policy applies to the correct entity.

Step 2: Create or Update the Meal Expense Category

Under Manage Policies by Expense Category, locate or create the Meals Expense Category.

If the Meals category does not exist:

Click Create Expense Category.

Enter Category Name: "Meals".

Category Type: "Meals and Entertainment".

Save the entry.

Step 3: Define Expense Limits for Evening Meals

Select the Meals Expense Category and click Edit.

Navigate to the Policies and Limits tab.

Under Amount Limits, click Add New Rule.

Description: "Evening Meal Limit".

Limit Type: "Maximum Allowed Amount".

Limit Amount: Enter 30 USD.

Per: Select Day.

Apply to All Employees (since this applies regardless of role and location).

Location-Based Rules: Leave blank since it applies universally.

Click Save and Close.

Step 4: Enable and Activate the Policy

Ensure the policy is enabled by selecting the checkbox for Active.

Click Submit to finalize the configuration.

Run the "Validate and Deploy Expense Policies" process to apply changes.

Step 5: Testing the Policy

Simulate an Expense Report Submission:

Have an employee create a new expense report.

Select Meals as the expense category.

Enter an evening meal expense of 35 USD (which exceeds the policy limit).

Verify if a policy violation warning appears, restricting the claim to 30 USD.

Submit an expense of 30 USD and ensure no policy violation occurs.

Expected Outcome:

Employees can claim up to 30 USD per day for an evening meal.

Any claim above 30 USD triggers a policy violation warning.

The rule applies to all employees regardless of role and location.

Conclusion

By following the above steps, you successfully configure an expense policy for meals that limits

evening meal claims to 30 USD per day. This ensures compliance with the company's expense

management guidelines while streamlining the expense approval process in Oracle Financials Cloud.

for Step- by-Step Solution. Explanation: TASK 2: CREATE EXPENSE ITEMS We need to create expense items with the following requirements: Effective Start Date: Set to current date. No tax implications. Projects are not used. Receipt and expense fields should match those from the expense report template created earlier. Dinner expense item must be linked to the Meal policy created in the previous task. Step-by-Step Solution: Configuring Expense Items in Oracle Financials Cloud Step 1: Navigate to the Expense Items Setup Log in to Oracle Financials Cloud as an Expense Manager or Financial Administrator. Navigate to Setup and Maintenance. In the Search Bar, type "Manage Expense Items". Click on Manage Expense Items. Step 2: Create Expense Items Click Create New Expense Item. Enter the following details: Expense Item: Internet Name: "Internet" Expense Category: "Meals and Entertainment" Effective Start Date: Current Date Tax Classification Code: None (No tax implications) Projects Used? No (Uncheck "Enable for Projects") Receipt Required? Follow Template Policy Expense Fields? Set as Optional Click Save and Close. Expense Item: Room Rate Click Create New Expense Item again. Enter the following details: Name: "Room Rate" Expense Category: "Lodging" Effective Start Date: Current Date Tax Classification Code: None Projects Used? No Receipt Required? Follow Template Policy Expense Fields? Set as Optional Click Save and Close. Expense Item: Dinner (Linked to Meal Policy) Click Create New Expense Item again. Enter the following details: Name: "Dinner" Expense Category: "Meals and Entertainment" Effective Start Date: Current Date Tax Classification Code: None Projects Used? No Receipt Required? Follow Template Policy Expense Fields? Set as Optional Link to the Meal Policy Created Earlier: Navigate to Expense Policies. Select the previously created Meal Policy. Ensure that Dinner Expense Item is associated with this policy. Set Limit Type: Warning Only (if applicable). Click Save and Close. Step 3: Validate and Confirm the Expense Items Review the created expense items. Ensure that: No tax classification codes are applied. Projects are disabled. Receipt and expense fields match those in the Expense Report Template. Dinner Expense Item is correctly linked to the Meal Policy. Click Submit and Activate. Step 4: Test the Expense Items Simulate an Expense Report Submission: Select Internet, Room Rate, and Dinner as expense types. Enter sample amounts. Ensure that: No tax implications appear. Projects field is disabled. Receipt rules match the Expense Report Template. A warning is displayed if the Dinner Expense exceeds the Meal Policy limit. Expected Outcome: Expense items are successfully created. No tax implications are applied. Projects are not enabled. Receipts and expense fields match the template. Dinner expense item is linked to the Meal Policy and displays a warning if the limit is exceeded. Conclusion By following these steps, we have successfully created expense items that comply with all business requirements.

for Step-

by-Step Solution.

Explanation:

Step-by-Step Solution: Configuring an Expense Policy in Oracle Financials Cloud

To configure this expense policy in Oracle Financials Cloud, follow these steps:

Step 1: Access the Expense Policies Setup Page

Log in to Oracle Financials Cloud with the appropriate Expense Manager or Financial Administrator

role.

Navigate to Setup and Maintenance.

Select the Task: Manage Policies by Expense Category.

Step 2: Create or Locate the Meal Expense Category

Search for the Meals expense category.

If the Meals category does not exist:

Click Create Expense Category.

Category Name: "Meals".

Category Type: "Meals and Entertainment".

Save the entry.

Step 3: Define a Policy Rule for Raising a Warning

Select the Meals Expense Category and click Edit.

Navigate to the Policies and Limits tab.

Under Amount Limits, click Add New Rule.

Configure the Expense Policy Rule:

Description: "Meal Expense Warning Policy".

Limit Type: "Warning Only".

Limit Amount: Enter the prescribed limit (e.g., 50 USD).

Per: Select Day (or another relevant time frame).

Applies To: Select All Employees.

Location-Based Rules: Leave blank if not location-specific.

Set Warning Behavior:

Select Raise a Warning if the expense exceeds the prescribed limit.

Ensure the policy does not block submission or approval.

Click Save and Close.

Step 4: Associate the Policy with an Expense Report Template

Navigate to Setup and Maintenance > Manage Expense Report Templates.

Search for the Expense Report Template where the Meals category should be included.

Click Edit and go to the Expense Types section.

Add the Meals Expense Type and associate it with the newly created Meals Expense Warning Policy.

Click Save and Close.

Step 5: Enable and Validate the Policy

Ensure the policy is marked as Active.

Click Submit to finalize the policy configuration.

Run the Validate and Deploy Expense Policies process.

Step 6: Testing the Policy

Simulate an Expense Report Submission:

Create a new expense report and select Meals as the expense type.

Enter an expense amount exceeding the limit (e.g., 55 USD).

Verify that a warning message appears, but the expense is still allowed to proceed.

Submit an expense below the limit (e.g., 45 USD) and ensure no warning appears.

Expected Outcome:

If the meal expense exceeds the limit, the system raises a warning but does not block the expense

submission.

If the meal expense is within the limit, the system processes it without warnings.

The policy is successfully associated with an expense type in an expense report template.

Conclusion

By following these steps, you successfully configure an expense policy that raises a warning for meals

exceeding a specified limit without blocking submission or processing. This ensures that employees

are notified about policy violations while allowing flexibility in expense approvals.

The "Process Corporate Card Transactions for Inactive Employees" process is designed to create expense reports automatically for former employees. To control which transactions are processed, the system uses two key parameters. It identifies employees based on their Employee Termination Date. It also uses a Grace Period, which is a specified number of days after the termination date, during which transactions are still considered valid for processing. This ensures that legitimate business expenses incurred around the time of termination are paid.

B. Outstanding Cash Advances are a separate financial item and not a direct parameter or capability for processing card transactions for inactive employees.

C. Individual Pay Liability is the outcome of processing the transactions (an expense report is created), not a capability or input parameter of the process itself.

1. Oracle Fusion Cloud Financials

Implementing Expenses

23D

Chapter 5: Manage Corporate Cards. Section: "Process Corporate Card Transactions for Inactive Employees". This section describes the process and its parameters

explicitly mentioning the use of a grace period and the employee's termination date.

2. Oracle Fusion Cloud Financials

Using Expenses

23D

Chapter 5: Corporate Cards. Section: "Corporate Card Transaction Processing for Inactive Employees". This guide details the functionality

stating the process uses the termination date and a grace period to select transactions.

A Payables Supervisor can use the 'Manage Invoices' page to directly query for invoices with an 'Incomplete' status, and can also filter by other attributes like the creation source (e.g., Supplier Portal). This provides a real-time, interactive method for identification. Additionally, during the period close process, the 'Payables Period Close Exception Report' is run. This report explicitly lists all transactions, including incomplete invoices, that are preventing the period from being closed. Both are standard tools for this task.

A. Query the Payables Invoice Register: This report primarily lists validated and accounted invoices, making it unsuitable for finding incomplete ones which have not passed validation.

B. Run the Period Invoice Audit Report: This report tracks changes made to invoices (auditing), rather than identifying invoices based on their current status like 'Incomplete'.

1. Oracle Fusion Cloud Financials

"Invoices". Section: "How You Manage Invoices". The documentation describes using the Manage Invoices page to search for invoices based on status

including 'Incomplete'.

2. Oracle Fusion Cloud Financials

"Period Close". Section: "Payables Period Close Exceptions Report". This document explains that the report is the primary tool for identifying transactions

such as unvalidated invoices

that hold up the period close.

To set up Business Intelligence Publisher (BIP) reports for AI Apps, a custom role is required. According to Oracle's implementation guidelines, this custom role must inherit permissions from two specific predefined roles. These roles are AIAPPSAuthor and AIAPPSDataModelDeveloper. AIAPPSAuthor provides the necessary privileges to create and edit BI Publisher reports within the AI Apps context, while AIAPPSDataModelDeveloper grants permissions to create and manage the underlying data models that feed these reports.

B. BIIntegration

This role is intended for web service integrations and is not used for creating or managing user-facing BI reports or data models.

C. BIAuthor

This is a generic BI authoring role. The AI Apps setup requires the specific AIAPPSAuthor role for its dedicated content.

E. BIPDataModelDeveloper

This is a generic BI data model role. The AI Apps setup requires the specific AIAPPSDataModelDeveloper role.

1. Oracle Fusion Cloud AI Apps for ERP

Implementing AI Apps for ERP

24B

Chapter 2: Set Up AI Apps for ERP

Section: Set Up Security. The guide explicitly instructs to "Add the AIAPPSAuthor and AIAPPSDataModelDeveloper role hierarchies" when creating the custom BI role for AI Apps.

Adaptive Learning for Invoice Lines enhances Intelligent Document Recognition (IDR) by learning from user corrections made in the interactive invoice viewer. This feature specifically applies to certain line-level attributes. When a user corrects the Amount, Quantity, or Description on an invoice line, the system's machine learning algorithms are trained. This improves the accuracy of data extraction for these fields on future invoices from the same supplier, leading to increased touchless processing rates. Other correctable line-level attributes not listed as options include Unit Price and UOM (Unit of Measure).

C. Supplier is a header-level attribute, not a line-level attribute. Adaptive learning for suppliers is a separate capability.

E. Invoice Date is a header-level attribute, and corrections are learned at the invoice header level, not the line level.

F. Invoice Number is a key header-level attribute, not a line-level attribute.

G. Invoice Requestor is a routing attribute, not a standard line-level attribute extracted from the invoice image for learning.

1. Oracle Fusion Cloud Financials

What's New in Oracle Cloud: Financials 21D

Document ID F45903-01

December 2021

"Payables" section

"Adaptive Learning for Invoice Lines" feature description. The document states

"When you make corrections to the following invoice line-level attributes in the interactive invoice viewer

the application learns from them to improve recognition for future invoices: Amount

Quantity

Unit Price

UOM

Description."

The Monthly and Lifetime Rate Limit feature for miscellaneous expense policies provides granular control over spending. To apply different limits based on various contexts, the system allows configuration using specific rate determinants. The available determinants for this feature are the expense type being claimed, the geographical location of the expense, the employee's assigned role, and the currency of the transaction. These four values enable organizations to tailor spending policies precisely to their business needs, ensuring compliance and managing costs effectively across different scenarios.

B: Gender is not a valid or appropriate determinant for financial policies and would be discriminatory.

C: Exchange rate conversion is a process applied to foreign currency transactions, not a determinant for setting policy limits.

F: Employee management level is not a standard rate determinant for this feature; the system uses 'Role' for this purpose.

G: This option describes applying a single universal limit, which is the opposite of configuring rates based on specific determinant values.

- Oracle Cloud Financials

"What's New in Oracle Cloud: Financials 22C"

Section: Expenses > Monthly and Lifetime Rate Limit Enforcement for Miscellaneous Policies. (This document details the feature and its configuration options

explicitly listing expense type

location

role

and currency as determinants).

- Oracle Help Center

Implementing Expenses

Chapter: Expense Policies and Rules

Section: "Rate Limits for Miscellaneous Expense Policies".