oaTenTativeMdtl

### 1. Overview
 The `oaTenTativeMdtl` (Order Amendment Tentative Master Detail) table stores line-item level data for tentative order schedules. It tracks projected or "tentative" quantities alongside planned and actual quantities for specific items linked to customer Purchase Orders (PO). This table is primarily used in planning and forecasting modules (like the `RMREQGen` procedure) to estimate raw material requirements before orders are finalized.
 
 ### 2. Column Dictionary
 
 | Column | Type | Nullable | Meaning | Allowed Values | SQL Usage |
 | :--- | :--- | :--- | :--- | :--- | :--- |
 | **index** | integer | NO | Primary key/Internal row identifier. | | PK |
 | **compcode** | string | NO | Company identifier code. | e.g., "DAS" | Join; Filter |
 | **oano** | integer | NO | Order Amendment Number; links to the header record. | | Join; FK |
 | **oadate** | datetime | YES | Date the tentative order/amendment was created. | | Range Filter |
 | **itemcode** | string | NO | Internal unique identifier for the product/item. | e.g., "CP-068" | Join; FK |
 | **qty** | number | YES | Actual or confirmed quantity for the line item. | | Calculation |
 | **pono** | string | YES | Customer's Purchase Order number. | | Join; Filter |
 | **variant** | string | YES | Specific version or variation of the item. | | Filter |
 | **partno** | string | YES | The physical part number associated with the item. | | Search/Filter |
 | **planqty** | number | YES | The quantity currently planned for production/dispatch. | | Calculation |
 | **tantativeQty** | number | YES | The forecasted or tentative quantity for planning purposes. | | Calculation |
 | **amendno** | string | YES | Specific revision or amendment number. | | Filter |
 
 ---
 
 ### 3. Relationships & Join Map
 
 #### Parent Table (Header)
 * **oaTenTativeMhdr**: Joined via `compcode` and `oano`. This relationship provides the customer code (`custcode`) and the schedule validity period (`schdatefrom`, `schdateto`).
 
 #### Master Data Joins
 * **itemmas / saleitemmas**: Join on `compcode` and `itemcode`. Used to retrieve technical specifications, unit of measure (`uom`), and the associated Raw Material item code (`rmitemcode`) for material requirement planning.
 * **cust**: Joined indirectly via `oaTenTativeMhdr.custcode` to get customer details.
 
 #### Usage in Business Logic
 * **Material Requirements (RMREQGen)**: The table is a critical input for calculating the `SchQty`. It specifically aggregates `tantativeQty` to determine how much raw material must be procured or allocated to satisfy upcoming (but not yet firm) demand.
 
 ---