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