All tables
tables · table

jobdtl

The jobdtl table serves as the transaction detail layer for manufacturing job cards. It records the sequence of operations (oprcode) required for a specific item within a job card, along with associated processing rates, quantities (pcs), weights, and allowed scrap percentages. It is primarily used in job work auditing, vendor operation reporting, and production tracking.

Row count
12,727
Last entry
2025-11-24
Source
tables

Columns

15
ColumnTypeNullableMeaning
indexintegerNoPrimary Key
compcodestringNoCompany Code
jobcardnointegerNoUnique Job Card Identifier
itemcodestringNoFinished or semi-finished item code
oprcodestringNoOperation/Process code
ratenumberYesProcessing rate per unit for the operation
pcsintegerYesQuantity in pieces allocated to this operation
weightnumberYesTotal weight associated with the operation
lotnostringYesInternal batch or lot number
uomstringYesUnit of Measure
ponostringYesPurchase Order Number
podatestringYesPurchase Order Date
amndnostringYesAmendment number (if any)
amnddatestringYesDate of amendment
Allowed_ScrapPernumberYesMaximum permissible scrap percentage for this process

Full documentation

### 1) Overview
 The `jobdtl` table serves as the transaction detail layer for manufacturing job cards. It records the sequence of operations (`oprcode`) required for a specific item within a job card, along with associated processing rates, quantities (`pcs`), weights, and allowed scrap percentages. It is primarily used in job work auditing, vendor operation reporting, and production tracking.
 
 ### 2) Column Dictionary
 
 | Column | Type | Nullable | Meaning | Allowed Values | SQL Usage |
 | :--- | :--- | :--- | :--- | :--- | :--- |
 | **index** | integer | No | Primary Key | | Row identifier |
 | **compcode** | string | No | Company Code | e.g., "DAS" | Join key |
 | **jobcardno** | integer | No | Unique Job Card Identifier | | Join to `jobhdr` |
 | **itemcode** | string | No | Finished or semi-finished item code | e.g., "CP-066", "TOP5" | Join to `itemmas` |
 | **oprcode** | string | No | Operation/Process code | e.g., "BC", "CNC1", "DRAW" | Join to `oprmas` |
 | **rate** | number | Yes | Processing rate per unit for the operation | | Cost calculation |
 | **pcs** | integer | Yes | Quantity in pieces allocated to this operation | | Production tracking |
 | **weight** | number | Yes | Total weight associated with the operation | | Material accounting |
 | **lotno** | string | Yes | Internal batch or lot number | | Traceability |
 | **uom** | string | Yes | Unit of Measure | "PCS", "KGS" | Conversion logic |
 | **pono** | string | Yes | Purchase Order Number | | Reference to PO |
 | **podate** | string | Yes | Purchase Order Date | | Date reference |
 | **amndno** | string | Yes | Amendment number (if any) | | Versioning |
 | **amnddate** | string | Yes | Date of amendment | | Audit trail |
 | **Allowed_ScrapPer** | number | Yes | Maximum permissible scrap percentage for this process | | Quality control |
 
 ### 3) Relationships & Join Map
 
 #### Real Physical Joins (via SCHEMA_MAP)
 * **dbo.jobhdr**: Joins on `compcode` and `jobcardno`. This is the primary header-to-detail relationship.
 * **dbo.oprmas**: Joins on `compcode` and `oprcode`. Used to retrieve operation names and station details.
 * **dbo.itemmas**: Joins on `compcode` and `itemcode`. Used to fetch item descriptions, part numbers, and base UOM.
 * **dbo.itemopr**: Joins on `compcode`, `itemcode`, and `oprcode`. Used to validate operation-specific parameters (drawing numbers, operation weight).
 * **dbo.machineitem**: Joins on `compcode`, `itemcode`, and `oprcode`. (Likely) Used for machine-specific production rates.
 
 #### Logical Joins (via REFERENCE_JSON)
 * **dbo.mrcirhdr**: Linked via `jobcardno` and `itemcode` to track received vs. issued quantities in job work reports.
 * **dbo.rmmrphdr**: Linked via `jobcardno` for raw material requirement tracking against job card operations.
 * **dbo.billagainstwo**: Linked via `jobno` (matching `jobcardno`) to associate billing invoices with job card details.