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
When a new supplier user account is created in the application, an email is sent to the new user to reset password and log into the system. This email, however, does not contain the username information by default. Buying organization usually determines the username format internally, for example, firstname.lastname@<company domain>.com; this format information is not clear to its supplier users. You can follow the steps below to include the username information in the email so that supplier user will have the complete account information to access the Supplier Portal application.
Emails sent to new supplier users will contain the username information to help user successfully log into Supplier Portal. (See the screenshot for an example email below.)
Please note that since all new users in the application is assigned to Default user category by default, the notification template change above will impact all new users in the application.
You can reference more details on defining notification template in the following link:
Good People,
How to track the supplier logins form supplier portals ?
Thanks,
Soumya
When a user account is created for a supplier contact, email is used to generate the username by default. This can be changed if other rule is preferred. Please follow these steps:
Supplier user account created onward will use the new username generation rule. Note that the username generation rule is applicable to all user accounts including non-supplier users.
This is determined by supplier user data access.
While managing supplier contact user account, alongside the Roles tab, there is a Data Access tab. The Restrict Access To field determines which set of documents a supplier user can access in Supplier Portal. Supplier data security supports two data access levels to control which transactions supplier users can access in Supplier Portal:
• Supplier level data access allows the supplier user to access all transaction documents that belong to the supplier for which the supplier user is associated with.
• Supplier site level data access limits the supplier user to access only the transaction documents that contain the specific supplier sites for which the user has been granted access to.
TIP: Data access controls the transaction access for supplier portal users. Since data access definition can expand to parent-child relationship, user with proper data access can see transactions from child suppliers. For supplier profile, users with Supplier Self Service Administrator job role can only manage profile for their own company.
I have created several Self Registered Suppliers - complete with Contacts (sometimes multiple). After we have approved them and start to create Requisitions, Purchase Orders, Contracts and Negotiations using these Suppliers, the Contact name (and email) are unavailable. Thinking that I may have missed a step in the setup, I went back and tried to get the Contact to appear. No Luck! Any thoughts? Anyone else find this? We had the problem in 19B and have just updated to 19C with the same issue...
Thanks,
Bill
This dashboard will allow you to retrieve a list of your supplier contacts and filter it by the Contact Status and User Account Status.
The Contact Name and Phone columns of the report are designed to display the Name and Phone Number as concatenated values. The report can be updated to display other contact information such as Mobile and Fax easily.
The attached Deployment_Instructions.pdf contains steps for importing the dashboard to your instance. Also attached is the Supplier Contacts Listing.catalog file to import the dashboard to your instance.
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
We would like to create a custom role for certain suppliers to prevent submitting invoices via Supplier portal. I see that the seeded role "Supplier Accounts Receivable Specialist " needs to be copied and modified to achieve this. I need to know what are the priveleges that needs to be removed. Should this be removed in the Role Hierarchy or the Function security policies?
Is there any document to setup the custom role?
Hi,
I've got through the guides and have enabled *every* checkbox (that's not an attribute). However when we make an amendment to a supplier contact, as an example, make a change to their phone number, this is now shown in the audit report
Should it be? If so, why is it not showing for me? If not, how can I see this amendment?
Thanks
Hi,
I've tried reading the guides on "Implementing Supplier Audit History" but all the references are to the procurement application but all we have is the supplier product.
Is there any useful guidance on viewing supplier audit history in R13?
Thanks