Header

The Header tab of the Solicitation transaction lists general information describing the procurement.

Procurement Folder LogicProcurement Folder Logic

If this is the first transaction within a procurement folder, then on validate of a draft transaction, the system assigns a unique Procurement Folder ID on the procurement Header. Or if it is associated with another procurement transaction and that transaction was the first transaction within the Procurement Folder, then Procurement Folder, Procurement Type ID and Procurement Type fields are populated with inferred values on copy forward. When the Procurement Folder ID field is populated indicating that it is associated with a folder, the View Procurement Folder action is activated on the transaction Header allowing users to transition to the Procurement Management page to review other Procurement Folder information associated with this selected folder. Once the user has transitioned to the Procurement Management page a Back link is displayed allowing the user to transition back to the transaction Header where the transition began.

Solicitation Category LogicSolicitation Category Logic

The Solicitation Category field is used to define a high level solicitation category group. The Solicitation Category is defined by each site on the Solicitation Category page and is intended to make the solicitation bidding easier for vendors by allowing them to narrow their search in VSS by Solicitation Categories. Examples of Solicitation Categories are: Construction, Services/Consulting, Technology, Equipment, Printing, Supplies, Sub Contracting, and Professional.

The following Solicitation Category inference logic applies:

  • On validate of SO Transaction Type transaction and Solicitation Category field is blank, the system will perform the first lookup to the Solicitation Category field on PRDOC for this Solicitation Transaction Code.

  • If no value is specified in the Solicitation Category field on PRDOC, then the system performs next lookup to the Solicitation Category field from the Procurement Type.

  • If no value is specified in the Solicitation Category field on Procurement Type, then the default Solicitation Category is inferred from the ‘Default’ entry on the Solicitation Category table for this transaction.

  • In all cases, the user is allowed to change the default value of the Solicitation Category that is inferred to the SO Transaction Type transaction.

Vendor RestrictionsVendor Restrictions

The following vendor restriction flags are available on the Header of the solicitation transactions:

  • Vendor List Restricted Access to Solicitations? - This flag, when selected, indicates that the solicitation can only be viewed by those vendors and their associated VSS users that are listed in the Vendor List tab of the SO transaction. This flag has no system relationship to the Vendor List Restricted Responses? flag.

  • Vendor List Restricted Responses? - This flag indicates whether the vendors on the Vendor List are allowed to submit a response for this solicitation. If this check box is selected, then only vendors on the Vendor List are authorized to submit responses (SR transactions) in VSS.

  • Restrict Public Access Ask Questions  - This flag indicates whether public access users in VSS are allowed to ask questions online for a published solicitation.

Required/Conditionally Required FieldsRequired/Conditionally Required Fields

The following fields are required, and if left blank are automatically populated:

  • Record Date

  • Procurement Type

The following fields are conditionally required based on site specific setup on the Transaction Control (DCTRL) table:

  • Transaction Description

  • Issuer ID

  • Requestor ID

  • Name

  • Phone

  • Email

The following fields are conditionally required based on site specific setup on the Procurement Transaction Control (PRDOC):

  • Terms and Conditions Template

  • Reason for Modification

  • Grant Year (this field is delivered hidden and can be changed to displayed via Configure Page (DESIGNER), to make it available for use on SO type Grantor transactions.)

If the Enforce Transaction Department Validation field on the Transaction Control (DCTRL) page is selected, the values entered in the following fields are validated against the Transaction Department to verify that the value entered is authorized for that specific Transaction Department:

  • Bid Receiving Location

  • Issuer ID

  • Requestor ID

  • T & C Template

TasksTasks

Create a Terms and Conditions TemplateCreate a Terms and Conditions Template

The Add Templates section allows you to optionally place the Terms and Conditions you have set up on the current solicitation into a template on the Terms and Conditions Template (TRMTM) table. 

  1. Enter a value in the T & C field.

  2. Enter a value in the Name field

  3. Select the Add Template check box.

Create a Vendor List TemplateCreate a Vendor List Template

The Add Templates section allows you to optionally place the Vendors you have set up on the Vendor List tab for the current solicitation into a template on the Vendor List Template page. (Note: Vendors added by the Vendor Rotation tab or by the Free Form Vendor tab will not be added to the template.)

  1. Enter a value in the Vendor List field.

  2. Enter a value in the Name field.

  3. Enter a value in the Buyer ID field.

  4. Enter a value in the Department field.

  5. Enter a value in the Comm Class field

  6.  You can optionally select the Prequalified List check box to indicate whether a pre-qualified vendor list was used for the Solicitation.

  7. Select the Add Template check box.

Once added, the newly created template can be selected on future transactions.

Create an Evaluation Criteria TemplateCreate an Evaluation Criteria Template

The Add Templates section allows you to optionally place the Evaluation Criteria you have set up on the current solicitation into a template on the Evaluation Criteria Template page. 

  1. Enter a value in the Evaluation Criteria field.

  2. Enter a value in the Name field

  3. Select the Add Template check box.

Once added, the newly created template can be selected on future transactions.

The Header tab contains the following actions/links:

Page-Level ActionsPage-Level Actions

Refer to the "Transaction Actions" topic in the Transactions User Guide for information on common actions that apply to the entire transaction.

Tab-Level actions/linksTab-Level actions/links