All tables
tables · table

vendmasitem

The vendmasitem table serves as a configuration mapping between vendors and items within a specific company. It defines the production or logistical capacity and grace day constraints specific to a vendor-item pair, likely categorized into two stages (Stage I/ist and Stage II/iind). This data is typically used in supply chain planning and procurement modules to manage vendor expectations and lead times.

Row count
2
Last entry
Source
tables

Columns

7
ColumnTypeNullableMeaning
compcodestringNoUnique identifier for the company/legal entity.
vendcodestringNoThe unique code identifying the vendor.
itemcodestringNoThe unique code identifying the item or product.
capacityistnumberYesCapacity allocated for Stage I (In-stage I).
capacityiindnumberYesCapacity allocated for Stage II (In-stage II).
gracedaysistintegerYesAllowed grace period (days) for Stage I deliveries.
gracedaysiindintegerYesAllowed grace period (days) for Stage II deliveries.

Full documentation

### 1. Overview
 The `vendmasitem` table serves as a configuration mapping between vendors and items within a specific company. It defines the production or logistical **capacity** and **grace day** constraints specific to a vendor-item pair, likely categorized into two stages (Stage I/`ist` and Stage II/`iind`). This data is typically used in supply chain planning and procurement modules to manage vendor expectations and lead times.
 
 ### 2. Column Dictionary
 
 | Column | Type | Nullable | Meaning | Allowed Values | SQL Usage |
 | :--- | :--- | :--- | :--- | :--- | :--- |
 | **compcode** | string | No | Unique identifier for the company/legal entity. | e.g., "DAS" | `WHERE compcode = 'DAS'` |
 | **vendcode** | string | No | The unique code identifying the vendor. | e.g., "SKE", "JGDFORG01" | `JOIN vendmas ON vendcode` |
 | **itemcode** | string | No | The unique code identifying the item or product. | e.g., "PSRGS", "GPDN" | `JOIN itemmas ON itemcode` |
 | **capacityist** | number | Yes | Capacity allocated for Stage I (In-stage I). | e.g., 0.0, 500.0 | Planning calculations |
 | **capacityiind** | number | Yes | Capacity allocated for Stage II (In-stage II). | e.g., 0.0, 350.0 | Planning calculations |
 | **gracedaysist** | integer | Yes | Allowed grace period (days) for Stage I deliveries. | e.g., 0, 5 | `DATEADD` operations |
 | **gracedaysiind** | integer | Yes | Allowed grace period (days) for Stage II deliveries. | e.g., 0, 3 | `DATEADD` operations |
 
 ### 3. Relationships & Join Map
 
 Based on the `SCHEMA_MAP`, the following physical relationships are authoritative:
 
 #### Primary Master Joins
 * **Vendor Master**: Joins to `dbo.vendmas` on `compcode` and `vendcode`. This retrieves vendor names and addresses.
 * **Item Master**: Joins to `dbo.itemmas` or `dbo.saleitemmas` on `compcode` and `itemcode`. This retrieves item descriptions and specifications.
 
 #### Operational Joins
 * **Vendor Item Operations**: Joins to `dbo.vitemopr` on `compcode`, `vendcode`, and `itemcode`. This is the most direct operational link for vendor-item specific settings.
 * **Job Planning/Orders**:
  * **Likely** joins to `dbo.jobpohdr` on `compcode` and `vendcode` to validate capacity against purchase orders.
  * **Likely** joins to `dbo.job` or `dbo.jobhdr` on `compcode`, `vendcode`, and `itemcode` to apply grace day logic to specific production jobs.
  * **Likely** joins to `dbo.joboadtl` on `compcode` and `itemcode` for schedule vs. capacity analysis.
 
 #### Column-Specific Join Table Reference
 * **compcode**: Present in almost all `dbo` tables.
 * **vendcode**: `dbo.vendmas`, `dbo.jobpohdr`, `dbo.jobhdr`, `dbo.vitemopr`, `dbo.mrci_rep`.
 * **itemcode**: `dbo.itemmas`, `dbo.job`, `dbo.vitemopr`, `dbo.itemopr`, `dbo.podtl`.