Configuring data for Vendor Persona

You need to set up data to use the Vendor Persona.

Before you begin

  • Import the vendorportal.zip file. For more information, see Importing data model - Vendor Persona.
  • Add the following properties to the common.properties file in the <install_dir>/etc/default folder of the application and restart the Product Master services after the update:
    • vendor_organization_hierarchy=Vendor Organization Hierarchy
    • vendor_product_workflow=Product Enrichment Workflow
    • vendor_collab_table=Vendor Collab Table
    • vendor_role_name=Vendor
    • owner_approval_workflow=Supplier Products Approval Workflow

Procedure

  1. Browse to the following locations and verify that the Catalog ACG, Hierarchy ACG, Vendor role, Vendor Organization Hierarchy, Vendor Lookup Table, Vendor Collab Table, and Vendor User are available as follows.
    Browse to... Verify that you see..
    Data Model Manager > Security > Access Control Groups > Access Control Group Console Catalog1 ACG and Hierarchy1 ACG
    Data Model Manager > Security > Role Console Vendor role
    Module > Please select a module to add Vendor Organization Hierarchy
    Product Manager > Lookup Table > Lookup Table Console Vendor Lookup Table and Vendor Collab Table
  2. Browse toModule > Please select a module to add > Vendor Organization Hierarchy > + to add the Vendor Organization Hierarchy from the Modules section to the left pane.
  3. Create Spec, Hierarchy, Catalog, and Attribute Collection for the catalog attributes as follows.
    Create.. Browse to...
    Spec Data Model Manager > Specs/Mapping > Specs Console
    Hierarchy Product Manager > Hierarchy > New Hierarchy
    Catalog Module > Please select a module to add > Select Catalog > +
    Attribute Collection Data Model Manager > Attribute Collection > New attribute collection
  4. In the left pane, right-click the catalog that you added in the Step 3 and browse toCatalog Attributes > add secondary hierarchylist, select Vendor Organization Hierarchy, and click Add to add the Vendor Organization hierarchy as a secondary hierarchy to the catalog.
  5. Right-clickVendor Organization Hierarchy > Add Organization, enter Vendor Name, and click Save to add a vendor organization under the Vendor Organization Hierarchy.
    The collaboration area for the newly added vendor organization is created and mapped into the Lookup table. Verify this by browsing to Collaboration Area > Collaboration Areas > Collaboration Area Console.
  6. Browse toReport > Report Console > Vendor User Creation Report Job, enter User Details, then browse toSave > Back, and click Report Console icon to add the user data in the Vendor User Creation job and run the report.
    Note: The User Details or Vendornamefield in the user details sections for the user creation report needs to be an existing vendor category.
    This step adds the user as an administrator for the collaboration created.
  7. Browse the Product Enrichment Workflow and Supplier Products Approval Workflow and add the attribute collection that is created for catalog attributes into all the workflow steps including the Initial step. Add the attribute collection that is created for catalog attributes to,
    • General Information tab of the Rework step in the Product Enrichment Workflow.
    • General Information tab of the Internal Approval Step in the Supplier Products Approval Workflow.
  8. Browse toReport > Report Console > Supplier Products Collab Creation Job, and select the created catalog to create the Supplier Products Approval - <catalog name> by running the report job.
  9. Browse toVendor Organization Hierarchy > Specs and verify that the VendorInfo secondary spec is mapped to the vendor organization.
    Important: The items coming from the Vendor to the Owners Collaboration Area get mapped to the Vendor Organization Hierarchy and the administrator should not add, edit, or delete any other vendor hierarchy to the item. If the administrator deletes the vendor hierarchy from the Category tab, the item is lost as due to no linking. If the administrator adds other vendor hierarchy to the item, it is a security breach as one vendor's item gets mapped to the other vendor.

What to do next

Add the full admin access to the Catalog 1 ACG, which is used for the catalog that is created for the vendor.