Skip to main content
Skip table of contents

Setup - BQ

System Requirements

  • Bid/Quote Management Module
  • Purchasing Module
  • Documents Online (for file attachment support)
  • BusinessPlus Dashboard
  • Click, Drag, and Drill (CDD)
  • Workflow

Required Interfaces

  • Purchasing System (Interface is Bid Number and Product Code) — You must create a purchase request prior to entering the bid.
  • Purchase Request Number — The Bid number, Contract number and Purchase Request number must be different.
  • Accounts Payable (Interface is Bid Number)
  • Product Information (Interface is Product Code)
  • Vendor Information (Interface is Vendor ID and Product Code)
  • Commodity and User Selection or Association Code
  • Stores Inventory (Interface is Product Code)

General Configuration

The general configuration settings for the BusinessPlus side of Bid Online are made through the BQUPON screen. One record should be created for each entity and ledger that will be communicating with the Bid Online server.

Attachment Definitions

Two attachment definitions must be defined in the Administrative Console:

  1. The first one is linked to table BD_BDFBID to track attachments to bids. Bids in the Bid/Quote module are only tracked by bid number, so only one column needs be defined: BIDNUMBER.
  2. The second definition is linked to the BD_BDITEM and BQ_OPEN_RSP_DTL tables and is used to track attachments provided by responding bidders. BD_BDITEM is the standard Bid/Quote table where bid responses are stored. BQ_OPEN_RSP_DTL stores all of the answers from opened bids imported from Bid Online. Bid responses are tracked by bid number and vendor ID, so two columns must be defined: BIDNUMBER and VENDORID. For BQ_OPEN_RSP_DTL, columns BID_NUMBER and PE_ID are needed.

Commodity Codes

The client must license one of the following supported commodity code sets:

  • 5-Digit NIGP
  • 8-Digit UNSPSC

For more information, see Load Commodity Codes.

Common Codes

  • PEAS/BOID — Vendors from the BusinessPlus system are linked to bidders through their tax ID and Bid Online Nucleus ID. Each PEID that is linked to a bidder will have a PE association code of "BOID" (Bid Online ID). Before any PE association code can be used, it must be defined in common codes under the PEAS category.
  • NUAS/BQADMIN — Only BusinessPlus users who have been granted access will be able to use the Bid Online dashboard area. Access is granted by assigning a Nucleus association code of BQADMIN to each user in Nucleus User Security. Before any Nucleus association code can be used, it must be defined in common codes under the NUAS category. Typically, users that are assigned the BQADMIN security association are buyers in the purchasing department or users who administer bids published online.
  • BQEN/ENTITY — When the BusinessPlus 7i server communicates with the Bid Online server it must identify the user's assigned entity code.
  • NUAS/BIDDER — To allow bidders access to the non-public portions of Bid Online, each bidder's Nucleus ID will have an association assigned. While this assignment is done automatically as bidders register, you must still define the BIDDER association, so the system knows it is a valid association code.
  • SYNO/BIDDERID — If a new seed is being used for the bidder IDs in Nucleus, create this common code. The Nucleus Bidder ID is used only to link records on the Bid Online server, so the format is mostly irrelevant. Most important is that the format of the seed be different than other groups of Nucleus users on this server.

BQ Codes

The Bid/Quote Management Codes (BQUPCD) pagerepresents the code table associated with the Bid/Quote Management Subsystem. This table must be set up prior to using Bid/Quote Management. Coded values will be determined for specific fields. The codes will be determined by the staff to allow consistent and fast data entry. 


 

JavaScript errors detected

Please note, these errors can depend on your browser setup.

If this problem persists, please contact our support.