All tables
tables · table

PackingSlipdtl

The PackingSlipdtl table serves as the line-item detail repository for Packing Slips within the ERP system. It records specific quantities, batch information, and box counts for items being prepared for shipment. It links specific inventory items to invoice numbers (Invno) and forging work orders (ForgingWono), providing a bridge between production output and the dispatch process.

Row count
1
Last entry
Source
tables

Columns

12
ColumnTypeNullableMeaning
indexintegerNOPrimary key for the detail record
compcodestringNOCompany identifier code
SlipNointegerNOThe parent Packing Slip unique identifier
itemcodestringNOUnique code for the finished or semi-finished item
TotQtynumberYESTotal quantity associated with the line item
NoOfBoxintegerYESNumber of physical boxes/containers for this item
BatchnostringYESProduction batch or heat identification code
FIRNostringYESLikely refers to "First Inspection Report" number
InvnointegerYESAssociated Sales Invoice number
ForgingWonostringYESReference to the Forging Work Order
PackedQtynumberYESActual quantity packed into containers
PackModeQtynumberYESStandard quantity per packing unit/mode

Full documentation

### 1. Overview
 The `PackingSlipdtl` table serves as the line-item detail repository for Packing Slips within the ERP system. It records specific quantities, batch information, and box counts for items being prepared for shipment. It links specific inventory items to invoice numbers (`Invno`) and forging work orders (`ForgingWono`), providing a bridge between production output and the dispatch process.
 
 ### 2. Column Dictionary
 | Column | Type | Nullable | Meaning | Allowed Values | SQL Usage |
 | :--- | :--- | :--- | :--- | :--- | :--- |
 | **index** | integer | NO | Primary key for the detail record | | Unique ID |
 | **compcode** | string | NO | Company identifier code | e.g., "DAS" | FK (Multi-table) |
 | **SlipNo** | integer | NO | The parent Packing Slip unique identifier | | FK to `PackingSlipHdr` |
 | **itemcode** | string | NO | Unique code for the finished or semi-finished item | | FK to `itemmas` |
 | **TotQty** | number | YES | Total quantity associated with the line item | | Aggregates |
 | **NoOfBox** | integer | YES | Number of physical boxes/containers for this item | | Logistics calculation |
 | **Batchno** | string | YES | Production batch or heat identification code | | Tracking/Traceability |
 | **FIRNo** | string | YES | Likely refers to "First Inspection Report" number | | Quality Reference |
 | **Invno** | integer | YES | Associated Sales Invoice number | | FK to `invhdr` |
 | **ForgingWono** | string | YES | Reference to the Forging Work Order | | FK to `mchdr` |
 | **PackedQty** | number | YES | Actual quantity packed into containers | | Reconciliation |
 | **PackModeQty** | number | YES | Standard quantity per packing unit/mode | | Packaging Logic |
 
 ---
 
 ### 3. Relationships & Join Map
 
 #### Logical Parent Table
 * **PackingSlipHdr**: Linked via `compcode` and `SlipNo`. This table contains the header info (date, customer, etc.).
 
 #### Reference Tables
 * **itemmas / saleitemmas**: Linked via `compcode` and `itemcode`. Used to retrieve item descriptions and master data.
 * **invhdr**: Linked via `compcode` and `Invno` (maps to `invno` in `invhdr`). Used to associate packing slips with specific sales billing.
 * **mchdr**: Linked via `compcode` and `ForgingWono` (maps to `wono` in `mchdr`). Used to trace back to the production work order.
 
 #### Join Examples
 ```sql
 -- Get full packing slip details with item names
 SELECT a.SlipNo, a.itemcode, b.itemname, a.PackedQty, a.NoOfBox
 FROM PackingSlipdtl a
 JOIN itemmas b ON a.compcode = b.compcode AND a.itemcode = b.itemcode;
 
 -- Link packing slip to invoice details
 SELECT a.SlipNo, a.Invno, b.invdate, b.invamt
 FROM PackingSlipdtl a
 JOIN invhdr b ON a.compcode = b.compcode AND a.Invno = b.invno;
 ```