Skip to main content
Skip table of contents

Bid Cycle Definition - BQUPCY

The primary purpose of the Bid/Quote Management (BQ) Bid Cycle Definition (BQUPCY) page is to establish the complete cycle of any formal bid process. Each site will have numerous occurrences of this page. The overall flow of the cycle being defined is controlled by the order in which the task numbers are entered. The system will, based upon the tasks entered, calculate both the business days and calendar days necessary to complete the entire process. One line for miscellaneous comments is allowed at the bottom of the page.

Cycle ID: Up to nine characters identifying the Cycle ID. The Cycle ID may be auto-generated by defining a seed value in NU Common Codes, with a Category/Value of SYNO/CYCLEID. The unique Cycle ID key is a combination of Cycle ID and Task ID. There can be multiple Task IDs for the same Cycle ID but only one unique combination.
Title: Free form title of the bid cycle.
Description: Free form text, unlimited length, used to describe the bid cycle.
Total Days Needed: This field is display only. System generated total based upon task entered below. Display is in business days. System will need to convert task created using calendar days into business days.
Total Calendar Time: This field is display only. System generated total based upon task entered below. All tasks that reference business days will be converted to calendar days (by the system) for this total.
Step: System numbered, unlimited numbers.
Task ID: Enter Ctrl+L or click on ellipsis for a list to select from. Validated against tasks defined on the BQ Task Definition (BQUPTD) page.
Title: Display only based upon task #.
Days Req: Display only, based upon task #.
Type: Display only based upon task #.
Code: Code for other requirements. Codes in the drop-down are defined on the BQ Codes (BQUPCD) page.
Comments: Free form text. This field is limited to the one line.

JavaScript errors detected

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

If this problem persists, please contact our support.