Using AI Capabilities in Payables - All Points Notes
Using AI Capabilities in Payables - All Points Notes
From Data Tsunami to Smart Data: "It has become impossible for humans to handle
and interpret huge volumes of data. That's where AI comes into play," explained Melissa
Boxer, Oracle VP Product Management, in her session about The AI-Powered Marketer.
Hungry for meaningful and accessible insight: Too many companies suffer from
“data rich but insight poor” syndrome. "Tell me something I didn't already know" is the
underlying promise of how emerging tech applied in HR can lead to new insights,
predictions, and make work more human, according to Kai Petzelt, VP of Product
Marketing HCM at Oracle. Applied AI/ML is already built into Oracle’s IoT apps to provide
insights (e.g. anomalies, predictions, trend detection) and actionable recommendations.
"Now you have data science in a box!" exclaimed Bhagat Nainani, Group Vice President
for IoT and Blockchain Applications Development. For example, Titan International is an
Oracle customer benefiting from the access to Oracle Cloud and advanced technologies
to improve their inventory process and get on their path to smart manufacturing.
AI contributes to business agility within the finance function: "We are building AI
and analytics into our EPM applications with regular updates to enable a more agile
organization,” said Jennifer Toomey, Senior Director, EPM Cloud Product Marketing in her
“Value Realization of EPM in the Cloud” session. Our customers can drive better decisions
through analytic insights and automate manual processes. Brian Pawlus, Senior Director
of Product Management for Oracle AI Apps, gave an overview of how AI and data-driven,
ready-to-go applications for ERP help you manage supplier health, and build intelligent
and self-learning dynamic discounting programs using trusted data sources, decision
science, and a modern cloud infrastructure. Steve Cox, Group VP for ERP/EPM Product
Marketing, challenged the audience to forget the 4.8 day benchmark for financial close,
and aim for continuous close! By leveraging emerging tech into streamlined business
processes, you can simply revolutionize the finance function.
Leverage intelligence and automation with embedded AI to support supply chain decision-
making and optimize supply chain management and manufacturing processes. All delivered as
standard in Oracle Fusion Cloud SCM.
Functional
Use case Business benefit
area
Order
Predict order fulfilment Automatically calculate average order cycle
Management
cycle times times and show impact vs required ship dates.
and Logistics
Supply Chain New product Forecast demand of new products learning from
Planning introduction the past product launches.
Manufacturing
Generate shift notes Facilitate the smooth hand off of work to the next
and
for operator hand off* operator.
Maintenance
Manufacturing
Generate repair Streamline the process of repairing multiple
and
summary* assets on a single work order.
Maintenance
1. At first glance, our Business is not happy. We are looking to give full
demo after we train the model for few suppliers so that the CC will default
as it learns when we type in Non-Prod. To train the model:
In Non-prod instance, I created 2 to 3 invoices with same supplier/Supplier
Site and provided the correct Code combinations. I expected that with this
training, system (as document mentioned real time), it pulls the data and
learns from recent invoices and the next 4th invoice will generate with
defaulting code combination. But it didn't happen.
https://docs.oracle.com/en/cloud/saas/adaptive-intelligent-apps/aigsd/faqs-
for-intelligent-account-combination-defaulting.html#When-does-the-
Intelligent-Account-Combination-Defaulting-feature-predict-values%3F
I will try to address the questions that you have raised in your message
above.
a. Training the Model
How can we train the model once it is configured?
What is the frequency with which the Adaptive AI pulls data from ERP
Cloud
for training after the model has been implemented? Specifically:
o Does the data get sent from ERP Cloud to the model each time
an invoice is validated (either online or via a batch process)?
o Or is there a scheduled frequency (e.g., daily) at which this data
transfer occurs?
In Production, the model is retrained every 24 hours if new validated data is
available. In test, the same still applies however only new data prior to the
P2T Refresh Date is considered.
c. Training Independence for Each Instance
1. Independence of Training Across Instances:
Do these Adaptive AI applications require independent training
for each instance (Non-Prod, Pre-Prod, Prod)?
Alternatively,
is it possible to move a trained model from Non-Prod to Pre-Prod
and
subsequently to Production? Please provide guidance on this
process.
Models cannot be moved from one instance to another. However the model
is always trained on the historical data available in the respective
environment (up to 18 months of history).
d. Architecture Diagram
1. Architecture Overview:
Could you provide an architecture diagram illustrating the
interaction
between ERP Cloud and Adaptive Intelligence Apps? Specifically, I
am
interested in understanding where these Adaptive AI apps reside
within
the overall architecture.
AI Apps environments are provisioned to customers in the same region as
the related Fusion ERP Cloud environment. The environment are
customer/pod specific and are only integrated with the respective customer
pod. The data ingestion mechanism is automated and currently leverages
BI Publisher (this may change in the future). The data (and model) is stored
in a customer/pod specific OCI object storage and prepared for model
training. No data is shared across customers or environments. An API call
from the Fusion environment invokes the prediction from the AI Apps Model.
e. Support for Custom Invoice Sources
1. Support for Various Invoice Sources:
The FAQ mentions that "all invoice sources are supported."
Previously, I
noted that support was limited to MANUAL/IDR sources. Could
you confirm
whether this indeed includes custom invoice sources as well?
The models are trained on models from all invoice sources with the
exception of the invoice source "spreadsheet". Also invoices that have more
than 25 lines or invoice lines that are booked against a distribution set or
have multiple distributions are excluded from model training. All other
invoice lines within the last 18 months can be considered in the model
training.
a. Training the Model
Today is 01-Oct-24, and in our Non-Prod environment, we set the P2T
refresh date to 01-Jul-24. For training the model, it considers the last 18
months of invoice history. Specifically, it includes:
1. From Prod: It reads invoices with invoice_date later than 01-Jul-24
through to 01-Oct-24.
2. From Non-Prod: It reads invoices with invoice_date from 01-Mar-23
(18 months prior to today) to 30-Jun-24.
i. To train the Non-Prod model (as part of convincing the business for
approval), if we create invoices in Non-Prod today with invoice_date ranging
from 01-Mar-23 to 30-Sep-24, these new invoices should be included in the
training from Non-Prod. is it?
ii. And if I change the P2T refresh date to today in NonProd then all 18
months invoices, to train the Non-Prod model, will be considering from Non-
Prod only . is it?
iii. And also I believe it takes only the validated invoices (though not
accounted).
iv. I believe the new data for training is based on the invoice_date and not
the creation_date. Can you confirm if this understanding is correct and
provide any additional comments?
iv.
d. Architecture Diagram
Your explanation was very helpful. We encountered an issue with assigning
'Dynamic Discounting' Adaptive AI application roles to a user. Even our
Admins, who possess the necessary access, are unable to see these
application roles in 'Oracle Cloud Services' when navigating to the Adaptive
AI Apps page from ERP Cloud.
Since the AI Apps exist in the same POD, I assume the admin access for
these PODs is equivalent to the admin access for SaaS ERP Cloud. We
logged an SR two weeks ago but have not received a satisfactory response
yet. If you have any insights or can share related information, that would be
appreciated. Alternatively, I can start a separate thread for this issue.
e. Support for Custom Invoice Sources
Thank you for confirming that this feature applies to all invoice sources
except for one. To elaborate on its practical application:
We can create only Manual Invoices from the UI where it defaults.
For IDR, similar defaulting behavior might be applicable.
For other custom sources, typically created using FBDI, how does
defaulting work? Specifically, should we omit the Expense account for
lines so that the importing program defaults them? Will this approach
ensure that the segments default correctly and the statuses remain
valid?
f. Default from Invoice Distribution Combination or Accounted
Combination (Post-SLA)
1. Invoice Accounting Combination:
We create invoices (using FBDI) for custom sources with a
specific code combination for the expense account. Later, while
executing 'Create Accounting,' SLA rules apply, updating the
initial invoice distribution code combination with the final, SLA
rule-based code combination.
Does the IACD train the model based on the initial Invoice
Distribution Code Combination, or is it the final accounted Code
Combination post-SLA application?
2. Training Attributes:
While defaulting the Code Combination, do the training attributes
include POET information along with Supplier/Supplier Site,
Business Unit, Legal Entity, Header-Line description, etc.?
a. Training the Model
Today
is 01-Oct-24, and in our Non-Prod environment, we set the P2T refresh
date to 01-Jul-24. For training the model, it considers the last 18
months of invoice history. Specifically, it includes:
1. From Prod: It reads invoices with invoice_date later than 01-Jul-24
through to 01-Oct-24. - No, the AI Apps features only ingest data from
the related Fusion environment for model training. Hence only data
from non-prod is ingested to train the model in non-prod
2. From Non-Prod: It reads invoices with invoice_date from 01-Mar-23
(18 months prior to today) to 30-Jun-24. - yes only the data from prior
to the P2T Refresh date will be used up to 18 months from today's
date
i. To train the Non-Prod model (as part of convincing the business for
approval), if we create invoices in Non-Prod today with invoice_date ranging
from 01-Mar-23 to 30-Sep-24, these new invoices should be included in the
training from Non-Prod. is it? No, the date criteria for ingestion and model
training is the creation date, not the ingestion date. If you want to train a
model on new data that you generate in test, then you will have to move
the P2T Refresh date after that date. So if you enter data on the 2nd
October, set the P2T Refresh date to 3rd October. However, this is not
recommended as test data will also be included in the training set. Also the
new data that you create will only be in the evaluation but not in the
training set of the model. The feature is optimised for Production and to
test based on Production data. The feature is not optimised to support to
test on new training data as this typically is not a true reflection of the
model that customers will have in Production
ii.
And if I change the P2T refresh date to today in NonProd then all 18
months invoices, to train the Non-Prod model, will be considering from
Non-Prod only . is it? Yes correct, see above
iii. And also I believe it takes only the validated invoices (though not
accounted). Correct
iv. I believe the new data for training is based on the invoice_date and not
the creation_date. Can you confirm if this understanding is correct and
provide any additional comments? The date criteria is based on the
creation date of the respective invoice distributions
iv.
d. Architecture Diagram
Your
explanation was very helpful. We encountered an issue with assigning
'Dynamic Discounting' Adaptive AI application roles to a user. Even our
Admins, who possess the necessary access, are unable to see these
application roles in 'Oracle Cloud Services' when navigating to the
Adaptive AI Apps page from ERP Cloud.
Since the AI Apps exist in
the same POD, I assume the admin access for these PODs is equivalent to
the admin access for SaaS ERP Cloud. We logged an SR two weeks ago but
have not received a satisfactory response yet. If you have any insights
or can share related information, that would be appreciated.
Alternatively, I can start a separate thread for this issue.
AI Apps have a separate IDCS stripe and only the default IDCS
Administrators are provisioned with the respective IDCS Administrator roles
in this new stripe. If you send me the pod name in a Direct Message, I can
check if the engineering team can find the respective resources. However,
if the default IDCS Adminstrators are not known, raising a SR is the correct
process
e. Support for Custom Invoice Sources
Thank
you for confirming that this feature applies to all invoice sources
except for one. To elaborate on its practical application:
We can create only Manual Invoices from the UI where it defaults.
For IDR, similar defaulting behavior might be applicable.
For
other custom sources, typically created using FBDI, how does
defaulting
work? Specifically, should we omit the Expense account for lines so
that the importing program defaults them? Will this approach ensure
that
the segments default correctly and the statuses remain valid?
The prediction service can currently only be invoked from the invoice line
and is not invoked during the invoice import. Hence the spreadsheet source
is excluded from model training as it will be more efficient to enter the
account code combination in the FBDI spreadsheet. Also the feature is
optimised that values are only defaulted if the dynamically calculated
confidence score threshold is reached. Hence for some invoice lines the
segment values are not defaulted. The feature is intended to drive a high
level of accuracy of the data that is captured in the Account Combination
but support the user by defaulting the values with sufficient confidence.
f. Default from Invoice Distribution Combination or Accounted
Combination (Post-SLA)
1. Invoice Accounting Combination:
We
create invoices (using FBDI) for custom sources with a specific
code
combination for the expense account. Later, while executing
'Create
Accounting,' SLA rules apply, updating the initial invoice
distribution
code combination with the final, SLA rule-based code
combination.
Does
the IACD train the model based on the initial Invoice Distribution
Code
Combination, or is it the final accounted Code Combination post-
SLA
application?
The model is trained based on the initial code combination and not post
SLA. This is to default the same values as are visible in Payables. Hence in
your scenario, if the SLA rules derive the correct code combination in all
instances, it will be more efficient to maintain the existing process
1. Training Attributes:
While
defaulting the Code Combination, do the training attributes
include
POET information along with Supplier/Supplier Site, Business Unit,
Legal
Entity, Header-Line description, etc.?
POET information is currently not used. The full list of attributes used in
Here are two product specific solutions found on the Oracle Cloud
Marketplace
OAN Accounts Payable for Fusion Apps
https://cloudmarketplace.oracle.com/marketplace/en_US/listing/154474834
OAN Sales Order Automation
https://cloudmarketplace.oracle.com/marketplace/en_US/listing/146393995