All tables
tables · table

scheduledtl

The scheduledtl table serves as the granular line-item storage for supplier delivery schedules. It decomposes a master schedule (from schedulehdr) into specific items, total quantities, and a weekly delivery breakdown across four distinct week buckets. Each bucket includes specific "from" and "to" date ranges, allowing for precise tracking of expected versus actual procurement.

Row count
6,157
Last entry
2026-04-01
Source
tables

Columns

24
ColumnTypeNullableMeaning
compcodestringNoUnique identifier for the company/organization.
schnointegerNoSchedule Number linking to the header table.
itemcodestringNoInternal identifier for the part or material.
uomstringYesUnit of Measure for the scheduled quantity.
schqtyintegerYesTotal quantity scheduled for the entire period.
istweekintegerYesQuantity scheduled for delivery in Week 1.
iindweekintegerYesQuantity scheduled for delivery in Week 2.
iiirdweekintegerYesQuantity scheduled for delivery in Week 3.
ivthweekintegerYesQuantity scheduled for delivery in Week 4.
frdateweek1datetimeYesStart date for the first delivery week.
todateweek1datetimeYesEnd date for the first delivery week.
frdateweek2datetimeYesStart date for the second delivery week.
todateweek2datetimeYesEnd date for the second delivery week.
frdateweek3datetimeYesStart date for the third delivery week.
todateweek3datetimeYesEnd date for the third delivery week.
frdateweek4datetimeYesStart date for the fourth delivery week.
todateweek4datetimeYesEnd date for the fourth delivery week.
ratenumberYesAgreed unit price for the item in this schedule.
ratetypestringYesClassification of the item (Raw Material vs Finished).
ponostringYesPurchase Order Number associated with this schedule.
PartNostringYesCustomer or Supplier specific part number.
SNointegerYesSerial Number / Line Number within the schedule.
makestringYesBrand or manufacturer of the item.
ItemNamestringYesDescriptive name of the item.

Full documentation

### 1. Overview
 The `scheduledtl` table serves as the granular line-item storage for supplier delivery schedules. It decomposes a master schedule (from `schedulehdr`) into specific items, total quantities, and a weekly delivery breakdown across four distinct week buckets. Each bucket includes specific "from" and "to" date ranges, allowing for precise tracking of expected versus actual procurement.
 
 ### 2. Column Dictionary
 
 | Column | Type | Nullable | Meaning | Allowed Values | SQL Usage |
 | :--- | :--- | :--- | :--- | :--- | :--- |
 | **compcode** | string | No | Unique identifier for the company/organization. | e.g., "DAS", "MNP" | Primary Join Key |
 | **schno** | integer | No | Schedule Number linking to the header table. | | Primary Join Key |
 | **itemcode** | string | No | Internal identifier for the part or material. | e.g., "ROD45", "TQJ01" | Join to `itemmas`/`rmmas` |
 | **uom** | string | Yes | Unit of Measure for the scheduled quantity. | PCS, KGS, LTR, MTR | Information |
 | **schqty** | integer | Yes | Total quantity scheduled for the entire period. | | Aggregate Calculation |
 | **istweek** | integer | Yes | Quantity scheduled for delivery in Week 1. | | Bucket Distribution |
 | **iindweek** | integer | Yes | Quantity scheduled for delivery in Week 2. | | Bucket Distribution |
 | **iiirdweek** | integer | Yes | Quantity scheduled for delivery in Week 3. | | Bucket Distribution |
 | **ivthweek** | integer | Yes | Quantity scheduled for delivery in Week 4. | | Bucket Distribution |
 | **frdateweek1** | datetime | Yes | Start date for the first delivery week. | | Date Filtering |
 | **todateweek1** | datetime | Yes | End date for the first delivery week. | | Date Filtering |
 | **frdateweek2** | datetime | Yes | Start date for the second delivery week. | | Information |
 | **todateweek2** | datetime | Yes | End date for the second delivery week. | | Information |
 | **frdateweek3** | datetime | Yes | Start date for the third delivery week. | | Information |
 | **todateweek3** | datetime | Yes | End date for the third delivery week. | | Information |
 | **frdateweek4** | datetime | Yes | Start date for the fourth delivery week. | | Information |
 | **todateweek4** | datetime | Yes | End date for the fourth delivery week. | | Information |
 | **rate** | number | Yes | Agreed unit price for the item in this schedule. | | Financial Reporting |
 | **ratetype** | string | Yes | Classification of the item (Raw Material vs Finished). | 'R', 'I', 'G' | Filter Logic |
 | **pono** | string | Yes | Purchase Order Number associated with this schedule. | | Join to `rmpotab` |
 | **PartNo** | string | Yes | Customer or Supplier specific part number. | | Information |
 | **SNo** | integer | Yes | Serial Number / Line Number within the schedule. | | Ordering |
 | **make** | string | Yes | Brand or manufacturer of the item. | | Information |
 | **ItemName** | string | Yes | Descriptive name of the item. | | Information |
 
 ### 3. Relationships & Join Map
 
 #### Logical Parents
 * **schedulehdr**: Linked via `compcode` and `schno`. This contains the vendor info (`supcode`) and schedule date.
 * **itemmas**: Linked via `compcode` and `itemcode`. Used when `ratetype` is 'I' (Finished/Semi-Finished Items).
 * **rmmas**: Linked via `compcode` and `itemcode`. Used when `ratetype` is 'R' (Raw Materials).
 * **citemmas**: Linked via `compcode` and `itemcode`. Used when `ratetype` is 'G' (Consumables).
 
 #### Logical Children
 * **scheduledtlamnd**: Historically linked via `compcode`, `schno`, and `itemcode` to track revision history of specific lines.
 
 #### Strict Join Map (Based on SCHEMA_MAP)
 
 | Target Table | Join Columns | Relationship Type |
 | :--- | :--- | :--- |
 | `dbo.schedulehdr` | `compcode`, `schno` | Many-to-One |
 | `dbo.itemmas` | `compcode`, `itemcode` | Many-to-One (Likely) |
 | `dbo.rmmas` | `compcode`, `rmcode` (as `itemcode`) | Many-to-One (Likely) |
 | `dbo.citemmas` | `compcode`, `citmcode` (as `itemcode`) | Many-to-One (Likely) |
 | `dbo.rmpotab` | `compcode`, `pono` | Many-to-One (Likely) |
 | `dbo.scheduledtlamnd` | `compcode`, `schno`, `itemcode` | One-to-Many |