Roadmap for Setting up Supplier Portal
Product data stewards need to carry out the following tasks before supplier users can begin managing their products in Product Hub Portal.
|
Required Setup |
Description |
|---|---|
|
Associate the Job Role with the Supplier User |
All supplier users need to be assigned the Supplier Product Administrator job role for accessing Product Hub Portal. Note: Oracle recommends that security administrators don't assign these
predefined roles directly to users. Instead, make a copy of a predefined
role, remove the privileges that your users don't need, and assign users the
role that contains only the privileges they need.
|
|
Define Spoke Systems |
Separate spoke systems must be setup for every supplier who uploads product data. |
|
Item Class Security |
Item class security needs to be setup for the supplier users who upload product data. On the Edit Item Class page Security tab, the Supplier Product Administrator job role needs to be given item data privileges similar to other job roles such as the Product Data Steward. |
|
Define a Default Catalog |
The default catalog must be set using the Manage Advanced Item Profile Option task. |
|
Create Catalog Category Mappings |
Mappings between the categories of the default catalog and item class need to be setup for deriving the item class of supplier products. |
|
Set up Item Extensible Attributes for Product Hub Portal |
Use the Edit Item Class task in the Setup and Maintenance work area to expose item extensible attributes to suppliers. Attributes are selected on the Product Hub Portal subtab in the Pages and Attribute Groups tab of the Edit Item Class task. |
|
Set up Import Maps |
Import maps are used to allow suppliers to import their product data with generated pre-defined templates. Import Maps must be set to External in order for suppliers to access the associated templates. |