The 19C feature: Navigate to Supplier Profile from Reports allows you to include links in your ad hoc OTBI and BIP reports. These links can be used to navigate to and view supplier profiles.

Below is an example of one such ad hoc OTBI report that lists suppliers missing Business Classifications. This report can be used to review the list of such suppliers and update their profiles to include the missing information.

Derive Bank Account Number from IBAN is a Payments feature introduced in update 18C. The following link contains the steps to enable this feature: Derive bank account number from IBAN.

The same feature has been incorporated into supplier profile management flows through a couple of updates. Here is the summary of the timeline:

19A - this feature is available in the profile management flow for internal supplier administrators/supplier managers as well as self-service profile management for supplier users from Supplier Portal.

19B - in addition to the 19A scope, this feature is also available in supplier registration for internal and external users.

Supplier has more than one Site that need to be marked as 1099 reportable

Summary:

Unable to select more than one site for tax reporting

Content:

We have suppliers that have multiple sites for payable/remittance addresses. We need to be able to make all sites 1099 reportable but get an error when trying to select more than one. Is there a workaround for this?

There is a requirement to subscribe Supplier create/update event in OIC, which is currently not available in ERP cloud event catalog service. I just went through the below document, which has all the events of Procurement and SCM, I still didn't find the event for creating/updating supplier. Can you please help me with this?

Also, I didn't find the event for Location, that gets triggered as soon as there is an updates in the location.

Need to create supplier contact in SAAS environment, we didn't find any rest API's to create/update supplier contact, there are rest api's available for getting supplier contact. Can someone please help me with this?

Understanding the approval rules setup and how these are evaluated to route a supplier profile change request.

Content:

In an earlier post (link), we explained how a supplier profile change request is determined for approval requirement using two setup pages. The first one determines if an approval is required or not. If from the first setup, application identifies that approval is required, then it uses the second setup to determine the approvers for the change request.

The setup pages are:

1. Configure Supplier Registration and Profile Change Request, and

2. Manage Supplier Profile Change Approvals

Through this post, we will explain how Manage Supplier Profile Change Approvals setup page can be used to meet your approval routing requirements.

Manage Supplier Profile Change Approvals

This setup page has two stages and six participants in total. For the detailed explanation on stages and participants, you can review our whitepaper: Setting up Document Approvals Oracle Fusion Procurement Cloud (Doc ID 2264952.1).

Using this setup page you can author approval rules with conditions based on which a change request will be routed for approval. As part of rule configuration, you also choose the list of approvers who should receive the request for their approval when a rule evaluates to true.

To author approval rules, it is important to understand how application uses approval attributes based conditions to evaluate approval rules. Following are the key points along with examples to explain how this is done. Please note, the values denoted in single quotes are valid values for given supplier attribute that will be used as an approval attribute or change request attribute or both.

If the value of approval attribute is changed, the changed value of the approval attribute is considered to evaluate if the approval condition is true.

Examples:

Approval Rule Attribute

Approval Rule Condition

Change Request

Rule outcome/Case from flowchart

Supplier Type

Supplier Profile Value = ‘Sub-Contractor’

Supplier Type equals ‘Manufacturing’

Supplier Type Changed to ‘Manufacturing’

True/Case 1B

Supplier Type Changed to ‘Internal’

False/Case 1A

If the value of approval attribute is not changed, but another supplier profile attribute belonging to the dimension of the approval attribute is changed, then the supplier profile value of the approval attribute is considered to evaluate if the approval condition is true.

If the changed attribute does not belong to approval attribute’s dimension, then following additional cases apply:

If the approval attribute belongs to one of the following dimensions - change request header, change request organization detail and change request tax identifier, then the supplier profile value of approval attribute is considered to evaluate if the condition is true.

Examples:

Approval Rule Attribute

Approval Rule Condition

Change Request

Rule outcome/Case from flowchart

Supplier Type

Supplier Profile Value = ‘Sub-Contractor’

Dimension: Change Request Organization Detail

Supplier Type equals ‘Sub-Contractor’

Products and Services Category added: ‘Hardware’

True/Case 4BB

Supplier Type equals ‘Manufacturing’

Products and Services Category added: ‘Hardware’

False/Case 4BA

If the approval attribute does not belong to one of the following dimensions - change request header, change request organization detail or change request tax identifier, then the condition will always be evaluated to false.

What is the best way to move Supplier data from a DEV POD to Production

Content:

The client's existing supplier information is in poor shape - no/missing emails, no contacts, Business classifications are non existent and Products and Services offered is not available.

We are considering having ALL suppliers register into a Protected DEV environment thereby getting all of our necessary information verified and updated prior to going live. The issue is how can we best move that good data into the Prod environment?