PON_REQUIREMENTS
PON_REQUIREMENTS stores header level requirements defined by the negotiation owner for auctions, RFQ, and RFIs. These requirements enable buyers to request information with more detail than is possible with the standard fields.
Details
-
Schema: FUSION
-
Object owner: PON
-
Object type: TABLE
-
Tablespace: Default
Primary Key
| Name | Columns |
|---|---|
|
PON_REQUIREMENTS_PK |
REQUIREMENT_ID |
Columns
| Name | Datatype | Length | Precision | Not-null | Comments |
|---|---|---|---|---|---|
| AUCTION_HEADER_ID | NUMBER | 18 | Yes | Auction Header Id | |
| REQUIREMENT_ID | NUMBER | 18 | Yes | Requirement Id | |
| PARENT_LEVEL | VARCHAR2 | 10 | Yes | Type of the requirement. SECTION if it's a first level requirement (parent of the requirement is a section). SCORE if it's not a first level requiremement (parent of the requirement is an acceptable value). | |
| SECTION_ID | NUMBER | 18 | Yes | Section id. This field will always be set for first level requirements and requirements whose parent is an acceptable value. | |
| SCORE_ID | NUMBER | 18 | Yes | Score id. It will be set to -1 if parent_level is "SECTION". Otherwise, it will be set to score_id of pon_requirement_scores. | |
| ROOT_REQUIREMENT_ID | NUMBER | 18 | Requirement id of the first level requirement in this branch. If this is a first-level requirement,it will be set to requirement_id. | ||
| PARENT_REQUIREMENT_ID | NUMBER | 18 | Requirement id for the parent requirement of a non-first level requirement. If this is a first-level requirement, it will be set to NULL. | ||
| SEQUENCE_NUMBER | NUMBER | Sequence number. Unique across all the sections in the negotiation. Store values such as 10,20,30... | |||
| DISP_SEQ_NUMBER | NUMBER | Requirement order within its containing parent (section or acceptable value). Store values such as 10,20,30... | |||
| ABSOLUTE_SECTION_SEQUENCE | NUMBER | For first level requirements (requirements that are children of sections), the absolute_section_sequence will be in increments of 100 like 100, 200, 300 and requirements that are children of scores will be in increments of 1 of their first level requirement. For example, 101-199 ; 201-299. This will allow us to only have to renumber within a first level requirement if it's children requirements change instead of all requirements in a section. | |||
| REQUIREMENT_TREE_LEVEL | NUMBER | The level at which the requirement is located at. Store values such as 1,2,3... | |||
| REQ_DISPLAY_NUMBER | VARCHAR2 | 80 | Identifier of the requirement. Store values such as "1.A.2.E.1". | ||
| REQUIREMENT_NAME | VARCHAR2 | 80 | Requirement name entered by the buyer. | ||
| REQUIREMENT_TEXT | CLOB | Requirement text. Use a clob to be consistent with POQ. This will help since questions could be added as requirements. | |||
| HINT | VARCHAR2 | 1000 | Requirement hint. | ||
| SUPPLIER_LEVEL | VARCHAR2 | 30 | Supplier level this requirement is targeted at. Values could be SUPPLIER or SUPPLIER_SITE. Stores the lookup value of PON_SUPPLIER_LEVEL. | ||
| RESPONSE_TYPE | VARCHAR2 | 30 | Requirement response type. Stores the lookup code for lookup type PON_HDR_ATTR_RESPONSE_TYPE. Possible Values are DISPLAY_ONLY, INTERNAL, OPTIONAL and REQUIRED. | ||
| REQUIREMENT_TYPE | VARCHAR2 | 30 | Requirement type. There are 3 possible types: 1) a multiple choice requirement with single selection, 2) a multiple choice requirement with multiple selections, or 3) a requirement where the response is entered in a field. Stores the lookup code of lookup type PON_REQUIREMENT_TYPE. Possible Values: MCSS MCMS INPUT_BOX | ||
| DATATYPE | VARCHAR2 | 30 | Requirement value type. Stores the lookup code of lookup type PON_REQ_RESPONSE_TYPE. Possible values are SINGLE_LINE_TEXT, MULTIPLE_LINE_TEXT, NUMBER, DATE and DATE_AND_TIME. URL | ||
| TEXT_VALUE | VARCHAR2 | 4000 | Target value of a Text/URL requirement. | ||
| NUMBER_VALUE | NUMBER | Target value of a Number requirement. | |||
| DATE_VALUE | DATE | Target value of a Date requirement | |||
| DATETIME_VALUE | DATE | Target value of a Datetime requirement. | |||
| DISPLAY_TARGET_FLAG | VARCHAR2 | 1 | Indicate whether display target value to supplier. | ||
| ALLOW_ATTACHMENT_CODE | VARCHAR2 | 30 | Indicate whether allow attachements from supplier. Stores the value of lookup type PON_REQ_ALLOW_ATTACHMENT. Possible Values are NOT_ALLOWED, OPTIONAL and REQUIRED. | ||
| ALLOW_COMMENTS | VARCHAR2 | 1 | Indicate whether allow comments from suppliers. | ||
| SCORING_METHOD | VARCHAR2 | 30 | Scoring method. Stores the lookup code of lookup type PON_SCORING_TYPE. Possible values are NONE, MANUAL and AUTOMATIC. | ||
| SCORING_TYPE | VARCHAR2 | 30 | Acceptable Response Values Type (NONE, LOV, RANGE). This is not based off a lookup_type. These are internal codes. | ||
| WEIGHT | NUMBER | Weight. | |||
| MAX_SCORE | NUMBER | Maximum Score | |||
| KNOCKOUT_SCORE | NUMBER | Knockout Score | |||
| MODIFIED_FLAG | VARCHAR2 | 1 | Modified Flag (Used for amendment/new round). | ||
| MODIFIED_DATE | DATE | Modified date (used for amendment/new round). | |||
| LAST_AMENDMENT_UPDATE | NUMBER | Last amendment update (used for amendment/new round). | |||
| QUESTION_ID | NUMBER | 18 | Stores question id for requirements that are tied to questions. | ||
| REVISION_NUMBER | NUMBER | 9 | Denormalized column for poq_questions_vl.revision_number. | ||
| IS_QUESTION_BRANCH | VARCHAR2 | 1 | Indicate whether the requirement was brought over as a branch from a predefined question. | ||
| PREVIOUS_REQUIREMENT_ID | NUMBER | 18 | Stores the previous document requirement's requirement_id during copy/new round/amendment. | ||
| CREATION_DATE | TIMESTAMP | Yes | Who column: indicates the date and time of the creation of the row. | ||
| CREATED_BY | VARCHAR2 | 64 | Yes | Who column: indicates the user who created the row. | |
| LAST_UPDATE_DATE | TIMESTAMP | Yes | Who column: indicates the date and time of the last update of the row. | ||
| LAST_UPDATED_BY | VARCHAR2 | 64 | Yes | Who column: indicates the user who last updated the row. | |
| LAST_UPDATE_LOGIN | VARCHAR2 | 32 | Who column: indicates the session login associated to the user who last updated the row. | ||
| OBJECT_VERSION_NUMBER | NUMBER | 9 | Yes | Used to implement optimistic locking. This number is incremented every time that the row is updated. The number is compared at the start and end of a transaction to detect whether another session has updated the row since it was queried. | |
| CATEGORY_CODE | VARCHAR2 | 30 | A code identifying the categorization of a supplier attribute, such as business classification or product and services. | ||
| IS_QUESTION_SCORED | VARCHAR2 | 1 | Y/N flag to indicate whether scoring is defined on the predefined question. | ||
| SEEDED_FLAG | VARCHAR2 | 1 | Stores 'Y' for default read only response amount requirement. 'N' for normal requirements. |
Foreign Keys
| Table | Foreign Table | Foreign Key Column |
|---|---|---|
| PON_REQUIREMENTS | pon_auction_headers_all | AUCTION_HEADER_ID |
| PON_REQUIREMENTS | pon_requirement_sections | SECTION_ID |
| PON_REQUIREMENTS | pon_requirement_scores | SCORE_ID |
| pon_bid_requirements | pon_requirements | REQUIREMENT_ID |
| pon_requirement_scores_int | pon_requirements | REQUIREMENT_ID |
| pon_requirements_int | pon_requirements | REQUIREMENT_ID |
| pon_requirement_scores | pon_requirements | REQUIREMENT_ID |
| pon_team_requirement_scores | pon_requirements | REQUIREMENT_ID |
| pon_bid_requirement_values | pon_requirements | REQUIREMENT_ID |
Indexes
| Index | Uniqueness | Tablespace | Columns |
|---|---|---|---|
| PON_REQUIREMENTS_N1 | Non Unique | Default | SECTION_ID, PARENT_LEVEL |
| PON_REQUIREMENTS_N2 | Non Unique | Default | SCORE_ID |
| PON_REQUIREMENTS_N3 | Non Unique | Default | AUCTION_HEADER_ID |
| PON_REQUIREMENTS_U1 | Unique | Default | REQUIREMENT_ID |