Setting up the back office for the Vendor Portal

This chapter contains information about setting up for your Vendor Portal. After this setup is complete, vendors will be able to review purchase orders, planned orders, inventory, documents, interactions, and more.

This table shows the necessary setup tasks. For multi-site implementation, the table shows whether to perform each step in the Primary Site, all sites, or only desired sites. If your implementation has only one site, then that is the Primary Site.

✔	Description	Back office form	For multi-site, perform in...
❑	Set up the site group.	Site Groups Portal Parameters	Primary Site
❑	Define replication rules. Required for multi-site implementations.	Replication Rules	All sites
❑	Specify the forms database	Sites/Entities	All sites
❑	Set up information about the vendor's company.	Vendors Vendor Contracts	Primary Site*
❑	Set up contact information for your company.	General Parameters Vendors	All sites
❑	Set up the back office to manage consigned inventory. (Optional)	Warehouses Item/Warehouse	All sites from which consigned inventory is provided
❑	Set up documents. (Optional)	Groups Document Types Attached Documents	All sites
❑	Set up interactions. (Optional)	Employees Interaction Topics	All sites
❑	Set up item price requests.	Items Item Categories or Vendors	All sites
❑	Set up planned orders.	Purchasing Parameters Vendor Contracts Vendors or Multi-Site Vendors Report Options	All sites
❑	Set up a default bank code.	Accounts Payable Parameters	All sites
❑	Maintain ISO unit of measure codes.	Unit of Measure Codes	All sites
❑	Add portal-enabled user accounts.	See Setting up portal user accounts	All sites*
❑	Set up event notifications: Activate workflow event handlers. Subscribe users to publications. Specify the forms database. (Optional) Assign users to event global constants. Choose whether to use rich HTML-portal email. (Optional)	Workflow Event Handler Activation Publication Subscribers Sites/Entities Event Global Constants Portal Parameters Portal Manager	All sites

* The user account record must exist in all sites. The vendor record must exist in the Primary Site but does not have to exist in other sites of the portal site group. The vendor user association record must exist in the Primary Site but does not have to exist in the other sites. If you want to display vendor data from all sites, then you would create all records in all sites.

If the vendor user association record does exist in another site, the record must point to the same vendor number used on the vendor user record in the Primary Site. Failure to use the same number results in a login error.

In the Vendor Portal, partial data is displayed when a user account exists in all sites (as required) but the vendor user record exists in only some sites. Data is displayed from the sites where the vendor user record is included, because IDO filtering is used.

An IPF session start script includes an account correction routine that creates missing vendor user association records in the non-primary sites, if the user and vendor records exist in those sites. This routine does not create vendor records or user records.