For partners that build or integrate commercially available applications and service solutions with the Oracle Cloud Platform
For partners that provide implementation or managed services around Oracle Cloud Applications
Hi,
since a few days, all external supplier registration requests keep beging rejected straight away. I have linked a rule that should automatically approve all registrations, but every supplier I try keeps being rejected. The message just says ' supplier rejected' and I cannot see any additional information why the supplier is rejected. In the supplier data I cannot see any details, it just says error (see attachment).
Internal supplier registrations do work (similar rules) and also the promote to spend approval flow works properly.
Can I see somewhere what is the cause of this issue (why is it rejected) and what could be the cause?
Thank you
Jasper
Created a new business unit under an existing ledger. Performed required tasks associated with business units.
At the time of creation of new supplier site for BU, I do not see the name of new BU in the list of values of Business units while creating a supplier site. Please suggest me with your feedback.
I am in R13 -18A enviroment of Fusion Cloud Enviroment.
Thanking You
Binayak
We have 900 and plus supplier sites which have gone to inactive status and now we want to make them active.
We tried using the Supplier Site Import process and kept inactive date blank, but still, we are unable to make them active.
Any another process we should follow?
Any suggestions are welcome.
Reg,
Sanket S
In the Prospective Supplier Registration Page in the section of Roles a supplier can add certain roles.
We want to adjust the values in the LOV.
We want to keep the roles active but some of them we don't want to have them appear in this LOV
Where can we change the setup of the values in this LOV?
We have a requirement to be able to segregate which product a user can query in the audit reports; so for example a Vendor Help Desk user can query only those attributes associated to the product "Supplier Model" vs all products currently set to audit.
Has anyone else found a way to split up the audit reports search function? Currently the privilege "View Audit History" grants access to every Product.
Name | View Audit History |
Code | FND_VIEW_AUDIT_HISTORY_PRIV |
Description | Allows to view the audit history of all the business object attributes enabled for auditing. |
Thank you
There are two levels of security that allows access the supplier site information:
Let’s review these use cases to better understand the data access control on supplier sites:
To ensure the user has view access to all sites information i.e. sites belonging to all procurement business units, grant the privilege View Supplier Site to the user.
There are two steps involved:
Points to Consider:
Hi,
Need help in Audit tables list for Oracle cloud, as per the requirement we enabled the audit feature for supplier model for few columns like Supplier name, Supplier site, IBAN etc.
We need to see in which table these history will be saved, I am unable to get the Audit table names, Please help.
After a supplier's spend authorization request is approved, the following changes will be applied on the supplier profile:
Sites and site assignments are necessary for any financial transactions for the supplier. Site creation is automated so that sites are available at the earliest and with minimal manual intervention.
Site assignments are also auto created based on the Procurement BU of the site. For more flexibility, you have the option to control the auto creation of the site assignments i.e. you can configure whether auto creation should happen for site assignments or not.
This configuration is controlled by a checkbox option ‘Auto create site assignments for spend authorized suppliers’ present on the Configure Supplier Registration and Profile Change Request setup. By default, the checkbox is enabled that means site assignments will be created automatically. Unchecking this checkbox will prevent the auto creation of site assignments post spend authorization request approval.
If you choose to not auto create site assignments, you will have to create them manually from the Edit Supplier page before you enter transactions for such suppliers.
Best Practice:
Based on the business unit setup, consider the number of client BUs that will need to transact with the sites. If the majority of them will need to use the sites for transactions, enable the auto create site assignments option. Otherwise, it may be better to manually create the site assignments rather than deleting the unwanted assignments created from the auto create configuration.
Submit your questions for the SCM – Supplier Onboarding: Deep Dive and Best Practices session to have them answered during the live event. Post your questions by posting a new comment to this topic.
Please submit your questions by Wednesday, 20 November 2019.
If SSO is enabled, user account creation emails are generally disabled and this causes a challenge to implement supplier portal. As suppliers do not get communicated about their account creations automatically as soon as the account is created, followings are the possible solutions (and their challenges) which can be suggested to clients (there can be few more but these are based on my understandings of the application):
1: Once supplier is registered and account is crated, go to security console, change the user category and reset the password to resend the emails to suppliers.
Challenges - In most of the public (even in private) sectors, this activity is performed by a dedicated team of supplier admins/managers and they are not supposed to have the access of "Security Console" because of organisations security policies. Hence this solution doesn't sound feasible to clients.
2- Keep notifications enabled and modify the content of user account email. Detail clear cut instructions for employees and suppliers on how they can access the application but again it comes with the risk that employees (new) might miss the instruction and start using it with the credentials provided in email rather that the SSO ones, which is again big concern for organisations.
These are the 2 possible solutions which I could have thought of based on my understanding of Cloud application. Please feel free to correct me or suggest any alternate solution if you have come across similar requirement.
Thanks
Vineet Gangwar