All tables
tables · table

bcdataHH

The bcdataHH table appears to be a "Barcode Data Handheld" (HH) transaction table, likely used for capturing or staging data from handheld scanners or mobile devices during the dispatch or receiving process. It stores detailed invoice-level and item-level information, including tax breakdowns (CGST, SGST, IGST), quantities, and vehicle tracking information. It acts as a bridge between physical handheld scanning and the core ERP modules like Sales or Procurement.

Row count
1
Last entry
Source
tables

Columns

19
ColumnTypeNullableMeaning
indexintegerNoPrimary Key; unique record identifier.
compcodestringNoCompany Code; links the record to a specific legal entity.
vcodestringYesLikely Vendor Code or Voucher Code.
ponostringYesPurchase Order Number related to the transaction.
invnostringYesInvoice Number.
invdatestringYesDate the invoice was generated (stored as string).
gststringYesGST Registration number of the party involved.
inv_amtnumberYesTotal Gross Invoice Amount including taxes.
basic_amtnumberYesTaxable value or Basic value before taxes.
vehnumberstringYesRegistration number of the vehicle used for transport.
sgst_amtnumberYesState GST amount.
igst_amtnumberYesIntegrated GST amount.
cgst_amtnumberYesCentral GST amount.
partnostringYesThe physical part or item number.
hsnstringYesHarmonized System of Nomenclature code for taxation.
itemqtynumberYesQuantity of the specific item/part.
itemamtnumberYesUnit Rate or price per item.
ItemWtstringYesWeight of the scanned item.
tcsamtnumberYesTax Collected at Source amount.

Full documentation

### 1) Overview
 The `bcdataHH` table appears to be a "Barcode Data Handheld" (HH) transaction table, likely used for capturing or staging data from handheld scanners or mobile devices during the dispatch or receiving process. It stores detailed invoice-level and item-level information, including tax breakdowns (CGST, SGST, IGST), quantities, and vehicle tracking information. It acts as a bridge between physical handheld scanning and the core ERP modules like Sales or Procurement.
 
 ### 2) Column Dictionary
 
 | Column | Type | Nullable | Meaning | Allowed Values | SQL Usage |
 | :--- | :--- | :--- | :--- | :--- | :--- |
 | **index** | integer | No | Primary Key; unique record identifier. | | `WHERE index = 101` |
 | **compcode** | string | No | Company Code; links the record to a specific legal entity. | e.g., "DAS" | `JOIN dbo.company ON ...` |
 | **vcode** | string | Yes | Likely Vendor Code or Voucher Code. | | `WHERE vcode = 'V001'` |
 | **pono** | string | Yes | Purchase Order Number related to the transaction. | | `JOIN dbo.pohdr ON ...` |
 | **invno** | string | Yes | Invoice Number. | | `JOIN dbo.invhdr ON ...` |
 | **invdate** | string | Yes | Date the invoice was generated (stored as string). | | `CAST(invdate AS DATE)` |
 | **gst** | string | Yes | GST Registration number of the party involved. | 15-digit Alpha-numeric | `JOIN dbo.cust ON ...` |
 | **inv_amt** | number | Yes | Total Gross Invoice Amount including taxes. | | `SUM(inv_amt)` |
 | **basic_amt** | number | Yes | Taxable value or Basic value before taxes. | | `SUM(basic_amt)` |
 | **vehnumber** | string | Yes | Registration number of the vehicle used for transport. | | `JOIN dbo.Vehiclemas ON ...` |
 | **sgst_amt** | number | Yes | State GST amount. | | |
 | **igst_amt** | number | Yes | Integrated GST amount. | | |
 | **cgst_amt** | number | Yes | Central GST amount. | | |
 | **partno** | string | Yes | The physical part or item number. | | `JOIN dbo.itemmas ON ...` |
 | **hsn** | string | Yes | Harmonized System of Nomenclature code for taxation. | | |
 | **itemqty** | number | Yes | Quantity of the specific item/part. | | |
 | **itemamt** | number | Yes | Unit Rate or price per item. | | `itemqty * itemamt` |
 | **ItemWt** | string | Yes | Weight of the scanned item. | | |
 | **tcsamt** | number | Yes | Tax Collected at Source amount. | | |
 
 ---
 
 ### 3) Relationships & Join Map
 
 The `bcdataHH` table acts as a transactional link between inventory items, vendors/customers, and logistics.
 
 #### Primary Joins (Authoritative):
 * **dbo.invhdr (invno, compcode):** Joins to retrieve header-level details like shipment status, transport IDs, and IRN numbers.
 * **dbo.invdtl (invno, partno, compcode):** Joins to compare handheld scanned data against recorded system invoice lines.
 * **dbo.pohdr (pono, compcode):** Joins to validate handheld entries against original Purchase Orders.
 * **dbo.itemmas (partno, compcode):** Joins to fetch item descriptions, units of measure, and categories based on the scanned `partno`.
 * **dbo.vendmas (gst, compcode):** Joins to identify the vendor associated with the GST number captured.
 * **dbo.cust (gst, compcode):** Joins to identify the customer if the handheld data is for an outbound shipment.
 * **dbo.Vehiclemas (vehnumber, compcode):** Joins to validate vehicle credentials and types.
 
 #### Likely Joins:
 * **dbo.bcdata (pono, invno):** This table is likely a legacy or non-handheld version of the same data structure.
 * **dbo.Performainvdtl (partno, pono):** Used if the scanning happens during the Proforma Invoice stage.