joboadtl

### 1. Overview
 The `joboadtl` (Job Open Order Detail) table serves as the granular line-item repository for Job Open Orders (Schedules) within the manufacturing or procurement system. It decomposes a header job order into specific items, total quantities, and a week-by-week delivery schedule (typically spanning a 4-week horizon). It is primarily used for vendor scheduling, production planning, and tracking delivery performance against scheduled targets.
 
 ### 2. Column Dictionary
 
 | Column | Type | Nullable | Meaning | Allowed Values | SQL Usage |
 | :--- | :--- | :--- | :--- | :--- | :--- |
 | **index** | integer | NO | Internal primary key identifier. | Auto-incrementing | `PRIMARY KEY` |
 | **compcode** | string | NO | Unique identifier for the company/division. | e.g., "DAS", "OMA" | `JOIN`, `WHERE` |
 | **joboano** | integer | NO | Job Open Order Number. Links to the header record. | | `JOIN`, `WHERE` |
 | **joboadate** | datetime | YES | The date the job order/schedule was issued. | | `ORDER BY`, `RANGE` |
 | **itemcode** | string | NO | Unique identifier for the product or component. | e.g., "CP-138" | `JOIN`, `WHERE` |
 | **qty** | number | YES | Total aggregate quantity ordered for this item. | | `SUM`, `CALC` |
 | **uom** | string | YES | Unit of Measure for the quantity. | e.g., "KGS", "PCS" | `SELECT` |
 | **frdateweek1** | datetime | YES | Start date for the 1st week delivery window. | | `FILTER` |
 | **todateweek1** | datetime | YES | End date for the 1st week delivery window. | | `FILTER` |
 | **frdateweek2** | datetime | YES | Start date for the 2nd week delivery window. | | `FILTER` |
 | **todateweek2** | datetime | YES | End date for the 2nd week delivery window. | | `FILTER` |
 | **frdateweek3** | datetime | YES | Start date for the 3rd week delivery window. | | `FILTER` |
 | **todateweek3** | datetime | YES | End date for the 3rd week delivery window. | | `FILTER` |
 | **frdateweek4** | datetime | YES | Start date for the 4th week delivery window. | | `FILTER` |
 | **todateweek4** | datetime | YES | End date for the 4th week delivery window. | | `FILTER` |
 | **rate** | string | YES | Unit price or rate for the item. | | `CALC` |
 | **istweek** | string | YES | Scheduled quantity for the 1st week. | Numeric as string | `CALC` |
 | **iindweek** | string | YES | Scheduled quantity for the 2nd week. | Numeric as string | `CALC` |
 | **iiirdweek** | string | YES | Scheduled quantity for the 3rd week. | Numeric as string | `CALC` |
 | **ivthweek** | string | YES | Scheduled quantity for the 4th week. | Numeric as string | `CALC` |
 | **exdetail** | string | YES | Extra information or descriptive notes for the item. | | `SELECT` |
 
 ### 3. Relationships & Join Map
 
 #### Parent Table (Authority)
 * **joboahdr**: Joined on `compcode` and `joboano`. This relationship provides vendor information (`vendcode`) and master job order dates.
 
 #### Related Tables (Lookups & Tracking)
 * **itemmas**: Joined on `compcode` and `itemcode`. Used to retrieve `itemname` and other material specifications.
 * **mrcirhdr**: Joined on `compcode`, `itemcode`, and often filtered by `vendcode` (from header). Used to calculate `RecdQtyIst` (Received Quantity) to determine balance quantities.
 * **mrci_rep**: Joined on `compcode` and `itemcode`. Used to calculate `RecdQtyIind` (Second-stage receipt quantities) for scheduling reports.
 
 #### Known Join Path (Logic from Reference)
 ```sql
 SELECT q.* 
 FROM joboadtl q
 INNER JOIN joboahdr p ON p.joboano = q.joboano AND p.compcode = q.compcode
 INNER JOIN itemmas m ON m.itemcode = q.itemcode AND m.compcode = q.compcode
 LEFT JOIN mrcirhdr r ON r.itemcode = q.itemcode AND r.compcode = q.compcode
 ```