tables · table
rejectionmas
The rejectionmas table serves as a central master repository for rejection, scrap, and rework reasons within the manufacturing and quality control modules. It provides descriptive labels for numeric codes used in production logs to identify why parts failed inspection (e.g., "OVER SIZE", "HARDNESS LOW"). This table is critical for quality analytics and production reporting.
Row count
242
Last entry
—
Source
tables
Columns
7| Column | Type | Nullable | Meaning |
|---|---|---|---|
index | integer | NO | Primary Key - internal unique identifier. |
compcode | string | NO | Company Code identifier. |
rejcode | integer | NO | Unique code for the specific rejection/scrap reason. |
rejreason | string | YES | Textual description of the rejection or failure cause. |
username | string | YES | The user account or department that created/maintains the reason. |
reasontype | string | YES | Categorization of the reason code. |
Sr | number | YES | Serial number or display order priority. |
Full documentation
### 1. Overview The `rejectionmas` table serves as a central master repository for rejection, scrap, and rework reasons within the manufacturing and quality control modules. It provides descriptive labels for numeric codes used in production logs to identify why parts failed inspection (e.g., "OVER SIZE", "HARDNESS LOW"). This table is critical for quality analytics and production reporting. ### 2. Column Dictionary | Column | Type | Nullable | Meaning | Allowed Values | SQL Usage | | :--- | :--- | :--- | :--- | :--- | :--- | | **index** | integer | NO | Primary Key - internal unique identifier. | | Primary Key | | **compcode** | string | NO | Company Code identifier. | e.g., "DAS", "BAM" | Filter/Join | | **rejcode** | integer | NO | Unique code for the specific rejection/scrap reason. | 1, 2, 3... | **Join Key** | | **rejreason** | string | YES | Textual description of the rejection or failure cause. | e.g., "UNCLEAN", "CRACK" | Reporting/Labels | | **username** | string | YES | The user account or department that created/maintains the reason. | e.g., "system", "lab", "amit" | Auditing | | **reasontype** | string | YES | Categorization of the reason code. | R (Rejection), W (Wework) | Filter | | **Sr** | number | YES | Serial number or display order priority. | | Ordering (Likely) | ### 3. Relationships & Join Map The `rejcode` (and occasionally `compcode`) is the authoritative key for linking descriptive reasons to transaction tables. #### Primary Join Relationships * **dbo.prodscrap**: Joins `rejectionmas.rejcode` to `prodscrap.scrapcode`. Used to report on scrap quantities by reason name. * **dbo.ReasonMappedWithOperation**: Joins `rejectionmas.rejcode` to `ReasonMappedWithOperation.Rejcode`. Used to restrict rejection reasons to specific machine operations. * **dbo.onlinerej_dtl**: Joins `rejectionmas.rejcode` to `onlinerej_dtl.rejcode` for real-time production line rejection tracking. * **dbo.prodfhdr / dbo.product2**: Joins `rejectionmas.rejcode` to `prodfhdr.rejcode` (or `product2.rejcode`) to identify the primary reason for a failed production batch. #### Likely Join Relationships (Inferred from Logic) * **dbo.mrci2dtlscrap**: (As seen in stored procedures) Joins `rejectionmas.rejcode` to `mrci2dtlscrap.scrapcode`. * **dbo.prodfrw**: Joins `rejectionmas.rejcode` to `prodfrw.rwcode` to identify specific rework reasons.