Overview
Document Type contains the catalogue with all the procurement document types such as Request for Proposal – RFP, Request for Quotation – RFQ, Expression of Interest – EOI, etc.Each Document Type can have one or more Sections defined. Also users can configure the behavior that Document Type must have on each Stage.
Navigation
Procurement ► Support Entities ► Document Type
Document Types screen Fields and Tab
Field | Definition |
Id | Unique auto-generated numeric code of Document Type. |
Custom Domain Type | Users can use Custom Domain Type (CDT) to add information in addition to the entities included with the base Procurement Document Information. This CDT is inherited to the Procurement Document and users can add more if it is needed, or clone existing CDT to add more to the Procurement Document. |
Language | Country specific language used to describe Document Type. |
Name | Name of the Document Type. |
Description | Brief explanation of document type. |
Purchasing Vehicle Required? | If true, the system will require a Purchasing Vehicle when creating a Procurement Document. |
Expiration Date Required? | If true, an expiration date is required when the vendor is uploading the proposal information. |
Intend to Award Period | It must be expressed in calendar days and applies only if the Procurement Document Type Stage 'Intend to Award' has been set mandatory or optional. |
Type of Result Expected | Users must select the final result expected for the evaluation of the procurement document. |
Purchasing Vehicle | Users select one Purchasing Vehicle. When there is a value in this attribute it is copied to the Procurement Document once the Procurement Document Type has been selected. |
Is Ownership validation required ? | Indicate when Ownership Validation is required to be executed by users for the procurement Documents of this Procurement Document Type. |
Sections Tab | Each procurement document type can have a collection of 1 or many sections related and the order of such sections. |