tables · table
rmindent
The rmindent table serves as the header record for Raw Material Indents within the procurement system. It captures high-level request information including the unique indent number, date, requesting department, and the intended supplier. It is a critical component in the purchasing workflow, bridging the gap between a department's requirement and the creation of a Purchase Order (PO).
Row count
84
Last entry
2025-12-01
Source
tables
Columns
16| Column | Type | Nullable | Meaning |
|---|---|---|---|
index | integer | No | Internal row identifier |
compcode | string | No | Company Code |
indentno | integer | No | Unique Indent Number |
indentdate | datetime | No | Date the indent was created |
supcode | string | Yes | Supplier Code |
dpcode | string | Yes | Department Code |
delivdate | datetime | Yes | Expected delivery date |
purpose | string | Yes | Reason for the requirement |
username | string | Yes | Current active user |
useradd | string | Yes | User who created the record |
addtime | string | Yes | Timestamp of creation |
usermod | string | Yes | User who last modified the record |
modtime | string | Yes | Timestamp of last modification |
printflag | string | Yes | Flag indicating if printed |
authflag | string | Yes | Authorization status |
lock | string | Yes | Lock status for editing |
Full documentation
### 1) Overview The `rmindent` table serves as the **header record for Raw Material Indents** within the procurement system. It captures high-level request information including the unique indent number, date, requesting department, and the intended supplier. It is a critical component in the purchasing workflow, bridging the gap between a department's requirement and the creation of a Purchase Order (PO). ### 2) Column Dictionary | Column | Type | Nullable | Meaning | Allowed Values | SQL Usage | | :--- | :--- | :--- | :--- | :--- | :--- | | **index** | integer | No | Internal row identifier | | Primary Key | | **compcode** | string | No | Company Code | e.g., "DAS" | Join key to all master/transaction tables | | **indentno** | integer | No | Unique Indent Number | | Business PK; Join to `rmindentitem`, `rmpotab` | | **indentdate** | datetime | No | Date the indent was created | | Filtering/Reporting | | **supcode** | string | Yes | Supplier Code | e.g., "ST", "VSSL" | Join to `suppmas` | | **dpcode** | string | Yes | Department Code | e.g., "PPC", "29", "30" | Join to `dprt_mas` | | **delivdate** | datetime | Yes | Expected delivery date | | Scheduling | | **purpose** | string | Yes | Reason for the requirement | | Descriptive | | **username** | string | Yes | Current active user | e.g., "system", "khannaji" | Audit trail | | **useradd** | string | Yes | User who created the record | | Audit trail | | **addtime** | string | Yes | Timestamp of creation | | Audit trail | | **usermod** | string | Yes | User who last modified the record | | Audit trail | | **modtime** | string | Yes | Timestamp of last modification | | Audit trail | | **printflag** | string | Yes | Flag indicating if printed | | UI/Workflow control | | **authflag** | string | Yes | Authorization status | "Y" (Authorized), null | Workflow filtering | | **lock** | string | Yes | Lock status for editing | "N" (No), "Y" (Yes) | UI/Workflow control | ### 3) Relationships & Join Map The `rmindent` table acts as a central hub for raw material requests. #### Primary Business Joins: * **rmindentitem (Line Items):** One-to-Many. `rmindent` holds the header, while `rmindentitem` holds specific raw materials and quantities. * `Join: rmindent.indentno = rmindentitem.indentno AND rmindent.compcode = rmindentitem.compcode` * **rmpotab (Purchase Orders):** Many-to-One. Indents are referenced when creating Purchase Orders for raw materials. * `Join: rmindent.indentno = rmpotab.indentno AND rmindent.compcode = rmpotab.compcode` * **suppmas (Supplier Master):** Many-to-One. To retrieve the name and details of the intended supplier. * `Join: rmindent.supcode = suppmas.supcode AND rmindent.compcode = suppmas.compcode` * **dprt_mas (Department Master):** Many-to-One. To identify the requesting department. * `Join: rmindent.dpcode = dprt_mas.dpcode AND rmindent.compcode = dprt_mas.compcode` #### Indirect Joins (Likely): * **cpohdr:** Reference data suggests some indents might be referenced in General/Capital Purchase Orders. * `Join: rmindent.indentno = cpohdr.indentno AND rmindent.compcode = cpohdr.compcode`