scheduledtlamnd

### 1. Overview
 The `scheduledtlamnd` table stores the line-item details for **amended delivery schedules**. It tracks modifications to original schedules, specifically breaking down total quantities into a four-week delivery window (`istweek` through `ivthweek`) with specific date ranges for each period. This table is the historical or "versioned" counterpart to the active `scheduledtl` table and works in conjunction with schedule amendment headers to maintain an audit trail of changes to supply chain requirements.
 
 ### 2. Column dictionary
 
 | Column | Type | Nullable | Meaning | Allowed Values | SQL Usage |
 | :--- | :--- | :--- | :--- | :--- | :--- |
 | **index** | integer | No | Primary Key | Auto-incremented | Unique row identifier |
 | **compcode** | string | No | Company Code | e.g., "DAS" | Partitioning key for multi-tenant data |
 | **schno** | integer | No | Schedule Number | e.g., 370, 367 | Foreign Key to Schedule Header tables |
 | **itemcode** | string | No | Item/Material Identifier | e.g., "S48C50" | Join to `itemmas` or `rmmas` |
 | **uom** | string | Yes | Unit of Measure | KGS, PCS, NOS | Quantitative context |
 | **schqty** | integer | Yes | Total Quantity for this amendment | | Aggregate requirement for the period |
 | **istweek** | integer | Yes | Quantity for 1st week | | Periodic breakdown |
 | **iindweek** | integer | Yes | Quantity for 2nd week | | Periodic breakdown |
 | **iiirdweek** | integer | Yes | Quantity for 3rd week | | Periodic breakdown |
 | **ivthweek** | integer | Yes | Quantity for 4th week | | Periodic breakdown |
 | **frdateweek1** | datetime | Yes | Start date for Week 1 | | Date range filtering |
 | **todateweek1** | datetime | Yes | End date for Week 1 | | Date range filtering |
 | **frdateweek2** | datetime | Yes | Start date for Week 2 | | Date range filtering |
 | **todateweek2** | datetime | Yes | End date for Week 2 | | Date range filtering |
 | **frdateweek3** | datetime | Yes | Start date for Week 3 | | Date range filtering |
 | **todateweek3** | datetime | Yes | End date for Week 3 | | Date range filtering |
 | **frdateweek4** | datetime | Yes | Start date for Week 4 | | Date range filtering |
 | **todateweek4** | datetime | Yes | End date for Week 4 | | Date range filtering |
 | **rate** | number | Yes | Unit price at time of amendment | | Financial calculation |
 | **ratetype** | string | Yes | Category of item/rate | R (Raw Mat), I (Item), G (General) | Determining source item table |
 | **amendno** | integer | No | Amendment Version Number | 0, 1, 2... | Version tracking |
 | **pono** | string | Yes | Purchase Order Number | | Join to `pohdr` or `podtl` |
 | **PartNo** | string | Yes | Customer/Internal Part Number | | Cross-reference |
 | **SNo** | integer | Yes | Serial number within schedule | | Sorting / Line ordering |
 
 ### 3. Relationships & join map
 
 #### Primary Relationships (Verified)
 * **dbo.schedulehdramnd**: Joined via `compcode` and `schno` to retrieve amendment header information (dates, vendor codes).
 * **dbo.schedulehdr**: Joined via `compcode` and `schno` when comparing current versus amended statuses.
 * **dbo.pohdr**: Joined via `pono` (and `compcode`) to link schedules to their originating Purchase Orders.
 
 #### Conditional Item Joins (Based on `ratetype`)
 * **dbo.rmmas**: If `ratetype = 'R'`, join `itemcode` to `rmcode`.
 * **dbo.itemmas**: If `ratetype = 'I'`, join `itemcode` to `itemcode`.
 * **dbo.citemmas**: If `ratetype = 'G'`, join `itemcode` to `citmcode`.
 
 #### Downstream Joins
 * **dbo.suppmas**: Indirectly joined via the Vendor Code found in `schedulehdramnd` to identify the supplier receiving the schedule.