pur.requisitions (Header)
Documentation | Procurement |
Schema | pur |
Name | requisitions |
Title | Header |
Module | Requisitions |
Requisition is the first step in procurement. Someone in the organization files requisition for specific items.
Requistinion is represented in requisition document that comprises of a list of items, their quantities and expected dates.
For each requisition there is one row in requisitions table. Lines/items are held in requisition_lines table.
Columns
Key | Name | Data type | Null | Attributes | References | Description | Sensitive | ||
---|---|---|---|---|---|---|---|---|---|
1 | requisition_id | int | Identity | Requisition header id | |||||
Requisition header id Identity |
|||||||||
2 | requested_at | nchar(10) | Date requistion. For paper filed requisitions this is the date on the header. For system filed requisitions this is the date of creation in the system (the same as created_date). | ||||||
Date requistion. For paper filed requisitions this is the date on the header. For system filed requisitions this is the date of creation in the system (the same as created_date). |
|||||||||
3 | department | nvarchar(50) | HR.HR.DEPT (Departments) | Code of the department that filed requisition. It must comply with org dictionary. | |||||
Code of the department that filed requisition. It must comply with org dictionary. References: HR.HR.DEPT (Departments) |
|||||||||
4 | requested_by | nvarchar(50) | Name of the person who filed requisition. Free hand text. See attribute3 for key. | ||||||
Name of the person who filed requisition. Free hand text. See attribute3 for key. |
|||||||||
5 | requisition_ref | nvarchar(20) | Requisition reference number | ||||||
Requisition reference number |
|||||||||
6 | created_date | date | Date requisition was created in the system | ||||||
Date requisition was created in the system |
|||||||||
7 | employee | nvarchar(50) | Login of employee who entered requisition to the system | Y | |||||
Login of employee who entered requisition to the system Sensitive: Y |
|||||||||
8 | approved_flag | bit | Default: 0 | Each requsition needs to be approved. This is a flag that determines approval status. 1 - approved, 0 - otherwise | |||||
Each requsition needs to be approved. This is a flag that determines approval status. 1 - approved, 0 - otherwise Default: 0 |
|||||||||
9 | attribute1 | nvarchar(150) | Unused | ||||||
Unused |
|||||||||
10 | attribute2 | nvarchar(150) | Unused | ||||||
Unused |
|||||||||
11 | attribute3 | nvarchar(150) | HR.HR.EMP (Employees) | Employee number of person who filed requisition if found in HR database. System doesn't keep data consistency. | |||||
Employee number of person who filed requisition if found in HR database. System doesn't keep data consistency. References: HR.HR.EMP (Employees) |
|||||||||
12 | attribute4 | nvarchar(150) | Unused | ||||||
Unused |
|||||||||
13 | attribute5 | nvarchar(150) | Login of employee who approved document | ||||||
Login of employee who approved document |
Relations
Foreign table | Primary table | Join | Title / Name / Description | |
---|---|---|---|---|
pur.requisitions (Header) | HR.HR.DEPT (Departments) | pur.requisitions.department = HR.HR.DEPT.CODE | User-defined relation |
|
pur.requisitions.department = HR.HR.DEPT.CODE Name: User-defined relation |
||||
pur.requisitions (Header) | HR.HR.EMP (Employees) | pur.requisitions.attribute3 = HR.HR.EMP.EMP_NO | User-defined relation |
|
pur.requisitions.attribute3 = HR.HR.EMP.EMP_NO Name: User-defined relation |
||||
pur.requisition_lines (Line) | pur.requisitions (Header) | pur.requisition_lines.requisition_id = pur.requisitions.requisition_id | FK_requisition_lines_req |
|
pur.requisition_lines.requisition_id = pur.requisitions.requisition_id Name: FK_requisition_lines_req |
Unique keys
Key name | Columns | Description | |
---|---|---|---|
PK_requisitions | requisition_id | ||
Uses
Name |
---|
pur.requisitions (Header)
|
Used by
Name |
---|
pur.requisitions (Header)
|
Exported: 2019-02-04 23:17, Last imported: 2018-10-31 15:19