tables · table
tempsuplinvdetail
The tempsuplinvdetail table serves as a temporary staging or reporting table for supplemental invoice details. It aggregates sales quantities and amounts at the item and part number level for specific customers. Based on its structure and naming convention, it is likely used for generating sales reports or calculating invoice adjustments before finalizing records in the core invoice tables (invdtl or invhdr).
Row count
24
Last entry
—
Source
tables
Columns
8| Column | Type | Nullable | Meaning |
|---|---|---|---|
index | integer | NO | Internal unique identifier and Primary Key. |
compcode | string | YES | Internal company identifier used for multi-tenant data partitioning. |
custcode | string | YES | The unique code identifying the customer. |
itemcode | string | YES | The internal system code for the product/material. |
partno | string | YES | The manufacturer's or customer's specific part number. |
uom | string | YES | Unit of Measure for the item. |
saleqty | number | YES | The quantity of the item sold in this specific transaction detail. |
saleamount | number | YES | The total monetary value associated with the sale quantity. |
Full documentation
### 1. Overview The `tempsuplinvdetail` table serves as a temporary staging or reporting table for supplemental invoice details. It aggregates sales quantities and amounts at the item and part number level for specific customers. Based on its structure and naming convention, it is likely used for generating sales reports or calculating invoice adjustments before finalizing records in the core invoice tables (`invdtl` or `invhdr`). ### 2. Column Dictionary | Column | Type | Nullable | Meaning | Allowed Values | SQL Usage | | :--- | :--- | :--- | :--- | :--- | :--- | | **index** | integer | NO | Internal unique identifier and Primary Key. | | Primary Key | | **compcode** | string | YES | Internal company identifier used for multi-tenant data partitioning. | E.g., "DAS" | Join Filter | | **custcode** | string | YES | The unique code identifying the customer. | | Join to `dbo.cust` | | **itemcode** | string | YES | The internal system code for the product/material. | | Join to `dbo.itemmas` | | **partno** | string | YES | The manufacturer's or customer's specific part number. | | Filtering/Display | | **uom** | string | YES | Unit of Measure for the item. | E.g., "NOS", "Nos" | Join to `dbo.UoMMaster` | | **saleqty** | number | YES | The quantity of the item sold in this specific transaction detail. | | Aggregation (SUM) | | **saleamount** | number | YES | The total monetary value associated with the sale quantity. | | Aggregation (SUM) | ### 3. Relationships & Join Map The table connects primarily to master data tables and invoice transaction tables via the following keys: #### Primary Joins (SCHEMA_MAP Verified) * **Customer Master**: `dbo.cust` (Join on `custcode` and `compcode`) * **Item Master**: `dbo.itemmas` or `dbo.saleitemmas` (Join on `itemcode` and `compcode`) * **Unit of Measure**: `dbo.UoMMaster` (Join on `uom` as `PUoM` and `compcode`) #### Transactional Context (Likely Joins) * **Invoice Details**: `dbo.invdtl` (Join on `itemcode`, `custcode`, and `compcode`) - Used to reconcile temporary data against finalized invoices. * **Sales Registration**: `dbo.TEMPSALEREGISTER` (Join on `custcode` and `compcode`) - Often used in tandem for temporary reporting sessions.