All tables
tables · table

citemiss

The citemiss table functions as the header for Consumable Item Issue transactions. It records high-level metadata regarding the movement of consumable materials from inventory to specific departments or individuals. It tracks who received the items (issueto), which department requested them (dpcode), and the timing of the transaction (issuedate, issueshift). It is frequently joined with citisdtl to retrieve the specific items and quantities associated with each issue number.

Row count
347,502
Last entry
2026-01-15
Source
tables

Columns

11
ColumnTypeNullableMeaning
indexintegerNOInternal row identifier.
compcodestringNOUnique code identifying the company/branch.
issuenointegerNOThe unique transaction number for the item issue.
issuetostringYESThe name of the person or machine receiving the item.
issuedatedatetimeYESThe date the issue transaction was recorded.
dpcodestringYESDepartment code responsible for the request.
slipnointegerYESReference number (often links to an Indent/Requirement number).
issueshiftstringYESThe work shift during which the issue occurred.
issuetimestringYESSpecific time of the issue.
remarksstringYESUser-defined notes regarding the issue.
subdpcodestringYESSub-department code (if applicable).

Full documentation

### 1) Overview
 The `citemiss` table functions as the header for **Consumable Item Issue** transactions. It records high-level metadata regarding the movement of consumable materials from inventory to specific departments or individuals. It tracks who received the items (`issueto`), which department requested them (`dpcode`), and the timing of the transaction (`issuedate`, `issueshift`). It is frequently joined with `citisdtl` to retrieve the specific items and quantities associated with each issue number.
 
 ### 2) Column Dictionary
 
 | Column | Type | Nullable | Meaning | Allowed Values | SQL Usage |
 | :--- | :--- | :--- | :--- | :--- | :--- |
 | **index** | integer | NO | Internal row identifier. | | Primary Key |
 | **compcode** | string | NO | Unique code identifying the company/branch. | e.g., "DAS", "SFR" | Join Key |
 | **issueno** | integer | NO | The unique transaction number for the item issue. | | Join Key (to `citisdtl`) |
 | **issueto** | string | YES | The name of the person or machine receiving the item. | e.g., "NAVEEN", "M/C-45" | Filter / Report |
 | **issuedate** | datetime | YES | The date the issue transaction was recorded. | | Filter / Time Analysis |
 | **dpcode** | string | YES | Department code responsible for the request. | e.g., "12", "PD70", "nd" | Join Key (to `dprt_mas`) |
 | **slipno** | integer | YES | Reference number (often links to an Indent/Requirement number). | | Join Key (to `cmrpreq`) |
 | **issueshift** | string | YES | The work shift during which the issue occurred. | "A", "B", "C" | Filter |
 | **issuetime** | string | YES | Specific time of the issue. | HH:mm format | Metadata |
 | **remarks** | string | YES | User-defined notes regarding the issue. | | Metadata |
 | **subdpcode** | string | YES | Sub-department code (if applicable). | | Filter |
 
 ### 3) Relationships & Join Map
 
 Based on `SCHEMA_MAP` and the logic within the provided stored procedures (`CostCenterWiseConsumption`, `itemledger_det`), the following joins are authoritative:
 
 #### Primary Joins (Physical)
 * **`dbo.citisdtl`**: Joined via `issueno` and `compcode`. This link retrieves the line-item details (specific consumable items) for a header issue.
  * `citemiss.issueno = citisdtl.issueno`
  * `citemiss.compcode = citisdtl.compcode`
 * **`dbo.dprt_mas`**: Joined via `dpcode` and `compcode` to resolve the department name (`dpname`).
  * `citemiss.dpcode = dprt_mas.dpcode`
  * `citemiss.compcode = dprt_mas.compcode`
 
 #### Functional/Logical Joins (Inference Based on SP Usage)
 * **`dbo.cmrpreq`**: The `slipno` in `citemiss` is logically treated as the `indentno` (Material Requirement Number) in procurement workflows.
  * `citemiss.slipno = cmrpreq.indentno` (Likely)
  * `citemiss.compcode = cmrpreq.compcode`
 * **`dbo.citemmas`**: While not directly joined, the `citisdtl` table (linked to `citemiss`) joins to `citemmas` via `citmcode` to get item descriptions.